Skip to content

Developer documentation #19

@CarterA

Description

@CarterA

We need documentation for end-users, but we also need documentation for developers. Tribo is meant to be open and accessible for hackers, so an overview of the architecture of the whole system would be helpful. I don't think we necessarily need Doxygen-style documentation for every single method of every single class, but getting oriented in a project with zero documentation can be tough.

Developer documentation would also include information about the file format, how templates are set up, and how you could write import and export scripts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions