What is Component Content Management? ~ Appatura

What is Component Content Management?

Traditional Content Management systems evolved to allow enterprises to manage content at the document level. Over time, the definition of content started to morph as the World Wide Web became more of an accepted method of communication for companies. At this point systems designed to allow companies to manage their Websites began to emerge. These sites also embraced the term: “Content Management”.

We now had Content Management systems to manage documents, and to manage website content.

But how do we manage content that needs to appear in documents, on websites, as well as other products – i.e. printed media, apps, etc? What if some of this content needed to be slightly different although be drawn from the same source?

As messaging and content grew to become more in demand, the curators of content – those responsible for gathering the content and disseminating it – found themselves having to deal with different systems to get much the same message for different dissemination purposes.

What if we were able to manage content in more granular form – the chapter, the paragraph or even the word or number and then assemble the relevant pieces together to form output specific to its required use? Rather than force the consumer to adhere to the construct of the content, we could then tailor the content for its consumer without jeopardizing its integrity.

Thus the concept of Component Content Management came to be. Actually the concept and in fact implementation of this concept had already existed for some time – DocuBuilder (shameless plug) was designed with this in mind. However, the term was not nearly so prevalent, as users, vendors and enterprises were just really learning how to manage the larger pieces of content – documents such as prospectuses, contracts and agreements – rather than Portfolio Manager biographical information, Fund Objectives, State-specific HR policies, etc…

By looking at content in smaller more-granular pieces, one starts to be able to manage the specific content and effectively update all of the downstream consumers of that content automatically.

(In the next post(s) I will cover an example of the differences between traditional CM and CCM and begin to discuss the pros & cons)