This document discusses how to properly document code using ReadTheDocs. It recommends documenting code for reasons such as making complex code more understandable, explaining business rules, and avoiding having to re-find details. It recommends documenting dependencies, installation instructions, guides, change logs, and supported versions. The document then explains how to set up documentation on ReadTheDocs, including installing Sphinx, setting up a ReadTheDocs project, and adding a post-commit hook to automatically rebuild documentation on commits. It provides several resources for learning more about documentation best practices and ReadTheDocs.