|
|
|
|
|
by kqr
3008 days ago
|
|
For Google Docs-like tasks I prefer a combination of Org and git. Org is a powerful-but-easy-to-learn document structuring language. You ca write it in any editor, but in an Org-aware editor your document really comes alive. The oldest, most feature-complete implementation is in Emacs. Org documents can be exported to virtually any final format. I don't specifically recommend git so much as any distributed VCS, to share changes with collaborators in a controlled and structured way. I find it much easier to catch up on other's work when it comes as a self-contained, clearly labeled commit in the correct branch rather than a jumble of tiny edits here and there. If you are working with lazy people who don't want to learn stuff, you may want to consider whether you'd be okay with keeping your private data with GitHub instead. If your Org document lives in a repo there, anyone with commit access can edit it in the GitHub web editor, with a formatted preview available. |
|