I'm writing a paper, and I've found a decent approach to keep things organized:
1) Everything is in a #git repo, and i collaborate with the other authors through #github (private repo, for now).
Changes to the text are discussed through github issues and PR.
2) To overcome writer's block I wrote a one line comment where each paragraph will be, so that I get an idea of the logic of the paper.
The paragraphs then are folded (using #vim) into the one line summaries, to keep the overview.
@mprv
Sounds really good. I've been looking for a solution to #2 every now and then, i.e. how to toggle between viewing the full text and an outline without maintaining separate files.
Come to think of it, maybe occur mode could do this with some kind of markers for the outline elements (I'm using emacs)
@jamie
I used pandoc too for a while, and I still think that most papers could be written in markdown.
This workflow should be language independent, though: you can version control *anything* 😁
And the other thing is mostly a mental order question (and editor capability).
What does your workflow look like?
@mmin
@mprv @jamie I agree that language independence is important. My previous workflow was built around org and then supplemented with org-bibtex and org-brain (a mindmap extension), but for some reason this was very slow and was becoming unwieldy. Now I use zotero for references and reading notes, a paper notebook for quick notes and tiddlywiki for more permanent notes.
But this seems to be constantly a work in progress 😀
I like tiddlywiki a lot although setting up is nontrivial. It needs a browser plugin and the wiki needs to be under the downloads directory, otherwise it can't save with modern browsers. Once it works, it's really nice because you can use tags, links etc. You can even visualise the network with the tiddlymap plugin. Can't say about math support.
To be honest though I overestimated my need for a research wiki. I haven't used it nearly as much as I initially thought.