|
|
|
|
|
|
by bitschubser_
1622 days ago
|
|
|
In my old (and soon current again) shop we used confluence extensively, to get the best from both worlds we usually kept the documentation next to the code in markdown or asciidoc files and synchronized them to confluence in a CI/CD pipeline (confluence was read only for these sections) maybe I can open source these helpers when I'm back... a two way merge was also in the making :). we could sync whole file trees with automatic link crosslink generation, asset management and versioning support in confluence |
|
|
I once found a plug-in that did almost the same, allowed Confluence to read and render markdown files directly from (private) GitHub repos thus allowing me to get the best of both worlds!
- docs stays in the repo (thus is much more likely to actually get updated)
- docs get exposed in Confluence (thus is accessible for the business folks that does not do git)
- docs are easy to update (as you can use any editor: vi, emacs, IDE’s etc)
So conceptually the same as you’re solution ;-)
Unfortunately we did not implement the plug-in as we have too many eggs in the Jira basket (+1.000 users) which have the unfortunate side effect that the licensing price is derived from the +1000 users even though only the much lower number of devs would use it.
That is one repeated problem we face in the Atlassian stack (well a source of their income…)- even a seemingly cheap plugin (extension or whatever they’re called) ends up in the person suggesting how to ‘work smart/not hard’ having to find the funding typically a two digit thousands of € or year (thus I never bother with that anymore :(