I'm attending the #WriteTheDocs PDX this year. Here's what it's about.
Tags: opensource, documentation, virtualevents, a11y
Published: 2020-08-10 04:41:15

---
title: I'm attending the #WriteTheDocs PDX this year. Here's what it's about.
published: true
series: "#WriteTheDocs - Technical Documentation Insights"
description: A multi-part series sharing my experiences with attending #WriteTheDocs events in 2020.
tags: opensource, documentation, virtualevents, accessibility
cover_image: https://dev-to-uploads.s3.amazonaws.com/i/7p2zfsc10sfitli9mg61.png
---

# About #WriteTheDocs

It was over a year ago that one of my colleagues approached me and recommended I watch this talk. 

{% youtube Zvys6tUmEzg %}

Titling the talk "Draw the Docs", the speaker asked _"How can I make drawing part of my job?"_ and walked through a 5-step master plan to bring visual vocabularies into workflows in a technical ecosystem.

As a long-time sketchnoter, I was fascinated! I remember posting this tweet and thinking I needed to learn more about the conference called [WriteTheDocs](https://www.writethedocs.org/), run by a community of folks who cared about technical documentation.

{% twitter 1139774107476774912 %}

Fast forward a year, and this time the conference is being run as a virtual event over 3-days from August 9-11. Microsoft is one of the sponsors and I was fortunate that our team had access to a few tickets for anyone who wanted to attend. 

---

## Schedule

The conference this year is split into three days. 

> Aug 9 is [Writing Day]
(https://www.writethedocs.org/conf/portland/2020/writing-day/)

The focus is on _open source documentation sprints_. Anyone can bring a writing or documentation project and dedicate their day to working on it. Or, they can join one of the many [projects looking for contributors](https://www.writethedocs.org/conf/portland/2020/writing-day/) and spend time working on identified issues with support from project members.

I chose to participate in the Microsoft-run Accessibility Worksop and sprint, and it was incredible. Expect a follow-up post focused on just my Writing Day experiences soon!
{% twitter 1292493170509524994 %}

> [Aug 10](https://www.writethedocs.org/conf/portland/2020/schedule/#monday-august-10) and [Aug 11](https://www.writethedocs.org/conf/portland/2020/schedule/#tuesday-august-11) are Conference Days

I'm genuinely excited for these talks given the [caliber of speakers](https://www.writethedocs.org/conf/portland/2020/speakers/) and topics ranging from board games (as inspiration) to building accessible documentation and dealing with documentation debt! I hope to have write-ups for each day of the conference as we progress.

Also, as a first-time attendee, I was wondering what I should focus on and how I should engage, given this was a virtual conference. Huge props to the organizers for their [Welcome Wagon Guide](https://www.writethedocs.org/conf/portland/2020/welcome-wagon/) with handy links and recommendations! 

I'm excited for the [Unconference sessions!](https://www.writethedocs.org/conf/portland/2020/welcome-wagon/#unconference)

---

## Why does this matter?

Documentation is at the heart of technology understanding and adoption. Whether we are talking about platforms (docs for the services and APIs) or products (user manuals and troubleshooting), the _docs_ are the first line of engagement between the end user of that technology and the effective use of its capabilities.

As a community and technology advocate, I want to make it easier for everyone to translate awareness of a technology into actionable learning. It is my hope that learning the tips & tricks of technical writing - and engaging in conversations around how we can make learning easier and more inclusive for a global audience - will help me be a better educator and learner myself. I hope you all join me. 

---

## Technical Writing Resources 

Some resources to help your learning journey:

1. [Microsoft Style Writing Guide](https://docs.microsoft.com/en-us/style-guide/welcome/?WT.mc_id=writethedocs_devto-ninarasi) - a revamped guide for technology communication with [tips for effective voice](https://docs.microsoft.com/en-us/style-guide/top-10-tips-style-voice?WT.mc_id=writethedocs_devto-ninarasi) and collections like [accessibility terms](https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/accessibility-terms?WT.mc_id=writethedocs_devto-ninarasi) that make docs more inclusive.

2. [Google Technical Writing Courses](https://developers.google.com/tech-writing) - free self-paced courses that won't take more than a day or so to review.

3. [Google Style Guide](https://developers.google.com/style) provides a set of editorial guidelines for anyone writing developer documentation for Google-related projects.

4. [Mozilla: How to do an editorial review](https://wiki.developer.mozilla.org/en-US/docs/MDN/Contribute/Howto/Do_an_editorial_review)

5. [Wikipedia: List of Style Guides](https://en.wikipedia.org/wiki/List_of_style_guides) - a growing list of writing style guides spanning muliple industries (including tech)

6. [Community Writer Programs](https://github.com/malgamves/CommunityWriterPrograms) - a repo listing developer community writer programs (and more) that will pay for good content.


## Calls To Action 
I'll update this with more resources as I go. If you find this area interesting, consider taking some of these actions:

* Bookmark [this post](https://dev.to/azure/i-m-attending-the-writethedocs-pdx-this-year-here-s-what-it-s-about-3f8g) 👉🏽 get resource updates.
* Follow [#documentation](https://dev.to/t/documentation) 👉🏽 read posts on documentation
* Follow [#virtualevents](https://dev.to/t/virtualevents) 👉🏽 get virtual event recaps
* Browse [#writethedocs](https://twitter.com/search?q=writethedocs&src=typed_query&f=live) 👉🏽 twitter discussions