Documenters

The Documenters keep the knowledge findable. Where a Tinkerer’s pride is the working device on the bench and an Architect’s pride is the long view that admits no fashion, a Documenter’s pride is the record that survives both of them — the page a stranger lands on five years later when their own version of the same problem arrives.

This page is a living document. Section headings mirror the information architecture §5 list for /callings/[name].

What the calling is

A Documenter writes the repair guides, records the techniques, maintains the wikis, shoots the video tutorials, updates the README, and posts the teardown. The work is unglamorous and compounding: each clean record makes the next fix faster for someone who is not in the room. The discipline is capture — what is held in one head dies with that head; what is written down survives the death of the writer and the death of the device.

The Documenter accepts that some of their work will be wrong, will go out of date, and will be corrected by strangers — and that the alternative, not writing it down, is worse than being wrong in public.

Lineage

The named ancestors of this calling include the iFixit contributors who built the largest open repair-manual archive in the world; the technical writers who made manufacturer documentation legible to humans not on the company payroll; the archivists of obsolete platforms — the abandoned-OS librarians, the floppy-image curators, the people preserving forum threads before the host shutters; the hackerspace wiki gardeners who tend the inventory page and the laser cutter SOP and the membership rules; and every patient soul who has ever explained their work in public.

The lineage is not credential. It is example.

How to develop in the calling

This is a curriculum, not a credential. Nothing on this list is required. Each item is the kind of practice that, taken seriously over months and years, forms the eye and the hand of a Documenter.

• Write down the next thing you fix. Title, date, device, steps, what went wrong, what you would do differently. Photograph each step before disturbing it. Publish the result somewhere public, even if no one reads it. The practice is the curriculum.
• Adopt a wiki. Find a documentation surface that needs a gardener — an iFixit guide that’s wrong, a hackerspace inventory page that’s stale, a README that hasn’t been updated since the project began — and steward it for a season.
• Read the field’s standards. RFC 1925, The Pragmatic Programmer, the Diátaxis documentation framework, the iFixit Technical Writing Project style guide. Read them less for the rules than for the shape of attention.
• Practice the inverse pyramid. The reader who needs the third step is rarely the reader who needs the introduction. Write so that any single paragraph can stand on its own.
• Adopt one device, one technique, one tradition and become the public record-keeper for it. Depth beats breadth for the first decade.

What contribution looks like

Concrete examples of Documenter contribution to the Open Circuit and the wider commons:

• Writing repair walkthroughs for /library/repair — original work, clearly attributed, with the practitioner’s name, the device, the date, and the outcome.
• Maintaining sections of /library/reading — adding annotations to existing entries, proposing new ones with named reasoning, marking entries that have fallen out of print.
• Editing canonical documents through public proposals — Documenters often catch the typo, the broken cross-reference, the section that drifted out of parallel with another.
• Translating canonical or living documents — translation is documentation in another tongue.
• Contributing to iFixit, Repair Café International event documentation, the Internet Archive’s software collections, hackerspace wikis, or any of the long-running archival projects that hold the commons.

Practitioners who currently identify with this calling

[OPT-IN] — practitioners who name themselves Documenters may add themselves to this list by amendment, with whatever specificity they choose to share. The list is opt-in and never asked-for.