The Technical Basis of Content Experience

From Issue #19

I wrote a new blog post last week about how to differentiate a content repository from a full “CMS.” I drew the line around a system’s ability to provide an orchestrated response to an abstract request.

I think the soul of a CMS lies in its ability to reason about abstractions. A CMS can interpret and respond to an abstracted, intentional request – don’t just give me a specific content object, but rather here is my need, and respond with the bundle of content structured in such a way that meets that need.

This is item #94 in a sequence of 305 items.

You can use your left/right arrow keys to navigate