[lopkeny12ko]

Why store markdown files in Google Drive of all places and not a git repository?

Google Drive, to me, is object storage with a consumer-friendly user interface. It does not sound like the right place for constantly-changing text files for which you'd want revision history and commit-oriented editing.

[BeFlatXIII]

> Why store markdown files in Google Drive of all places and not a git repository?

Git diffing doesn't play nice with paragraph-based prose.

[spondylosaurus]

Does it not? All of our docs are Markdown files maintained in GitHub and diffs have never been an issue. PRs in particular are great for collaborative updates because reviewers can jump straight to the paragraphs that changed instead of reading everything top to bottom.

[BeFlatXIII]

How do you handle text wrapping or otherwise manage long paragraphs? Do you use a newline per sentence or use soft-wrapping to write each paragraph on a single line?

[spondylosaurus]

I thiiiink soft wrapping, but I'm not at my computer to verify.

[vel0city]

Live collaboration is a radically different experience than pushing branches. Pros and cons to each, really depends on what you're wanting with a given document.