Frequently asked questions

Docks is a small library for building documentation surfaces — sidebars, article layouts, search, code blocks — without wiring them together yourself. It ships as a single package with no runtime dependencies.

No. Docks works from a CDN script tag as well as from a bundler. The CDN build is the same code, pre-bundled — you lose tree-shaking and nothing else.

The last two versions of Chrome, Edge, Firefox and Safari. Docks uses IntersectionObserver and CSS custom properties, so anything older needs a polyfill.

Yes — everything visual is driven by tokens. Override the token values once and every component follows, including the ones you register yourself.

See the Theming guide for the full token list and the precedence rules between light, dark and explicit overrides.

Register your own under the same name. The built-in is replaced for that instance only, and the rest of the system keeps working because the contract is the props, not the implementation.

Usually. Docks scopes its styles to the instance root, so conflicts only arise when a global rule has higher specificity. Loading the Docks stylesheet last resolves almost every case.

Search runs entirely on the client against an index built at load time. Titles and headings are weighted above body copy, and results collapse to one row per document.

Both ship as layouts in the starter set. They read from your own content source, so adding an entry or a question is a content change rather than a code change.

Yes. Docks does not own your content — it renders whatever you hand it. Markdown, a CMS, or a plain array of objects all work the same way.

Open an issue with the version, the options you passed, and the smallest markup that reproduces the problem. A minimal reproduction is almost always enough to identify the cause.

Community support is available through the issue tracker and is where most questions get answered. Response times are best-effort rather than guaranteed.