Idea
GitHub for documents: branch, fork, and merge knowledge work
Maples describes his portfolio company Almanac as bringing GitHub-style collaboration to documents. Just as GitHub made code social and Figma did it for design, document tools should let teams branch, fork, merge, and track every version, including when a forked employee handbook gets reused elsewhere.
“Why shouldn't you, just like GitHub, be able to branch and merge and fork documents and be able to, within that one document, know every version of that document that ever existed and everybody's— and if somebody forks it and uses it, let's say it's an employee handbook, if somebody uses it for their next company, why not want to know that as well?”
Steal thisApply the GitHub branch/fork/merge model to a category of knowledge work that still ships static files around.
mfmindex.com№ 0191-775