Skip to content

Documentation #171

@JHopeCollins

Description

@JHopeCollins

What documentation should we have, and what would we like to have?

We currently have docstrings on everything(?), but these require either reading through the code, or knowing what the classes/methods are called to check them with pydoc.

Possible improvements include:

  1. API documentation on a webpage. We could see how gusto / irksome / defcon do things.
  2. Manual pages on a webpage.
    • Overview of asQ / library aims
    • Library structure / design philosophy
    • Explanations of the various modules and example uses
    • FAQ / troubleshooting
  3. Jupyter notebooks with serial examples

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions