New blog post: “Conditional JSX in Astro”.
https://blog.kizu.dev/conditional-jsx-in-astro/
This is me documenting the way I am handling some of the more complex conditional rendering in Astro’s JSX. Well, not strictly _JSX_ — but its “Component Template” part of `.astro` components and assigning them to variables.
Anyone using #WithAstro willing to help a noob?
I am setting up a website with two pages A.mdx and B.mdx. I want to put a link to page B on page A. But of course I don't want to hardcode the whole site's URL, I want to put a relative link.
I tried to use Astro.url from page A, but the Astro context object is only available in .astro files. I was thinking I could inject the URL base path into the page from outside of it, but it doesn't actually seem possible to inject data into mdx files?
How would you go about putting relative links in your pages?
I migrated my website from Jekyll to Astro over a year and a half ago. Here's how it went.
https://tommyoldfield.co.uk/blog/migrating-from-jekyll-to-astro/
Our second @astro integration is available in Astro integrations library.
It's a simple utility that handles trailing slashes in URLs when using trailingSlash config option.
Check it out at https://github.com/ReunMedia/astro-normalize-trailing-slash
Any Astro devs curious about Nuxt 4?
We've been itching to try out the alpha, so we recreated our blackspike Astro theme to Nuxt and blogged about the process.
https://www.blackspike.com/blog/converting-an-astro-website-to-nuxt-4/
Hey, #withastro users,
Are there any best practices, guides or similar on build setups for combining multiple astro projects in one?
I have a website with a main page (radiki.dev)
a blog (radiki.dev/blog)
and multiple subprojects ( radiki.dev/project1, radiki.dev/project2 etc)
All these share some components and CSS, but they also have their own.
I guess I can make do with Makefiles or shell scripts, I was just wondering if there is a more idiomatic solution.
https://prass.tech/blog/upgrading-astro-to-5/
Upgrading to Astro 5 has not been effortlessly but it was a good upgrade experience nonetheless. For a blog as small as mine the changes were minimal.
I upgraded my personal website to Astro v5! 🥳
The upgrade didn't break anything on my site. I converted my content collections to the new Content Layer API anyway and updated the Typescript configuration.
Switching my content collections to the Content Layer API briefly changed the dynamic routes for my notes and articles. However, the issue magically fixed itself, probably by me restarting the dev server. Everything else went smoothly!
Apres Vite 6 https://vite.dev/blog/announcing-vite6 Voici Astro 5! https://astro.build/blog/astro-5/
added a lightbox component to my blog using glightbox and tested it out with some photos from a trip to the Sali Pazari market in #istanbul yesterday. seems to work well! #withastro @astro
Blogged: Launching the GitHub Discussions Blog Loader for Astro.
If you read my last post on creating a GitHub Discussions powered blog and felt like giving it a go, then I’ve just made it a heck of a lot easier for you 😁
https://mattbrailsford.dev/launching-the-github-discussions-blog-loader-for-astro
Blogged: A client needed to show different currencies and prices depending on the region they were visiting from. Here's how we used Cloudflare and Astro server islands to do that #withastro #Cloudflare #astrojs @astro @cloudflare
https://www.blackspike.com/blog/astro-server-islands-cloudflare-geolocation/
🚀 Just published a new blog post: My Experience with Astro! 🌌
We recently transitioned from Next.js to Astro at our agency, focusing on SEO and performance. I discuss the shift, rediscovering vanilla JavaScript, and how Astro's server-side rendering has improved our projects.
If, like me, you've been using the Zed editor #withastro — you'll be happy to know the language server is now working properly in @astro templates. 🎉 So you'll now get all those nice code actions and completions, leveraging your nicely typed content collections. Yasss.
//thanks: @erika for the fix 👏🏼
ICYMI: @astro is holding our very first in-person launch event in #montreal and you're invited!
**Let's build the web we want, together **#withastro.
Free food, drinks, and Astro merch (lovingly designed by yours truly). While the event will not be streamed, we'll be making the announcements with a published video after the fact.
Can't wait to meet you in Montreal! 🎉
Now that I actually have a place to blog again, posting some updates on recent adventures #withastro https://distresssignal.org/astro-dev-toolbar-breakpoints/
If you're mixing both MDX and MD when building #withastro this is a nice way to normalize your template props:
I wrote about configuring @astro to use #LightningCSS, the #Rust #CSS parser in #MozillaFirefox, to handle all the CSS things. It's actually pretty simple. And fast 😉
Zed pre-release v0.123.1 is out 🎉 and it adds support for @astro If you like your text editors 'blazingly-fast' 🦅, and you build #withastro have a look: https://github.com/zed-industries/zed/releases
Adding my standard tailwind-breakpoints component (a dumb little widget to display the current viewport-size-as-Tailwind-class) as a proper @astro dev-toolbar app.
I think the dev toolbar is a pretty rad idea. If you haven't checked it out yet, and you build #withastro have a look: https://docs.astro.build/en/reference/dev-toolbar-app-reference/
