Your repo docs, as real Confluence pages

Repo Docs turns the markdown in a GitHub repository into ordinary Confluence pages, in the space you choose, and keeps them up to date.

Why not just embed them?

Because embedded content is not indexed. Every other way of getting markdown into Confluence renders it inside a macro, and Confluence search cannot see inside a macro. You move your documentation in, then cannot find it, which is the one thing Confluence is for.

Repo Docs makes pages. Real ones. They are indexed, they can be linked and commented on, they respect your space permissions, and they show up in search like everything else.

What it does

Real, searchable pages

Not a macro. Search finds the words inside your documents.

Your folder tree, kept

Folders become parent pages, so the shape of the repository survives.

Titles from your headings

The first # heading becomes the page title, not the file name.

Private repositories

Add a GitHub token and it reads private repos. The token is stored as a secret and never shown again.

Hourly sync

Switch it on and the pages follow the repository without anyone clicking anything.

Safe to run twice

A second run updates the same pages. It never makes duplicates.

It cannot delete your pages

Repo Docs does not hold the permission to delete anything, by design. When a file leaves your repository it tells you which page has nothing behind it any more, and leaves the page alone for you to decide about. A tool that writes into your company wiki should not also be able to empty it.

Price

$1.50 per user per month

Free for sites of up to 10 users.

Billed by Atlassian with the rest of your apps.