Public documentation

Serving files from a private git repository on a public Confluence space

Here's a typical use case that we see a lot. Confluence can be used to share content with anonymous users, i.e. the content will be publicly available.

Examples of this kind of content could be:

• a publicly available roadmap

• an open knowledge base

• support documentation

Source code

Let's say you need to reference source code in your documentation that you have readily available in a Git repository. You can easily share this in your public space, and as a bonus, the source code will always be up to date! You can just push out updates, git commit them and your new version will be available.

UML diagrams

Your roadmap may contain design diagrams to explain about an upcoming feature. That design may already be available as a PlantUML file in your Git repository. Git for Confluence can render that PlantUML file and show it inside Confluence. PlantUML file gets updated? Boom, your image will update as a result. Always up to date.

Downloadable assets

We hear a lot of customers want to make files from Git available for download. The problem? The Git repository is the single source of truth, but often secured and therefor the content is not publicly available for download. As a result assets get copied to other places for download, often resulting in outdated content.

With Git for Confluence you can easily share assets on a public page in Confluence without that content ever getting out of date. A deployment package you want to publish to the world? Share it on a Confluence page and it will always automatically be the latest version.

You have marketing assets that get updated all the time that you want to share with your partner network. Just put them on a page in Confluence and just worry about the content in Git from that point on

Want to know more about public spaces in Confluence, refer to the Confluence documentation about sharing a space.