Docsloth / developers
Self-hostStart quickstart

docsloth.dev

Templates

A template sets the default audience, page set and component allowlist. It is a starting point you edit, not a closed theme. Preview a preset to see exactly which pages and components it keeps — the lists below come from the planner that applies them.

Developer portal

Reference, quickstart, recipes and API console for integrating developers.

Default audience: integrating-developer

Preview preset (5 pages)

Pages

OverviewQuickstartReferenceRecipesAPI console

Component allowlist

api-consolecode-diffschema-explorergraph

Consumer help

Task-first installation and troubleshooting in nontechnical language.

Default audience: end-user

Preview preset (3 pages)

Pages

Getting startedHow-to guidesTroubleshooting

Component allowlist

media-transcriptwizard

API reference

Schema-driven reference with executable examples bound to a capability.

Default audience: api-consumer

Preview preset (3 pages)

Pages

OverviewEndpointsSchemas

Component allowlist

api-consoleschema-explorercode-diff

Operations runbooks

Service graph, on-call procedures and rollback steps with evidence links.

Default audience: on-call-engineer

Preview preset (4 pages)

Pages

Service overviewRunbooksRollbackEvidence

Component allowlist

graphlogsmetrics

Executable tutorials

Step verification inside an approved sandbox, recorded per step.

Default audience: learning-developer

Preview preset (3 pages)

Pages

OverviewTutorialVerification

Component allowlist

code-diffwebhook-debugger

Custom interface

No filtering: compose any page set from the document program and component catalogue.

Default audience: integrating-developer

Preview preset (0 pages)

Pages

Any page set

Component allowlist

No component filtering

What every template keeps

  • Evidence links on every generated claim, and owner-source marking where code cannot establish a fact.
  • Protected human writing under company/* and legal/* that auto-update cannot overwrite.
  • Accessibility checks and non-JavaScript reading for public pages.

Actions

Actions

  • Preview

    Expands a preset above to show the exact page set and component allowlist from the planner that applies it; all data is local and static.

  • Remix

    Presets are applied by the planner during onboarding, not by a one-click endpoint; the preview flow is free to start and nothing is published without review.