You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Restructure the documentation to start simple and provide progressively more details, e.g.:
Tutorials
Lessons/exercise to learn from for beginners that cannot yet ask technical questions.
Writer decides actions & outcome, exercise turns learners into users. Must be bulletproof, 100% repeatable.
Does not explain, instead focuses on doing things without options/alternatives.
Basic concepts.
Guides / How-Tos
Problem oriented, takes through a series of steps. Provides answer to a meaningful technical question.
Some flexibility, covers alternatives/variations for slightly different problems users might have. Must be reliable.
Practical usability over completeness. Needs good sentence title: "Howto create a class-based view"
Reference
Technical description of the machinery. Code determines structure. Covers lifetimes, fields, interactions.
Provides information like an encyclopedia. Must be kept in sync with code.
Explanation / Discussion
Background explanations, historical contexts. Rationales for design decisions. Touches on approach alternatives.
Our documentation needs to be modernize and reorganized in several places.
Here is how to keep track of the tasks involved, feedback welcome:
Lessons/exercise to learn from for beginners that cannot yet ask technical questions.
Writer decides actions & outcome, exercise turns learners into users. Must be bulletproof, 100% repeatable.
Does not explain, instead focuses on doing things without options/alternatives.
Basic concepts.
Problem oriented, takes through a series of steps. Provides answer to a meaningful technical question.
Some flexibility, covers alternatives/variations for slightly different problems users might have. Must be reliable.
Practical usability over completeness. Needs good sentence title: "Howto create a class-based view"
Technical description of the machinery. Code determines structure. Covers lifetimes, fields, interactions.
Provides information like an encyclopedia. Must be kept in sync with code.
Background explanations, historical contexts. Rationales for design decisions. Touches on approach alternatives.
Related: What nobody tells you about documentation A Framework for Better Documentation
The text was updated successfully, but these errors were encountered: