In “GitHub for the rest of us” I argued that GitHub’s superpowers could serve everyone, not just coders. Ever since then (2015) I’ve felt that I overstated the case. GitHub was, and remains, a tool that is deeply optimized for programmers who create and review versioned source code. Other uses are possible but awkward, and the tools that I thought could make GitHub friendlier to non-coders mostly haven’t arrived.
Recently, though, I’ve been revisiting what GitHub can do for non-coders. As I’ve helped colleagues write blog posts and documentation I’ve been reflecting on my editing process and reaching for tools that can help me narrate the principles that guide it.
