Shared code tabs audit
2026-09-15
The documentation already depended on Dockit, but several pages still imported an older local tab component. The final integration includes Dockit 0.2.25 and the 0.1.18 docs styling release. Three parallel work batches audited Hosts, other public guides, and developer documentation. This pass converts 22 pages and removes the unused local component. Existing standalone examples remain visible when they describe sequential steps, inputs/results, or different workflows.
Task list
- Audit existing tab imports and alternative fenced examples.
- Convert host enrollment, credentials and private-run examples.
- Convert public installation, Notes, relay, provider and access alternatives.
- Convert developer plans and recovery examples; replace unsupported
labelsusage. - Remove the legacy local tab component.
- Check that all 181 original fences in the changed pages remain unchanged and ordered.
- Build and verify HTML, Markdown exports and representative browser interactions.
- Regenerate and commit agent references.
- Merge all work before the single production deployment (see PR receipt).
- Verify the deployed enrollment page and representative code tabs (see PR receipt).
Merge and deployment receipts are recorded on the pull request; check those receipts for the completed delivery state.
Changed pages
The existing host testing guide already used Dockit's shared tabs. The remote-agent setup guide stays sequential. Public pages were reviewed beyond the changed list: schemas and responses, source/CLI differences, provider-specific workflows, and independent tutorial steps were not collapsed into tabs.
Validation
The static/rendered audit passed for 23 pages, 54 groups and 110 panels. Browser checks passed for enrollment, credentials, Notes, provider registration and a developer plan: language switching, Home navigation, copy feedback, and a 390px viewport without page overflow. The Markdown regression suite protects code placeholders, literal imports/JSX, whitespace, Callouts, fence markers and links inside code. Tab labels are retained in exported Markdown.
Run node docs/scripts/check-shared-code-tabs.mjs for import/API/panel checks. After pnpm build, add --built to verify every tabbed page's HTML group count and that all fenced examples remain in public Markdown exports (noindex developer pages intentionally have none). The check covers existing and newly converted groups, including hidden developer pages.
Browser checks cover the enrollment page, credentials, Notes, provider registration and a developer plan. Verify click and arrow/Home/End navigation, one visible panel, copy and line-number controls, and narrow-screen layout. Tabs must not execute the documented commands.