Now instead of a database I have a folder full of Markdown files, and I can fire up any old text editor to work on them. I can’t recommend Jekyll for everyone—it requires a comfort level with GitHub and the command line that I wouldn’t impose on many writers—but it made perfect sense for me.
I find a comment like this very valuable coming from Mandy — not least because she founded Editorially, which (as I will argue later) provided nearly all the collaboration and versioning functionality that a lot of writers are trying to approximate with git, and did a vastly better job at it.
Here's what I infer from this (though I could be wrong): Mandy doesn’t think imposing git as part of a collaboration or publishing workflow is a very good idea for most writers.
Curious: does she use git simply as a hit-publish mechanism, or is she finding value in git’s core features like versioning and branching? Has she ever tried using git for collaboration on works of prose?