If you have to choose CMS (Content Management System) today which CMS do you use and why?
For further actions, you may consider blocking this person and/or reporting abuse
If you have to choose CMS (Content Management System) today which CMS do you use and why?
For further actions, you may consider blocking this person and/or reporting abuse
Kathryn Grayson Nanz -
Paul -
花间酒 -
Roseanne -
Top comments (5)
There is no global answer to this question. As rhymes said, everything depends on the context or the requirements and the character of the project. Global answers result in using WordPress for 50% of all websites, and I am pretty sure, that this is a wrong decision in 90% of the cases.
I think to make the right decision you should:
In the CMS-market you have a lot of segments, like:
So it should be pretty clear that it does not make any sense to choose any CMS without analyzing the requirements and context of the customer first. If your customer is a fortune500 company, then chances are high that they use some highly complex proprietary CMS like Adobe AEM, CoreMedia or maybe open source systems like drupal or similar. If your client is your friend with a private website, than even a flat-file-cms might be too much. If your customer is a midsize e-commerce company, well, than it looks different again. If your customer focuses on content marketing, well, another context again. Or if he simply want's a primitive online business card, why not use a website builder.
So, to find an answer I would suggest: Never use a CMS because someone said, that it is the best CMS ...
Hello Sebastian Schürmanns,
Thank you for detailed explanation. It is really helpful.
As most things it depends on the context or your needs :-D
But if I had to choose a CMS to integrate in a web app I would probably choose a headless CMS.
Most CMS are built as a very coupled system where you have to take everything or nothing at all.
Headless CMS have been popping up more and more the latest years because often what you're actually looking for is the CMS "model", not the presentation layer. This way you can integrate a CMS inside your application, not the other way around.
You build your application that does X and then someone in a meeting says: "why don't we integrate a CMS to do Y?" (which means they want Wordpress inside your Python/Ruby app) and then you start dying slowly inside because your app is custom built and to make it work with a CMS is an insane amount of work (especially because not every framework stack has a full fledged CMS to pair with).
A headless CMS allows you to grow at your pace.
I don't know which headless CMS honestly because between three years ago when I tried Contentful and now there are so many new (and probably better) ones.
Start here: cmswire.com/web-cms/13-headless-cm...
I've used Camaleon CMS with Rails for all my projects. For anyone needing a Wordpress-ish CMS in a Rails project, it's great. It also seems to pay a lot more attention to translation features than is common in most projects. I haven't used these features myself, but it seems to be gaining some use in the non-English speaking world for this reason. It's also got good plugin development features, though it doesn't have the range of existing plugins that the big PHP CMSes have.
Headless CMS's are awesome and I think should be use for most of the solutions we would develop. But how about that Wordpress? :)