Separate repositories

[sonntagd]

Source and output repositories could be separated, so the markdown, the converter script and the travis.yml would not live in the repository that contains the HTML files.

The safest way would be three repositories:

1. The source repository only containing the markdown files and the HTML template.
2. The converter software.
3. The output repository only containing the generated HTML.

With this setup you could restrict access to the third repository only to the deploy key of the converter software. So the maintainers of the website source are not directly able to edit the converter workflow.

The .travis.yml would only clone the converter repository and execute a shell script there that runs everything we currently define in the .travis.yml configuration file.