Consider more structured documentation #214
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
orinoco/dump-things-service#214
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ATM all documentation is in a 1000-line README with no table of contents (TOC). This is not very accessible. It is hard to understand what the system components are, what could be configured, and how it should be configured.
IMHO at minimum there should be a TOC. However, I doubt that this will provide a lasting improvement. We can assume the number of backends to increase, the number of API endpoints to increase, and the number of "common" use cases to increase. It might be worth moving to a more suitable documentation framework like sphinx even now.
That is very true. I will move documentaton to sphinx.