Modeling and Storing Content in a Content Management System: Can Content Models Make or Break Your Content Management Implementation?

You’ve made the investment in a content management system (CMS). It’s been rolled out to the business units and content updates and maintenance is now in the realm of content experts. Finally, everyone can get back to strategic objectives and growing the business, rather than struggling to
keep content up-to-date.

So, why aren’t the owners publishing content? Why is the IT department deluged with requests to help with content issues? Why are content edits still becoming full-blown IT projects? Why is the one person who knows HTML still the only one actually doing the publishing? Has the CMS actually changed anything?

The difficulty users have with accurately finding their content – as well as the limitations that a CMS can place on presentation – can be directly traced to the way content is stored within the system. In order to avoid user frustration and abandonment of a CMS, it is essential that the content is modeled and stored in such a way that meets the business’ publishing needs and the needs of the end users.

Request a PDF of this point of view >>  

More Molecular Perspectives >>