About Nexus Docs

Nexus Docs is an open-source documentation system built by Qoliber and Jakub Winkler.

It started as a practical need: we wanted a documentation portal that could be public where it should be public, private where it should be private, and still feel like a normal developer-friendly Markdown workflow.

Authors

Qoliber

Qoliber builds e-commerce tools, Magento modules, infrastructure helpers, and internal systems that need serious documentation without turning docs into a separate SaaS dependency.

Nexus Docs is part of that philosophy: own the stack, keep the content in git, and make the documentation experience fit the product instead of forcing the product into somebody else's documentation shape.

Jakub Winkler

Jakub Winkler created Nexus Docs as a pragmatic answer to a recurring problem: every existing option solved part of the documentation workflow, but not the whole thing we needed.

The goal is not to compete with every docs tool. The goal is to make a focused, self-hostable system for teams that need Markdown, access control, search, automation, and full UI ownership in one place.

But why?

We wanted a documentation system that is:

• Open source
• Built around Markdown files
• Able to control access per page and per product
• Flexible enough for public docs and gated customer docs
• Fully under our design control
• Pleasant and fun to use

We tried Wiki.js, MkDocs, Docusaurus, and VitePress. They are useful tools, but none of them gave us the full combination we needed without awkward tradeoffs.

What was missing

Need	Why it mattered
Markdown-first content	Docs should stay reviewable in git and easy to edit.
Access control	Some docs are public, some are customer-only, some are partner-only.
Product permissions	A user should see docs for products they actually have access to.
Full design control	The documentation UI should match the product and brand, not just a theme preset.
Automation hooks	GitLab, search indexing, access grants, and feedback should be part of the system.
Open-source ownership	The stack should be inspectable, forkable, and self-hostable.

The result

Nexus Docs is intentionally built as an application, not just a static site generator.

That means it can combine:

• File-based docs under content/
• MDX rendering and custom components
• Tier and permission checks
• Search filtering
• GitLab automation
• API-driven access grants
• Admin workflows
• SEO-ready public pages

The system is still simple where it should be simple: write Markdown, commit it, and publish it. The application layer exists for the parts that static docs tools usually struggle with.