~/conference

Write the Docs Portland 2020

technical writers, docs engineers, content designers, localization managers, developer advocates, engineering managers

accessibility practices for docs; translation memory and localization; migrating docs to new tooling; creating quality sample code; Jupyter notebook interactive tutorials; pandoc and XeLaTeX CI builds; model-based architecture diagramming; structured-data documentation; documentation as interactive application; SDK documentation best practices; search and intelligent search; content strategy and collaboration

titleauthorlength
IntroductionWrite the Docs Portland33m
Conference moves online as a working experiment: talks stream on Hopin with a moderated Q&A, live human captions by Vanessa, and Google Sheets running the…
Talk on
Moving beyond empathy: a11y in documentationAlexandra White37m
Argues that empathy alone is insufficient and documents must use concrete accessibility practices including semantic HTML, matching alt and aria text to…
Talk on
Globalise the docsLucy Carey47m
Argues that translating English docs needs concrete choices: use humans for boutique copy, leverage translation memory (CAT) tools to speed work, and use…
Talk on
Writing Backwards: Documenting the End-of-Life of a ProductAnni Bond30m
Manages the documentation for the end of Red Hat Network and the migration to Red Hat Subscription Management and shows concrete steps: a phased shutdown: UI…
Talk on
Read the Rules: What technical writers can learn from board game designMatthew Baldwin48m
Compares rulebooks like Wingspan that separate a short how-to-play and an appendix reference and teach from general to specific, shows step-by-step setup…
Talk on
Impactful writing during the pandemicNick Van der Auwermeulen06m
Documentation and processes enable rapid scale up of a COVID testing program by turning ad hoc practices into repeatable operations using standardized…
Lightning on
Hieroglyphic: visual annotations for codeAyman Nadeem05m
Claims a concrete prototype called hieroglyphic that embeds hand-drawn diagrams and markup as layers for code files inside the IDE, combining static analysis…
Lightning on
Collaboration is scary and makes us betterMatt Reiner05m
Says using Confluence and live editing makes work visible and sometimes terrifying but ultimately better, argues collaboration produces more robust outcomes…
Lightning on
Creating Quality Sample CodeJessica Garson28m
Creates GitHub-hosted samples for Twitter Labs with a focus on short, modular, runnable examples that actually work and get maintained. Uses a Postman…
Talk on
Building a content-focused, scientific document authoring workflowColin Dean30m
A reproducible authoring workflow based on pandoc + XeLaTeX build and git produces a versioned PDF artifact built by CI (Drone) and Make, created in about two…
Talk on
Don't Fear Migration! How to Successfully Move Docs to a New ToolBrooke Wayne27m
Company moves a messy support wiki into a neutral docs tool after finding agents spend 13% of their time hunting answers and only 3% of pages actually help…
Talk on
Where Docs, Cloud-hosted Interactive Tutorials and CI Testing IntersectDan Gunter19m
Uses Jupyter notebooks as single-source examples, with Sphinx to render docs, a separate GitHub repo for examples, and a lightweight CLI that fetches examples…
Talk on
Finding the line: Balancing business continuity and documentation debtLuca Janssens43m
Argues that documentation debt is a distinct, long‑term problem born of rapid delivery and that balancing it with documentation continuity requires treating…
Talk on
Collaborating w/teams on content strategy planning: pitfalls & best practicesKateryna Osadchenko42m
Argues that success hinges on specifics: establish clear communications up front, schedule regular touchpoints, and decompose work into visible chunks with…
Talk on
Model-view-docs: taming large-scale documentation projects using structured dataLuc Perkins43m
Argues that data-driven documentation makes large, changing docs maintainable by separating structured sources (JSON/YAML) from templates and automating…
Talk on
Set your data free with model-based architecture diagrammingAvi Flax45m
Claim: de‑confounding content from presentation — keep the architecture model separate from the visualization so one source of truth drives many views…
Talk on
Documentation as an application: enabling interactive content tailored to the userRyan Paul42m
Stripe reworks docs into an app: a React front end, a custom markdown superset called markdoc, and a ruby proxy that supplies primitive context variables…
Talk on
Write great learning objectives to power intelligent searchAdrian Stevens06m
Claims that hands-on interactivity increases transfer and automaticity and that practice produces retention and demonstrable experience. Evidence includes…
Lightning on
Can we (sometimes) go back to print documentation?Julia Evans04m
Argues that some core documentation is stable enough to justify physical publishing: a solo publisher called wizard Zen condenses big topics into 24-page…
Lightning on
When grammar rules matter, and when they get in the wayJanine Chan05m
Presented at Write the Docs Portland 2020 virtual conference, the claim centers on choosing descriptivism over prescriptivism: keep style guides as a tool but…
Lightning on
Emotional personas: another way to think about your usersRyan Macklin01m
A five‑minute slide deck claims a practical taxonomy: five emotional personas named after animals that map user emotion to content needs, presented as anxious…
Lightning on
Walking Backwards: New Customer Journey from Finish to Start to Help Shape ContentSally Stumbo36m
Audits of new-account support cases start from the end result and reveal concrete fixes: July 2019 sampling filters ~1,000 cases down to 76 cases filtered…
Talk on
The Search for SearchPaul Logan37m
Adds a site search to api.slack.com by indexing a unified catalog of docs and calling the Algolia REST API from the monolithic Hack/PHP codebase, not using…
Talk on
Why SDK Docs Matter — And What I’m Doing About It!Shavindri Dissanayake (Shavi)34m
Users land on Github and confuse similar client libraries so 25 sdks produce wrong choices; solution creates a per‑sdk table of sdks, a visible decision…
Talk on
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.