Skip to main content
tinymash
  • Screen mode

DocsMatter

DocsMatter is built for manuals, reference sites, knowledge bases, and page-led author spaces. Its fixed documentation shell gives the page tree priority over a conventional blogroll.

Page structure

Published pages form the sidebar tree. Nested pages remain nested, and the current page and its ancestors are identified in the tree. When a separate leaf page is opened, the last active branch stays expanded for the rest of that browser tab. Opening another branch replaces it. On narrow screens, the same navigation moves into the Browse panel.

Full pages can show an On this page list generated from authored headings. Headings inside plugin-owned components are excluded. Previous, home, and next controls follow the page structure.

The root or an author space can select a published documentation home page. Opening the section then redirects to that page. With no selected home page, DocsMatter shows the available top-level sections.

Author spaces and posts

An author space that explicitly selects DocsMatter remains page-led. An author space that merely inherits DocsMatter can fall back to its paginated posts when it has no usable landing page or published pages.

The fallback lets a site-wide DocsMatter installation contain an author blog without turning every documentation space into a blog.

Settings

DocsMatter includes:

  • header, sidebar, or hidden primary navigation
  • a footer menu below the sidebar
  • content width, with author-space override
  • a documentation home page, with author-space override
  • public Search, tags, and local syntax highlighting
  • child-page lists after page content

Inline code uses the prose font size and authored spacing. Fenced code blocks keep their contained, scrollable treatment.

Media and public regions

DocsMatter does not render site or author banners and does not use public background images. Its stable header, sidebar, and reading surfaces form the documentation shell.

Public plugin output remains available in supported content and sidebar/footer regions. Component headings do not become page-table-of-contents entries.