Consider more structured documentation #214

Open
opened 2026-06-23 06:32:43 +00:00 by mih · 1 comment
Owner

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.

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.
Owner

That is very true. I will move documentaton to sphinx.

That is very true. I will move documentaton to sphinx.
Sign in to join this conversation.
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
orinoco/dump-things-service#214
No description provided.