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.
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.
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.