API documentation
This is the definite source of information for developers, besides having a look at the actual source code. Each class and public method should be fully documented.
To get a more high-level overview of the overall package architecture first, you may have a look at the separate architecture section of the documentation. And just in case that you would like to contribute to the package, make sure to check out the contribution guidelines.
Modules
An alphabetic list of the modules available within the evedata package. The actual documentation is split in pages for each module, respectively.
Subpackages
An alphabetic list of the subpackages available within the evedata package. The actual documentation is split in pages for each module of each subpackage, respectively.
There are two layers of organisation: functional layers and within those technical layers. For each functional layer, typically three technical layers (boundaries, controllers, entities – BCE) are present. See Fig. 4 in the architecture section of the documentation for an overview.