Git and markdown language migration

[Colin Colwell]

My team is evaluating CMS solutions. We're currently publishing docs from Github where we write in markdown language - aka docs-as-code model.

Has anyone gone through this process?

How did you go about migrating your repositories and getting a clean start in Confluence?

I've been looking & looking online and see little to no information on this process.

thanks

[Bill Bailey · Accepted solution]

Well you are going to have a really hard time with the Cloud version. It has a lot of reduced functiionality and access versus the server version.

I have overseen projects to move content from MediWiki into Confluence. There is some code base out there, but it does require customization to handle special structures in the source to map to something equivelent in Confluence (often means creating a number of user macros, and a lot of Python scripting).

Similar to your model, we do push some software documentation stored in Perforce with markdown that writes to Confluence pages (again Python scripting and testing). The script is run on a daily basis to check for changes.

[Colin Colwell]

Thanks!

Confluence is only one option, and easy since other teams at the company use it, so it's essentially free for us. However, other tools certainly play much better with Git, so we're evaluating several options.