Skip to content

Figure out what to refer to the project/software as in shared docs like the API #21

@sushimustwrite

Description

@sushimustwrite

The Trovebox and Openphoto API use the same API docs, which is great except for that part where the projects have different names. We need to stay consistent and not refer to Trovebox as Openphoto in those docs, for example.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions