Главная
Study mode:
on
1
Intro
2
Mikeys background
3
Help desk
4
Why documentation
5
How documentation used to be
6
How to help a software project
7
Pros
8
Join the Docs Club
9
Content Strategy
10
Users
11
What do they want
12
When do they need it
13
Error messages
14
Why
15
Bugs
16
Who are you
17
Administrator
18
Developers
19
Arch Linux Wiki
20
Red Hat
21
Working on new guides
22
DevOps for docs
23
Unified tool chain
24
Continuous integration
25
Content curation
26
Community engagement
27
Outreach efforts
28
Example
29
Templates
30
Collaboration
31
Documentation conferences
32
Everyone can care
33
QA Questions
34
Organizational Position
35
When to hire a writer
Description:
Explore the fundamentals of technical communication for open-source projects in this EuroPython Conference talk. Learn how to improve documentation for better user onboarding, code contribution workflows, and overall project accessibility. Discover key principles including tone, style, process management, structure, and contribution workflows. Gain insights into content strategy, understanding user needs, error message crafting, and community engagement. Examine the evolution of documentation practices, the importance of a unified tool chain, continuous integration for docs, and strategies for content curation. Understand when to consider hiring a dedicated technical writer and how to foster a documentation-centric culture within your project.

FOSS DOCS 101 - Keep It Simple, Present

EuroPython Conference
Add to list