Don't Use Confluence for Technical Documentation

[@adrianmorse9252]

Good video. I would add that the Confluence restriction of having to use unique page titles is also a major obstacle (e.g you can only have one page called "Overview" in your entire documentation set). You end up with prefixes/suffixes that make it hard to read and navigate.

[@OutOfDevOps]

Good point!

[@DillPickl3s]

Have you used Nuclino? If so, would you recommend it for technical documentation?

[@trigramTransformation]

While I agree with the challenge to tightly couple documentation to versions you solve 1 problem with Git you create many more, how do you search across releases and branches to find the right documentation or changes. I'd also agree that some documentation can be split across both tools however I would suggest that with labelling and tagging Confluence can be tied to releases and be a better source of *knowledge management*. Further confluence pages with the associated list of stories or epic will quickly add value to explain the status of release delivery, owners and changes made. Very specific technical documents like a release doc with upgrade scripts or instructions indeed should be in git

[@OutOfDevOps]

Hi thanks for your comment. If you look at the title of the video is saying exactly that.

[@arcangeloguerriero8206]

❤