Technical Issues (Website Design)

1. Navigation on KS1 pages
   There is evidence that children at younger ages should not be presented with an overwhelming range of choice. Therefore, we will limit the navigational options on the KS1 pages. On these pages a 'handset' top window could be used for navigation, showing circa 10 species only. The only other navigational option will be to return to the home page. Temporarily, for research purposes, the handset options will be placed on the main page pending tests on the utility and effectiveness of secondary windows. In the long run, teachers would be able to make their own selection of 12 species for the handset, to allow useful comparisons that are in context with their lessons. For research purposes in the interim, we will make the selection.
   10/97: PS, RME, PG

2. Glossary
   A Glossary will be added to the KS3 pages, with a separate window linked to the body text by standard textual links. This will define key words used in the text. At present it will only be applied on the KS3 education pages, but if successful the glossary could also be applied to other levels.
   10/97: PS, RME, PG

3. Images on education pages
   Decision: one large image will ALWAYS be downloaded on education pages. Options to download alternates might be provided by Javascript? Or should educational use be more prescriptive?
   10/97: RME, PG

4. Education pages technical assumptions
   Should we use the same full range of technologies on the education pages as the public pages? Will schools access match, exceed or fall short of public access? Temporarily assume can use Shockwave, Javascript, but more cautiously. Avoid frames for basic pages - go for tables instead (simpler, more universal, more reliable).
   9/97: PG, RME

5. Shockwave adopted for sound
   Lengthy experimentation with sound suggests streamed Real Audio not suitable for current server provision, also limits scope to deliver offline via CD-ROM. Shockwave Audio adopted as alternative, with file sizes for spoken voice readings of name at 22kHz, 8 bit sound, delivering fils sizes in the order of 15K. Also allows responsive buttons and future scope for greater interactivity. Problem: time Netscape takes to upload plug-in for Shockwave. Also question over whether browsers effectively cache the Shocked Audio.
   9/97: RME, PG

6. Image size
   Larger images take longer to load, but are essential to see an animal/plant/whatever properly. On many pages smaller images (thumbnails) are provided as a guide. These thumbnails are useful but size is an awkward consideration. Some small images lack clarity. Furthermore, photos of some species, especially reptiles, in their natural habitats are difficult to see due to their natural camuflage. As an experiment, pictures of species on white backgrounds are sometimes used, or their environments masked out of some pictures. However, this denies context for the species - we do not see it in its natural habitat.
   9/97: JW, PG, RME

7. Navigation on KS3/4 pages
   Design of KS3/4 pages takes into account suggestion (Linda Skinner) that navigational icons on educational pages need to be rather large. Experiments with arranging them along bottom of screen (see below) cause problems due to lack of consistency in user screen or browser window sizes. Experiments with frames and Javascript unsuccessful - could we 'recommend' a suitable window size and trust users to use it?
   9/97: PS, PG

8. Target computers
   Once again discussed issue of the target computers for the website, i.e PowerMac/Pentium or 386. Millions of colours or 256. Target web Browser, Javascript capability, Shockwave, Plugins Required. Resolved to attempt to ramp up tech spec of target computers, in which case definitely use JPEG and provide some MPEG formats (see below), but also adopt frames, Javascript secondary windows. Now assume users have Netscape Communicator or MS Explorer 4.
   9/97: RME, PG, JW

9. Image formats
   Given the growing acceptance of the JPEG format across the web, we resolved to move towards that image format to provide higher quality at a given pixel size vis a vis GIF. However, some GIFs will remain awhile!
   9/97: PG, JW, RME

10. Digital video formats
    MPEG video rpovides much smaller file size than the Quicktimes used to date, however takes a long time to encode and a powerful computer is needed to play back the files at a large frame rate. MPEG encoding/decoding also places limits on which machines can exploit this format. Suggest provide both Quicktime and MPEG file formats (the latter at larger frame sizes).
    8/97: JW, PG, RME

11. Digital finger-printing images
    Should we register the photograph suppliers with digimark? Should we digimark the current images? Current watermarking only via visible ARK logo. Long-time issue of possibly using image provider logo unresolved. On the one hand it would obscure/clutter the image. On the other, providers may prefer identification to be more visible.
    8/97: JW, RME, PG

12. Windows file naming conventions
    There is a clear need to experiment with the material off-line. Unfortunately, Windows file-naming conventions aren't the same as UNIX, and this makes it impossible to simply pass the data across on disk. All files (and therefore links) need to be compatible with both. This new convention to be adopted with the 1997 web site design.
    7/97: RME, PS

13. Colour schemes
    Any future version of the web site must adopt the ARKive identity colours - orange and blue.
    7/97: RME, PG

14. Navigational icons on education pages
    Evidence that computers tend to be arranged for adult use, even in classrooms. Children therefore look UP at screens. Navigational devices for use by children may be more effective if arranged along BOTTOM of screen.
    3/97: PS

    Text by Jonathon Whitehead, Richard Egan Last updated 21 October 1997

    ---

    Return to the top of the page