[This document can be acquired from a sub-directory coombspapers via anonymous FTP or COOMBSQUEST gopher at the Australian National University, Canberra on the node COOMBS.ANU.EDU.AU or from the ANU Soc.Sci.WWW Server at http://coombs.anu.edu.au/CoombsHome.html] The document's ftp filename and the full directory path are given in the coombspapers top level INDEX files] [This version: 4 October 1994] ----------------------------------------------------------------------- GOPHER DESIGN TIPS ----------------------------------------------------------------------- Date: Wed, 31 Aug 1994 22:43:59 -0500 (CDT) From: Gleason Sackman Subject: GOPHER> Design Tips for Gopher (fwd) To: net-happenings ---------- Forwarded message ---------- SENDER: david.riggins@tpoint.com Date: Wed, 31 Aug 94 20:40:02 -0500 Central Subject: DESIGN TIPS This document was created for another project I'm working on. Thought I'd share it with everyone. Some language was changed to make it a Gopher Jewels resource document. This replaces an earlier document and was developed with the assistance of Wayne McDilda, Texas Dept. of Information Resources. Use what you like and trash the rest. :-) David Riggins Gopher Jewels Project david.riggins@tpoint.com ----------------------------- cut ----------------------------------- ___________________________________________________________________ DESIGN TIPS FOR GOPHER ___________________________________________________________________ Your design should assume that every user knows nothing of your organization, or the technology you are using - including gopher and related services. Assume the user has no idea what they are doing and add documents to assist them. The four most important and time consuming aspects of any good site are: the organization of the information the quality of the information the names of your files and directories supporting documentation in each directory ___________________________________________________________________ Menu Presentation Standards The main menu should be limited to one page (18 options). Primary menus should be limited to one page Secondary menus should be limited to 2 pages Exceptions: well known lists such as states, counties, cities etc. Terminating menus can be as long as needed to cover the topic The first option should be "Welcome -- Press Enter key and READ THIS FIRST!" and include: why you have the gopher, what types of information it has, who the target audience is, who runs the gopher, how that person(s) can be contacted. Users don't care what version of gopher you are using. Create another area for technical information, and clearly indicate that's what it is. If you offer a help section (and you should) it should be option 2 on the main menu, or a sub-option of option 1. You can point to some good help documents at the Gopher Jewels gopher, under its option 1. Make sure you name all files and directories so they work well with key word searches. How you name things is VERY VERY important! Name all menu options with global searching in mind. DON'T point to raw file names...use .cap or .link (gopher+) to map better names for your options. Offer key word search of all menus on your gopher, and always place the search option as the last option on your menu(s). (arrow up from option one takes you to the last option) Rename all your pointers so the user knows who you are pointing to. Offer an option that tells users what is new at your site. Don't put information in an area that does not fit the topic. Stick to the topic! This is a common mistake on gophers. Identify what items are not in English. Identify all items that originate from your site. Don't try and build a subject tree of all categories of information. There are at least 26 good subject trees out there you can point to. Concentrate on the information your gopher was established to deliver. DON'T USE ABBREVIATIONS! Especially your organization's name!!! Indicate, in the option name, that the option is empty, or at least add a document that states the area is still under development. All main menu options should offer an about file that explains the items offered in that menu. About files are the first option in every sub-menu. About files can serve as site overview in option one by creating a directory of pointers to the about files in each directory of the gopher Most relevant information should be organized at top of menu Alphabetizing is not the desired method of organizing menu options All menus (when possible) should be noted (fill in Admin. field) Data repeated in more than one location should be named the same, so searches won't hit on it twice. Document Standards All documents should have a title, source and date. Indent 4 spaces on left and make right margin 68-70. Center titles and hang subtitles one space from left edge of page. Use underline vs dashes ________ --------- for lines. _________________________________________________________________________ GOPHER TEMPLATE 1. Welcome -- Press Enter key and READ THIS FIRST!/ 1. Getting Started. (brief help document on basic navigation in gopher menus) 2. Overview of XXXXX Menus/ (point to about files) 3. Who. (contact info) 4. What. (overview of menus) 5. Where. (location of site) 6. Why. (target group and reason for site) Note: The above options can be combined into one or two, however, getting started and overview should stand alone. 7. Legal - copyright and trademark notices 8. Disclaimer (we are not responsible for damages - use at your own risk) 2. Help 1. About the Help Area 2. ***** Specific Help/ 3. Gopher Help/ (general) 4. Training Resources/ 5. Internet Access Providers/ 6. Technical Area/ (complex information - not for average user) 1. About. 2. Software Versions. 3. Hardware. 4. Links to Technical Documentation for Gopher & FAQs/ 5. Usage Statistics/ 6. This Document. Note: Technical area can also be placed in option 1 or as a main menu option. 3. XXXXXXXX/ 4. XXXXXXXX/ | XXXXXXXX/ 11. XXXXXXXX/ 12. General Information About XXXXXX/ Documents that are related to the site. Annual reports, Legislative mandates, strategic plans, local supporters, credits, press releases, press bibliography and so on. 13. What's New at XXXX. 14. Tell Us How we Are Doing/ 1. About Tell Us How We Are Doing. (includes instructions for using the gopher comment feature) 2. Leave a comment?? 3. Archives of comments (optional) 15. Search XXXX document contents (WAIS)/ (optional) 1. About. 2. Search....(?) 16. Search XXXXX Menus By Key Word(s)? (Jughead) _________________________________________________________________________ Last Updated: 8-31-94 _________________________________________________________________________ ----------------------------------------------------------------------- end of file -- [SIMPLE MACHINES] --> gopher://beaker.mdns.org (via proxy) http://www.floodgap.com/gopher/gw.lite?gopher://beaker.mdns.org:70/11/ .