Virtual attendance includes:
- Live streamed talks from the main stage
- Ability to participate in Q&A with speakers
- Real-time chat with other virtual attendees
- Virtual networking spaces
- Conference talk videos available 2-3 weeks after the event
Tickets: https://www.writethedocs.org/conf/portland/2026/tickets/
Sarah will share the combination of writing guidelines and structural changes that have kept MongoDBโs internal accuracy metrics at 93% across ~8 answer engines.
Donโt miss this talk at Write the Docs Portland, May 3-5!
๐ The wait is over! ๐
Our full conference schedule is officially LIVE for May 3-5 in Portland, and we are excited to welcome you!
โ Think coffee culture, food carts, and that perfect Pacific Northwest energy.
Itโs time to build your personal schedule and map out your adventure.
Full details: https://www.writethedocs.org/conf/portland/2026/news/announcing-schedule/
๐ฌ What are you most looking forward to?
Let us know in the comments!
Booked my flights and hotel for Write the Docs in Portland!
This was done through a systematic, data-driven process aligned with support metrics and product priorities.
Donโt miss this talk at Write the Docs Portland, May 3-5!
https://www.writethedocs.org/conf/portland/2026/speakers/#speaker-aileen-mary-how-we-deprecated-500-articles-cleaning-up-documentation-at-scale-aileen-mary
#writethedocs
Brian Christianโs book ๐๐๐ ๐๐ค๐จ๐ฉ ๐๐ช๐ข๐๐ฃ ๐๐ช๐ข๐๐ฃ explored what it means to be human through a competition between the best chatbots at the time via a tournament of Turing tests.
In his talk, โ๐ง๐ต๐ฒ ๐ ๐ผ๐๐ ๐๐๐บ๐ฎ๐ป ๐๐ผ๐ฐ๐๐บ๐ฒ๐ป๐๐ฎ๐๐ถ๐ผ๐ปโ, Christian Miles discusses how bespoke tools can help navigate a socially complex environment created by the proliferation of AI technologies.
Avoiding the docs slide into staleness takes some proactive effort. But a lot of that can be automated these days.
I talk about some suggestions in a blog post here: https://djw.fyi/portfolio/preventing-drift/
Photo by Aliaksei Semirski on Pexels. Weโve all been there. The team is firing on all cylinders, cranking out innovative new features. The documentation is perfect! Itโs comprehensive, clear, and included right in the Pull Request. Then, six months later, a bug report comes in. Somewhere along the way, a developer changed a timeout value, renamed a key in a JSON response, or updated a UI label, andโฆthe documentation didnโt move an inch.
For many years, Sarah has used Git the way many people do: just enough to feel competent, but not enough to recover if anything went sideways. This talk, โ๐ง๐ต๐ฒ ๐๐ถ๐ ๐๐ผ๐บ๐บ๐ฎ๐ป๐ฑ๐ ๐ ๐๐๐ผ๐ถ๐ฑ๐ฒ๐ฑ ๐ณ๐ผ๐ฟ 9 ๐ฌ๐ฒ๐ฎ๐ฟ๐ (๐ฎ๐ป๐ฑ ๐ช๐ต๐ ๐ ๐ช๐ถ๐๐ต ๐ ๐๐ฎ๐ฑ๐ป'๐)โ, is a writer-friendly tour of the Git commands Sarah Deaton avoided for years, and the calm workflows they unlock.
Being the first and only Technical Writer on a team doesnโt just mean documenting features; it means becoming a bridge, educator, advocate, and cultureโbuilder all at once. Over time, Alina learned that while documentation is often undervalued or taken for granted, it quietly shapes everything: from product clarity to better UI to an improved API experience.
Many technical communicators already practice the skills needed to shape high-impact technical narratives, but don't always see how those skills translate outside documentation contexts.
Write the Docs
Dysmorphia๐๐ค๐๐ค
Daryl the Admin