Why I Chose Astro for This Site

I built this site to share projects, write about technical topics, and keep a simple personal portfolio. Early on, I decided on Astro because it feels like plain HTML with a slice of interactivity—right where I need it.

Astro converts every page into static HTML by default. That means fast loading times and predictable behavior, even before any JavaScript runs. For a personal site where most content is text and images, I don’t need a lot of client-side code.

When I do need interactive bits—like theme switches or small animations—Astro lets me add scripts only on the components that need them. That keeps the overall bundle small and keeps most of the site lean.

I also appreciate how Astro handles Markdown. Writing blog posts in Markdown and having them turn into pages without extra setup is a huge time saver. I can organize content in simple files and let Astro’s routing handle the rest.

On the styling side, pairing Astro with Tailwind CSS and a bit of backdrop blur feels natural. The templates stay clean, and I don’t fight with complex configuration files.

In short, Astro gave me:

• Static, prebuilt pages for fast load times
• Optional, per-component JavaScript for interactivity
• Built-in support for Markdown and file-based routing
• A straightforward setup with familiar tools like Tailwind

Choosing Astro meant a simple project that focuses on content and performance. For a portfolio and blog site, it’s a solid fit with minimal overhead and plenty of flexibility.