mtbarta

It's a good callout.

Analysts typically don't know git. This would be a solution that allows analysts to work in a git repo while customized for their own workflow.

the open source version is available if you want to use it immediately. There's no team functionality, however.

I'm hoping to get a more fully-featured product out in a few months.

Sorry about that! I jammed several gifs and a video into the template without thinking about responsiveness. I know on Macs the video below the about section doesn't seem to play.

I'll look at it asap.

Not all notes belong in shared source code. I take notes on overall code structure and oddities, but also debug output, commands I've run, daily todos, thoughts on papers, experimental results, etc.

I used to save markdown files to git, but 1.) search was difficult and 2.) sometimes I wanted to see the evolution of a project while other times I wanted notes by day.

This project aims to make it easier to record and recall knowledge that teams need and take for granted. I tend to think about onboarding new members, how projects are run, and very specific, technical challenges not on Stack Overflow.

I'm open to feedback. I want to continue to push down a wiki/knowledge base path, but i'm not sure how other teams currently manage stale knowledge and dissemination of technical info.