Skip to content

User documentation. #22

@jfjlaros

Description

@jfjlaros

User documentation should be written in such a way that the user does not have to read any code. For example, here a "start rule" is mentioned without an explanation of what a start rule is, nor is an exhaustive list (or reference) given.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions