Every edit waits for an engineer
The docs live in a code repository, so a one-line fix needs someone who knows Git.
For product managers and writers
Product managers and writers work in a visual editor; engineers can stay in GitHub. Preview every change, publish versioned docs with your branding, and keep translations in step.

The docs live in a code repository, so a one-line fix needs someone who knows Git.
Customers on older versions read pages written for the newest one.
The English page changes and the other languages quietly fall out of date.
Editor
Type / to add callouts, steps, tabs, cards, tables, code and images. Pages are still stored as Markdown, so nothing is locked in.


Previews and versions
Preview changes privately, publish when ready, and keep separate docs for each product version. Every publish is a snapshot you can roll back to.
Themes
Pick one of three reader layouts, Harbor, Manuscript or Signal, and add your logo, colors and custom domain.
Availability: Available on Nibleaf Cloud, and when you self-host v0.2.1 or later.

Languages
Each language has its own page tree, and translated pages are linked so readers and search engines find the right one.
Requirements: Self-hosters turn it on first; it is off by default. Available on Nibleaf Cloud, and when you self-host v0.2.1 or later.


Start in the visual editor, or import a public Mintlify repository from GitHub.
Teammates comment on the text, or engineers review the change as a GitHub pull request.
Check the change privately before readers see it.
Publish for the right product version and language. Roll back to an earlier publish if you need to.
No. They write in the visual editor and publish from the browser. Pages are stored as Markdown behind the scenes, and engineers can use GitHub if they prefer.
GitHub syncs both ways, with a dedicated branch, pull requests and previews. Public GitLab and other Git repositories can be imported one way.
Nibleaf doesn’t offer live co-editing with shared cursors today. Teams use review comments, previews and GitHub pull requests to work together.
Each language has its own page tree, and you link a page to its translations. Nibleaf doesn’t machine-translate pages itself; your AI assistant can draft a translation through MCP for you to review.
Yes. Invite readers to private docs, or to single pages, separately from your dashboard team. This is not SAML or SCIM single sign-on.
Start free on Nibleaf Cloud, or run it on your own servers.