“You should never build a CMS”

(www.sanity.io)

140 points handfuloflight | 1 comments | 14 Dec 25 05:38 UTC | HN request time: 0s | source

Show context

camillomiller ◴[14 Dec 25 08:26 UTC] No.46261627[source]▶

This is a great testament to why 75% of the web runs on WordPress. Most of the problem mentioned have been solved by wordpress for ages, but there’s an entire industry set on reinventing the wheel in ways that really baffle me. If your actual goal is to publish on the web in a sane and understandable way, wordpress solves the problem for the largest number of cases. Scalability is solved. Usability by non tech editors is solved. Draft and approval flow is solved. Caching and speed is solved. You want headless? Oh, turns out wordpress is actually GREAT for that too.

It’s not sexy I guess? But if the goal is “work done” instead of “tech wank to impress investors with complexity”, that’s a solution that works very well.

replies(3): >>46261832 #>>46262027 #>>46262859 #

beezlewax ◴[14 Dec 25 10:08 UTC] No.46262027[source]▶

>>46261627 #

WordPress didn't solve anything. They just got the first.

replies(2): >>46262839 #>>46262851 #

1. Macha ◴[14 Dec 25 13:24 UTC] No.46262851[source]▶

>>46262027 #

Nah, the likes of Drupal and others were established before Wordpress was launched, even longer if you consider Wordpress 1 & 2 were “blog software for blogs” more than the behemoth modern versions have become.

I think being later actually worked in their favor as they caught the wave that Drupal and others were too early for. They were simpler when a lot of new developers and clients were around and grew in complexity as what people did on the web did, while Drupal and co just seemed bloated, even though arguably modern versions of Wordpress with the plugin setups that are common now are even more complicated than those old version of their competitors at the start

↑