The first time I attended Write the Docs, I expected an audience of technical writers comparing tools. What I got was amazing and inspirational experience. Write the Docs in one sentence wold be: a community built around the problem of communication, not around any particular technology or role.
Eric Holscher founded Write the Docs, and the community has grown into something genuinely global. Conferences run on four continents: Portland, Berlin, Australia, and Africa. The Portland 2025 conference brought 415 people in person and another 170 joining virtually. Those are not enormous numbers by tech conference standards, but the density of thoughtful conversation per attendee is higher than most conferences I’ve been to. People come to WtD because they actually care about the craft.
What’s unusual about WtD is that the topic is the craft of communication itself, not a framework, not a tool, not a language. Most tech conferences organize around a technology. WtD organizes around a question: how do you explain things to people who need to understand them? That question turns out to be interesting regardless of whether you’re a technical writer, a developer, a developer advocate, or a support engineer.
The talks range widely. You’ll hear about information architecture. You’ll hear about accessibility in documentation, about documentation tooling, about building documentation culture, about how open source projects attract contributors through better docs. And occasionally you’ll hear a talk that’s mostly a careful, honest account of what someone tried and what didn’t work, which is often the most useful kind.
The WtD Slack community is active and specific in a way that’s increasingly rare. It has channels for every subfield: API docs, docs-as-code, localization, UX writing, job hunting. If you post a specific question, you get specific answers. The community also maintains a salary survey that’s become one of the more reliable data sources on technical writing compensation in the industry.
What stayed with me from speaking there was a simpler observation: the people who care most about documentation are often not the ones with “documentation” in their title. They’re developers who’ve been frustrated by bad docs and decided to fix them. They’re support engineers who’ve watched the same confusion repeat at scale. They’re product managers who’ve measured the drop-off in the onboarding flow and traced it back to a missing explanation.
Documentation quality is a distributed responsibility. WtD is the community for everyone who cares about docs :)