Revision as of 10:15, 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 technical structure.

Step 1: Create a “Parent” Page

Create a main page that acts 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/Nordex to create that subpage.

Example:

Page title: Developers/Team Bornemann

Page content

= Team Bornemann =
Project Team Bornemann

[[Devolopers|← Back to Developers]]

Each page links back to its parent using:

[[ParentPageName|← Back to Parent Page]]

Step 3: (Optional) Add More Levels

You can continue nesting pages by creating deeper paths.

Example:

Page title: Developers/Team Bornemann/Planning

Page content

= Team Bornemann – Planning =
Details of the planning phase.

[[Developers/Team Bornemann|← Back to Team Bornemann]]

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

You can manually display a hierarchy by nesting 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 structure visually represents a hierarchy even though the wiki pages are flat.

Tips

Use consistent page names with slashes, such as Developers/Team Bornemann/Planning.
Add a “Back to parent” link on each subpage.
You can create a small template to simplify the “Back” link, for example:

{{Parent|Projects/ProjectA}}

Maintain a single “index” page (like Projects) that defines the hierarchy.

Summary

@@ Line 51: / Line 51: @@
 ; Page content
 <pre>
-= Project A =
+= Team Bornemann =
-This is Project A.
+Project Team Bornemann
-[[Projects|← Back to Projects]]
+[[Devolopers|← Back to Developers]]
 </pre>
@@ Line 67: / Line 67: @@
 '''Example:'''
 ; Page title
-: <code>Projects/Project A/Planning</code>
+: <code>Developers/Team Bornemann/Planning</code>
 ; Page content
 <pre>
-= Project A – Planning =
+= Team Bornemann – Planning =
 Details of the planning phase.
-[[Projects/Project A|← Back to Project A]]
+[[Developers/Team Bornemann|← Back to Team Bornemann]]
 </pre>
@@ Line 83: / Line 83: @@
 <pre>
-= Projects =
+= Developers =
-* [[Projects/Project A]]
-** [[Projects/Project A/Planning]]
+== Teams ==
-** [[Projects/Project A/Results]]
+* [[HF_ALL/Developers/TeamBornemann]]
-* [[Projects/Project B]]
+* [[HF_ALL/Developers/TeamOdoo]]
-** [[Projects/Project B/Planning]]
+* [[HF_ALL/Developers/TeamNordex]]
-** [[Projects/Project B/Results]]
+* [[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]]
 </pre>
@@ Line 97: / Line 107: @@
 == Tips ==
-* Use consistent page names with slashes, such as <code>Projects/ProjectA/Planning</code>.
+* 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: