Document 360: #1 Knowledge Base Software
Stay updated
Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 5,400+ subscribers

Search results

Document 360: #1 Knowledge Base Software

Tools FAQ for API doc site

by Tom Johnson on Feb 13, 2020 •
categories: api-doc

I've started adding responses to API doc questions to a FAQ page in my API doc course. I added three of the latest responses so far to questions. Since I anticipate a lot of questions around tools, I dedicated this page as the Tools FAQ.

Here are the initial questions I included:

  • Is it possible to author API documentation using DITA/XML or an XML editor (like Oxygen)? I saw your recommended list of tools in the Publishing API docs section, but it would be great if we could leverage existing tools.

  • We use Madcap Flare but document our APIs in Swagger. We’re considering dropping Flare and using Readme.com instead, which can import Swagger, but should we be looking at other tools? We also don’t document just APIs, but have protocols we document outside of the APIs too.

  • We’re considering using GitHub as our documentation CMS, but we’re unsure what it can support. Does it provide a documentation portal? HTML generation? An editor to add/update content? Themes? bi-directional sync with Git? Overall, what is the process flow if it allows documentation?

You can read my responses in the Tools FAQ.

By the way, I’m never quite sure what to call FAQ pages. They tend to be a catch-all for every question not answered elsewhere, not necessarily frequently asked questions. Some people despise FAQs, while others like them. However, I do think they are useful pages to hang a lot of questions not covered elsewhere.

follow us in feedly