RE: The humbling reality of writing multi-page articles

Subject: RE: The humbling reality of writing multi-page articles
From: Michele Marques <msmarques -at- rogers -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 11 Sep 2002 07:33:51 -0400


Darren Barefoot writes:

However, in some usability book
somewhere I read that it was good practice not to permit people to
scroll more than a couple of "screens" past their position at the top of
the page.

I believe that this is for one of two reasons:

(1) Your reader might not notice that there is a need to scroll... in which case you want everything (or at least everything important) to fit on one screen. In this case, you would want smaller chunks. Or design your page/article so that people don't think they got to the end early... yes they can always look at the scroll bar, but there are sometimes other clues that people use to tell they've reached the bottom. This probably isn't an issue in an article but more in a front page or index type page - for example if the page is divided into roughly screen-sized areas, users might not realize there is anything below the first screen.

(2) Many people on the web don't want to sit around reading page after page. In this case having a "next" button is just as bad as scrolling ... instead you would want to break your article into logical smaller chunks and set up some form of hypertext navigation - so that people can get to the specific type of information they want right away.

- Michele Marques
msmarques -at- rogers -dot- com
http://members.rogers.com/msmarques



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at http://www.ehelp.com/techwr-l

Absolutely FREE! FrameMaker/Win 6 & 7 Express Customization (v3):
Quick-access buttons & keys to common functions, char tag/font drop-down
lists, charset browser, QRef guides & much more: http://www.microtype.com/2

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.



Previous by Author: Re: Frame&SGML: looking for opinions of current users
Next by Author: RE: context sensitive help in .NET
Previous by Thread: Re:The humbling reality of writing multi-page articles
Next by Thread: RE: The humbling reality of writing multi-page articles


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


Sponsored Ads
http://www.techwr-l.com/archives/0209/techwhirl-0209-00368.html
www.techwr-l.com
crawl=CC-MAIN-2019-09
24517
application/http; msgtype=response
sha1:PT6BOBY5XTCFC7DL6Y4FZGQTC556JSES
<urn:uuid:669231ba-284f-4140-ac5f-6820a53e53f8>
2019-02-15T19:22:26Z
184.106.92.169
text/html
sha1:RBGWADWFE2XTKYQLLJ3GDWDI42IGUCLH
<urn:uuid:237ccbd5-8f6b-4d10-b378-63f3bebc7293>
http://www.techwr-l.com/archives/0209/techwhirl-0209-00368.html
response
<urn:uuid:1d7b240d-e36f-4bc9-9e9e-f2bbe20415a4>
isPartOf: CC-MAIN-2019-09
publisher: Common Crawl
description: Wide crawl of the web for February 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-141-122-116.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/