document academic writing end-to-end

[maxheld83]

covering:

• [ ] pandoc's markdown
• [ ] pandoc to LaTeX, HTML, Word ...
• [x] references @t-rop has already done much of this for references in #137.
• [ ] git
• [ ] ci/cd
• ...

So this issue is a little wide and fuzzy.

The background was that some students were interested in using RMarkdown (or maybe just Pandoc's Markdown?) in their projects, and it'd be worthwhile to make this easier.

We could do several things:

• tighten up / expand the existing resources in http://datascience.phil.fau.de/fossos/stack.html#technical__scientific_authoring
• motivate this more
• especially the CICD part

This stuff is already pretty extensively documented in a number of places I linked to, so there is a danger of reinventing the wheel here. (to be avoided).

[maxheld83]

there is now a new section on Technical and Scientific Authoring that covers this.

[maxheld83]

@samshaffer97 this issue is now more tightly just about documenting/getting this to work. My wilder idea of factoring out some of rmarkdown to its own bash pandoc wrappers for non-R users lives in #158.