The framework can be configured to create revisions each time a piece of content is edited. This allows for change rollback and also provides an audit trail for changes made to content within a multi-user system.

Further to this, custom workflows could be created that occur when content is created, moderated and published, and can be configured down such that the creation and assignment of arbitrary workflows to can be applied to specific content types (pages, newsletters, blogs, documents, etc).

Workflows are made up of workflow states such as Draft, Review and Published. This means that a website page (or any type of content) could be created in Draft, and a few users could work on it. Once its ready, it could then pushed to Review status, from which an authorised person could accept or reject the page. Acceptance would put the page into Published state, which makes it visible to the public.

Additionally transitions between workflow states can have actions assigned to them. In our example, we could assign an action so that when the page moves from the Draft state to the Review state an email is sent out. Another action could be assigned to the transition from Review to Published so that the node's status is set to Published (and becomes visible on your website).