Found this site when searching for answer to some git issues. It turns out to be a very nice way to teach stuff, simple and efficient:
A guide like this should be as easy to write as it is easy to learn from.
The key here is to associate problem / question / issue with a straightforward solution / answer in a very simple manner. Talk is expensive. We should talk as less as possible.
Deprive of any words that your tutorial or guide can live without but leave only those that are vital to the actual solution / answer.
A full tutorial or guide should be comprised of a list or a network of standalone articles that are simple yet powerful in addressing 1 — 3 problems each. They are more like a deck of cards wired together linearly or hierarchically that the readers can search or navigate back and forth.
Each article / card should be no more than 2 minutes of reading. This helps establish learning milestones for the readers thus keep them motivated to continue because each learning session is easy to finish and apply.