I like how you made your point on the deficiencies of Confluence in supporting development process. You are definitely right. What I have noticed over more than a decade of development is that there is hardly ever a culture of documenting software. Documentation is seen as a cost most of times but hardly ever as an investment. Talking about long-term investments like company products or services. If it was an investment, companies would invest in making sure their staff know how to document, first of all. It requires skill! Also, it is industry who collectively tried to instil a false conviction that code does not need to be documented - it is enough when it is written clearly. That is one big lie tough. You may write code so it reads well, but it will not document the business intention (there are many levels of that), assumptions, issues, dependencies and gaps developers were fighting with which predetermined their ways of thinking. Documentation is not a free lunch and many junior developers are shocked these days when they are asked to write a piece. Very often they do not even know where to start (tooling, style, format) since there is no culture at all - only ad-hoc need. They do not know what to focus on and what is truly expressed in the code. It is like being thrown in the deep ocean and told to learn to swim.