I think Astro is great for building small mostly (or entirely) static sites. It doesn't assume that you're building a blog, but it's plenty flexible enough to support it.
This said, blogs feel like a nice sweet spot for Astro. The current version of my blog came together without much fuss. (I've studiously avoided using Astro DB, or using Astro to build an API backend, etc. and so can't comment on them.)
Overall I've found Astro to be highly reliable. I identified one unexpected behavior (I think a bug, related to when CSS is rendered) while building my blog and was able to work around it but, other than that, Astro behaved exactly as documented.
There were days I wished that astro components didn't exist and, instead, I could just use the client:* attributes in (say) my Preact components. That said, astro components are well thought out and the tooling in vscode is solid.
Mostly that I don't have enough experience working with Astro on things that are more sophisticated than "interesting CMS-backed blog or publication" to really comment. Secondarily that there are plenty of tools, some quite venerable at this point (Rails! Django!), that have the more complex terrain covered already.
Comments
25 years last month.
Hand-spun HTML on day one; cobbled-together scripts for the next many years; Jekyll once it hit 1.0; today, Astro.
It feels like a real "moment" where people are reconsidering blogging and personal domain names; I'm excited to see what comes of it.
Would like to hear about your experience with astro since I consider switching to it
I think Astro is great for building small mostly (or entirely) static sites. It doesn't assume that you're building a blog, but it's plenty flexible enough to support it.
This said, blogs feel like a nice sweet spot for Astro. The current version of my blog came together without much fuss. (I've studiously avoided using Astro DB, or using Astro to build an API backend, etc. and so can't comment on them.)
Overall I've found Astro to be highly reliable. I identified one unexpected behavior (I think a bug, related to when CSS is rendered) while building my blog and was able to work around it but, other than that, Astro behaved exactly as documented.
There were days I wished that astro components didn't exist and, instead, I could just use the client:* attributes in (say) my Preact components. That said, astro components are well thought out and the tooling in vscode is solid.
Thank you for your thoughts. Why is it suitable for only small sites?
Mostly that I don't have enough experience working with Astro on things that are more sophisticated than "interesting CMS-backed blog or publication" to really comment. Secondarily that there are plenty of tools, some quite venerable at this point (Rails! Django!), that have the more complex terrain covered already.