Documentation is king when it comes to supporting consumers of your code and convincing newcomers that it actually makes sense to buy in and use your package. For most people, a documentation website is the first place they go to learn about the package. It is, by definition, assumed to be the single source of truth on the code in its current version.
The role of documentation is usually threefold:
- Explain how to install your package and what the general requirements are (for example, which Python versions are supported)
- Show how to use the package (preferably with a quick example showing its immediate value)
- Express the general idea and philosophy of the package
A documentation website does benefit from having tutorials, example cases, and a roadmap. With that being said, the core of any documentation website is, obviously, documentation...
