jookyboi

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

The initial results for my search queries look pretty good. Looking forward to having StackOverflow integrate this into their API.

Would be a great workflow to explore for our app: https://www.cacher.io

For a code-snippet focused alternative with plugins for major editors and support for team libraries: https://www.cacher.io

Not true. With expanded permissions (like access to all browser tabs), you will be subject to a full code review. I've had to wait anywhere from 2-5 business days before a draft extension was allowed to be published.

I learned design + frontend engineering together. My side project turned into my full-time startup: https://www.cacher.io

The best advice I can give in terms of managing UX:

0. Get Sketch (https://www.sketchapp.com) and use one of its UI kits (https://www.sketchappsources.com) to lay out your designs. While you should pay attention to visual details, you won't need to lay out every state since you won't be showing these to anyone else.

1. Build your project with one of the established frameworks (Material is pretty good). This will give you a sense of visual hierarchy and force you to think about why elements are placed where they are.

2. Introduce your own modifications and controls as needed. Even with a framework, you'll eventually come across a use-case that isn't readily handled.

3. Keep your modified framework in its own folder/repo. Continually update it as visual standards/technologies change. Doing this will cut down on the amount of re-work necessary when you're starting new projects.

Might want to check out cacher.io for a team-based app that integrates with VSCode, Atom and Sublime.

For a more robust team snippet organizer: https://www.cacher.io

Nice work. Happy to see a competitor in the space.

For a fully-managed option with desktop clients and integrations with VSCode, Atom and Sublime, check out Cacher: https://www.cacher.io