Documentation

A documentation page: a divided title and summary over sectioned body content.

Navigation that closes a page by linking the reader onward to the next page or to related pages.

Search across the documentation, opened from the page header.

An on-page outline of the article's headings that marks the section the reader is in.

A side-by-side comparison of the recommended approach and the one to avoid.

What the reader needs in place before starting a guide.

A comprehension check placed after a concept, with immediate feedback and a retry path.

A numbered procedure that walks the reader through a task one action at a time.

A term inside prose that reveals its definition without leaving the page.

A prompt at the end of a page that asks whether it helped and collects a follow-up.

Actions on the current page: copy it as Markdown, share it, open its source, or hand it to an AI assistant.

Collects a page's headings with stable slug ids and nests them into the tree a table of contents renders.

A scroll-spy hook that reports which heading the reader is on, for marking the current item in a table of contents.

Teaches an agent to assemble a product documentation page from this package's components, choosing each element by the job it does.

Teaches an agent to write a documentation article of the right type — tutorial, guide, reference, or concept — structured for the elements that will display it.

The landing page of a documentation site: a search field over a grid of entry cards, one per area of the docs.

A complete documentation page: section navigation, the article with its table of contents, and a footer that pages onward and asks for feedback.