For AI agents: a documentation index is available at https://idratherbewriting.com/llms.txt. Markdown versions of all pages are available by appending .md to any page URL.

Search results

PodcastFAQs.com: A New Information Resource for Podcasters

by Tom Johnson on Jan 28, 2008
categories: technical-writing

PodcastFAQ.com is a new site developed by Todd Cochrane of the Geek News Central podcast and several other prominent podcasters from RawVoice. PodcastFAQ is intended as a much-needed information resource for podcasters.

PodcastFAQ

I was exploring the site yesterday and discovered several things I was unaware of:

PodcastFAQ.com also has a forum, which I hope will grow in participation. On the topic of podcast forums, the Podcasters List Google Group also has an active community of users.

I'm glad to see the creation of this site, PodcastFAQ, since podcasting involves a lot of technical information about audio engineering and creation that can be overwhelming at times. Equipment is expensive, and the methods for producing, editing, and publishing podcasts vary widely.

Sponsored

About Tom Johnson

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, agent skills, tech comm careers, and more. Check out my AI courses for more on the latest in AI and tech comm. If you're looking for info about documenting APIs, see my API documentation course.

If you're a technical writer and want to keep on top of the latest trends in tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me.

Finally, I want to note a couple of things. I usually write the first drafts of my posts myself and then use AI to improve accuracy, clarity, and detail in places, so my writing is a mix of human and AI. (Hopefully that's not too off-putting.) Also, the opinions I express on my blog are my own perspectives, not those of my employer.