Confluence alternative

What documentation looks like in Skillok#

• A section is a folder, a page is a markdown file. The README in the root of the repository is shown on its main page — a handy table of contents.
• Markup: headings, tables, task lists, > [!NOTE] callouts, formulas, Mermaid diagrams, code with syntax highlighting, links between pages.
• Edit right in the browser, or locally in any editor and push the changes with git.
• Every page has a full history: who changed what and when, and you can open any earlier version.

Reviewing documentation#

An important change — a policy, an architecture decision, a guide for customers — does not have to go live at once. Propose it as a pull request. Colleagues leave comments, approve or request changes, and only then does the text land in the main branch. A CODEOWNERS file assigns the people responsible for each section.

Access#

Keep your team's documentation in a private organization repository. Access is granted to teams and people with roles: read only, triage, write, maintain. Public documentation goes into a public repository.

What is missing#

• a visual page editor with macros and embedded blocks;
• real-time co-editing of a single page;
• inline comments on a line of text in the interface;
• search through the contents of documents — only search for a file by name inside a repository;
• import of Confluence spaces.

How to move over#

Export your pages from Confluence in whatever format is available to you and save them as markdown — with a converter, or by hand for the key pages. Sort them into folders, upload them to a repository and check the links between pages. A move is also a good excuse to throw out what is out of date. If you are building the structure from scratch, see how to set up a company knowledge base.

Who it suits#

Technical teams that already write in markdown, and companies where documentation has to change in the open — with history and sign-off.

Was this helpful?

Yes No