You remember the exact moment you discovered CSS Zen Garden. It was the 2000s. A single, untouched HTML file transformed into a hundred wildly different, breathtaking designs through pure CSS magic. It was the web’s golden age, a promise of infinite creative flexibility.
Fast forward to today. A developer builds the design system for the new Firefox.com and proudly announces we’ve finally ‘shipped’ the Zen Garden dream. The separation of content and presentation, codified. We did it, right?
<
Wrong.
We spent two decades turning the web from a handcrafted masterpiece into a corporate bureaucracy, and we’re calling it progress.
Look at your screen. The Zen Garden promised infinite architectural flexibility. What did we get? Ten thousand websites that look exactly the same. The spirit of CSS Zen Garden was extracted into rigid, homogenous design systems where every button, form, and footer is identical. We traded creativity for scalability, masking our exhaustion with the polite euphemism of ‘design systems’.
But the visual sameness isn’t even the real threat. The real danger is the code-generating elephant in the room.
Semantic HTML is the skeleton of the web, but AI is busy vomiting div soup like a freshman programmer who just discovered frameworks.
The reason CSS Zen Garden worked was that the underlying HTML was pristine. Every <article>, <nav>, and <h1> meant something. It was an architectural marvel. Today, developers are prompting LLMs to build UI components, and what comes back is an endless nightmare of nested <div> and <span> tags.
You cannot layer a beautiful, scalable design system on top of structural garbage. Yet, that is exactly what we are doing. We are celebrating that we finally decoupled presentation from content, while AI generators are quietly sewing them back together, spitting out inline styles and meaningless tag soup.
You can feel the exhaustion in the industry. It’s in every Hacker News thread, every tired comment about AI writing, every complaint about framework bloat. We are pretending that a machine-generated div-nested hellhole is somehow equivalent to the architectural ideal Dave Shea handed us in 2003.
A design system is only as strong as the HTML beneath it, and AI is actively dismantling the semantic foundation we spent 20 years building.
If you’re a developer or a designer, stop celebrating the ‘shipped’ dream and start defending it. Stop accepting AI-generated garbage as your foundation. Demand semantic structure. Write meaningful HTML. Otherwise, we’re just building a beautiful, standardized facade over a rotting infrastructure.
The web deserves better than an infinitely nested div.
FAQ
Q: Doesn't AI just automate the tedious parts of coding? Why does semantic HTML matter if the UI looks right?
A: Because semantic HTML is the universal language of the web. It's what makes accessibility, SEO, and maintainability possible. When AI spits out endless divs, it breaks the contract between the web and the machines that rely on that structure. You aren't automating busywork; you're automating the web's structural integrity.
Q: If I'm using a modern design system, how do I actually prevent this AI rot?
A: Stop blindly copy-pasting AI-generated UI. Enforce strict linting rules that demand semantic tags over generic divs. Treat your design system as a contract of structural integrity, not just a visual component library.
Q: Isn't the Zen Garden dream already dead since all websites look the same anyway?
A: Yes. We won the architectural battle but lost the creative war. The promise of infinite visual flexibility was traded for scalable corporate sameness. We sacrificed the soul of the web to make it easier to ship a SaaS landing page.