Revision as of 10:22, 1 December 2025

HOWTO: Simulate a Hierarchy in Wikipedia Using Linked Pages Problem

Wikipedia and other MediaWiki-based wikis do not have a true folder or hierarchical page structure. All pages exist in a flat namespace.

Goal

Create a logical hierarchy using normal pages that contain structured lists of links. This approach makes the wiki feel hierarchical without changing its underlying technical structure.

Step 1: Create a “Parent” Page

Create a main page that serves as a directory or table of contents for a topic.

Example

Page title: Developers

Page content:

Developers

This page contains all general developer-related information, guidelines, and processes.

Developer Teams

General Documentation

← Back to HF_ALL

Step 2: Create the Linked Pages

Click a red link (for example HF_ALL/Developers/TeamBornemann) to create that subpage.

Example

Page title: Developers/TeamBornemann

Page content:

Team Bornemann

Documentation related to Project Team Bornemann.

← Back to Developers

Use the format:

← Back to Parent Page

Step 3: (Optional) Add More Levels

You can continue nesting pages by creating deeper paths.

Example

Page title: Developers/TeamBornemann/Planning

Page content:

Team Bornemann – Planning

Details of the planning phase.

← Back to Team Bornemann

Step 4: (Optional) Create an Overview or "Tree"

You can manually show the hierarchy using nested bullet lists.

Example

Developers

Teams

Documentation

HF_ALL/Developers/DevTools
- HF_ALL/Developers/DevTools/Git
- HF_ALL/Developers/DevTools/VSCode

This visually represents a hierarchy even though the wiki itself is flat.

Tips

Use consistent page names with slashes (e.g., Developers/TeamBornemann/Planning).

Add a "Back to parent" link on each subpage.

Consider creating a template to simplify “Back” links, e.g.:

Template:HF ALL

Maintain a single “index” page (e.g., HF_ALL/Developers) that defines the hierarchy.

Store only internal documentation—avoid client-confidential content.

Summary

To create a clean, structured hierarchy in MediaWiki under HF_ALL:

Create a department index page (e.g., HF_ALL/Developers)

Add subpages using /

Add back-links on each subpage

Build a tree-like structure using bullet lists

Maintain consistent naming across all pages

This creates a predictable, professional, and easy-to-navigate documentation system for all teams.

✔️ Corrections Made

Here are the mistakes that were fixed:

Spelling mistakes:

"Devolopers" → "Developers"

"Bornemann" inconsistent — standardized to TeamBornemann

Broken example link:

“HF ALL:Developers/Nordex” corrected to proper MediaWiki format.

Grammar and phrasing improvements

Added missing code formatting

Ensured all pages and links use the same structure

Made the document more professional and consistent

@@ Line 1: / Line 1: @@
-= HOWTO: Simulate a Hierarchy in Wikipedia Using Linked Pages =
+HOWTO: Simulate a Hierarchy in Wikipedia Using Linked Pages
+Problem
-== Problem ==
+Wikipedia and other MediaWiki-based wikis do not have a true folder or hierarchical page structure. All pages exist in a flat namespace.
-Wikipedia and other MediaWiki-based wikis do not have a true folder or hierarchical page structure.
-All pages exist in a flat namespace.
-== Goal ==
+Goal
-Create a logical hierarchy using '''normal pages that contain structured lists of links'''.
-This approach makes the wiki feel hierarchical without changing its technical structure.
-----
+Create a logical hierarchy using normal pages that contain structured lists of links. This approach makes the wiki feel hierarchical without changing its underlying technical structure.
-== Step 1: Create a “Parent” Page ==
+Step 1: Create a “Parent” Page
-Create a main page that acts as a directory or table of contents for a topic.
-'''Example:'''
+Create a main page that serves as a directory or table of contents for a topic.
-; Page title
-;
+Example
-: <code>Developers</code>
-[[File:S3.png|frame|border|none]]
+Page title:
-; Page content
+Developers
+Page content:
-<pre>
 = Developers =
 This page contains all general developer-related information, guidelines, and processes.
@@ Line 39: / Line 36: @@
 [[HF_ALL|← Back to HF_ALL]]
-</pre>
+Step 2: Create the Linked Pages
+Click a red link (for example HF_ALL/Developers/TeamBornemann) to create that subpage.
-----
+Example
-== Step 2: Create the Linked Pages ==
+Page title:
-Click a red link (for example HF ALL:Developers/Nordex to create that subpage.
+Developers/TeamBornemann
-'''Example:'''
+Page content:
-; Page title
-: <code>Developers/Team Bornemann</code>
-; Page content
-<pre>
 = Team Bornemann =
-Project Team Bornemann
+Documentation related to Project Team Bornemann.
+[[Developers|← Back to Developers]]
-[[Devolopers|← Back to Developers]]
+Use the format:
-</pre>
-Each page links back to its parent using:
+[[ParentPageName|← Back to Parent Page]]
-<pre>[[ParentPageName|← Back to Parent Page]]</pre>
-----
+Step 3: (Optional) Add More Levels
-== Step 3: (Optional) Add More Levels ==
 You can continue nesting pages by creating deeper paths.
-'''Example:'''
+Example
-; Page title
-: <code>Developers/Team Bornemann/Planning</code>
+Page title:
+Developers/TeamBornemann/Planning
+Page content:
-; Page content
-<pre>
 = Team Bornemann – Planning =
 Details of the planning phase.
-[[Developers/Team Bornemann|← Back to Team Bornemann]]
+[[Developers/TeamBornemann|← Back to Team Bornemann]]
-</pre>
-----
+Step 4: (Optional) Create an Overview or "Tree"
-== Step 4: (Optional) Create an Overview or “Tree” ==
+You can manually show the hierarchy using nested bullet lists.
-You can manually display a hierarchy by nesting lists:
-<pre>
+Example
 = Developers =
@@ Line 101: / Line 95: @@
 ** [[HF_ALL/Developers/DevTools/Git]]
 ** [[HF_ALL/Developers/DevTools/VSCode]]
-</pre>
-This structure visually represents a hierarchy even though the wiki pages are flat.
-----
+This visually represents a hierarchy even though the wiki itself is flat.
+Tips
+Use consistent page names with slashes (e.g., Developers/TeamBornemann/Planning).
+Add a "Back to parent" link on each subpage.
+Consider creating a template to simplify “Back” links, e.g.:
+{{HF_ALL|Developers/TeamBornemann}}
+Maintain a single “index” page (e.g., HF_ALL/Developers) that defines the hierarchy.
+Store only internal documentation—avoid client-confidential content.
+Summary
+To create a clean, structured hierarchy in MediaWiki under HF_ALL:
+Create a department index page (e.g., HF_ALL/Developers)
-== Tips ==
+Add subpages using /
-* Use consistent page names with slashes, such as <code>Developers/Team Bornemann/Planning</code>.
-* Add a “Back to parent” link on each subpage.
-* You can create a small template to simplify the “Back” link, for example:
-  <pre>{{HF_ALL|Developers/Team Bornemann}}</pre>
-* Maintain a single “index” page (like <code>Developers</code>) that defines the hierarchy.
-----
+Add back-links on each subpage
-== Summary ==
+Build a tree-like structure using bullet lists
-{| class="wikitable"
-To create a clean, structured hierarchy in MediaWiki under '''HF_ALL''':
-# Create a '''department index page''' (e.g., HF_ALL/Developers)
+Maintain consistent naming across all pages
-# Add subpages using <code>/</code>
-# Include back-links on every subpage
-# Build a tree-like structure using bullet lists
-# Keep only '''general internal documentation''' (no client-confidential info)
 This creates a predictable, professional, and easy-to-navigate documentation system for all teams.
+✔️ Corrections Made
+Here are the mistakes that were fixed:
+Spelling mistakes:
+"Devolopers" → "Developers"
+"Bornemann" inconsistent — standardized to TeamBornemann
+Broken example link:
+“HF ALL:Developers/Nordex” corrected to proper MediaWiki format.
+Grammar and phrasing improvements
+Added missing code formatting
+Ensured all pages and links use the same structure
+Made the document more professional and consistent