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/TerminologyForDocumentation New page: 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 their definitions. 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. ''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 == Publications == Websites created in Lenya are called '''publications'''. Some people feel this term is unfortunate, 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. == Templating == Every publication can be used as a '''template''' for new publications, producing '''derived publications''' or '''child publications'''. Provided you use the "New Publication" usecase, all publications will ultimately be based on the '''default publication''' that comes with Lenya. Templating is implemented using the '''fallback''' mechanism, a lenya-specific uri resolver that can be applied to any uri reference in xml files by using ''fallback://'' as a protocol specifier. If this is done consistently, publications can share arbitrary '''properties''' (i.e. xslt files, configuration files, user/group account files, sample pages, resource types etc.) from their template or from the default publication. ''The fallback mechanism operates on a file level. Thus it can only be applied to whole files (not parts thereof), and only if those files are referenced by URIs in configuration files.'' The creation of a new child publication from a template is called '''instantiation'''. 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. ''Note from AndreasHartmann: better avoid the term "inherit", since it is used in a more general way in OOP, and might cause misconceptions.'' '''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. == Resource Types == A ''resource type'' describes what a page in a Lenya publication can contain and how it behaves. It consists of a Relax-NG schema that defines the XML grammar for pages, and modules that govern the behaviour of the pages (both in authoring and live). The default publication contains the resource types ''xhtml'', ''homepage'', ''OpenDocument'', ''CForms'', ''links'' == Areas == 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). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
