Move documentation to new repository

[pb866]

• Create new repository for documentation
• Update Latex-files from version 8 to version 9
• In the long run, transfer Latex-files to md-files and create a wiki in the Mistra repository
• Include to-do-list from Improve documentation #5

[rs028]

What do you mean a new repo? Shouldn't it stay in the Mistra repo?

[pb866]

We can either have the latex files in the doc folder or move them to a new repo. I would keep the Mistra repo rather clean and outsource unnecessary/unrelated code to separate repos.
Having the documentation outsourced, we could also think to make the repo private as probably no one needs to know the latex code and only cares about the pdfs. I would make releases and attach pdfs of the manual and precompiled binaries to it. Or, we could have a public repo with the latex files and include it as a git submodule. It would help structuring the Mistra repo.

[rs028]

I see what you mean. I would be more inclined to keep the tex files together with the code. I think it makes everything easier, especially from the point of view of the user.

But I guess it makes more sense to have a separate repo (or a submodule), if we want to convert all the documentation to wiki format (i.e., md files) and manage the wiki with git. However, in this case I don't know how to create the pdf file to attach to the release.

[pb866]

Fine with me as well, probably worth to have at least a temporary external repo for the moment as the updates of the latex files from version 8 to 9 are not done over night, and then we have an outdated documentation in the Mistra repo.

To update everything to markdown is another story and we need to discuss priorities with the limited resources, we have.