Latest revision as of 11:11, 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 ==
* [[HF_ALL/Developers/TeamBornemann]]* [[HF_ALL/Developers/TeamOdoo]]* [[HF_ALL/Developers/TeamNordex]]* [[HF_ALL/Developers/TeamMercedes]]
== General Documentation ==
* [[HF_ALL/Developers/Onboarding]]* [[HF_ALL/Developers/CodeStandards]]* [[HF_ALL/Developers/DevTools]]* [[HF_ALL/Developers/BestPractices]][[HF_ALL|← 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.
[[Developers|← Back to Developers]]

Use the format:

[[ParentPageName|← 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.
[[Developers/TeamBornemann|← Back to Team Bornemann]]

Step 4: (Optional) Create an Overview or “Tree”

You can manually show the hierarchy using nested bullet lists.

= Developers =

== Teams ==
* [[HF_ALL/Developers/TeamBornemann]]* [[HF_ALL/Developers/TeamOdoo]]* [[HF_ALL/Developers/TeamNordex]]* [[HF_ALL/Developers/TeamMercedes]]
== Documentation ==
* [[HF_ALL/Developers/Onboarding]]* [[HF_ALL/Developers/CodeStandards]]** [[HF_ALL/Developers/CodeStandards/Python]]** [[HF_ALL/Developers/CodeStandards/JavaScript]]
* [[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.:
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.

{HF_ALL|Developers/TeamBornemann}}

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

Create a department index page (e.g., HF_ALL/Developers)
Add subpages using /
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.

@@ Line 2: / Line 2: @@
 == Problem ==
-Wikipedia and other MediaWiki-based wikis do not have a true folder or hierarchical page structure.
+Wikipedia and other MediaWiki-based wikis do not have a true folder or hierarchical page structure. All pages exist in a flat namespace.
-All pages exist in a flat namespace.
 == Goal ==
-Create a logical hierarchy using '''normal pages that contain structured lists of links'''.
+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.
-This approach makes the wiki feel hierarchical without changing its technical structure.
 ----
 == Step 1: Create a “Parent” Page ==
-Create a main page that acts as a directory or table of contents for a topic.
+Create a main page that serves as a directory or table of contents for a topic.
 '''Example:'''
 ; Page title
-: Devlopers
+: <code>Developers</code>
+[[File:S3.png|frame|border|none]]
+; Page content
-; Page content
 <pre>
-= Projects =
+= Developers =
-This page lists all ongoing projects.
+This page contains all general developer-related information, guidelines, and processes.
-== Active Projects ==
-* [[Projects/Project A]]
-* [[Projects/Project B]]
-== Completed Projects ==
+== Developer Teams ==
-* [[Projects/Old Project 1]]
+* [[HF_ALL/Developers/TeamBornemann]]* [[HF_ALL/Developers/TeamOdoo]]* [[HF_ALL/Developers/TeamNordex]]* [[HF_ALL/Developers/TeamMercedes]]
-* [[Projects/Old Project 2]]
+== General Documentation ==
+* [[HF_ALL/Developers/Onboarding]]* [[HF_ALL/Developers/CodeStandards]]* [[HF_ALL/Developers/DevTools]]* [[HF_ALL/Developers/BestPractices]][[HF_ALL|← Back to HF_ALL]]
 </pre>
@@ Line 35: / Line 31: @@
 == Step 2: Create the Linked Pages ==
-Click a red link (for example HF ALL:Developers/Nordex to create that subpage.
+Click a red link (for example <code>HF_ALL/Developers/TeamBornemann</code>) to create that subpage.
 '''Example:'''
 ; Page title
-: <code>Projects/Project A</code>
+: <code>Developers/TeamBornemann</code>
 ; Page content
 <pre>
-= Project A =
+= Team Bornemann =
-This is Project A.
+Documentation related to Project Team Bornemann.
+[[Developers|← Back to Developers]]
-[[Projects|← Back to Projects]]
 </pre>
-Each page links back to its parent using:
+Use the format:
-<pre>[[ParentPageName|← Back to Parent Page]]</pre>
+<pre>[[ParentPageName|← Back to Parent Page]] </pre>
 ----
@@ Line 59: / Line 54: @@
 '''Example:'''
 ; Page title
-: <code>Projects/Project A/Planning</code>
+: <code>Developers/TeamBornemann/Planning</code>
 ; Page content
 <pre>
-= Project A – Planning =
+= Team Bornemann – Planning =
 Details of the planning phase.
+[[Developers/TeamBornemann|← Back to Team Bornemann]]
-[[Projects/Project A|← Back to Project A]]
 </pre>
@@ Line 72: / Line 66: @@
 == Step 4: (Optional) Create an Overview or “Tree” ==
-You can manually display a hierarchy by nesting lists:
+You can manually show the hierarchy using nested bullet lists.
 <pre>
-= Projects =
+= Developers =
-* [[Projects/Project A]]
-** [[Projects/Project A/Planning]]
+== Teams ==
-** [[Projects/Project A/Results]]
+* [[HF_ALL/Developers/TeamBornemann]]* [[HF_ALL/Developers/TeamOdoo]]* [[HF_ALL/Developers/TeamNordex]]* [[HF_ALL/Developers/TeamMercedes]]
-* [[Projects/Project B]]
+== Documentation ==
-** [[Projects/Project B/Planning]]
+* [[HF_ALL/Developers/Onboarding]]* [[HF_ALL/Developers/CodeStandards]]** [[HF_ALL/Developers/CodeStandards/Python]]** [[HF_ALL/Developers/CodeStandards/JavaScript]]
-** [[Projects/Project B/Results]]
+* [[HF_ALL/Developers/DevTools]]** [[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, such as <code>Projects/ProjectA/Planning</code>.
-* Add a “Back to parent” link on each subpage.
+* Use consistent page names with slashes (e.g., <code>Developers/TeamBornemann/Planning</code>).
-* You can create a small template to simplify the “Back” link, for example:
+* Add a "Back to parent" link on each subpage.
-  <pre>{{Parent|Projects/ProjectA}}</pre>
+* Consider creating a template to simplify “Back” links, e.g.:
-* Maintain a single “index” page (like <code>Projects</code>) that defines the hierarchy.
+* Maintain a single “index” page (e.g., <code>HF_ALL/Developers</code>) that defines the hierarchy.
+* Store only internal documentation—avoid client-confidential content.
 ----
 == Summary ==
+To create a clean, structured hierarchy in MediaWiki under <code>HF_ALL</code>:
+* Create a department index page (e.g., <code>HF_ALL/Developers</code>)
+* Add subpages using <code>/</code>
+* 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.
+<code><nowiki>{HF_ALL|Developers/TeamBornemann}}</nowiki></code>
 {| class="wikitable"
+To create a clean, structured hierarchy in MediaWiki under '''HF_ALL''':
+# Create a '''department index page''' (e.g., HF_ALL/Developers)
+# 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.