Feature: build with github actions

[rdmueller]

we already have automated the steps to build the templates in the gitpod definition file.
Let's move this to github actions

[programming-wolf]

I support the idea to switch to GitHub actions. I will try to setup a pull request with a working GitHub action file within the next two weeks.

However, I've got a proposal to change the release process.
Instead of adding the binaries to the Repository and committing/pushing them every time, why don't we use the official Releases feature of GitHub? We can add all the *.zip files from the dist-folder and create a new release for, well, each new release. 🙂

On the website, we can still link to each downloadable asset. As the site is generated as well (as far as I understood the process), this can be adjusted as required.

[programming-wolf]

Similar to the process of the iSAQB curricula, https://github.com/isaqb-org/curriculum-foundation/releases/ .
We can also add the files to GitHub Pages to have links that are always the same and pointing to the latest release of the files, so we don't have to adjust the website.

[rdmueller]

great idea. We just didn't do it this way, because it was easier the other way :-)

[programming-wolf]

Shall we move the build process to the arc42-template repository? As the files are released there.. It would make this repository obsolete and reduce complexity?

[gernotstarke]

yes, definitely, if possible.

Let me briefly summarize the requirements:

• multiple natural languages (EN, DE, IT, ES, RU...)
• multiple target formats (md, rst, html, docx etc)
• every target format has two artifacts (with-help, no-help)

what did I forget?

[gernotstarke]

@programming-wolf we're still very interested in simplifying the build... maybe we do it stepwise:

1. migrate to current gradle/java version
2. migrate to github-actions
3. move the build process from THIS repository to the arc42-template repo