Are we going back to plain HTML, CSS, and JavaScript?

By: on Nov 19, 2026

AI didn't reinvent the web. It reminded us how simple the web could be.

Listen to this post

Back when building websites was simple

Back in 2012, I joined a web production company that was building websites for small businesses by the hundreds. Restaurants, hardware stores, beauty salons, grocery stores; you name it.

These weren't complicated applications. They were good-looking, functional websites built with HTML, CSS, and a little JavaScript. And the company was successful.

I came in as a WordPress developer, and we eventually developed a workflow that could turn an approved HTML design into a fully functional WordPress website in about two hours. Within six months, we'd doubled and tripled our production volume.

We were building so many WordPress sites that Matt Mullenweg himself sent me an email thanking me for my work. I printed it and hung it on my office wall. WordPress was taking over, and I thought we were riding the next big wave.

But looking back, something else stood out to me.

The magic wasn't necessarily in WordPress. It was in the HTML, CSS, and JavaScript underneath it.

The WordPress era: more features, more overhead

WordPress gave us some impressive capabilities. Contact Form 7, WooCommerce, user authentication, content management. Suddenly, we could give small businesses features that would have taken considerably longer to develop ourselves.

But those conveniences came with overhead.

PHP, databases, hosting requirements, plugin updates, security patches, and eventually the dreaded spinning wheel every time you wanted to do something in the admin interface.

I spent years optimizing WordPress websites, stripping away unnecessary scripts, stylesheets, plugins, and database overhead to squeeze out better performance. And I got pretty good at it.

But I kept coming back to the same question: Why am I spending so much time optimizing a system when the browser ultimately just needs HTML, CSS, and JavaScript?

A traditional WordPress page may require PHP execution and database queries before delivering its HTML. A prebuilt static page doesn't. That doesn't automatically make every static site faster, but it removes an entire layer of work from the request.

Eleventy brought me back to static HTML

Then along came static site generators, and I was hooked.

I started using Eleventy (11ty) before it reached version 1.0, and it felt like we'd rediscovered something. With Nunjucks, Liquid, reusable templates, and a Node.js build process, I could develop websites with the organizational benefits of a modern application while publishing plain static files.

Connect a Git repository to Netlify, run the build, and deploy the output to a CDN. No PHP runtime or production database required for a typical content-driven site.

And performance? The potential was tremendous.

Google's Core Web Vitals measure Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS), with recommended good thresholds of 2.5 seconds, 200 milliseconds, and 0.1 respectively.

Static architecture doesn't guarantee those scores, but it gives developers an excellent starting point. For years, I preached the advantages of static websites. I still do.

But something happened recently that made me question whether I even needed a static site generator anymore.

Then AI came along and went straight back to basics

I started building websites with AI.

Not AI-powered website builders or some proprietary platform. I'm talking about giving an assistant access to my project files and asking it to build what I have in mind.

I recently launched two projects, StoryGoPop.com, an interactive language-learning website, and AIGoPop.com, an AI-focused publication.

I let AI help determine the architecture, and when I looked under the hood, I almost had to laugh.

There it was: .html, .css, .js, and JSON files.

The same fundamental technologies we were using back in 2012.

Story Go Pop has interactive vocabulary, quizzes, learning activities, and content organized through JSON. I've even built Node.js utilities to generate videos and audio narration.

AI can create and maintain these pieces without requiring a full CMS or application framework for the published website. I can open a simple page locally, inspect the results, and drag my production folder into Netlify when I'm ready.

No mandatory npm run build, no deployment pipeline to configure, and no production PHP server to maintain.

More advanced features still need the appropriate tooling, and some browser features require a local server for testing. But for the basic publishing workflow, it's remarkably simple.

AI didn't reinvent the web

Here's what I find fascinating.

AI didn't invent a new way for browsers to work. It didn't replace HTML or create some magical new programming language. It learned to work with the same technologies developers have been using for decades, and it dramatically reduced the effort required to assemble them.

The browser still renders HTML, applies CSS, and executes JavaScript. Even applications built with React, Vue, or Angular ultimately deliver browser-compatible code.

And now an AI assistant can help manage the repetitive work that previously pushed us toward elaborate templating systems and build pipelines.

Need a new page? Generate it. Need consistent navigation across 30 pages? Refactor it into a reusable structure or automate the updates.

Need canonical URLs, a sitemap, structured data, or responsive layouts? Generate them, then validate them.

Of course, AI-generated code isn't automatically accessible, secure, maintainable, or SEO-friendly. You still have to know what you're looking at.

But the interesting question is no longer whether AI can write HTML.

It's whether we need as much infrastructure as we once did to organize and produce it.

The future of web development might be simpler than we think

And that brings me to what I think is the biggest change in web development.

I'm spending less time physically writing code and more time thinking about what I'm building. I'm directing the architecture, refining the user experience, testing the results, reviewing the code, and making decisions that used to get buried under hours of implementation.

I can experiment with an idea, see it working, change direction, and keep moving without losing an afternoon to configuration.

WordPress still has its place. Eleventy is still an excellent tool. Frameworks and build systems solve real problems, particularly as projects grow. But maybe we've reached a point where we should stop assuming every website needs one.

We've spent years adding layers of abstraction to make web development easier, only to discover that AI can help us manage the underlying technologies directly.

AI didn't reinvent the web. It reminded us how simple the web could be.

And maybe that's the real revolution: not a new framework, not another platform, but finally having the freedom to focus more on the website we're creating than the machinery required to build it.