Doqs documentation

Add Markdown documentation to an existing Angular and Analog application in a few minutes.

Packages, peer dependencies and the supported environment for @doqs/analog.

doq init scaffolds the documentation files; doq doctor diagnoses the integration.

The four places a Doqs integration touches — paths, Vite, Angular providers and the stylesheet.

Mount Doqs under /docs in a product site that keeps its own landing page and routes.

Make the whole application documentation by mounting Doqs at the root.

Frontmatter, groups, ordering, nested folders and slugs.

Callouts, tabs, code groups, steps and titled code in plain Markdown.

Place your own standalone Angular components between Markdown paragraphs.

Sidebar, table of contents, focus handling and optional static full-text search with Pagefind.

Keep the documentation of older releases readable at stable URLs.

Generate reference pages from your library's public TypeScript API with doq-api.

Restyle Doqs with --host-docs-* tokens, layout options and host-owned slots, without a second theme system.

Why doqDeterministicMarkdown() exists, how to add it and how to verify heading ids.

Build a static documentation site, index it for search and run checks in CI.

Common integration problems and the doq doctor findings that point to them.

What has been verified, what has not, and how upgrades behave.

The exports, binaries and styles of @doqs/analog, with their intended stability.