In this episode of the Cherryleaf Podcast, we look at Google’s announcement to support and promote rich, how-to structured data in Google Search and the Google Assistant. Transcript Hello and welcome to the latest episode of the Cherryleaf Podcast. In this episode we’re going to look at a recent announcement by Google (it was also on the Google Blog). We’ll provide a link… Read more »
Category: standards
Transcript from What’s the deal about structured content? Part 2/2
Below is a transcript of second half of our podcast episode What’s the deal about structured content? : So what’s come about is lots of different standards for the ways in which we can do structured writing. And you know the same about standards and toothbrushes? Everyone wants to use their own. No-one wants to use anybody… Read more »
Microsoft publishes its REST API Design Guidelines
Microsoft has published its REST API Design Guidelines to the API community. According to Gareth Jones, Principal API Architect, who announced its release: “The effort got started from hearing two key points of feedback from customers: It should be easier to get started with Microsoft APIs – Developers wanted to be able to run the curl tool… Read more »
Microsoft’s “No more robot speak” in action
Our post about how Microsoft is changing its writing style (Microsoft moves away from “robot speak” in its user documentation) generated a lot of interest, so I thought it might be useful to post some examples of it that we’ve spotted. These examples are from Office 365 Premium Edition.
Writing troubleshooting topics
It’s a fair bet that the introduction of the new Troubleshooting information type into the DITA 1.3 technical authoring standard will affect how all Technical Authors write troubleshooting topics, regardless of whether they use DITA or not. That’s because the proposed elements for troubleshooting topics make good sense, and it offers a standardised approach to writing… Read more »