←back to thread

“You should never build a CMS”

(www.sanity.io)
140 points handfuloflight | 4 comments | 14 Dec 25 05:38 UTC | HN request time: 0.633s | source
Show context
sublinear ◴[14 Dec 25 09:32 UTC] No.46261897[source]▶
> Give it six months. ... The "simple" system will accrete complexity because content management is complex.

Ah I was looking for the boogeyman threat and there it is.

I am so glad to see people finally getting away from all CMS platforms. They never worked well and have always caused a lot more problems than they solved. Everyone used them either out of ignorance or red tape.

replies(3): >>46261959 #>>46262934 #>>46264456 #
omnimus ◴[14 Dec 25 09:50 UTC] No.46261959[source]▶
No. Everyone used them because people editing the websites are almost never developers. Moving to some static site generator powered by git is cool until your marketing team constantly bothers your dev team to change a typo.
replies(4): >>46262197 #>>46262530 #>>46264326 #>>46264676 #
1. bonesss ◴[14 Dec 25 12:16 UTC] No.46262530[source]▶
Imagine if that dev team could create some kind of hyper intelligent interface to git so powerful even a marketer could use it…

Like a couple icons and some basic platform scripts for the 99% use cases of picking a branch, adding content, and occasionally saying “oops”?

Powered by Git doesn’t have to mean using Git raw.

replies(2): >>46264625 #>>46266908 #
2. sublinear ◴[14 Dec 25 17:07 UTC] No.46264625[source]▶
Or just hire people for your marketing team that have even a passing familiarity with web dev? They're not even that hard to find.

Keep those initial hires aboard and train up the rest. Get rid of the ones who don't want to learn. I mean really why do we try so hard to avoid bridging such simple knowledge gaps? It's not a big deal and we shouldn't shut people out of career development under all these obviously false excuses.

replies(1): >>46266962 #
3. omnimus ◴[14 Dec 25 21:08 UTC] No.46266908[source]▶
Whats with the git obsession?

Modern CMS workflows separate the content from the website code/app. The code is always version controlled and for content most CMSes have some sort of content versioning.

4. omnimus ◴[14 Dec 25 21:12 UTC] No.46266962[source]▶
You are forgetting that the websites/CMS is often tool for the organization. It's not just about publishing the content. CMSes are used for writing and editing. Event spaces use their website for planning, chefs use it to generate printed menus.

Static site generators are good for some usecases but too little or too niche for most cases.