Definitions first

It could be considered a triviality to call a Content Management Systema (CMS) a Content Orient CMS. However the reasons for this are easy to resume.

If we go back since the birth (2000/2001) of CMSs and this is more clear if we consider CMS Frameworks from open source (the ones which dominate now in the low end segment of the market) it is quite clear that CMS have been conceived as sort of panels organized to form a grid of predefined content sources. The most evident of those cases is the templating system. A template is quite restrictive on the content producer side. It requires content to be in some ways serialized unless one edits the template, in such case other and more serious problem arises like the CMS compatibility along the successive releases or the, mostly unwanted, need for programming skills.

A quite different path could be devised getting back to the concept of Context from John McCarthy (lisp's father among other things). I have taken this path.

But back to definitions COMS could be used to name a Content Oriented Management System as opposed/related to CMS.

The same for a Context I will identify a set of items belonging to the same Context, however organized (I will get on this soon).