Write the Docs Prague 2021
2021-10-03..2021-10-05
-- online --
[Write the Docs Prague 2014, Write the Docs Prague 2017, Write the Docs Prague 2020, Write the Docs Prague 2021, Write the Docs Prague 2022]
who it's for
technical writers, documentation managers, content designers, developer documentation engineers, knowledge managers, community managers, freelance technical writers
topics
information architecture reviews; content maps and inventories; Gatsby and Markdown pipelines; site search and findability; DITA concept task reference tagging; OpenAPI specs in Postman; API style guides and contract testing; Confluence Bitbucket Jira setups; feedback forms driving tickets; remote onboarding and virtual workflows
| title | author | length |
|---|---|---|
| Introduction to | Mikey Ariel | 39m |
Conference logistics and community rules explained clearly: talks are pre recorded with live Q&A on the Hoopin platform and the job fair runs from about 10:45… | ||
| More than words: Reviewing and updating your information architecture | Lana Brindley | 36m |
Shows a concrete workflow: inventory pages in a content map (spreadsheet or DB), tag each page by DITA: concepts tasks reference, run a simple user‑task matrix… | ||
| So you need to give bad news to users… | Ryan Macklin | 41m |
Claims five concrete tactics for writing bad news: understand dysregulated brains and a brain‑dollars cost model, surface a single clear action (subject line… | ||
| When documenting is designing | Fabrizio Ferri Benedetti | 40m |
Argues that technical writers step into API design by producing concrete artifacts: an API style guide, a collaborative design template and versioned OpenAPI… | ||
| Adventures in setting up a knowledge system for a research group | Victor Sluiter | 38m |
A research group builds a shared knowledge system using Confluence + Bitbucket + Jira, migrates all code and standardizes project spaces, and defines… | ||
| Alchemy in Adversity | Anna Korinna Németh Szabó | 43m |
A three-person technical writing team faces March 2020 lockdowns, sees meetings multiply and documentation quality dip, then hired two new members and moves… | ||
| Customer Feedback is the Fuel in our Engine | Kevin Hwang | 42m |
Describes actionable systems: a feedback form at bottom of every page that creates tickets, monitoring public Slack channels for real-world fixes, and a… | ||
| How to write a book for (and with) an open source community | Felicity Brand | 40m |
A community book claims to grow international adoption and funnels proceeds back into the Typo3 association and it uses Google Docs for authoring, hands off to… | ||
| Hustling for Fun and Profit as a Technical Writer: A Freelancing Starter Kit | Karen Sawrey | 44m |
Covers concrete steps to start freelancing: read and negotiate your employment contract and NDA, register a legal entity and pay taxes, and consult a lawyer or… | ||
| Cognitive Ergonomics in Technical Writing - Lessons from the Field | Anita Diamond | 40m |
Explains concrete fixes: crypto wallets generate a 12–24‑word master seed that signup flows force users to write down by disabling copy paste and screenshots… | ||
| How I use applied linguistics to be a better technical writer | Kat Stoica Ostenfeld | 36m |
Applied linguistics shows that shared context matters more than raw English proficiency so documentation success comes from aligning vocabularies not policing… | ||
| From travel content to technical content: my journey | Kate Santo | 43m |
Argues that “technical writer” is misleading and that the job is a product-focused technical content designer role, lays out a six‑step content design workflow… | ||
| Docs leadership: How to become a stronger leader for your team | Jenn Leaver | 50m |
Leadership centers on measurable choices: define values (kind, transparent), shift a single-writer workflow into a collaborative one with handoffs and… | ||
| The best tech writing you’ve never seen | Abi Sutherland | 08m |
Claims that a 1969 DIY manual actually invents modern tech docs and backs it with specifics: step-by-step procedures that start from “where is the engine” and… | ||
| The five people you meet in documentation | Swapnil Ogale | 06m |
A framework of five concrete archetypes appears: empathy allies who amplify impact, sacrificers who map systems and make handoffs work, anti‑documentation… | ||
| Bike the Docs | Bart Buerman | 06m |
Runs conference live streams from a living room and hauls gear around Rotterdam on a cargo bike, but sometimes rents a car when lighting and distance exceed… | ||
| Docs as GUI | Eugene Titerman | 06m |
Claim: when a product lacks a GUI, docs become the primary face and must act like an interface. The concrete prescription is three rules: invite users to… | ||
| New, first, & only | Coley Woyak | 05m |
Describes being the first and only technical writer at two French startups and the concrete work done: documented Kubernetes installations and a dcos code… | ||
| Apostrophe - a story of naming | Tony Ibbs | 03m |
A concrete failure story about naming: a Python test that checks two device identifiers passes locally but then fails with an unterminated string error because… | ||
| Design thinking is in tech writing all along | Qian Lu | 02m |
Claims that tech writing already uses design thinking and proves it by mapping concrete steps: ask why repeatedly about user needs and product strategy, run… | ||
| Process Recordings: Documenting Social Work Conversations | Emily Axel | 05m |
Describes a specific documentation practice: a four‑column template capturing verbatim transcript, what you were thinking, why actions were taken, and… | ||
| nothing matches | ||