Podcast: Help Authoring with Doc-To-Help 2009, Interview with Nicky Bleiel
Listen here:
ComponentOne recently released Doc-To-Help 2009, which introduces a complete redesign of their user interface. In this podcast, I talk with Nicky Bleiel, who works for ComponentOne, in depth about Doc-To-Help. Nicky has been a technical communicator for fourteen years and is now a director at large for the STC. I've met Nicky several times at Doc Train and STC conferences, and have interviewed her for other podcasts about web 2.0 and the STC.
This podcast is sponsored by ComponentOne, the makers of Doc-To-Help . It's one of my first sponsored podcasts, but even though it's sponsored, I've tried to keep my same interviewing style.
In this podcast, we focus exclusively on Doc-To-Help. Specifically, we talk about the following:
- Help outputs available from Doc-To-Help
- Flexibility in choosing your authoring editor
- Doc-To-Help's new ribbon-based interface
- Team authoring in Doc-To-Help, including file check-in and check-out
- Dynamic help controls available
- A sandcastle plugin for SDK and API writers
- The appeal of the technical communication field
We also cover a few other topics, such as Doc-To-Help's approach to DITA and Web 2.0.
To contact Nicky, send her an email at [email protected]. Also, feel free to drop me a line at [email protected].
About Tom Johnson
I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.
If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.