One of the best features of this pipeline is the fact that I can write a large chunk of the document whilst conducting research. I can jot down notes, caveats, schedule TODO items etc. and just tag the bits I want for my own reference as 'noexport', so that they don't make it into the exported tex or pdf document.
Another great feature is that I can embed code for producing tables/figures all within the document and specify whether I want the code or result or both to be included.
Finally, once I am happy I have most of the document the way I want it, I export to tex to deal with the final tweaks to finesse things -- spacing for the entire document, fine-grained adjustment of figure formatting.
This ensures that I have all the information that went into constructing the document and allows me to deal with various venue-specific constraints like submitting a source archive, or pdf as necessary.
Here are some resources for getting started with this:
- https://github.com/vikasrawal/orgpaper/blob/master/orgpapers...
- http://draketo.de/english/emacs/writing-papers-in-org-mode-a...
- http://www.clarkdonley.com/blog/2014-10-26-org-mode-and-writ...
I learned the hard way. I wrote some presentations using org-mode. Then they changed the exporters without updating the documentation. It would be especially problematic to write an academic article in org-mode, because you might have to return a year or two later, and that's not when you want to find out how much has changed since you last worked on the paper.
Example config for latex export (although I do not write academic articles):
https://github.com/cadadr/emacs.d/blob/c81ff8afa3ca4ab553013...