Top Banner
{ by Tom Johnson idratherbewriting.com Publishing strategies for API documentation STC Summit 2015 Columbus, Ohio @tomjohnson
30
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Publishing API documentation -- Presentation

{by Tom Johnsonidratherbewriting.com

Publishing strategies for API documentation

STC Summit 2015 Columbus, Ohio @tomjohnson

Page 2: Publishing API documentation -- Presentation

The variety of API docs

Page 3: Publishing API documentation -- Presentation

a. Guides

b. Tutorials

c. Reference

Breaking down API docs

Page 5: Publishing API documentation -- Presentation

b. Tutorial docs

Page 7: Publishing API documentation -- Presentation

• Resource description• Endpoint• Methods• Parameters• Request example• Response example• Status and error codes• Code samples

Reference sections

Page 8: Publishing API documentation -- Presentation

If developers will write …

Page 9: Publishing API documentation -- Presentation

Miredot – Java doc gen.

Page 10: Publishing API documentation -- Presentation

Github wikis

Page 11: Publishing API documentation -- Presentation

Source code to JSON

Scripts import JSON

Web CMS pushes JSON

into templates

Custom scripts

Page 12: Publishing API documentation -- Presentation

Swagger- Swagger- RAML- API Blueprint

Page 13: Publishing API documentation -- Presentation

API Blueprint and Apiary

- Mulesoft- Apigee- Apiary

Page 14: Publishing API documentation -- Presentation

RAML and Mulesoft

Page 15: Publishing API documentation -- Presentation

Static site gen. -- Jekyll

JekyllDocpadMiddleman Staticgen.com

Page 16: Publishing API documentation -- Presentation

Custom UX solutions

Page 17: Publishing API documentation -- Presentation

Readme.io

Readme.ioreadthedocs.com

Page 18: Publishing API documentation -- Presentation

readthedocs.com

Page 20: Publishing API documentation -- Presentation

API doc design patterns

Page 21: Publishing API documentation -- Presentation

1. Structure and templates

Page 23: Publishing API documentation -- Presentation

3. Lots of code samples

Page 25: Publishing API documentation -- Presentation

5. API Interactivity

Page 26: Publishing API documentation -- Presentation

Versioning

Translation

Authent-ication

Language switching

Challenging factors

Page 27: Publishing API documentation -- Presentation

Tools versus content

Page 28: Publishing API documentation -- Presentation

• Will developers be writing or contributing to the content?• Does your security group restrict you from using third-party

platforms to host documentation?• Do you have a budget to pay a third-party platform for

hosting?• Do you want to manage the web platform details yourself or

offload this onto another group/company?• How many endpoints do you have to document? How

structured is your content?• Should you push documentation from the source into your

documentation?• Does the documentation need be visible on the web, or does it

need to be private?• To what extent do you want customers to have a one-stop-

shopping experience — reading docs, logging support tickets, posting to forums, viewing news?

• Do you have UX resources to help you build a solution?

Questions to consider

Page 30: Publishing API documentation -- Presentation

Most images are screenshots linked to a webpage, but some are from Flickr and Vecteezy. Required attribution is as follows:

• Structure, https://flic.kr/p/oFD6MM Rafal Zych• Earth patterns. https://flic.kr/p/ssQqiL Evriel

Venefice• Dave’s Bike Tools, https://flic.kr/p/QMVMw Bri

Pettis• Vector icons from Vecteezy.com

Image credits