Think Info
Home
Exploring the information space
Just about every CMS vendor claims to separate content from presentation. While I cannot claim to know every CMS out there, I have yet to encounter one that truly divides these aspects of communication.
Content is a somewhat vague catch-all term. It refers to the information available to be presented. It may be words, images, video. Any granular element of communication is content; it is in this definition that the problem so often occurs: how granular is a granular element?
Is this post an element of content, or is it an aggregation of content elements? It contains both text and image; it has a defined order to the flow of headings and paragraphs. One content? Two content? More?
Presentation is the wrapper around content: the structure that holds the elements in place so their sequence makes sense to the audience. Presentation is the container. But how deep should our definition of what is a container go? How pedantic should we be about what is presentation layer, and what elements are part of the content? That line above that asks “What is presentation?” – should the fact that it is a heading, that renders as an <h3>, be a part of the content, or is that the presentation layer?
Too many CMS’s provide rich text formatting – the ability for the author to identify presentation control directly within a block of text; the inclusion and placement of images, the styling of paragraphs, the specification of link targets – to have any claim to separating content from presentation.
If an element of content is to be re-usable – say rendered onto a web site, into a print publication, through a mobile app, accessed via an API feed – it must exist in a form other than pre-formatted HTML. The element needs to be clean, a self-contained value. To then be usable, it needs to then be associated with metadata that couches its meaning.
I have no problem with the specification that a particular heading is heading-level-3, which will render into the web page as <h3>. This, however, is not the same as storing it wrapped within the <h3>. Including the tag in the body of the element intrinsically devalues the formatting instruction; the system then needs to strip off the wrapper and replace it when delivering to other platforms. If something needs to be stripped off to make content fit for delivery, it was not separated from its container to start with.
The root of the problem is compound.
Firstly: experience. Every message you have been exposed to combines content and container. They were developed together. (In advertising agencies, the standard is to pair a copy writer with a visual designer, so they can develop the message in tandem.) Take the content out of the context of its presentation, and much of its meaning is obfuscated.
Which leads to the second reason: abstraction. A message that needs to be presented with varying emphasis consists of multiple content elements, each independent. Consider any one on its own, without the context of the other elements, and it is too variable; uncontrolled.
That is the third reason: control. Content separated from presentation is free to be reused. One quickly discovers that there are not just two or three ways it can be combined with other elements, but dozens. Hundreds. So many variations leaves those responsible for the message fearful they do not know all the ways it will be presented, to all the audiences.
Knowing this, and being unable to create systems that harness the power of reusability without exposing the complexity that marketers shy away from, CMS vendors only need to pay lip service to the separation of content from presentation. How then should we model content and container to enable the reusable message?
Some people will say that metadata is the answer: put tags on each side, then have an engine bring the layers together. While this helps, it is an incomplete solution. It is little more than making a fine incision between the two halves, then marking the sides up so they must fit back together again.
We need a mechanism that does not simply match pre-structured pieces of the message, but can match one message with multiple containers; multiple messages with a single container. Based on the display environment, the system needs to select the right variant message, building it from constituent elements, wrapping it in a local container that fits both the content it carries and the environment wherein it is presented.
This mechanism is a context engine: a set of functional rules that manipulate and balance, evolving the elements of message and container into a coherent whole. Metadata’s role is not to align content to presentation; it is to allows the contextualisation mechanism to understand the building blocks available to construct the message, and find the appropriate container with which to wrap it.
Of course, to put this into practice, we would need:
a CMS designed to dynamically reconstruct the message from content, context and container…
the guardians of brand messaging to accept this is a dynamic conversation they cannot control as tightly as before…
and people who can visualise the abstract to maintain the contextualisation ruleset.
Separating Content from Presentation, by Chris Shipton – @ChrisShipton
Pingback: What does your CMS actually do? « Think Info
Luc Deniset 2013/04/29 at 10:54 Hi Rick, great article! “I have yet to encounter one that truly divides these aspects of communication” –> Try eZ Publish :-) Reply
Hi Rick, great article! “I have yet to encounter one that truly divides these aspects of communication” –> Try eZ Publish :-)
Fill in your details below or click an icon to log in:
You are commenting using your WordPress.com account. ( Log Out / Change )
You are commenting using your Twitter account. ( Log Out / Change )
You are commenting using your Facebook account. ( Log Out / Change )
You are commenting using your Google+ account. ( Log Out / Change )
Connecting to %s
Notify me of follow-up comments via email.
Notify me of new posts via email.
Enter your e-mail address to subscribe to this blog and receive notifications of new posts by e-mail.
Join 21 other followers
Rick Yagodich The biological imperative (ICC2014) Why technology and humanity must work together (ICC2014) … in “static” and “mobile” contexts (ICC2014)
The biological imperative (ICC2014)
Why technology and humanity must work together (ICC2014)
… in “static” and “mobile” contexts (ICC2014)
Michael Sadler The Enterprise as the Context
The Enterprise as the Context
March 2014
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
March 2013
June 2012
May 2012
April 2012
March 2012
January 2012
October 2011
September 2011
July 2011
June 2011
May 2011
March 2011
"Information is only of value if you give it to people who have the ability to do something with it." Gen. McChrystal bit.ly/1kMqdus - 4 days ago
Some very sensible (as to be expected from @ eaton ) thoughts on process and best practice: bit.ly/1hAJPCW on @ thepastrybox - 2 weeks ago
@ Amelia_Torode Thank you, but it's easy, really. All I tweet are the notes I take... Giving good talks is the real hard work. - 2 weeks ago
Let's put the minds in this room together to make the problems go away. That's when the real magic happens. per @ mrramibanna #LBSmagic - 2 weeks ago
1 in 10 Americans has an activity tracker. If only they could figure out how to get them to do the exercise. per @ mrramibanna #LBSmagic - 2 weeks ago
Get every new post delivered to your Inbox.