#30807
HelpScribe Technical Communication offers tips on writing technical manuals, help authoring, software documentation, and managing a TC career.
HelpScribe (2008). Resources>TC>Technical Writing>Blogs
#31697
Technical Communication is a broad term which includes technical writing, instructional designing, graphics, website designing or any form of communication which helps in communicating the technical information in a simpler way to the targeted user. This also includes audio tapes, video films and micro clips.
Malik, Suman Lata. Tripod.com (2007). Resources>TC>Writing>Technical Writing
#19770
Instructor's Guide for The Bedford Handbook 
An electronic edition of the best-selling handbook by Diana Hacker, The Electronic Bedford Handbook 6.0 combines the comprehensive coverage and class-tested reference features of the text with the cutting-edge convenience of an e-book, resulting in an interactive e-handbook that serves both as a guide to research and writing and as a reference for the electronic age.
Hacker, Diana. Bedford-St. Martin's. Resources>Education>TC>Technical Writing
#29266
A weblog about technical documentation, training, and marketing materials.
Campbell, Caren Weiner and Barry Campbell. Knowledge Work. Resources>TC>Technical Writing>Blogs
#14148
Piccola Scuola di Scrittura Technica 
Risorse, trucchi e consigli per scrivere testi professionali corretti ed efficaci.
#28743
Tech Writer Voices is a podcast specifically intended for technical writers. Podcasts include all topics relevant to the profession of technical writing, from single sourcing to collaborating with SMEs.
Johnson, Tom H., Heidi Hansen and Keith Hoffman. Tech Writer Voices. Resources>TC>Technical Writing>Podcasts
#15009
In the belief that tech writers are sorely underutilized, as well as unappreciated, misunderstood and wrongly blamed, UnTechnical Press is sponsoring the creation of a Tech Writer's Manifesto. We don't expect it to be adopted by any organizations, but we want it to apply to as many individual tech writers as possible. This is what we want it to accomplish: * Let employers and those who contract with us know what our capabilities are and how we may be of value to them in ways they never knew. * Let development teams know how we can contribute to team dynamics and product development. * Let consumers know that we, as technical writers and other technical communicators, really want to provide them with excellent, readable, understandable manuals and other documentation, and how they can help us help them.
#24350
#18636
An annotated listing of online resources for technical writers.
#24719
A website that publishes numerous articles for technical communicators, journalists and documentation specialists.
George, Ginu. Technocrats (2004). Resources>TC>Writing>Technical Writing
#13364
What's in a Name? Guidelines for Naming Files
While file naming may seem like an insignificant detail, developing an intuitive, descriptive file naming system can help minimize file access and management challenges. What's more, developing such a file naming system--especially when a consistent system is not in place--can have added benefits, such as improving access through better searchability and browseability, and improving access for everyone who may, now or later, need to access project files. In this article, you'll find several tips and examples for naming files, which used individually or in combination, can help ease file access and management.
Hower, Sean. TECHWR-L (2002). Resources>TC>Computers and Writing
#32737
A blog about aspects of technical communication, with special focus on accessibility, quality (work/documentation/etc.) processes, writing, editing, usability, and technology.
