authoring | Just Write Click

December 10, 2009 by annegentle

FLOSS Manuals interview for the Puget Sound STC chapter newsletter

Robert Reynolds contacted me requesting an interview for the STC Puget Sound chapter newsletter. It was published in PDF form, Writing for Free/Libre Open Source Software, but with permission, I’m using it for a blog entry as well. Thanks again, Robert! Writing for Free/Libre Open Source Software By Robert Reynolds When Tomas Krag needed a […]

November 30, 2009 by annegentle

Collaborative authoring – tools and costs

I’ve been working on some collaborative authoring scenarios for our Agile teams – we’re going from 5 people to 47 people in total who could author external or internal documentation within our two week sprints. Turns out, we likely represent some trends in the enterprise – Forrester just released a report about benchmarking your collaboration […]

« Previous Page

I’ve been thinking a lot about developer support at Cisco recently, especially for the way the world works today with multiple cloud providers. This post is a re-publish of my talk from over five years ago, but the techniques and tools for listening and helping others are still true today. At Rackspace, we watched several […]

Cisco DevNet is our developer program for outreach, education, and tools for developers at Cisco. From the beginning, the team has had a vision for how to run a developer program. Customers are first, and the team implements what Cisco customers need for automation, configuration, and deployment of our various offerings. Plus, the DevNet team […]

I had a great talk with Ellis Pratt of Cherryleaf Technical Writing consulting last week. Here are the show notes, full of links to all the topics we covered. Podcasts are great fun to listen to and participate in, if a bit nerve-wracking to think on your feet and make sure you answer questions succinctly […]

At the beginning of this year, I worked hard to summarize my thoughts on API documentation, continuous publishing, and technical accuracy for developer documentation. The result is an article on InfoQ.com, edited by Deepak Nadig, who also was forward-thinking in having me speak to a few teams at Intuit about API documentation coupled with code. Always […]