This post provides a bit of history about hypertext and discusses different options for displaying hyperlinks. It also seeks input from readers about whether full URLs (hyperlinks) are useful and their preferences for how URLs display.

Having clearly defined requirements at the start of a project is extremely important. Requirements help establish and maintain a solid target throughout a project, help minimize wasted time and frustration, and can help ensure an organization maximizes its return on investment. This document contains suggested steps for discovering and defining business requirements.

Gathering information for a writing assignment can be a very straightforward process. You are given (or pointed to) resources and collateral that provide you with product or project background, and you begin your investigation. Sometimes, however, when there just isn’t enough information to work with, you will likely need to interview a subject-matter expert (SME) [...]

Technical editor, John Cobb, shares his ghastly experience with projects involving Scope Creep. Just in time for Halloween, the following blog post includes five tips on how to avoid scary technical documentation scope creep.

Learn a cool tip for getting all the TechEd presentation content from the TechEd blog. A re-posted tip from the TechEd Team.

Steve Wacker explains the importance of having effective communication skills with subject matter experts and clients when it comes to writing technical documentation.

This post takes a poke or two at those who maim the language through verbicide as well as those who worry about how language evolves. It also meanders a bit into the world of puns and malapropisms but still manages to find its way home.

Steve Wacker, a technical documentation writer and editor at Wadeware, shares 5 good reasons to use a style guide when developing technical content.