Skip to content

Design Thinking docs missing sidebar ordering after Docusaurus migration #830

@WilliamBerryiii

Description

@WilliamBerryiii

Summary

The Design Thinking documentation category (docs/design-thinking/) was not updated during the Docusaurus migration that added sidebar_position frontmatter and _category_.json files to all other documentation categories. As a result, the 16 Design Thinking pages render in alphabetical order instead of the logical method sequence (1–9) with supporting pages correctly positioned around them.

Current Behavior

  • No _category_.json exists in docs/design-thinking/, so the category has no explicit label or position in the sidebar.
  • None of the 16 markdown files include a sidebar_position frontmatter field.
  • The sidebar uses autogenerated mode (sidebars.js), which means pages fall back to alphabetical ordering when no position metadata is present.
  • Alphabetical ordering produces a confusing sequence: dt-coachdt-learning-tutordt-rpi-integrationmethod-01 → ... → method-09READMEtutorial-handoff-to-rpiusing-togetherwhy-design-thinking.

Expected Behavior

Pages should follow the logical reading order: overview first, rationale, agent introductions, then Methods 1–9 in sequence, followed by integration and advanced usage topics. This matches the pattern established by every other documentation category (Getting Started, HVE Guide, RPI, Agents, Architecture, Contributing, Security, Templates).

Proposed Changes

1. Create docs/design-thinking/_category_.json

{
  "label": "Design Thinking",
  "position": 3,
  "collapsible": true,
  "collapsed": true,
  "link": {
    "type": "generated-index"
  }
}

Design Thinking logically belongs at position 3 (after Getting Started at 2), which requires bumping HVE Guide and all subsequent categories by one position.

Alternative: Use position 10 to append after Templates without renumbering. The right choice depends on the desired information architecture — Design Thinking as a core methodology guide (position 3) vs. a supplemental reference (position 10).

2. Add sidebar_position frontmatter to all 16 files

File sidebar_position Rationale
README.md 1 Category landing page / overview
why-design-thinking.md 2 Rationale — read before diving into methods
dt-coach.md 3 Primary agent introduction
dt-learning-tutor.md 4 Secondary agent (structured learning)
method-01-scope-conversations.md 5 Method 1 — Problem Space entry
method-02-design-research.md 6 Method 2
method-03-input-synthesis.md 7 Method 3 — Problem Space exit
method-04-brainstorming.md 8 Method 4 — Solution Space entry
method-05-user-concepts.md 9 Method 5
method-06-lofi-prototypes.md 10 Method 6 — Solution Space exit
method-07-hifi-prototypes.md 11 Method 7 — Validation Space entry
method-08-test-validate.md 12 Method 8
method-09-iteration-at-scale.md 13 Method 9 — Validation Space exit
dt-rpi-integration.md 14 Integration reference (bridges DT → RPI)
tutorial-handoff-to-rpi.md 15 Step-by-step handoff tutorial
using-together.md 16 End-to-end walkthrough

3. If position 3 is chosen, update existing _category_.json positions

Bump position by 1 in:

  • docs/hve-guide/_category_.json (3 → 4)
  • docs/rpi/_category_.json (4 → 5)
  • docs/agents/_category_.json (5 → 6)
  • docs/architecture/_category_.json (6 → 7)
  • docs/contributing/_category_.json (7 → 8)
  • docs/security/_category_.json (8 → 9)
  • docs/templates/_category_.json (9 → 10)

Context

Every other documentation category was updated during the docusaurus-serve-real-docs migration. Design Thinking appears to have been an oversight — the migration removed placeholder files from docs/docusaurus/docs/design-thinking/ but did not add ordering metadata to the real files in docs/design-thinking/.

Acceptance Criteria

  • docs/design-thinking/_category_.json exists with correct label and position
  • All 16 files in docs/design-thinking/ have sidebar_position in frontmatter
  • Sidebar renders pages in the logical order listed above
  • If category position 3 is used, downstream category positions are updated
  • Docusaurus build completes without warnings

Metadata

Metadata

Labels

documentationImprovements or additions to documentation

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions