Keeping the Site Static

A personal site is usually better when it stays boring in the right ways.

For this project, static output gives me three useful properties:

• no server process to keep alive
• no runtime database to migrate
• no framework choice that leaks into the content workflow

The implementation is still flexible enough for future pages, but the default posture stays simple. That matters more to me than having a more powerful stack on paper.

Where the complexity lives

Instead of putting complexity into infrastructure, I put it into the build step:

• Astro handles file-based routing
• Markdown collections handle validation
• layouts keep the structure consistent

That keeps the publishing workflow predictable. The pages are generated once, then served like any other static site.

What this leaves open

This approach still leaves room for additions like an RSS feed, a contact form, or better search later. None of those require the site to stop being static.