Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The CMS is dead, long live the CMS

next.jazzsequence.com

Post reply on HN
Print view View original

51–60 of 106 posts

Re: The CMS is dead, long live the CMS

#51

Post by ceejayoz »

dawnerd wrote: post #48
ceejayoz wrote: post #36

Earlier quoted context omitted.

> There is always something that can be added with a Wordpress plugin and there is somebody who needs that. They're asserting you can do that stuff yourself now. > There is a reason why NASA, White House, Techcrunch, Reuters et al are all on Wordpress and any of the 'better' cmses out there. First, those are large orgs. Most WP sites are not that large or complicated. Second, would those orgs use WP if they started f…

Those orgs choose WordPress today. Source: that’s our bread and butter doing enterprise WP.

> Those orgs choose WordPress today.

The organizations cited chose WordPress years ago.

Choosing to stay on it is, at least sometimes, going to be a matter of large institutional inertia.

Large enterprises are the last to move on things like this.

Re: The CMS is dead, long live the CMS

#52

Post by coldtea »

zrn900 wrote: post #35
tappio wrote: post #20

I have built a product which uses AI to built Astro sites. LLM builds the sites in steps and make sure that they get 100/100 scores in pagespeed insights. These sites are served with a CDN. You can edit the sites with LLM interface, or use markdown editor to edit sites, or edit texts directly on a dashboard. These sites are static. There is no vendor lock in. If you want to migrate and manage yourself, just go to clo…

> But 95% of web does not need it. Literally talking without knowledge here. There is always something that can be added with a Wordpress plugin and there is somebody who needs that. > static site There is no magic to that. You can make any Wordpress site basically static with one single plugin without losing any feature Wordpress provides. There is a reason why NASA, White House, Techcrunch, Reuters et al are all on…

>Literally talking without knowledge here. There is always something that can be added with a Wordpress plugin and there is somebody who needs that.

So? There's always somebody who needs this or that outlier shit. If all that shit combined is still a small niche, we can just ignore it. And it is.

>There is a reason why NASA, White House, Techcrunch, Reuters et al are all on Wordpress and any of the 'better' cmses out there.

And there reason is not because it has some obscure plugins for features few care about, but about the maturity of the core offering. They're not having any exotic features or have some random niche plugin. And even if they did, they're larger than 99% of websites, so we can ignore their special needs when talking about what MOST need.

Re: The CMS is dead, long live the CMS

#53

Post by gbro3n »

tappio wrote: post #20

I have built a product which uses AI to built Astro sites. LLM builds the sites in steps and make sure that they get 100/100 scores in pagespeed insights. These sites are served with a CDN. You can edit the sites with LLM interface, or use markdown editor to edit sites, or edit texts directly on a dashboard. These sites are static. There is no vendor lock in. If you want to migrate and manage yourself, just go to clo…

I agree. Now we have the ability to have agents reason over our notes, it's more important for them to be in plain text. It was a big part of the reason I developed the AS Notes extension for managing documentation and blogs in VS Code / Markdown (https://www.asnotes.io)

Re: The CMS is dead, long live the CMS

#54

Post by jiggunjer »

donohoe wrote: post #37

It’s important to note the use-cases here. A lot of this discussion treats "CMS" as a single thing, but the requirements vary wildly depending on scale: one blogger versus a five-person marketing team versus hundreds of authors and contributors. Different arenas. If you’re spinning up a personal CMS, great. Have fun, you’ll learn a lot. But once you’re dealing with multiple users (tens or hundreds) it’s a different p…

For my personal cms I'm using sveltia. But their oath page assumes the repo remote is also the IdP, this means my login button has a GitHub logo instead of Google logo. Now I had spare credits so I forked it. Next weekend I'm fixing their weird support for asset management in R2 buckets.

Re: The CMS is dead, long live the CMS

#55

Post by snowwrestler »

ceejayoz wrote: post #51
dawnerd wrote: post #48

Earlier quoted context omitted.

Those orgs choose WordPress today. Source: that’s our bread and butter doing enterprise WP.

> Those orgs choose WordPress today. The organizations cited chose WordPress years ago. Choosing to stay on it is, at least sometimes, going to be a matter of large institutional inertia. Large enterprises are the last to move on things like this.

The White House website is rebuilt by each administration. So in that case, it was quite a recent decision.

Re: The CMS is dead, long live the CMS

#56

Post by brandensilva »

donohoe wrote: post #37

It’s important to note the use-cases here. A lot of this discussion treats "CMS" as a single thing, but the requirements vary wildly depending on scale: one blogger versus a five-person marketing team versus hundreds of authors and contributors. Different arenas. If you’re spinning up a personal CMS, great. Have fun, you’ll learn a lot. But once you’re dealing with multiple users (tens or hundreds) it’s a different p…

Yup, even without multiple users I took an open source speed reading app and quickly found myself a month deep in features just to expose it to multiple integrations for maximum accessibility. OAuth, MCP, CLI, API keys, secure and rate limited endpoints for content ingestion, parsing engine, a nice CI/CD pipeline that builds cross platform, a marketing site and it just kept going.

It was a test to see how much work was involved and what vibe coding felt like in one month. I plan on releasing it soon because I feel like it is the best speed reading app available but man it's a lot of work for even what seem like simple cases.

I'd be worried for anyone touching what I did if they did not have experience doing this.

Re: The CMS is dead, long live the CMS

#57

Post by snowwrestler »

Wordpress specifically ended up in no man’s land for us. Not powerful enough for big sites with complex content types and design systems, and too big of a pain for ephemeral microsites. For the latter we switched to Squarespace years ago, and are now exploring AI options.

Re: The CMS is dead, long live the CMS

#58

Post by snowwrestler »

gman83 wrote: post #5

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?

Depends on the client, PR agencies end up building a lot of little sites where they are also managing most of the content for the client. Wordpress was huge for this because the software cost was zero and basic WP engineers were not expensive to hire. Now they’re paying for AI licenses so they might as well use those instead.

Re: The CMS is dead, long live the CMS

#59

Post by ceejayoz »

snowwrestler wrote: post #55
ceejayoz wrote: post #51

Earlier quoted context omitted.

> Those orgs choose WordPress today. The organizations cited chose WordPress years ago. Choosing to stay on it is, at least sometimes, going to be a matter of large institutional inertia. Large enterprises are the last to move on things like this.

The White House website is rebuilt by each administration. So in that case, it was quite a recent decision.

> The White House website is rebuilt by each administration.

The Federal government is very large bureaucratic organization with more inertia than most. (And probably long-term contracts in this realm!)

Re: The CMS is dead, long live the CMS

#60

Post by simonw »

huijzer wrote: post #23
threetonesun wrote: post #18

Earlier quoted context omitted.

There's Tina CMS for editing files in Git, but honestly editing flat files is probably the least interesting or complicated part of an enterprise CMS, and IMO there's rarely a good reason to interact with files directly versus a database that publishes files.

I ran git-based blogs for years and have gone back to CMS. The instant preview and the instant publishing really make it a lot more pleasant to work with it. With Git, my read-eval-print loop so to say was a minute which is just too long. Fixing a typo then takes 2 minutes.

Now I'm imagining a static site editing tool that runs the exact same templates client-side to power an accurate preview that are then used by the static page build process.
Post reply on HN