Why I Chose Next.js for My Portfolio

A portfolio site needs to load quickly, present content clearly, and scale as the writing and project archive grows.

Next.js gives me a strong balance of structure and flexibility. The routing is straightforward, the content model is manageable, and the app can grow without feeling fragile.

For a creator site, that matters more than chasing novelty.

The framework should make the work easier to publish, not make me fight the site every time I add something new.

The bigger reason is that a portfolio should behave like a living archive. It is not just a landing page. It is a place where projects, case studies, and writing can sit together without the site turning into a mess.

Next.js makes it easier to keep the content structured while still giving me room to tune performance and presentation. That balance is useful when the site has to represent both the products and the thinking behind them.

A portfolio that feels easy to update usually stays alive longer. That is more important than choosing a framework that sounds clever in a tweet.