Also wouldn't it make sense to move the static site generator content to https://github.com/pelias/documentation ?

Ah yeah, that's actually pretty nice. I started on a jekyll port, but I know not everyone loves Jekyll like I do :P

Material for Mkdocs looks real good, I bet with a few tweaks to the colors it could be very nicely Pelias branded. Also, check how quickly/easily it can be set up in Netlify, since that's what we currently use.

I'd definitely be in support of porting over the static site to it, assuming it's fairly easy to start with and supports Markdown.

As for where content goes, as mentioned in pelias/documentation#262 my thought was it all moves to this repo, but as long as it's in one place and easily edited/released, it's all good.

Hi there,

👍 Material for Mkdocs looks very good !

The interesting thing with jekyll is the native GitHub support.

I have my personal website hosted on GitHub (joxit.dev), the interesting part is I've created my theme on my main repository Joxit/joxit.github.io (using bulma 😉) and I use this theme on all my projects, for example Joxit/docker-registry-ui thanks to this line in _config.yml.

GitHub is mapping every projects by their name, that means my main website is joxit.dev, and my project will be hosted on joxit.dev/docker-registry-ui automatically.
Thanks to this all my project have the same look.

In this case, with GitHub, pelias/pelias can host the main website on pelias.io, and pelias/documentation the documentation on pelias.io/documentation ?

Worth mentioning doks by Henk Verlinde a Hugo theme.