Post #2969395
2026-05-06 21:16 UTC
@kouhai@social.treehouse.systems @cb@social.treehouse.systems and also the chance that people get frustrated by how long it takes to make docs PRs, so they decide not to do it again next time
Replies (1)
-
@cb@social.treehouse.systems 2026-05-07 14:34
@jyn@tech.lgbt so what i was thinking of is, i noticed a few projects moving away from separate wikis and towards documentation stored in i.e. git, explicitly because of the PR/review workflow, but also because of atomic multi-file commits (currently wiki engines are cvs history for one file at a time). but that wiki workflow is a lot nicer for non-programmers as you know (you know, working wysiwyg, can do it from a browser, etc) i think what'd be interesting is reconciling that workflow with a PR based git workflow. stuff like word has a concept of inline review comments and i.e. track changes, it's "just" a matter of making them work together