Migrate website away from wiki.gnome.org about gtg HOT 4 OPEN

Yeah, it seems like we're supposed to be migrating to apps.gnome.org (which is surely not something we have access to because #798 / #234) or to a bunch of markdown files in the git repo (which are not as flexible, so urgh...) or basically roll-our-own-website, none of which I have had the time and energy to try to do over the past year.

GTG used to have its own dedicated website (for the sake of marketing), which we could try doing again but that's way more work than a wiki page of course.

What would be the preferable way forward? Are we going to just turn everything into readme files in github, or should we also have a pretty standalone website? I don't mind designing and hosting the website, I have the infrastructure to do that, but I'd like to know if @diegogangl would actually want that to happen, and then I would need to find the time to do it (and probably get a new appropriate domain for it, etc.)

from gtg.

From a marketing standpoint, what I want to avoid is loss of control due to old content lingering on the read-only archived version of the GNOME Wiki eventually as it would become carbon-frozen and non-updateable; I would want our migration to delete all the old contents and put redirects in place.

from gtg.

The best solution considering visiblity would be apps.gnome.org but I'm guessing you have to be accepted.

There's also Github pages but I think the theme selection is more limited. If we go with the website way, I would make a very simple one page that links to flathub page, and the readme files in the docs for contributor stuff

from gtg.

GitHub pages is basically just HTML files, we can have any theme. Jekyll integration is just an integration, not an requirement.

from gtg.