Articles

Where does technical documentation stand with agile development methods? Watch and read about the talk Rob Woodgate (@agiledoc) did at the Write the Docs London-GDS mini conference on the practice of agile documentation.

Developer portals are important for your API's adoption and support. They are also a trust signal: a well designed and actively maintained developer portal shows that an organization is investing in its APIs. It helps convince developers that they can rely on them. In this post I’ll zoom in on the trust signals business model, partner policy, API quality, API uptime status, versioning policy, documentation and developer portal production quality.

At the API days in London, I gave a presentation about developer portals. In it I shared mental models and frameworks that I think can help improve the quality of a developer portal: I decided to write 6 dedicated blog posts about what I discussed.

Without proper documentation, an API team will spend countless hours on workshops, trainings and support. In this talk, presented at Apigee’s API Tech Forum in Amsterdam, Kristof Van Tomme explored 7 frameworks to help you build better API Developer Portals.

Kristof Van Tomme presented an evolved version of his "AI the docs!” talk at CIDM's European DITA conference in Munich, 2016 November 14-15. This time with the subtitle “Conversational UI, Embedded Help and Artificial Help. A fertile ground for minimalism and DITA".

Technical writer teams are asked the impossible: chronically understaffed, fulfill growing expectations, while dealing with the disruptions of a barrage of technological innovations. Technology however doesn’t need to be a curse, it could be a blessing: new technologies could also be used to help technical writers. In this series I want explore how artificial intelligence and new/rediscovered interaction models for software documentation could redefine technical writing and its deliverables. Part 4: Repeating Clippy’s mistakes with Walkthroughs Learning from Clippy’s mistakes. How can we define proactive support? How can we avoid repeating Clippy’s mistakes?