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 ------------------------------------------------------------------------------ ## page was renamed from TerminologyForDocumentation - This page is intended to clear up some terminology for use in new documentation of the Lenya directory tree. It contains proposed usages of many technical terms and short definitions. + This page is intended to summarize and define Lenya 1.4 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. - ''Please extend and review. Many documenters are not coders, but must they rely on coders to verify that the language in the docs is consistent with internal usage among developers and in the code. Hence this page.'' + ''Developers, please extend and review, to verify that the language in the docs is consistent with internal usage among developers and in the code. Some stuff is taken from the official docs and should be ok, but other parts may contain errors or misconceptions.'' + '''This page deals with Lenya 1.4 only. Some if not most concepts will also apply to Lenya 1.2.x, but users of this version had better refer to the (quite extensive) 1.2 docs.''' - ''This is an initial draft that has not seen much discussion on the lists, except for one comment. Developers, please look through this and suggest corrections or sign it off below so that people see it's been verified.'' --JörnNettingsmeier - - ''Oh drat, instead of the stupid page title this should have been "Glossary" right from the start. FIXME: move page.'' == Publications == - Websites created in Lenya are called '''publications'''. Some people feel this term is unfortunate, but for now we're stuck with it. + Websites created in Lenya are called '''publications'''. Some people feel this term is unfortunate (why not just call them "sites", but for now we're stuck with it. A Lenya installation can contain more than one publication. Publications can either be fully independent, or they can share common properties. See '''Templating''' below. @@ -54, +54 @@ 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 '''workflows'''. - In [http://lenya.apache.org/1_4/concepts/authoring_live.html] you will find term '''mode''' instead of "area" to describe the same concept. + 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]. == Mode == - See "Areas" + See "Area" - == Roles/groups == + == Roles == - - (FIXME: are groups analog to roles? If not, explain.) 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 new roles and workflows. + + Do not confuse roles and groups. OverviewAccessControl has a good explanation of how different they are. == Workflow == @@ -102, +106 @@ (FIXME: find out about different syntaxes, e.g. {fallback:....} - when do I use which?) * context + * user + * group + * usecase === misc === * cross-reference each term to the appropriate docs --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
