Structuring
Page
- "Specialpages": Automatically generated content; "Maintenance lists"; "Manager interface"
- "Contentpages": User generated content; versioned changes;
- "Wikipage"
- "File description pages": Hybrid page
- "Cagetory pages": Hybrid page
- ...
Namespace
- Avoid naming collisions
- Used for access restrictions
- A page can only be assigned to one namespace
- Can be identified by a prefix in the page name
- Exception: "Main namespace", aka "(Pages)"
- Special predefined namespaces, like "File", "Category", "User", "Template", ...
- Custom namespaces: E.g. for "Documenttypes" or "Organisational structuring"
- "Talk" namespaces: Associated namespace, like "User_talk", "Template_talk", ...
- Certain functions of the wiki can be activated/deactivated based on namespaces
Category
- "Tagging" mechanism --> Multiple categories for a page
- Namespace independent
- Part of the content --> Everyone that can edit a regular contentpage can also create categories
- Category pages can be categorized --> Treelike catgegory structure
Subpage
- Path indicated by "/" (=forward slash)
- Example: "Product:N52000786-2/Technical notes"
- "Product:" => "namespace prefix"
- "N52000786-2" => "root / parent pagename"
- "Technical notes" => "subpage name"
- Recommendation: not more than two levels
- When to use?
- "strong association" of pages
- "avoid naming collisions"
- When not to use?
- Knowledge base-like content
Content and formatting
Templates (=Text-templates, Text-blocks)
- Include contents
- "Transclusion" => Transfrom + Include
- Dedicated namespace "Template"
- Can take parameters
Page templates
- Only used then a new page is created
- Prefill mechanism
Wikitext
- Simple to learn
- Effcient to create
- Easy to compare
