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 ------------------------------------------------------------------------------ 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. + Other, less frequently used areas are '''archive''' (for old, no longer publicly available documents) and '''info''' (FIXME: explain). In the docs you will sometimes find term '''mode''' instead of "area" to describe the same concept. - see also [http://lenya.apache.org/1_4/concepts/authoring_live.html] + ''(see also [http://lenya.apache.org/1_4/concepts/authoring_live.html])'' ''[The area concept is currently debated.]'' @@ -32, +33 @@ context:: + deactivate:: see '''=>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.]'' + ''[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'''. group:: @@ -49, +54 @@ * a repository implementation (e.g., jdbc module) * a collection of XSLTs (e.g., content2svg module) - see also [http://lenya.apache.org/1_4/reference/modules/index.html]. + ''(see also [http://lenya.apache.org/1_4/reference/modules/index.html])'' 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'''. - see also [http://lenya.apache.org/1_4/concepts/publication.html] + ''(see also [http://lenya.apache.org/1_4/concepts/publication.html])'' ''[Some people feel this term is unfortunate (why not just call it a "site"?), but for now we're stuck with it.]'' @@ -66, +71 @@ Child publications can use features of their template(s) in two ways: by '''copying''' files from the template during instantiation, or by '''referencing''' those files. '''Copying''' severs the link between child and template - later changes to the template will not affect the child. '''Referencing''' implies that all changes to the template will immediately affect the child as well, since the child uses the template's property. - see also [http://lenya.apache.org/1_4/reference/publication-templating/index.html] + ''(see also [http://lenya.apache.org/1_4/reference/publication-templating/index.html])'' + + publish:: see '''=>workflow''' + + resource:: A generic term in need of clarification that can mean almost anything. resource type:: An XML source format for Lenya '''=>documents''', together with processing options. It typically consists of * an XML structure definition (e.g., Relax NG) @@ -75, +84 @@ * usecases to manipulate documents. The default publication contains the resource types ''xhtml'', ''homepage'', ''OpenDocument'', ''CForms'' and ''links''. - see also [http://lenya.apache.org/1_4/reference/resource-types.html] + ''(see also [http://lenya.apache.org/1_4/reference/resource-types.html])'' 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. 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. + site:: A synonym for '''=>publication'''. + sitemap:: source factory:: @@ -93, +104 @@ 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'''. - Workflow actions are implemented with '''=>usecases'''. Moreover, "usecase" is often used as a synonym for the rather kludgy "workflow action". + '''Workflow transitions''' are implemented with '''=>usecases'''. Moreover, in a workflow context, "usecase" is sometimes used as a synonym for "workflow transition". - You can define new workflow actions and rules for changing between states, but this requires custom java code. + You can define new workflow transitions and rules for changing between states, but this requires custom java code. == to do == --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
