This page is intended to summarize and define Lenya terminology, to point out usage inconsistencies and synonymous terms, and to collect pointers to more detailed information either in the official Lenya documentation or other pages in this wiki.

It is aimed at new Lenya users looking for a short primer, at proficient users in need of a handy reference and at developers and documentation writers who need a quick refresher in order to maintain consistent usage of technical terms in their code comments and docs.

For a comparison of Lenya's terminology with that of other Content Management Systems see CMSTerminologyComparison.

A more concise top-down overview of those key terms concerning Lenya content structure can be found at GlossaryStructure.

access control
The functionality needed to restrict and control who may edit, publish or visit the content of a Lenya publication.

(see also OverviewAuthenticationAndAuthorization)


An access control object which can have certain =>roles on URLs. See also =>policies. Currently used accreditables are:

  • =>user

  • =>group

  • =>IP range

  • =>world

  • archive

    (1) n: An =>area. (2) v: The act of moving a deactivated document to the archive area for later reference or re-use (as opposed to deleting it).

    In Lenya, the content can exist in different versions at the same time. The "storage containers" of the content version sets are called areas. At the moment, the following areas are supported:
  • authoring - edit pages
  • live - the published pages, visible to site visitors
  • archive - archived pages, can be restored
  • trash - deleted pages, can be restored until trash is emptied.
  • admin - administration area (not really a content area, just a tab for administrative tasks).
  • staging - review edited pages (this is not supported in Lenya 2.0)
  • In Lenya 1.2, the prefix "info-" can be added to the authoring, staging, archive, and trash areas. This is used to display the sitetree and page information (commonly refered to as "info area").

    The areas share many properties (notably the presentation of the content), but can have additional properties of their own (an obvious example are the editing menus in the authoring area). Live and authoring can have different content.

    In Lenya, the workflow of a document is controlled by a with arbitrary states, transitions, and events, which is expressed using XML. Each resource type can use its own workflow schema. You can implement custom conditions to be checked before a transition can fire, this requires custom java code.


    The Lenya staging server under It hosts the Lenya demos and the latest auto-generated docs from SVN.

    To do

    New terms coined for this section

    Are there better, already established terms for these concepts? If so, let's use them instead and get rid of these new ones.

    Glossary (last edited 2009-09-20 23:27:40 by localhost)