Why I Chose Astro for My Portfolio

When I planned this portfolio refresh, I wanted one thing first: speed.
Not just Lighthouse scores, but fast development feedback, clean page architecture, and fewer moving parts to maintain over time.

Astro fit that goal quickly. Its default model of shipping less JavaScript to the browser helped me keep pages light without requiring endless optimization passes later. I could render content-heavy pages statically and only add interactivity where it was needed, which made trade-offs very explicit.

Another reason was content workflow. I wanted project case studies and blog posts to live close to the codebase but still feel structured. Content Collections gave me strong schemas, predictable frontmatter, and a better editing experience when adding new entries. That made scaling content less error-prone.

I also liked how easy it was to combine plain markdown with component-level enhancements using MDX. It lets me keep writing simple while still dropping in richer examples if needed.

The biggest takeaway is that Astro helps me focus on what matters: clear content, thoughtful design, and reliable performance. For a portfolio that needs to stay easy to update over months and years, that balance is exactly what I wanted.