Organize documentation into roots, folders and articles
Version 0.7.16Create multiple documentation roots, organize folders without placeholder articles and keep every article visible in the editor and published navigation.
Added
Create multiple documentation roots.
The top navigation switches between published documentation roots; the sidebar shows the selected root's folders and articles.
Organize folders without placeholder articles.
Create empty groups or folders, add several articles to the same folder, and keep all of them selectable in the editor.
Improved
Protect edits when changing articles.
The editor saves before switching; a failed save keeps the current input available for retry.
Move, copy and recover documentation more safely.
Copies retain article content and SEO as drafts. Folder recovery respects deletion batches and preserves earlier publication history.
Release notes
LitPage 0.7.16 gives documentation a clearer structure: roots at the top, folders and articles on the left, and the current article's outline on the right.
Separate different documentation areas
Create separate roots for areas such as Guides, Reference and Help. Readers switch between them through the top documentation navigation. Each root leads to a real published article: its overview when available, or an accessible published article below it.
Empty roots and unpublished articles do not become public navigation destinations. The article sidebar shows the selected root's content rather than mixing every documentation area together.
Put several articles in one folder
In the Builder, create a root, add groups or folders, and place multiple articles in the same location. A folder does not need a placeholder article just to exist. Every article remains visible and selectable.
Roots have a language, and documents inherit their root's language. Public navigation separates language versions; translations still need to be authored.
Edit and reorganize with clearer safeguards
The editor gives the article body more space and separates document settings from SEO settings. It saves before switching to another article. If saving fails, your current input stays available so you can retry before leaving.
Move, copy, recycle and restore documentation through the existing controls. Copies preserve the source content and SEO as drafts, and folder recovery avoids restoring articles that had already been deleted separately.
Availability
Documentation organization is available in the web Builder. The expanded CLI workflow for root, parent and Markdown document templates is not yet included in a publicly released npm package. MCP publishing is still planned.
See Documentation sites for agents and the published documentation center.