In the eyes of a lot of users a major drawback of Plone is the missing "versioning" feature. This is especially true for intranet deployments and document management based on Plone.

Plone needs to have a consistent, core solution for simple versioning tasks. This is expected of modern CMS packages. CMFEditions want to be the answer to such needs.

Goals

• Work safely. If you make a mistake, you can go back to an earlier version.
• Collaboration.

  Version comments and version history help you communicate to co-workers the high-level changes during a document's lifecycle.

• Comparison.

  Easily see how a document has changed between versions.

• Stable repository.

  Authoritative version information is stored in a solid, pluggable repository (default repository is Zope Version Control).

• Archetypes friendly.

  Custom content types should just work, anticipating special needs such as relations.

• Stable.

  Don't rely on too much machinery and infrastructure that isn't already being used.

Dependencies

CMFEditions works fine not only with default Plone but also with LinguaPlone (multilingual contents), Archetypes, ATContent Types or any other AT based custom content type.