Six-week cohort · next intake 6 April

Write technical documentation people actually read.

A practical course for engineers and support leads who keep being asked to fix the docs. You will rewrite your own real pages, every week, with feedback.

Enrol for the April cohort

6 weeks · 3 hours a week · live sessions recorded

Who this is for

The reluctant owner

You inherited the docs because you wrote the feature. Now every question in support is somehow your fault.

The support lead

You answer the same six questions weekly and know a better page would end it.

The lone technical writer

You are the whole documentation team and you want a system, not more opinions.

Not for you if: you want a certificate without doing the writing. Every week has homework and it gets read out loud.

What we cover

  1. 1. Finding the real question

    Mining support tickets and search logs for what people actually needed.

    4 lessons · 1 assignment
  2. 2. The shape of a good page

    Task pages, reference pages, and knowing which one you are writing.

    5 lessons · 1 assignment
  3. 3. Writing the first sentence

    Openings that tell someone in ten words whether to keep reading.

    3 lessons · 1 assignment
  4. 4. Code examples that run

    Samples people can paste, plus how to keep them from rotting.

    4 lessons · 1 assignment
  5. 5. Structure at scale

    Navigation, naming and the discipline of deleting pages.

    4 lessons · 1 assignment
  6. 6. Keeping it alive

    Review cycles, ownership and metrics that are not pageviews.

    3 lessons · final project

Taught by Helena Vasquez

Twelve years writing and leading documentation, most recently for a developer platform with two million monthly readers. Before that, support engineering, which is where the opinions come from.

  • Rebuilt three developer documentation sites end to end
  • Trained 400+ engineers in workshops since 2019
  • Writes the Plain Technical newsletter, 26,000 readers

What people did with it

We cut our getting-started page from 3,000 words to 600 and new-user setup tickets dropped by half.

Tomas Berg, platform engineer

I finally had a reason to delete 80 pages. Nobody has missed one of them.

Nadia Farouk, technical writer

The support team now writes the first draft and I edit. That was not possible before this course.

Owen Pryce, support lead

April cohort

$690one payment

  • Six live sessions, recorded
  • Weekly written feedback on your own pages
  • Templates, checklists and a review rubric
  • Lifetime access to the cohort channel
Enrol now

Come to the first two sessions. If it is not for you, tell us and we refund it in full, no forms.