NoSubject:Navbox governance
NoSubject:Navbox governance
This page defines the official policy governing the creation, structure, and use of navigation boxes (navboxes) on NoSubject, a MediaWiki-based encyclopedia of psychoanalysis.
This policy is binding on all editors, template maintainers, and bot operators.
---
1. Purpose
Navboxes on NoSubject exist to structure conceptual navigation within psychoanalytic theory. They are not exhaustive indexes or categorical listings, but architectural tools designed to make complex theoretical fields—particularly Lacanian psychoanalysis—legible, traversable, and coherent.
Navboxes must reduce cognitive load, clarify conceptual axes, and support rigorous cross-navigation without redundancy or sprawl.
---
2. Scope
This policy applies to:
- All navbox templates
- All Scribunto (Lua) modules used for navboxes
- All hub pages that anchor navbox systems
- All documentation pages associated with navboxes
---
3. Navbox types
NoSubject recognizes three navbox types.
3.1 Master navbox
- Example:
- Function: High-level conceptual orientation
- Placement: Bottom of core concept and hub pages
- Content: Curated, non-exhaustive lists only
The master navbox must remain compact and delegate deep navigation to sub-navboxes and hub pages.
---
3.2 Sub-navboxes (axis-specific)
- Examples:
- Function: Deep navigation within a single theoretical axis
- Placement:
- Hub pages (expanded)
- Concept pages (collapsed)
Sub-navboxes must correspond to a clearly defined conceptual axis and must not function as general indexes.
---
3.3 Hub pages
- Examples:
- Function: Define and anchor a conceptual axis
- Requirement: Each hub page must include exactly one corresponding sub-navbox
Hub pages serve as interpretive anchors, not mere lists.
---
4. Technical architecture (mandatory)
All sub-navboxes must follow a three-layer Scribunto architecture:
- Template – thin wrapper only
- Module – rendering logic only
- Module:/data – conceptual content only
4.1 Separation of concerns
| Layer | Permitted content | Prohibited content |
|---|---|---|
| Template | Parameter passthrough | Logic, examples, concept lists |
| Module | Rendering, state handling | Concept lists |
| Module:/data | Labels, links, structure | State logic, page detection |
State control (e.g. collapsed/expanded) must never be hard-coded in data modules.
---
5. Expansion rules
5.1 Default behavior
All navboxes are collapsed by default.
5.2 Hub pages
Sub-navboxes must be expanded explicitly on hub pages using:
{{NavboxName|state=expanded}}
5.3 Prohibited methods
The following are not permitted:
- Page-title detection in Lua
- Automatic expansion logic
- Hard-coded expansion in modules or data files
Explicit, local expansion is required.
---
6. Documentation standards
=== 6.1