Ask HN: How does your engineering team manage knowledge?

I've been thinking recently about how my team manages knowledge. The 5 of us keep engineering notebooks committed in git, but we also try to maintain a wiki. There's also a ton of information lost in git commits, jira comments, javadocs, readmes, etc.

Our main method of sharing information has become Q&A in slack. I encourage communication, but a lot of questions are purely from information loss during development.

some generic examples: "I ran project X with <query> and received error Y. Has anyone seen this error before?" "Where is system Z deployed?" "The search algorithm for system Z should return I, but I think it should return K. Where can i find background on the algorithm's development?"

I've considered something like a private stack overflow, but I don't think we'd gain anything without some sort of smart plugin for our notebooks and code.

Are other teams experiencing this? We have a PM for external information sharing, and I'm the tech/team lead. I feel like if we could optimize some of this information sharing, the team would work more efficiently.

* How are you guys documenting what you learn in development? * Who is responsible for documenting? * How do you keep track of it, manage it, and search it efficiently?