Hacker News new | past | comments | ask | show | jobs | submit login

> choose one for an upcoming CMS project.

Thing is, none are CMS's. If that's what you need, why would you start with a framework? Sure it's fun to build and I always think I can do better than the existing CMS's do, but it's never a good use of my time - or good for the client.

Please, if you need a CMS, use a CMS. If you need a Content Management Framework (CMF) one of the above could save time. If it's an application surrounded by managed content, your choices are different again. But please don't reinvent the wheel if you can avoid it.




I actually disagree. There's a big difference between reinventing the wheel - which happens because you didn't know that somebody else had thought of this before and already solved the problem - and building your own wheel because none of the off-the-shelf wheels work that great for your needs.

If this is a small business website and will never be built on ever again, then absolutely ignore the hate and go Wordpress. If it's something that might be extended over the years into use cases beyond just a webform to post an article with a title and a body then it's worth evaluating if you might be able to custom tailor a better fit for your business.


I agree with the above. That said, even if you are doing something new, you don't need to reinvent the wheel – it may be worthwhile taking a look at https://www.contentful.com/ (not affiliated, just an interesting service) and utilising their API to build an application which purely delivers the added value.


Prismic.io is another excellent "CMS as a service":

https://prismic.io

I've used it on a project and was quite pleased. Using their API, separating content publishing from the presentation becomes much more robust than with a traditional integrated CMS that you customize using themes or whatever.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: