Why I Chose Astro for My Portfolio Website

Why I Chose Astro for My Portfolio Website

Published: 2026-02-07 Updated: 2026-02-07
astro web development typescript tailwind css

This article explains why I chose Astro for my personal portfolio website, highlighting the benefits of static site generation, better SEO, and a simpler development experience compared to other frameworks like Jekyll. It also discusses the reasons for switching from Jekyll to Astro, emphasizing the advantages of modern tooling and minimal JavaScript for a content-driven site.

The Goal of My Portfolio

My portfolio is meant to be a professional showcase, not a complex web application. It highlights my projects, technical skills, and learning journey while providing an easy way for people to discover my work and connect with me.

Because of that, I didn’t need features like real-time interactivity, client-side state management, or a heavy single-page application. What I needed was:

  • Excellent SEO
  • Fast page loads
  • Clean and readable code
  • Minimal JavaScript
  • A structure that’s easy to maintain over time

Astro fits these goals almost perfectly.


Why I Chose Astro

Better SEO by Default

Astro is designed around static site generation, which means pages are built ahead of time and served as plain HTML. Search engines love this. There’s no dependency on client-side rendering for content visibility, which gives my portfolio a strong SEO foundation without extra configuration.

For a portfolio website—where discoverability matters—this is a huge win.


Static Site Generation Without Complexity

Astro embraces the idea that most websites don’t need to be SPAs. My portfolio doesn’t need dynamic routing, client-side hydration, or runtime JavaScript logic for most pages.

With Astro:

  • Pages are static by default
  • JavaScript is shipped only when needed
  • Performance stays consistently high

This approach keeps the site fast and predictable.


Simple Architecture, Simple Maintenance

One of the biggest reasons I like Astro is its low mental overhead.

There’s no forced JSX or TSX everywhere. I can:

  • Write clean HTML
  • Use JavaScript or TypeScript only when necessary
  • Keep logic and structure easy to understand

For a long-lived project like a portfolio, this simplicity matters more than flashy abstractions.


Minimal JavaScript, Maximum Performance

Astro follows a “less JavaScript by default” philosophy. Since my portfolio is content-driven, this aligns perfectly with my needs.

Less JavaScript means:

  • Faster load times
  • Better Lighthouse scores
  • Fewer bugs
  • Easier debugging

This also reflects how I think as a backend developer—optimize for reliability and efficiency.


Why I Switched from Jekyll to Astro

Before Astro, I used Jekyll, which is still a powerful and widely-used static site generator. However, over time, I realized it wasn’t the right fit for me anymore.

Ruby and Cognitive Overhead

Jekyll is Ruby-based, and while Ruby itself is a great language, it added unnecessary friction for me. Switching mental context just to maintain a personal site wasn’t ideal.

On top of that:

  • Jekyll has its own templating engine
  • There are multiple conventions to remember
  • Configuration can feel scattered

This increased the cognitive load during development.


Templating Complexity

Jekyll’s templating system works well, but it requires memorizing its own syntax and patterns. Over time, this made simple changes feel heavier than they should be.

Astro, on the other hand, lets me work with plain HTML, JavaScript, and TypeScript—tools I already use daily. There’s no need to learn or remember a complex, opinionated templating language.


Modern Tooling and Tailwind Support

Astro integrates naturally with modern frontend tooling. Tailwind CSS works seamlessly out of the box, which was a major advantage for me.

With Jekyll, adding Tailwind requires extra setup and workarounds. With Astro, it feels native and clean—no hacks, no friction.


A Better Fit for My Workflow

Astro gives me:

  • A clean project structure
  • Modern developer experience
  • Strong performance without effort
  • No unnecessary abstractions

Most importantly, it lets me focus on content and structure, not framework-specific complexity.


Final Thoughts

Choosing Astro for my portfolio was a deliberate decision based on clarity and purpose. I didn’t want a framework that does everything—I wanted one that does exactly what a portfolio needs, and nothing more.

Astro gives me:

  • Better SEO
  • Static generation with simplicity
  • Minimal JavaScript
  • Easy maintenance
  • A modern, clean workflow

For a personal portfolio, that balance matters. And for me, Astro hits it just right.

Built simply, intentionally, and with long-term clarity in mind.

Browse other blog posts. This is the end of the article.