Hugo’s native TailwindCSS v4 integration through css.TailwindCSS eliminates the need for external build tools. Here’s how to set it up properly.
Why this stack? # Hugo handles Markdown content and templating. TailwindCSS handles styling. Together, they produce a fast static site with minimal tooling overhead.
The key insight: Hugo v0.128+ includes native TailwindCSS v4 support via css.TailwindCSS. No PostCSS config, no separate build step, no Webpack.
There’s a growing movement of founders and builders who share their journey openly - revenue numbers, user metrics, failures, and pivots. I’ve been doing this for years, and here’s why I think it matters.
The fear of transparency # Most business owners guard their numbers jealously. Revenue is a secret. Failures are hidden. The public persona is always “crushing it.”
In 2017, I shut down an e-commerce venture after 18 months. It was painful, expensive, and one of the best things that happened to my career. Here’s what I learned.
1. Validate before you build # We spent three months building before talking to a single potential customer. By the time we launched, we’d built features nobody asked for and missed features everyone needed.