Dev stack

[rugk]

https://github.com/westnordost/StreetComplete/issues/1130#issue-339964972:

• a one-page is fine, IMHO (there is really not the need for more pages)
• I'd prefer a 100% static version, or (if really need – and I doubt so) maybe Jekyll or another static site processor, but in the end it should be hostable on GitHub Pages, if needed. There is just no need for dynamic stuff and static sites are always the fastest to load
• we hopefully need not so much JS, maybe only for scrolling effects (i.e. click on -> visually scroll to part of the page)

I'll add one more aim: As I want to use CSS Grids (https://github.com/rugk/streetcomplete-website/issues/1), which is a fairly new feature, we may need some fallback.

So what stack do we choose?

• modernizr to support old browsers
• jekyll, because ehm… can it include (similar stuff as) modernizr?
• nothing, plain sites

[rugk]

So I guess the best way may be to do progressive enhancement. It requires testing in older browsers though, but I think with browser stacks and so on, it should work.

[rugk]

the choice fell to Jekyll in "safe" mode (so it can be build on GitHub)…

This gives a lot of flexibility in case we need it while we still have static files as an output and a small toolchain.