Choosing a Blog Engine
After Hugo and Next.js, I chose Astro because minimalism — content first, framework second.
Background
I’ve built sites with Hugo before. Its templating is powerful but verbose to customize. Next.js is overkill for a blog.
Why Astro
- Content collections built-in — typed frontmatter schemas, feels safe
- Zero JS by default — article pages have no business running client scripts
- Minimal starting point — no React/Vue needed, Astro syntax is enough
On i18n
The translationKey links translated versions of the same post. Language switcher appears automatically. No third-party i18n plugin needed.
Closing Thought
A framework serves content, not the other way around. Fewer config lines = fewer things to maintain.