Web Development

The Hindsight of Two Decades

Twenty years in web development. Hundreds of projects. Dozens of technologies learned, mastered, and eventually discarded. If I could step into a time machine and talk to my younger self on day one, my advice wouldn’t be about the latest “hot” framework or a specific library. It would be about compound interest in knowledge.

The industry is noisier than ever. Every week, there’s a new “game-changing” tool that promises to make you 10x more productive. But here’s the cold truth: the most successful developers I know aren’t the ones who know the most frameworks; they are the ones who understand the fundamentals so deeply that they can pick up any framework in a weekend.

Hugo is often marketed as the “world’s fastest framework for building websites,” but speed is only half the story. The real power of Hugo lies in its flexibility. While many developers use it as a simple blog engine, it is actually a robust, data-driven content platform that can handle complex documentation, enterprise portfolios, and even headless CMS architectures.

In this deep dive, we’ll move beyond the basics of “hugo new site” and explore how to extend the engine to suit sophisticated requirements. If you haven’t yet, check out my Introducing Olivero Hugo Theme for a practical example of how these concepts come together in a production-ready theme.

The Static Site Renaissance

In 2026, the “Static Site” label is almost a misnomer. What started as simple tools for generating HTML from Markdown has evolved into a sophisticated ecosystem known as the JAMstack (JavaScript, APIs, and Markup). Static Site Generators (SSGs) now power everything from massive documentation portals for companies like Google and Microsoft to high-performance e-commerce frontends.

The choice of an SSG is no longer just about which language you prefer; it’s about where your project sits on the Content vs. Application spectrum. Are you building a content-heavy blog, or a dynamic web app that happens to have some static pages? Let’s dive into the three heavyweights of the industry.

I have been building sites with Hugo for years. I wrote my own theme, tuned my build pipeline, and deployed more static sites than I can count. But I rarely see a resource that captures the why behind Hugo as well as the how. Brian P. Hogan’s Build Websites With Hugo does exactly that.

Published by Pragmatic Bookshelf in 2020, this 154-page book is not a reference manual. It is a guided tour through building a real portfolio site from scratch. You install Hugo, create a theme, add projects and a blog, wire up data sources, and deploy the final result — all while learning Hugo’s mental model.

The Book That Changed How I See Websites

I have recently read Just Enough Design by Taku Satoh, a slim but powerful book published by Chronicle Books. Satoh is one of Japan’s most respected living designers — he has shaped everything from packaging for major brands to museum exhibits — and in this book he distills decades of work into a single idea: hodo-hodo (ほどほど).

The word is ancient Japanese. It means “just enough,” “moderation,” or “the right amount.” When Satoh applies it to his work, it becomes a design philosophy: deliberately holding back, leaving room for the person on the other side to engage with an object according to their own sensibility.

The Framework-First Fallacy

In the landscape of 2026, the default response to almost any web development project is to start with a framework. Need a personal landing page? Reach for Next.js. Building a simple data dashboard? Boot up a React template. Creating a documentation site? Gatsby or Nuxt is the presumed choice.

We have reached a point where many developers — especially those who entered the industry in the last five years — literally cannot build a website without first installing a framework. This isn’t just a shift in preference; it’s a Framework-First Fallacy that prioritizes the developer’s comfort over the user’s experience and the project’s long-term health.