Maintainers wanted

[avivace]

Unfortunately this repository is not being maintained right now and PRs are being abandoned/ignored.
We're looking for new maintainers to take on the project. If you think you can help, please reach out here/on discord.

A good starting point would be submitting reviews of the current PRs.

[nummacway]

I'd like to put a wiki on the table. I think GitHub isn't a good platform for continuous (as in 'frequent') improvements on what can be considered single (individual) files. Editing a page on a wiki will not have global effects that must be taken care of.

For example:
If you carelessly change something in a software project, a greater number things can break and bad things can happen. Git makes sense here.
The worst thing you can do to a wiki is adding wrong information to a page. But that's a single page that anyone can revert.

WikiBooks has a similar idea and seems to work, at least if someone has already written a few pages and a general outline (so people know the scope of a "book"). ISSO has provided even more.
We're all technically skilled and should be able to edit a wiki. Additionally, the GB Dev community has proved that we are able to have an orderly discussion.

However, I'm not sure if gg8 wiki is suited for this. It looks like its goal (or scope) wasn't a 100% clear and this sadly made it a bit ... messy. From my experience with a large wiki (20,000 articles), wikis are best started with a clear goal and the commitment of a few people who add information (unique information at best) so any potential contributor understands where this goes. But I'm not sure if such a group of people exists in this community.
The scope of this tutorial however is very clear and everyone should be able to understand what it wants to teach.