Re: Screen captures

Subject: Re: Screen captures
From: Gene Kim-Eng <techwr -at- genek -dot- com>
To: Jim Shaeffer <jlshaeffer -at- aol -dot- com>
Date: Mon, 11 Feb 2013 10:40:43 -0800

Looking at this strictly as a user, since my SW documenting experience is mostly in SW as something that operates HW, I like screen captures in printed docs so I can actually read them productively when I'm not in front of a screen with the SW running. Screencaps in online docs that are likely to be consulted while I have the SW up and running are generally a waste of screen real estate, except for images of small areas of a screen that show where to find things in a particularly chaotic UI. Which there are far too many of in the world.

Gene Kim-Eng

On 2/11/2013 9:59 AM, Jim Shaeffer wrote:

In my mumble-mumble years documenting software, the primary value of screen captures has been as signposts to reassure users that they and the documentation are still in synch. Screen captures let users know that they are on the same path as the guide and have not missed a step or been led astray.

STC Vice President Nicky Bleiel is giving a free webinar on best practices
for creating mobile help.

Learn more:


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Screen captures: From: Anonymous
Re: Screen captures: From: Jim Shaeffer

Previous by Author: RE: Do as I say, not as I do
Next by Author: Re: Recruiting dilemma
Previous by Thread: RE: Screen captures
Next by Thread: RE: Screen captures

What this post helpful? Share it with friends and colleagues:

Sponsored Ads