I’m re-writing my site in Astro. You can find my reasons for leaving 11ty here.
This page is notes on the ground-up rewrite of a blog in Astro, featuring heavily customized markdown, tag collections, a feed page, sitemap, and rss feeds.
This is not a tutorial. You won’t find elaborate step-by-step instructions, but high-level decisions and outcomes.
Astro provides several ways to start a blog:
When I say “in-depth” I mean, it really seems like they’re assuming you’ve never programmed before. Fortunately, you can skip to Unit 2 and bypass all the “This is a code editor” stuff that doesn’t belong in this type of tutorial.
This starts a cli wizard. You’ll select a starting template and typescript preferences.
You can chose between three project types:
I tried all of them and they cleanly do what they say on the tin.
But for this particular project (a port from a previous site), I’m looking for as little existing opinion as is reasonable.
a few best practices (recommended) because it has the common folder structure of
pages is seem “best practice” in Astro.
An aside on “best practice.”
The idea of having dedicated, root-level
/pages feels very
next@old-and-busted. SvelteKit is leading innovation in file-system based routing and I’d welcome it in Astro.
So, if I think SvelteKit is the most innovative framework, why not build my blog with SvelteKit?
That’s a good question.
- I like that Astro has few blog/content-forward conventions
- I like the “Islands” concept for content sites, like a blog
- I’m still most productive in React
- Astro would let me easily add demos to my site using any UI library
For those reasons, I’m willing to concede a less progressive and productive folder structure.