Effective Practices To Create and Document Project Knowledge

I don't necessarily have a good answer to to this, but I will note that I'm working my way through this very problem on my current project. As I gather information and begin creating things like Mission Statements, Scope Statements, Quality Requirements, Constraint Documents, and even Design Solution ideas, and as the number of Stakeholders seems to grow every week, I'm scrambling to find a way to capture a "common" understanding of the project. Our organization has been using Atlassian products in recent years (primarily Jira), and Confluence is becoming a more popular tool some of us are using. I just took an informal intro course on Confluence and it seems like a reasonable solution, but I'll know more as the rubber continues to hit the road in the coming weeks....