Context
The current top-level docs navigation has Build and Core Concepts. The content under Core Concepts has contents beyond introductory concept material: it now includes protocol documentation, VM docs, node docs, compiler docs, and soon likely miden-standards reference material.
That section is closer to a technical reference surface than a beginner-facing concepts section.
Recommendation
Rename Core Concepts to Reference.
This is shorter than Technical Reference, but broader and less formal than Specs. It can comfortably contain:
- Protocol reference
- Standards reference
- Miden VM reference
- Node reference
- Compiler reference
- Architecture pages that explain how the system works
Why not "Specs"?
"Specs" is concise, but it may be too narrow and too formal for the current content mix. It implies normative protocol specifications only, while this section also contains explanatory architecture docs, implementation-facing VM/compiler/node docs, and reference pages that are not always written as formal specs.
A shorter Reference label keeps the section professional and scannable without overpromising that every page is a formal specification.
Scope
- Rename the top-level nav label from Core Concepts to Reference.
- Update sidebar comments, landing page copy, and any internal references that describe this section as Core Concepts.
- Preserve existing URLs unless there is a separate decision to migrate paths. Avoid creating unnecessary redirect churn.
- Ensure versioned docs are handled consistently if the visible label appears there.
- Keep Build as the task-oriented section for tutorials and working examples.
Out of scope
- Moving standards content itself.
- Restructuring protocol, VM, node, or compiler docs beyond the naming update.
- Changing URL paths from
/core-concepts/... unless separately approved.
Context
The current top-level docs navigation has Build and Core Concepts. The content under Core Concepts has contents beyond introductory concept material: it now includes protocol documentation, VM docs, node docs, compiler docs, and soon likely
miden-standardsreference material.That section is closer to a technical reference surface than a beginner-facing concepts section.
Recommendation
Rename Core Concepts to Reference.
This is shorter than Technical Reference, but broader and less formal than Specs. It can comfortably contain:
Why not "Specs"?
"Specs" is concise, but it may be too narrow and too formal for the current content mix. It implies normative protocol specifications only, while this section also contains explanatory architecture docs, implementation-facing VM/compiler/node docs, and reference pages that are not always written as formal specs.
A shorter Reference label keeps the section professional and scannable without overpromising that every page is a formal specification.
Scope
Out of scope
/core-concepts/...unless separately approved.