tl;dr: Developer Hub (www.developerhub.io) is a new product that makes it easy to create documentation in minutes. It is clean, has core features, and is headed in the right direction.
Developer Hub is a new documentation product that clearly aims to get you writing and publishing quickly and easily. It succeeds. Within seconds of sitting down to the website, you’ll be creating instantly available documentation. With no need to build, convert, or template your docs, this is SaaS publishing at its easiest.
Developer Hub has a simple and intuitive WYSIWYG editor, which means anybody can use it. Adding an image or a code block is as simple as a mouse click. The control panel is simple and reasonably intuitive. As a result, tasks like creating a new version from an existing version are also easy.
You get basic white-labeling options: you can customize the color scheme, logo, and favicon. Obviously this customization will not be enough for some enterprises. For most of us looking to just get up and running, it’s plenty.
The output is clean and simple.
You can play with the little mini docs demo I made: API Ambassador Demo Docs.
Developer Hub is a turnkey SaaS docs portal for small scale documentation projects. As indicated by the code block feature and, well, the name, this product clearly has an eye toward products that include code samples. It could be used easily for other small documentatio projects. Other such products and services include:
These products are all SaaS docs portals.
I distinguish Developer Hub and its competition from products such as Adobe RoboHelp, Madcap Flare, and OxygenXML Editor. The key distinctions are platform, scale, and end product. Developer Hub is SaaS. These products are enterprise installations. Developer Hub helps smaller documentation projects through their life cycle. These products cope with thousands of documents across multiple projects and are overkill and have too much overhead for smaller projects. Developer Hub provides a live website as output. Those products support multiple export and output paths.
Paligo is in some ways the closest. Its UI is perhaps most similar to Developer Hub’s. In reality, though, Paligo is an XML content authoring tool and probably more akin to OxygenXML for practical purposes. Its key value offering is single-source multi-channel authoring.
Developer Hub probably shouldn’t get into multi-channel output at this point. It’s for a developer audience mainly and for that purpose can stick to the web and really dig into easy web docs authoring. Its team can really get into that fight by adding some single-source magic.
Make formatting controls a bit more obvious: It’s probably me. The formatting controls weren’t obvious to me, but they are there. Once you figure them out or guess, they do make sense, so I’m not sure something better is really possible. Just something for the team to consider.
Snippets and variables for easy single-source writing: Writers, like coders, often want to reuse blocks of code. Very often, they want to be able to edit this blocks in one place and have the edits mirrored in the other instances. We usually call thse blocks ‘snippets’. Variables allow users to insert values like current year that are updated at build or display time. Both snippets and variables are a common approach to keeping content fresh and consistent. In the case of either snippets or variables, the team will need to pay careful attention to how styling is applied: whether from the source, the referring location, or some cascading approach.
Internal references: It would be great to have hyperlinks within the documentation automatically updated in the event that a page’s URL or name changes.
Swagger integration: The dream here is a fancy and configurable UI for OpenAPI/Swagger documentation built into the product. The API reference could be a stand-alone page or it could be inserted into existing docs. The ability to directly edit the HTML of a page would provide a short-term or less dreamy approach to this enhancement.
I suggest a basic tier of use for free with the product scaling along with customers’ needs and ability to pay.
I suggest the DeveloperHub team charge for: additional users, additional customizations, additional plugins, bulk import/export or maybe import/export at a data level.
Another service to consider supplying and charging for: an embeddable HTML element with supporting CSS/JS that does a quick, autocomplete/suggested-completion query of the documentation. Content developers can embed such an element in, among other places, customer support request pages.
- Technical writing trade shows, associations, and forums seem a pretty obvious forum for getting the word out.