Uno/Meta/Organization
From Apache OpenOffice Wiki
Conventions
- Naming
- Structural Grammar
- Description = ("Spec"|"Impl"|"Test")/<text>
- Effort = "Effort"/(<submodule>/)*<text>
- Article = "Article"/<text>
- start = <module>/((<submodule>/)*Description|Effort|Article|"Todo")
- Categories
-
- Each subpage gets categorized by the category of the parent page.
- E.g.: Uno/Spec -category-> Uno
- Each parent page (a page with children) forwards to its direct category page.
- E.g: Uno/Spec -forwards-> Category:Uno:Spec
- Examples
-
- Uno Specifications
- Page: Uno/Spec
- Purpose: Parent page for Uno specifications
- Category: Uno
- Content: forwards to Category:Uno
- Binary Uno Module
- Page: Uno/Binary
- Purpose: Parent page for Binary Uno
- Category: Uno
- Content: forwards to Category Uno:Binary
- Binary Uno specifications
- Page: Uno/Binary/Spec
- Purpose: Parent page for Binary Uno Specifications
- Category: Uno/Binary
- Content: forwards to Category Uno:Binary:Spec
- Specifications of the Binary Uno Component Loader
- Page: Uno/Binary/Component Loader/Spec
- Purpose: Parent page for the Binary Uno Component Loader Specifications
- Content: forwards to Category Uno:Binary:Component Loader:Spec
- Specification of the Binary Uno Component Loader wrt Implementation Environments
- Page: Uno/Binary/Component Loader/Spec/Implementation Environment
- Purpose: Describes the specific behavior of the Binary Uno Component Loader wrt Implementation Environments.
- Content: A specification.