You can read the event details on the STC San Francisco site.
Here’s the description:
Beyond mere endpoint reference — the overlooked content in API documentation
Most discussions about API documentation center on the reference content — the endpoints, parameters, sample requests, and responses, and so on. But actually, the reference docs make up only a fraction of the total documentation related to an API. API documentation also includes how-to topics, tutorials, and other conceptual information. In this presentation, we’ll dive into the non-reference content that is typically found in API documentation. Some of these non-reference sections include the following:
- API Overview
- Getting started with the API
- Hello World tutorial
- Authorization and authentication
- Status and error codes
- Rate limiting and thresholds
- Code samples and tutorials
- SDK and sample apps
- Quick reference for the endpoints
Here’s a little more detail of what we’ll cover with these topics:
How-to topics. When it comes to documenting common tasks (the how-to topics in documentation), API docs pose unique challenges for technical writers. The common paradigm of providing step-by-step instructions for achieving a goal doesn’t always come so easily with APIs. The endpoints can often be used in innumerable ways and combinations to support a variety of outcomes and purposes. As such, how do you go about creating documentation around specific tasks? When the tasks involve assembling chunks of code, is step-by-step the right approach? In what scenarios would you provide the code up front followed by lengthy explanations or inline comments?
Hello World tutorials The Hello World tutorial is one of the most common topics for getting started. But this kind of tutorial varies significantly from the traditional task-based topics in regular documentation. What should a Hello World tutorial cover? What is an acceptable “Time to Hello World?” And how can you accelerate the success of this key tutorial without getting bogged down in lengthy explanations of authorization and configuration?
Sample apps and SDKs. Although most APIs are language agnostic, you often provide client SDKs in specific programming languages, such as Java or C++. A single API might have 3-4 SDKs, including implementations for Android and iOS apps. How should technical writers document these sample apps, especially when they’re in programming languages the tech writer doesn’t know? Should you document a sample app with inline code comments?
The event details are available on the STC SF site.
Workday San Francisco
160 Spear Street, Suite 1700 (between Mission and Howard)
San Francisco, CA 94105
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. Topics I write about on this blog include the following technical communication topics: Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, and certificate programs. I'm interested in information design, API documentation, visual communication, information architecture and findability, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.