NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
The CMS is dead. Long live the CMS (next.jazzsequence.com)
reconnecting 30 minutes ago [-]
There is indeed not always a need for WordPress. I have been using ProcessWire (1) for over a decade. Open-source, zero dependencies, no-nonsense CMS — and when it comes time to build a new website, I go back to it even in 2026, because you make it once and it works for 10 years and counting.

Cloudflare is just jealous that most of their customers are actually running WordPress, but this is not something they will be able to solve with AI hype.

1. https://github.com/processwire/processwire

christoph 3 minutes ago [-]
+1 for Processwire! I’ve mentioned it here a few times over the years and nobody seems to have ever heard of it! I’ve got a few sites well past 10 years now still happily chugging away on it! Basically zero issues with it, ever. It’s still my go to for all sorts of projects - installs in a few seconds, loads of really useful functionality out the box, easy API, beautifully flexible for all sorts of projects and a great community and ecosystem around it as well!
gman83 6 minutes ago [-]
I never really understood the argument, you can design the frontend with AI anyway and then use WordPress as the CMS for clients. Clients want to be able to log in, update CPTs, edit a calendar, post pictures, things like that. Surely the idea isn't to vibe-code an admin panel/cms from scratch for every project?
librasteve 20 minutes ago [-]
I’m not sure that I buy all the points made. I can imagine an AI centric CMS where the technical interface (implement this site on MySQL, host it there, use Next.js, etc) is distinct from the content interface (change store hours) or even the design (change the background).

I have used Wordpress a lot (too much) and came to the view that for most websites it is just overkill. So I built https://harcstack.org and vowed to write all my new sites in actual code.

HTMX to the rescue since you can write server side code in a sensible way and still have quite a dymanic UX.

btown 27 minutes ago [-]
The same way coding agents don’t replace the need for an IDE, content generation needs to support arbitrary human-to-agent handoffs, where the human can say “this is the wrong direction, I sketched this change of what I want it to look like, see how it’s different and apply that pattern.”

And, in the broadest sense, that human interface is a CMS; the agent is just another editor, albeit one that happens to read and write raw data rather than using a WYSIWIG (or similar) editor.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 12:52:59 GMT+0000 (Coordinated Universal Time) with Vercel.