Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by JörnNettingsmeier: http://wiki.apache.org/lenya/Glossary ------------------------------------------------------------------------------ ---- access control:: + + archive:: see '''=>area''' area:: Lenya differenciates between two areas: '''authoring''' (which is what you use while you edit your pages) and '''live''' (which is what the visitors of your website will see). Both 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. A page moves from authoring to live and back according to '''=>workflow'''s. @@ -22, +24 @@ ''[The area concept is currently debated.]'' asset:: A generic term for image and other media files embedded in an XML document. - + + authoring:: see '''=>area''' + content:: content item:: A generic term including XML content (language versions) and assets. @@ -33, +37 @@ context:: - deactivate:: see '''=>workflow'''. + deactivate:: The act of removing a document from the '''=>live''' '''=>area'''. See also: '''=>workflow'''. document:: The set of '''=>language versions''' and other '''=>assets''' of a piece of information grouped under a common '''document id''', with potentially multiple representations (e.g., HTML and PDF formats). ''[This is awkward. There is an ongoing debate about unifying asset and document handling.]'' - edit:: To open a file in one of the editors, make changes, and save those changes. Editors are implemented with '''=>usecases'''. + edit:: To open a file in one of the editors, make changes, and save those changes. See also: '''=>workflow'''. group:: + + info:: see '''=>area''' language version:: A version of a document in a certain language. ''[This is awkward.]'' + + live:: see '''=>area''' mode:: A synonym for '''=>area''' @@ -55, +63 @@ * a collection of XSLTs (e.g., content2svg module) ''(see also [http://lenya.apache.org/1_4/reference/modules/index.html])'' + + navigation:: publication:: A website created with Lenya. A Lenya installation can contain more than one publication. Publications can either be fully independent, or they can share common properties via '''=>publication templating'''. @@ -86, +96 @@ ''(see also [http://lenya.apache.org/1_4/reference/resource-types.html])'' + review:: The act of proof-reading a '''=>submit''ted document and deciding whether to '''=>publish''' or to '''=>reject''' it. See also: '''=>workflow'''. + + revision control:: + - role:: By default, Lenya defines three basic roles that a lenya user can have. An '''admin''' can control all aspects of a publication and create, delete or modify users and groups. An '''editor''' can modify and create new content, but cannot publish it; for this, s/he hands the work to a '''reviewer''', who does the final check and decides whether the page can go live. + role:: The capabilities and privileges of a user as part of a '''=>workflow'''. By default, Lenya defines three basic roles that a lenya user can have. An '''admin''' can control all aspects of a publication and create, delete or modify users and groups. An '''editor''' can modify and create new content, but cannot publish it; for this, s/he hands the work to a '''reviewer''', who does the final check and decides whether the page can go live. You can define custom roles and workflows. Roles are frequently assigned via '''=>group''' membership, but do not confuse roles and groups. OverviewAccessControl has a good explanation of how different they are. @@ -95, +109 @@ sitemap:: + site tree:: The tree-representation of the hierarchical relationship of documents within a site. Currently implemented as an XML file under <pubname>/content/sitetree.xml. + + site tree node:: A particular document entry within the site tree. + source factory:: + + submit:: The act of passing on an '''=>edit'''ed document to '''=>review'''. See also: '''=>workflow'''. usecase:: user:: + + version:: A particular state of a document with a time stamp, used in '''=>revision control'''. workflow:: A sequence of actions necessary to accomplish a task. For instance, in order to move a page from the authoring to the live area, an editor must '''submit''' it. A reviewer can then '''reject''' it (it gets sent back to the editor for some more polishing) or '''publish''' it, in which case the page moves to the live area. To move a page back from live to authoring, a reviewer must '''deactivate''' it. Afterwards, it can either be re-published or '''deleted'''. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
