Why so little focus on API doc at tech comm conferences?
Either I’m becoming more distanced from mainstream tech comm topics, or else tech comm conferences are veering away from trending topics. I can’t decide who is moving off course.
I’m interested in API documentation. It seems like API documentation is one of the hottest trends in the San Francisco Bay area and other IT hubs as well.
And yet, in browsing the agenda of the current conferences this season — Lavacon, Information Development World, and Tech Comm UK — topics related to API documentation are virtually non-existent. There’s maybe one workshop and one presentation related to API doc at a couple of the conferences, but that’s it. Hmmm.
The tracks for Info Development World are as follows:
- DITA summit
- Software localization summit
- Content management
- Content matters
- Content strategy
- Medical device summit
- Content matters
- Language and culture
- Content engineering
- Content marketing
The tracks for Lavacon are as follows:
- Tools and Technology
- User Experience
- Management and Governance
- Content Strategy
- Content Production
Tech Comm UK doesn’t seem to have tracks, but in looking over the sessions, I didn’t see anything API related.
The tracks for the upcoming STC Summit are as follows:
- Profession and Promotion
- Graphics and illustrations
- Management/Leadership
- Writing/Communication
- Tools/Technology
- Training/Research
Interestingly, with the STC Summit, “API documentation” is listed as a possible topic for the Writing/Communication track, rather than being its own separate track (as it was last year). For other conferences, it could be that API doc is a sub-category in one of the other main tracks, but I don’t see any sessions focused on APIs there either.
I’m not downplaying these “mainstream” topics (localization, content strategy, DITA, etc.). They’re all good and relevant. But I would’ve thought API documentation topics might have a larger presence at tech writer conferences.
It could be that API doc is mostly a Bay area trend, and not nearly as common outside this area.
To really assess things, I’d need to look at job descriptions across the US (globally would be even better, but an increase in scope) and analyze how many tech writer jobs include API documentation. If API doc is truly a nationwide trend in tech writer job requirements, then I could better gauge whether API doc is a small sub-specialization within our field, hardly worthy of major attention at conferences, or whether conferences are out of alignment with trends for API doc skills.
What do you think? Approximately what percentage of tech writer jobs in your area include API documentation as a task or requirement?
Even if 5% of job descriptions include a focus on API doc, that’s still relatively on par with DITA usage. And given DITA’s attention at conferences, API doc should be equally visible. The difference is that DITA is the tech comm vendor’s favorite problem to solve. But almost no tech comm tools (at least those advertised at tech comm conferences) accommodate API doc.
If you’re thinking of submitting a proposal to the STC Summit in Anaheim next year, consider including a focus on API doc. Proposals are due October 5.
About Tom Johnson
I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.
If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.