Once a project is deemed complete (you can always revisit it later with a revision), there are a couple of housekeeping things you should think about. While we added a few comments and basic docstrings to our code, more complete in-code documentation never hurts. By doing that, we can set the project up to help autogenerate user documentation. Finally, it's important to conduct a lessons-learned review of the project to see what went wrong and what could be improved in the future.
In this chapter, we will cover the following topics:
- Writing more complete docstrings
- Generating Sphinx documentation
- Conducting an after-action review
