The talk is about how to approach writing for developers and take project documentation to the next level. It emphasizes the importance of documentation in open source projects and how it can meet user needs. The hero's journey is used as a framing device to explain how to write good docs from the user's perspective.
- Great documentation and community support are key when choosing an open source project to use in production.
- Documentation maintenance is important in open source projects as there is no dedicated support team, sales team, or technical writers.
- The hero's journey is a useful framing device to explain how to write good docs from the user's perspective.
- Users always have a goal and understanding that goal is the first task in writing documentation.
- Documentation can meet user needs such as evaluating new tech stacks, learning, supporting existing systems, and developing new features.
- Concept topics briefly describe or link to other topics related to the feature at hand and describe why a user might care about a feature or what the common use cases for using something are.
- Task topics explain how to use a feature to accomplish a goal and can include information about potential pitfalls.
- Reference topics show all the things that a feature can do and help users decide which functionalities to use to solve their problem.
- Good documentation is well-organized, searchable, and explains concepts, tasks, and references.
- Documentation can explain anything by using these three styles of writing: concept, task, and reference.
The hero's journey is a common archetype in English literature and can be used to explain the user's journey through documentation. Users are like heroes who are given a call to adventure, go through trials and tribulations, and gain the skills to accomplish their goals. Good documentation can help users on their journey and meet their needs such as evaluating new tech stacks, learning, supporting existing systems, and developing new features.