That does sound nice, but I'm a bit confused about using it for _project documentation_. Are any of these open-source? Although org is plaintext and thus technically cross-editor compatible, it's meant to be edited in Emacs, so would contributors just need to use Emacs?
> would contributors just need to use Emacs?
As you note, org-mode text is just special plaintext, no different from Markdown (other than being rather more powerful).
And of course folks should want to use emacs, or a similarly-powerful editor in which it's possible to build something like org-mode. Why use worse tools when better ones are equally available?
Re:The Many Uses of Org Mode
by hprotagonist on Wednesday May 09, 2018 @07:46PM
(#17035299)
I render org to HTML (or let github do it for me for readmes, just as it does for markdown).
What org is very good at is treating HTML, LaTeX, markdown, etc. as, effectively, compilation targets.
`C-c C-e h h` : spits out foo.html
`C-c C-e l p` : spits out foo.tex, foo.pdf.
Org-mode is the digital lab notebook that I have needed forever. I have a private repo with one folder per general project and one or more org files inside. I mostly treat them as append-only FILO pipes.
PI wants a progress report? Export the relevant headings to a PDF and email it.
I want some literate-programming style "work in progress"? Easy, you can even hook jupyter in, and dump plots out simply. Export it to a PDF if you want, or make it a blog post with some nice HTML styling.
Project documentation? easy.
Paper drafts? Yup.
It's wonderful.