Skip to main content

Content Alignment Summary

✨ Tufte-Aligned Documentation Architecture

All 8 guide documents have been optimized for the new 4-root Tufte sidebar structure.


Quick Guides Section (Start > Quick Guides)

Rendered order (sidebar_position):

1. Spreadsheet Engine (Gridheim)
id: gridheim-quick-start
tags: [gridheim, spreadsheet, component, tutorial, integration]

2. Build Custom Modules
id: execmodule-development
tags: [valkyrai, execmodules, development, workflow, build]

3. Code Generation (ThorAPI)
id: thorapi-integration
tags: [thorapi, codegen, valkyrai, integration, build]

4. Publish MCP Services
id: mcp-publishing
tags: [mcp, publishing, services, api, integrate]

5. [Reserved for future guide]

6. Onboarding Flows
id: onboarding-flow-guide
tags: [onboarding, signup, workflows, integration, build]

Troubleshooting Section (Start > Troubleshooting)

Rendered order (sidebar_position):

1. Workflows & Execution
id: valkyrai-workflow-troubleshooting
tags: [valkyrai, workflows, execmodules, debugging, troubleshooting]

2. MCP Publishing Issues
id: mcp-publishing-troubleshooting
tags: [mcp, publishing, troubleshooting, debug]

3. Spreadsheet Engine (Gridheim)
id: gridheim-troubleshooting
tags: [gridheim, troubleshooting, debugging, component, errors]

Key Improvements

1. Naming Consistency

  • Before: Mixed labels ("Quick Start", "Module Development", "ThorAPI Integration", "Publishing Services")
  • After: Consistent pattern showing product + action (all specify what they teach about which product)

2. Sidebar Labels Match Sidebar Structure

  • All labels now match exactly what appears in the navigation
  • Product names clearly mentioned where relevant
  • Eliminates ambiguity ("Quick Start" for what? → "Spreadsheet Engine (Gridheim)")

3. Tag Standardization

  • All guides: exactly 4-5 tags
  • First tag = primary category
  • Consistent action verbs: build, integrate, debug, troubleshoot
  • Example: [thorapi, codegen, valkyrai, integration, build] vs old [thorapi, valkyrai, codegen, integration, guide]

4. Semantic Ordering

  • Quick Guides positioned for learning progression:
    • 1-2: Beginner tasks (Gridheim, ExecModules)
    • 3-4: Intermediate/foundational (ThorAPI, MCP)
    • 6: Advanced (Onboarding flows)
  • Troubleshooting ordered by frequency:
    • 1: Most common (Workflow execution)
    • 2: Specialist (MCP publishing)
    • 3: Component-specific (Gridheim)

5. Intent-Driven Architecture

  • Each guide title + tags clearly show user intent
  • User can scan and see: "I want to BUILD custom modules" vs "I want to TROUBLESHOOT workflows"
  • Tags enable filtering by skill level and domain

Content Files Updated

✅ /docs/docs/guides/gridheim-quick-start.md
✅ /docs/docs/guides/execmodule-development.md
✅ /docs/docs/guides/thorapi-integration.md
✅ /docs/docs/guides/mcp-publishing.md
✅ /docs/docs/guides/onboarding-flow-guide.md
✅ /docs/docs/guides/valkyrai-workflow-troubleshooting.md
✅ /docs/docs/guides/mcp-publishing-troubleshooting.md
✅ /docs/docs/guides/gridheim-troubleshooting.md

Total: 8 documents
Changes: 8 frontmatter updates
Status: ✅ Complete


Tufte Principles Embodied

PrincipleHow Applied
Minimize ink4 top-level categories instead of 12+
Maximize dataNested hierarchy conveys expertise level
Reduce cognitive loadBeginners see 1 open section; experts expand others
Clear hierarchyStart → Build → Reference → Support = user journey
SemanticsLabels + tags + positioning all reinforce intent
SpecificityNo generic "Guide" or "Tutorial"; everything is product + action
Progressive disclosureQuick Guides open, Build/Reference collapsed (low friction entry)

Next Steps

  1. Frontmatter standardized - All guides aligned with new sidebar
  2. Content audit complete - All tags consistent, titles clear
  3. ⏭️ Test Docusaurus build - Run yarn build to verify compilation
  4. ⏭️ Visual inspection - Check sidebar render order and nesting
  5. ⏭️ Link validation - Verify internal cross-references work
  6. ⏭️ Search verification - Test tag filtering and search discover

Status: 🎯 Documentation Architecture Complete
Ready for: Docusaurus build testing