Reconnecting…
Waiting for the connection. It is taking a while. Reload the page
This page hit a problem
It is reconnecting and will carry on from where it was.
Knowledge base
Pages of documentation, how-tos, runbooks, decisions and meeting notes, in spaces for the workspace and for every project, written in Markdown with every version kept. A ticket key in a page links the ticket and the ticket lists the page; published pages answer customers before they ask; and a space can be the documentation folder of a Git repository, read here with every push.
Workspace spaces with grants of their own, project spaces that follow the project's roles, and personal spaces, each with a tree of pages and folders that you reorder by dragging.
In the guide →Pages with a preview, images pasted or dropped into the text, files kept with the page, labels, drafts until you publish, and a note on what changed with every save.
In the guide →The history lists who saved what and when. Compare any two versions line by line and restore an earlier one, which is saved as a new version, so nothing is lost.
In the guide →Threads under the page, and inline comments on the words you select, marked in the text, resolved when done, and kept even when the passage leaves the page.
In the guide →View restrictions that apply to a page and everything below it, and edit restrictions on a page alone. A page you may not read appears nowhere, not even in search.
In the guide →Pages are found by title, headings, labels and words from the header's search box and the search page, with the passage the words were found in, whatever they were written in.
In the guide →The knowledge base and the tickets know about each other. A ticket key in a page is a link for anyone who may see the ticket, and plain text for everyone else; a ticket lists the pages that mention it; a resolved ticket can be written up as a page in one step. Published pages reach customers in the portal and on request forms.
Name a GitHub or GitLab repository, a branch and a folder. Its Markdown files become pages, in the tree the tool's navigation gives them, and every push brings the change across; nothing is edited here, and Edit on GitHub opens the file there.
In the guide →A space or site export brings every page in every version, folders, blog posts, comments, files, labels, restrictions and the addresses pages had, verified against the export.
In the guide →A ZIP of Markdown or HTML from any documentation tool becomes a space, in the tree the tool showed it in and with its links and images working.
In the guide →Every module is in every workspace, at one price per seat. A workspace takes a couple of minutes and asks for no card; an installation is one container image and a compose file.