Trifork Blog

Axon Framework, DDD, Microservices

A perspective on content management

May 19th, 2009 by
|

DiagramsPerspectiveCMS.pngFor 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.

A Perspective On Content Management

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.

3 Responses

  1. […] A perspective on content management […]

  2. May 20, 2009 at 14:46 by Ed Steenhoek

    Hi Jettro,

    Surprised to see a blog and paper about content management from your hand. At first I was afraid it was going to be an all tech approach (not in the last place because of this paper being part of the tech corner…). Fortunately it wasn’t about tech at all. Sadly it was about the 20% of content management that is easy. That 20% is about what it can do and does offer. Reality however is, that implementing content management is a change management project with emphasis on change, culture, buy-in, employee/user satisfaction (“What’s in it for me”). It’s also something you shouldn’t be implementing as such. It has to be for a reason that is bigger and more important than content management. A CMS has to be a piece of the puzzle that solves the business issue. Content isn’t created by an author for his own sake. It is a response to something. There was an event (not a process as some may think) that triggered the author. It will cause other events to occur. That chain of events includes inbound and outbound communication and passes content management along the way. A choice for a CMS should be done in that context and that is much broader than managing content.

    Having said all this… WELCOME TO CONTENT MANAGEMENT 😉

    Cheers,
    Ed

  3. May 21, 2009 at 04:07 by Toolman

    Nice work on the CMS overview. Good list of considerations; one important technical consideration one I think is worth mentioning.

    A distinction in solutions is influenced by whether the content is ‘baked’ or ‘fried’. Does the content get rendered once to a static file (usually HTML) each time a change in the repository occurs, (baked), or is the outpiut dynamically constructed on requests (fried)?

    Not my own terms, check out: http://www.aaronsw.com/weblog/000404 for discussion.

    With some systems, you can mix and match static and dynamic content. These terms are good for discussion how different elements are going to be delivered.