WordPress is dying?

I have a question I hear more and more often: is WordPress dying?

For a long time, WordPress was my default answer when a client asked for a simple “business card” website: a few pages about the company, services, contacts, a news feed if they insisted. It was the familiar route — click a few buttons in a hosting panel, run the installer, pick a theme, add a couple of plugins, and start typing. You could hand the keys to a non‑technical person and they could add or edit pages without much training. That simplicity is the reason so many people chose it in the first place.

But the web changed. And so did the trade‑offs.

Today, with powerful AI assistants and platforms like Replit and AI website/app builders such as Lovable, Bolt.new, v0, and Framer AI, people are quietly leaving WordPress for static sites. Not because WordPress stopped working, but because the old bargain — convenience in exchange for a living, moving, server‑side system — no longer feels worth it for a lot of small company websites. Here is why I say that, and why I moved our own site away from WordPress.

The constant update treadmill

If you have ever managed even one production WordPress site, you know the feeling: updates for the core, updates for the theme, updates for a dozen plugins you barely remember installing. Each update is a small risk. Will something break? Will two plugins fight? Will the theme override some setting I relied on?

When you multiply that by a portfolio of client sites, the treadmill becomes real work. You either spend time clicking update buttons and testing, or you accept that some pieces will become outdated and hope nothing bad happens. And when you are busy delivering features and supporting paying customers, “log in to run updates just in case” easily slips down the list.

A wide attack surface

Updates exist because vulnerabilities exist — not only in WordPress core, but in themes and plugins, too. Each moving part on a dynamic stack increases the attack surface. Popular targets attract automated scans. A single weak link is enough to get inside. You might harden logins, you might limit plugins to well‑known names, you might use a security plugin and a firewall. It still takes only one missed update, one plugin with a flaw, one mistake.

I am not pointing fingers at anyone. WordPress and the plugin authors work hard. But the model is what it is: dynamic PHP code, a database, and many optional extensions that run on a live server all the time. It is convenient — and it is open to the world.

The hack that taught me a lesson

I keep my projects organized. For convenience, I had several small sites under one hosting account. They were not high‑risk targets. One site, the least important one, sat for a while without updates. That was enough. It was compromised, and because everything shared the same account, malicious code spread across the whole tree.

The most embarrassing part? Our own company site got spam injected into it — dark‑web‑market style junk posts with links I would never want to see again. Cleaning that up was no fun. It took time to identify modified files, compare backups, and remove the mess. The experience left me with a simple conclusion: for basic company websites, the dynamic platform was more trouble than it was worth.

The way out: go static

A modern static site has none of the moving server‑side parts. No PHP runtime, no database, no plugin ecosystem that executes on every request. The site is pre‑rendered to plain HTML, CSS, and a bit of JavaScript where it matters. You host those files on an edge CDN, and you are done. There is almost nothing to patch because there is almost nothing running. The attack surface collapses.

I chose Astro for our rebuild. Astro is a site generator that focuses on shipping as little client‑side JavaScript as possible. It’s fast by design and a pleasure to work in. I also used an AI assistant — in my case, Cursor — as a pair‑programmer. I took the old WordPress site, described how I wanted it modernized, and iterated. The assistant generated components, migrated copy, suggested structure, and rewrote the theme into clean, readable code. I reviewed every change and kept full control. The result felt like magic without giving up ownership of the codebase.

From Git to Cloudflare automatically

The final step was deployment. I put the new Astro project into a GitHub repository and connected it to Cloudflare. Each push builds the site and publishes it to Cloudflare’s global edge. There is a preview URL for every branch, so I can test changes with the team before merging. The production site is just a protected branch away. Hosting static files on the edge is exactly what Cloudflare is good at — fast, resilient, and pleasantly boring.

No cron jobs, no scheduled updates, no fear that a plugin left unmaintained will quietly open a door. When I want to change something, I change the code, commit, and push. Cloudflare does the rest. If I want to add a page, I add a file. If I want to translate the site, I add a localized route. If I want to publish an article like this one, I write Markdown and the generator takes care of templates, metadata, and the sitemap.

“But I need to edit pages easily”

That was the main reason people picked WordPress. They wanted to add and edit pages without calling a developer. Today, that is possible without a heavy CMS. There are Git‑based CMS interfaces that sit on top of a repository and let non‑technical users edit content in forms. There are headless options if you truly need them. And AI assistants can draft copy from your notes and place it where it belongs. For a small marketing site, a static setup is enough and keeps you in control.

Our personal checklist after the migration

• A clean codebase we understand end‑to‑end.
• A fast site that ships almost no JavaScript by default.
• Automatic deploys from GitHub to Cloudflare.
• No database, no PHP, no plugins to patch.
• Content in Markdown so articles are easy to draft and review.
• A tiny “attack surface” — there is almost nothing to attack.

That list is exactly what I wanted as a developer and as a business owner.

The bigger trend

This is not about hating WordPress. It built a huge part of the web and still powers complex, content‑heavy sites very well. But the default choice for simple company pages is changing. With AI to help you build, with generators like Astro that compile to static HTML, and with edge hosting from providers like Cloudflare, you can get a cleaner result with fewer headaches.

If your site is a few pages and a contact form, the whole WordPress platform is often overkill. You do not need a live server‑side system just to render an “About” page. You do not need a plugin ecosystem if all you want is a fast, secure brochure site. A static site generator plus an AI co‑pilot is an “AI website builder” in the most practical sense — not a toy, but a productive workflow that keeps you in charge.

What we did, step by step

1. Audited the old site and exported the copy and images we still liked.
2. Asked Cursor to help scaffold an Astro project and rewrite the theme structure.
3. Committed the result into a clean GitHub repository.
4. Connected the repo to Cloudflare and set up automatic preview builds per branch.
5. Moved forms and small bits of interactivity to simple, robust alternatives.
6. Wrote this blog post in Markdown, with localized routes for English, Russian, and Estonian.

That was it. The site now lives on Cloudflare’s edge as a static site. It is fast, inexpensive to operate, and it no longer needs frequent updates to stay safe.

Where to next?

If you are maintaining a small business site on WordPress today and it keeps demanding attention — updates, patches, and occasional scares — consider going static. Try Astro. Pair with an AI assistant if you like. Put your repo on GitHub and let Cloudflare publish it globally on each push. You will still be able to add and edit pages easily, and you will likely sleep better.

If you want help or just want to talk through options, write to us. We build Astro sites, migrate existing sites, and integrate forms, analytics, and small bits of custom logic where needed. And if you want to see what kinds of projects we ship besides websites, take a look at our services page — and let’s build something durable together.