DocsFlow

“Google Docs” for the Markdown files in your git repo.

DocsFlow gives non-technical collaborators friendly view/suggest/diff/approve/comment functionality for the Markdown files in git. Suggestions become commits, and commits are shown back in that same friendly view.

Workflow

We have a great experience with MS Word + email review Markdown/Git/DocsFlow workflow between the technical team and the product owner.

The core architecture relies on manual syncs automatic two-way git sync.

alice

12:50 PM Today

✓

⋮

Keep the old workflow as a footnote?

Reply…

alice

12:50 PM Today

✓

Remove: “MS Word + email review”

Add: “Markdown/Git/DocsFlow”

Reply…

Notify me →

A broad range of people can read and write Markdown.

Collaboration between agents, developers, and everyone else should follow naturally. It doesn't. Two walls keep non-technical collaborators out:

@@ -1,4 +1,4 @@  ## Disadvantages of raw Markdown diffs  1. Headings and decorations aren't rendered- 2. One-char edit reddens the whole paragraph+ 1. One-char edit reddens the whole paragraph- 3. No wrapping — scroll right to see changes+ 1. No wrapping — scroll right to see changes- 4. Tables diff into unreadable noise+ 1. Tables diff into unreadable noise

Markdown editing & diffing UX

Viewing, creating, or editing a diff is non-existent or painful in most tools.

$ git pull --rebase
Auto-merging README.md
CONFLICT (content): Merge conflict in README.md
<<<<<<< HEAD
- Ship v1 in Q3 with the migration guide.
=======
- Launch v1 in Q3 alongside docs.
>>>>>>> origin/main
error: could not apply ...
Resolve all conflicts manually, mark them as
resolved with "git add", then run "git rebase --continue"

git UX

Git dominates "file-sharing" in the software industry, yet remains unrealistic for non-technical people to learn.

Bridge the gap between your repo and non-technical collaborators.

Notify me when DocsFlow launches.