| Founder of https://www.cacher.io here. Cacher was built for the express purpose of team knowledge sharing via code snippets and Markdown docs. It has also been successfully scaled out to teams of dozens, with a few customers rolling out to hundreds of members. We believe successful knowledge sharing comes down to several parts: 1) Organization via categorization. While retrieving knowledge, labels/tags are an important heuristic shortcut. We often have trouble remembering but details but can usually recall the purpose of the piece of knowledge. 2) Integration with existing tools. People hate changing their workflows. We've found that engineers who are used to coding in VSCode or IntelliJ would rather not leave their editor to retrieve snippets. The context switching is just too expensive. Cacher is integrated with major editors/IDEs for this reason. 3) The ability to keep other team members updated on progress and changes. A proper knowledge system uses notifications judiciously to keep everyone on the same page. Cacher does this via customizable desktop/email/Slack notifications. 4) A professional understanding of the knowledge workflow. It is important, regardless of which tool you adopt, to come to a consensus on how the knowledge will be used. Marketing and e-commerce teams use us to store HTML/CSS with the intent of creating a large library of components and patterns. Technical support teams create snippets for remembering how to update a user's billing account. Before settling on a tool, consider what kind of knowledge is important day-to-day and agree as a group on how you'd like to retrieve it. I hope that helps! If you're team is looking to try it out and would like thoughts on how to set up an adoptable workflow, feel free to ping me: rui[at]cacher.io |