Documentation website

A documentation website is a structured knowledge base for your product: guides, instructions, a reference, architecture descriptions, code samples. On the left there is a navigation tree, at the top a search; articles have a table of contents and links between them; you can maintain several documentation versions. It is broader than a help center (which has short answer articles for user support, see the “Help Center” service) and broader than API documentation (which only describes endpoints, see the “API documentation” service): documentation is about how the product works and how to use it, as a whole. Ready engines (Docusaurus, GitBook, MkDocs) suit standard documentation; your own site is needed when documentation must be an inseparable part of the product — single sign-on with the product, per-article analytics, integration with support and CRM, your own brand without a third-party logo and without a monthly fee. The base price starts from 100,000 ₽ for a starter structure with search and a one-time content migration; versions, multiple languages and complex integrations are estimated separately.

• Documentation is scattered across PDFs, Notion and Google Docs — users cannot find what they need and write to support.
• Support answers the same questions — there is no single base with search.
• Documentation becomes outdated: there are no versions, and it is unclear what is current for which product version.
• The current docs look foreign — without your brand and convenient navigation.

• Structure: navigation tree, sidebar, article table of contents, breadcrumbs
• Content: guides, instructions, reference, code samples with highlighting and copy
• Search across all documentation — fast, with suggestions
• Documentation versions: several product versions in parallel (optional)
• Convenient content editing: markdown or an admin, edits without layout
• Responsive, dark theme, fast loading; links between articles
• SEO foundation: articles get indexed and bring traffic from search
• Integrations: feedback on articles, analytics, multiple languages (optional)

• Users and developers find answers themselves — fewer support requests
• A single knowledge base with search instead of scattered files
• Several documentation versions — everyone knows what is current for their product version
• Documentation under your brand, indexed and bringing traffic from search

• You leave a request and describe the product, structure and documentation versions
• We design the structure, navigation, search and content workflow
• We develop, migrate materials and launch

• How is a documentation website different from a help center and API documentation?

  A documentation website is the product as a whole: guides, instructions, reference, architecture, code samples. A help center has short answer articles for user support (how to use it, what to do when there is a problem). API documentation only describes endpoints for developers. They are often part of one portal, but these are different formats and a different scope.

• How is your own site better than ready engines (Docusaurus, GitBook)?

  Ready engines are fast and cheap for standard documentation — often enough. Your own site is needed when documentation must be an inseparable part of the product: single sign-on with the product, per-article analytics, integration with support and CRM, a non-standard UX, your own brand without a third-party logo and without a monthly fee.

• How much does it cost and what does the price depend on?

  The base price starts from 100,000 ₽ for a starter structure with search and a one-time content migration. Several versions, multiple languages, complex integrations and large migrations are estimated separately. We calculate it after you describe the task.