Write the definitive guide to an underdocumented tool

No riders yet

Docs for a tool everyone struggles with.

Pick an open-source tool that many people use and few understand, and write the guide its users keep wishing existed. Read the source and the issue tracker, run every example on a real machine so each one works as written, cover the common tasks and the sharp edges, and publish it as a readable artifact with its code. Note where the tool’s own documentation is wrong, and say what the guide does not cover.