A perspective on content management
For more than a year I am working with the Hippo CMS. I started with hippo 6. For the project OnsOranje, I created a springframework layer on top of hippo. This layer enabled us to create a website using the techniques we are familiar with (spring mvc). After the onsoranje project, my interest for content management was rising. At that moment I started using the new Hippo CMS 7. It is this version that we use at my current project as well. While using hippo for the projects, we also created our own website using magnolia. After a presentation about JackRabbit, Erik pointed me to yet another CMS called Brix. Based on these choices and some evaluations I did of other CMS systems, I wanted to make a choice for the CMS. I concluded that the best CMS does not exist, you can try to make the best choice for a CMS for your requirements. That is what this blog post is about.
The best CMS for your requirements
To find the best CMS for your requirements, you need to have a good idea about your requirements. There is a lot to tell about requirements. There will be more requirements than adding content and showing that content on the webpage. The image in this article gives you an idea about the type of requirements.
There are multiple different content management systems. I already mentioned Hippo, Magnolia and Brix. Of course there are many others. Some focus on web content management, others on document management. Based on your requirements (there they are again), you need to make a choice.
Are you curious? Do you have questions? Are you looking for information on finding the right CMS implementation? Start with the white paper we have written. This white paper can be a start in your CMS evaluation. It can also be an inspiration to start your own search for your optimal CMS.
If you have questions or remarks feel free to contact us. You can also send me a mail (jettro at our domain) or just place a comment on this blog post.