Move to a CI-powered release process

[birjj]

Although it is nice to be able to simply let GitHub worry about building our website, it does limit our choice of build tools significantly. Jekyll - the only static page generator GH supports - puts rather strict restrictions on data structure (this is also why the _data folder is named as it is) and Liquid, the templating language, is rather underwhelming.

I would prefer moving to a build process that is powered by our CI (currently Travis). This would allow us to build using whatever build tool we want (even a custom one), and allow us far greater freedom over how the project is structured.

We could additionally perform automatic git tagged releases, which would give us a formal changelog (#747).

This is all a bit abstract for now, as this issue is mostly created in order to allow discussion on the topic, but it is a future plan for the project (along with #485)

[ericcornelissen]

In the light of #942, I just wanted to add to this that we can and should also do this with the NPM release, more information here

[birjj]

We are actually already doing this for NPM releases. All PRs into master (with a new version in package.json) will trigger an NPM publish through Travis, and a GitHub Pages rebuild through GitHub (and will spam my email with updates on the NPM publishing 😄)

I'd like to move everything to Travis to give us better control over the process, and e.g. allow us to write the website in something other than Liquid.

[ericcornelissen]

My bad 😓 For some reason I just completely missed this snippet of code...

[runxel]

Closed with #77

[ericcornelissen]

Not sure how #77 resolved this issue, but I'm fine closing this as it is more or less resolved with https://github.com/simple-icons/simple-icons-website