KIT MOBLEY BBS · islamorada, florida keys · node 1
- From:
- Kit Mobley (Sysop)
- To:
- All
- Subj:
Sam Parr Asked If WordPress Is Dead. The Thread Argued About the Wrong Thing.
- Date:
- 2026-10-22 · 6 min read

Sam Parr, the Hampton founder, put a question on LinkedIn this week. Lifelong WordPress user. Still on it. But Claude is doing all the work now, and he figures the theme and plugin businesses are about to get demolished. “Are y’all still using WP or just making your own site?”
Over two hundred people answered. I read every one, because this is my whole job.
The thread split three ways
The biggest camp says RIP WordPress. Astro, Next.js, Cloudflare, Vercel, static files, Claude doing everything. “All static files with Claude is the way to go.” “GitHub + Astro + Cloudflare and you’re good.” One guy said he’s hosting several 400 to 600 page sites for five bucks a month. Several people pointed out, a little gleefully, that “WordPress” and “security” don’t usually show up in the same sentence as a compliment.
The second camp is WordPress, but leaner. These folks kept the platform and dropped the junk. Custom lightweight theme, six plugins instead of twenty-five, and Claude writes the little features they used to buy. Somebody said his plugin list is going through the five stages of grief and is currently on bargaining. That one made me laugh.
Then there’s a small third group asking who’s going to maintain all this, and they’re the ones I agree with. A CTO in the thread put it better than anyone: themes and plugins sold two things, the code and somebody else carrying the updates. Claude makes the code nearly free. The updates are now your problem. Another person asked the question I wish the whole thread had started with: who edits this site six months from now?
The platform was never the point
I build Astro sites, static, on Netlify. But I inherit a lot of clients who show up on WordPress, Wix, and Squarespace, so I see what every one of these platforms looks like a few years after launch. I don’t have a team jersey on.
What I’ve learned down here is that the platform question gets settled by three boring questions:
- Who changes the site after launch? The owner, a marketing hire, three outside vendors, or me?
- What does it have to do? Show trips and take a phone call, or run a store with shipping rules and inventory sync?
- Who carries the updates? Somebody has to. If the answer is “nobody,” that’s the answer that gets sites hacked.
Once you’ve answered those, the platform choice is usually obvious.
What that looks like for a charter captain
Most of my clients run boats. A charter site has a handful of trips, a price list, photos, a phone number, and maybe a booking widget. Two recent rebuilds show how this plays out. Neither one came off WordPress, and that’s sort of my point: the pain looks the same on every page builder.
Island Daze Charters in Key West came off Squarespace. On a phone, Lighthouse scored it 26 out of 100, with a 27-second largest contentful paint and a 10.3 MB homepage. The stock robots.txt was blocking the AI crawlers, so ChatGPT and Claude couldn’t read it even if they wanted to. The Astro rebuild loads in about three seconds, ships 2.1 MB, scored 94, and went from five indexable pages to eighteen. The crew edits trips, prices, and photos through Decap CMS without calling me.
Satisfaction Charters in Islamorada came off Wix, where pages lived at addresses like /blank-9. The new site scores 91 for mobile performance and 100 for accessibility, best practices, and SEO, and the whole homepage is 881 KB. Every trip price lives in one file, so the home page, tours page, and rates page can’t disagree. Captain Brian doesn’t want an admin login. He wants people to call him. So every button calls or texts him, and when a price changes, he texts me.
Neither of those captains will ever patch a plugin, because there isn’t one. No PHP, no database behind the pages, nothing to update on a Tuesday night. When people say static is more secure, that’s what they mean.
Where WordPress still wins
I’ll defend it where it earns it. Big publishers haven’t left: WordPress VIP, Automattic’s enterprise tier, says it hosts more than 700 enterprises, including CNN, Salesforce, News Corp, NBCUniversal, Meta, and Bloomberg. If you’ve got a team of writers publishing every day, multiple vendors who all need to make landing pages, or a WooCommerce store running payments, shipping, and inventory, the maintained plugins are worth paying for. A commenter who builds WooCommerce systems said it well: generating the first version is easy, and keeping the payment rules working as the store changes is the hard part. Same goes for the person who said they won’t hand-roll security, backups, or payments. Neither would I.
What’s dying is the middle: the premium theme you fight with for six months, the plugin that does one small visual thing for a yearly fee, the page builder that ships megabytes of scripts to show a phone number. Somebody in the thread said WordPress always felt like doing it 70% good because they didn’t know how to do it 95% good. The 95% version used to need a developer. Now it mostly needs someone who knows what to ask for.
The catch
A handful of replies got to it. One SEO said he sees a lot of Claude-built sites that are invisible to Google and ChatGPT: bad rendering, bloated code, missing the basics. Another said everyone’s AI site is starting to look the same.
They’re both right. “Claude built it” isn’t a plan. Somebody still has to know what the schema should say, why the robots.txt matters, what a captain’s customers type into Google, and when the AI did something dumb. The building got fast. Knowing what to build didn’t.
So, to answer Sam: I’m not using WordPress for new builds, and I’m not telling anyone to rip out a WordPress site that’s working. Figure out who’s touching the site next year. Then pick the thing that makes their life easy.
If you’re not sure where your site stands, run it through my free audit or send me a note. I’ll tell you straight whether it’s worth rebuilding.
FREQUENTLY ASKED
Is WordPress dead now that AI can build websites?
No. The paid theme market and the small do-one-thing plugins are getting squeezed, because Claude can write a layout or a 40-line feature in minutes. WordPress core still makes sense when lots of people need to edit lots of content, or when a store depends on maintained plugins for payments and shipping. For a small business brochure or booking site, a static build is usually faster, cheaper to host, and has less to patch.
Can a business owner edit a static Astro site without a developer?
Yes, if it's set up for it. I add a Git-based CMS like Decap so the owner can change trips, prices, and photos from a simple admin screen. For owners who would rather not log in at all, the change is a text to me and it's live the same day.
Should I move my WordPress site off WordPress?
Only if it's costing you something. If it's slow, if you're paying for plugins you barely use, or if updates keep breaking it, a rebuild usually pays for itself. If it's fast, secure, and your team is happy in the editor, there's no prize for switching.
© 2026 · built on the Spark lab — OG imagery rendered on-prem via ComfyUI + Flux LoRA. Type: IBM VGA 9x16 from The Ultimate Oldschool PC Font Pack by VileR, CC BY-SA 4.0.