AnsweredAssumed Answered

Granularity of CMS objects

Question asked by jocsch on Jul 6, 2005
in your preview release it seems that your approach of CMS objects is very document centric.
Does the underlying engine also allows for more granularity?
E.g., a html page is very seldom one document. Instead it's a template which references to articles, images from imagegalleries, paragraphs which themselves are under versioncontrol and have their own ACLs.

If this is possible, how do you handle versioning? Do versioned objects (which means the objects in the version history, not the most recent one) preserve the references. Or do you have a concept like the "frozen nodes" in JSR 170 (references are no longer actively checked when a node is versioned)?