A lot of commenters on that thread mentioned DigitalOcean as an example of great docs for a product.
Does anyone have examples of great docs / user guides for open source projects? I'd like to study well done open source docs and learn more about what can be added to the docs to make them more useful for devs.
Laravel - Build an end to end complete full stack application. You can incorporate just about every boilerplate feature you can think of by just following the docs.
Gitlab - Open and complete docs on source management, and the Gitlab product. But also very easy to understand docs on different aspects of running a software business, including style guides, and messages from executives.
(Unfortunately, a lot of modern software lacks documentation, making it difficult to use. Do not assume that the user interface is understandable. If you do not include comprehensive documentation, then it will not be understandable.)
I recently submitted a package to MELPA (an emacs package repo) and part of the process was cleaning up the doc strings in the code to ensure that they fit the standard.
It's all docstrings type stuff, and very incomplete