Document 360: #1 Knowledge Base Software
Stay updated
Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 5,500+ subscribers. (See email archive here.)

Search results

Document 360: #1 Knowledge Base Software

Podcast -- Blogging for Technical Communicators Webinar (Part 1)

by Tom Johnson on Mar 3, 2009 •
categories: bloggingpodcasts

Download MP3 (to download, right-click and select Save Target As)
Length: 30 min.

This podcast is a recording of the Blogging for Technical Communicators webinar that I gave to the STC-Rocky Mountain chapter on February 19, 2009. I split the recording into two parts due to length. This first half covers the following four topics:

  • The Blog as an Expected Format
  • Why Bother to Blog?
  • Search Engine Optimization: The #1 Perceived Value of Blogging
  • The Most Difficult Part of Blogging: Generating Content Regularly

Here's the accompanying PowerPoint visual.

Note: After you listen to Part 1, be sure to continue to Part 2.

Links Mentioned in the Webinar

At some point during the webinar (either first or second part) I mentioned the following sites. Here are links to each:

Buy me a coffeeBuy me a coffee
Stay current with the latest in tech comm
Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 5,500+ subscribers. (See email archive here.)

follow us in feedly

About Tom Johnson

Tom Johnson

I'm a technical writer based in the San Francisco Bay area. In this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, visual communication, information architecture, writing techniques, plain language, tech comm careers, and more. Check out simplifying complexity and API documentation for some deep dives into these topics. If you're a technical writer and want to keep on top of the latest trends in the field, be sure to subscribe to email updates. You can also learn more about me or contact me.

Comments