I made the Rust compiler and the Rust Markdown pipeline (https://satteri.bruits.org) in this, let me know if you have any questions, glad to answer anything!
The TL;DR is that `marked` is very light, but a bit on the slower side compared to Sätteri and `markdown-it` (and its forks). I'm not sure how friendly the extensibility is, but Sätteri re-use the same AST format as the unified ecosystem, which might feel more friendly.
I probably only use 1 % of Astro's features, but I like how it's enabled me to build static sides as back in the days, but with a build pipeline.
So I can use components, reuse stuff, include stuff etc, basically what I would do with PHP back in the days, but now it spits out a compiled page I can host for cheap (often even free). And easy to add in some interactivity when needed. Like I render a list as a component, and very easy to ship some dynamic filtering on the frontend using the same code, but the content is still statically in the html, so served fast and good SEO.
The switch to strict HTML compilation is just not cool, and actively prevents upgrading sites which need to deal with remote content that is not written in strict HTML.
I also wish there could be a general purpose content processing API so I can plug a different format than markdown (such as typst)
Unfortunately, I've also come across .astro files that I'm not allowed to touch and yet have to work with them (some internal corporate dinosaur which has not been updated for a while).
For my personal site, it was a 5 minute work, as usual :)
I upgraded my website recently and it's exciting! That being said, I admit my builds didn't get faster (they actually on average slowed down a bit). Hopefully that improves, but worth noting.
I have been trying to convince my marketing department to replace there archaic wordpress with an Astro build with AstroCMS and markdown for there needs.
I have build several sites using Astro 6, and i am finding the ease of building the sites amazing and exceptional in SEO as well.
It was partially that, but mostly the Vite version with the Rolldown bundling etc. We typically always need to do a major whenever Vite releases one because it tends to impact us a lot compared to other frameworks for various reasons.
The TL;DR is that `marked` is very light, but a bit on the slower side compared to Sätteri and `markdown-it` (and its forks). I'm not sure how friendly the extensibility is, but Sätteri re-use the same AST format as the unified ecosystem, which might feel more friendly.
Both good options, though!
So I can use components, reuse stuff, include stuff etc, basically what I would do with PHP back in the days, but now it spits out a compiled page I can host for cheap (often even free). And easy to add in some interactivity when needed. Like I render a list as a component, and very easy to ship some dynamic filtering on the frontend using the same code, but the content is still statically in the html, so served fast and good SEO.
Astro has gone from 247 deps in v6 to 190 in v7.
https://node-modules.dev/#install=astro@7.0.6
https://node-modules.dev/#install=astro@6.0.0
I still have some plans in this area that should reduce the overall count further, though.
I also wish there could be a general purpose content processing API so I can plug a different format than markdown (such as typst)
See this example: https://stackblitz.com/edit/github-ug3paw61?file=src%2Fpages...
For my personal site, it was a 5 minute work, as usual :)
I'm personally awaiting the rewrite to assembly.
I have build several sites using Astro 6, and i am finding the ease of building the sites amazing and exceptional in SEO as well.
I just recently updated my website to Astro 6 and now... there's Astro 7. Maybe by the time I update, Astro 8 will be a few weeks in the future.
My understanding is that astro isn't considered particularly slow?