Hacker News new | ask | show | jobs
by setquk 2982 days ago
When someone suggests an enterprise CMS, the usual best case outcome is to go back to the requirements analysis and remove enough requirements until an enterprise CMS is not required.

I've done my fair share of work on the things over the years and the outcome has never been the best one for the organisation.

1 comments

Ah yes, training up people to handcraft html every time a new press release needs to go up on the site, or a VP changes on thecabout us page. Not fun.
There are apps that generate static websites.
By that definition, everything that has a WYSIWYG editor is an "enterprise CMS"?
Hire someone to do it. Cheaper than an enterprise CMS is to run and/or commission.
Lets see, my Wordpress install running a well known theme, using Wordfence to alert for plugin updates, with me keeping an eye on it cost about £2,000 to set up and has ongoing costs of about £1,000 a year.

No. Its not cheaper to hire someone to hand-code the site and then hand-code every change.

If you're doing that, just use wordpress.com. Wordpress is way out of scope for the term "enterprise CMS".
So we've gone from "there's no need for a CMS, write HTML flat files" to "Use a hosted CMS" - OK.