The ToAD project follows the divio documentation system philosophy, which at a high level encourages documentation authors to think in terms of 4 types of documentation that solve fundamentally different problems:
^
TUTORIALS | HOW DO I _
practical
|
|
<-- studying ----- working -->
|
|
theoretical
EXPLANATION | REFERENCE
v
Learning Oriented
People unfamiliar with the project, curious about CoAP
Make the project approachable, with recipes for success that people with little context can follow and have a working solution to a problem.
- meaningful
- achievable
- valuable
- zero assumed shared context
toad.dev Book
Solutions to specific problems users are likely to encounter, answers to questions they're likely to have
People with some experience, working directly with the project
Make common issues, questions, problems easily solvable. Offer atomic guides that offer a lot of value in a little copy
- meaningful
- specific
- non-explanatory
- documents assumed shared context
- blogposts?
- wiki?
- faq?
clarify and illuminate various topics; broaden a documentation's coverage of a topic; understanding-oriented
Anyone at any level of experience or context (think dictionary or wikipedia)