• °Ô½ÃÆÇ
  • ¼ÒÇÁÆ®
  • È£½ºÆÃ
  • °øµ¿±¸¸Å
  • À̺¥Æ®
  • ÆÃÇ÷¯½º
  • ¼³¹®Á¶»ç
  • »ý°¢µé
  • Àüüº¸±â


³×ƼÄÏÀ̶õ...

 
 

WCPPE Web Authoring Guidelines 1999.

Written by Joanne Woolley, Multi-media designer, WCPPE

and David J. Temple, Director of WCPPE

 

At the WCPPE, we encourage and openly endorse the development and full use of the World Wide Web. Electronic commerce is on the brink of explosion. It is almost vital nowadays to own a web site, at least one that lets the world know who are you are, where you are, what you sell, and how to contact you. It is almost as vital as a listing in the phone book.

Our aim is to promote the World Wide Web as an information resource, and to help our colleagues become information providers over the Internet. In doing this, we must ensure that we offer the best advice possible, although unfortunately advice is all we can offer. Time, experience, and most importantly trial and error has enabled us to put together this set of guidelines, which we hope will aid you in developing your own site. We appreciate that web site development demands your own imagination and creativity, but hopefully by following some of these simple rules, you will create your own site without making some of the mistakes we have all made in the past.

Note: When writing an HTML web page, you are designing a set of instructions that the viewers computer interprets to generate it's own page. There is no guarantee that the resultant page will be precisely what you designed. Because of this, it is vital that when designing on-line information, you must focus on the recipient much more than with print-based material.

 

Guideline's structure

 Planning your Web Site

  1. Define your outcomes
  2. Establish your audience
  3. Research
  4. Set Standards
  5. Maintenance
  6. Publicity

 

Building your Web site

  1. The HTML protocol
  2. Content
  3. Text
  4. Colour
  5. Images
  6. Width
  7. Frames
  8. Advanced HTML
  9. Keep it legal
  10. Make yourself searchable
  11. Restricted access

 

On Completion of your Site

  1. Test your pages
  2. Selling your site
  3. Maintenance

 

Planning your Web Site

Define your outcomes

  1. Determine your motive for wanting a web site; what are its objectives? Is it educational, an information resource, an advertising ploy etc? In a professional capacity you may find that a web site is needed to support departmental development plans.
  2. What do you expect to gain from hosting a site? A bigger clientele? Better use of the service you already offer? Happier regular customers? Are your expectations achievable?
  3. Is the site going to be cost effective? Is there a cheaper and more efficient way to disseminate information? Will people be genuinely interested in your site and will they use it?

 

Establish your audience

  1. Define your target audience. What will your visitors expect from the site and what are their needs? Be aware of any pre-conceived expectations your reader may have. Structure your site so that these needs are met.
  2. Think BIG! Despite your target audience, you should still aim to make your information available to as wide an audience as possible.
    Remember anyone anywhere in the world will be able to access your site, unless you have opted to restrict access
    (see later)

 

Research

  1. Value yourself. Study access figures of similar sites to yours to evaluate their usage - is it really worth spending all the time and effort on creating a site that is value-less?

  2. Review competitors web pages. Study sites of similar style, structure and content to the site you have in mind to design. Note what makes the web pages good and bad i.e.

    1. Funtionality - Does the page serve it's purpose? Is it printable? Do you leave the page feeling satisfied?
    2. Accessability - how easy were the pages to find? Has it got so many new gadgets that an older browser can not cope? Are there good links into the site from other relative resources? Is the URL a memorable size and structure?
    3. Navigation - Are there sufficient navigation tools? Can you always find what you are looking for? Were you constantly wondering how to get out of a page or how to jump back to a different topic?
    4. Content - Is the content legible, clear and intuitive? Is the content relevant to the title of the page, or was the title misleading? Was the content structured well, into well defined, understandable topics?

  3. Consider your platform. HTML pages must be viewable on as many browsers as possible. Most "text only" browsers have become redundant. Nontheless, when designing you must make provisions for all types of browser, for example by always ensuring that you have alternative text (<ALT>) for every image you display. This will also relate to the many people who tend to keep "images" switched off for faster down load time). In practice, Netscape and Microsoft Explorer now dominate the browser scene. However, each is available in many different versions, which may react differently to the same html code. Remember too, that web pages look different from machine to machine, so what looks great on a PC, may look dreadful on an Apple Macintosh and vice-versa.

 

Setting standards

You must be able to look objectively at your planned site and decide how you will assess it's quality. Ideally, the site should:

  1. Comply with a pre-defined "house style"
  2. Meet HTML validation standards
  3. Be consistent with good practice regarding web publishing
  4. Comply with netiquette.
  5. Be up-to-date and well maintained.

 

Maintenance

A maintenance plan is an important part of your over all strategy in developing your site. A well thought out site will need less maintenance than a poorly designed site. We will talk at greater length about how to maintain your site later in these guidelines, but at this stage you should at least be thinking about the following points:

  1. How is the site going to develop? Do you already have expansion plans? If so they must be accounted for in your maintenance strategy.
  2. Who will maintain this site?
  3. Will this task be added to their usual daily tasks and if so is this target achievable?
  4. Who is your back up 'maintainer' should something go drastically wrong in your regular maintainer's absence?
  5. How often will this site need to be maintained? Is it a daily task, or a monthly task etc?
  6. Allocate time slots for maintenance and stick to them. Allow for extra time for development and expansion.
  7. If maintenance is a problem then you should design your site around this.

 

Publicity

There isn't going to be an awful lot of point in creating a web site if you do not have a publicity strategy for marketing your site. You need to be thinking about where and how you are planning on advertising your site, and getting people interested in it. Read the later section 'Selling your site', for further information on publicising.

 

Building your Web Site

HTML Protocol

  1. Stick to recommended standards. The W3C (The World Wide Web Consortium) are an international industry consortium, which was founded in order to develop common protocols across the World Wide Web and promote its evolution and inter-operability.

    W3C produces what are known as "Recommendations" for HTML. These are specifications, developed by W3C working groups, and then voted in by Members of the Consortium. A W3C recommendation indicates that consensus has been reached among the Consortium Members that a specification is appropriate for widespread use and we are all advised to adhere to these standards for universal compatibility.

    HTML 4.01 is W3C's recommendation for the latest version of HTML, it supports the latest browsers and HTML tags and takes advantage of HTML's presentational features, but it also continues to support HTML 3.2. features, allowing those with older browsers to view pages successfully. (W3C recommendation revised on 24 April 1998)

    N.B. some browsers use unique tags. Try to avoid these, because other browsers may default and hence produce a flawed page.

    For more information about HTML standards, visit the W3C site at:

    //www.w3.org/

  2. Validate your HTML. Your web pages should always contain valid HTML, which will ensure that your pages will work universally on any browser. If you have followed the HTML standard set out by W3C then your pages should validate, but to be sure that your pages meet the required HTML standards you should always run your pages through an HTML checker. Most web authoring software will offer its own HTML standard checker, but if you are writing raw HTML you can use the validation service provided by W3C.

    //validator.w3.org/

  3. Design legible HTML. When you are writing raw HTML it should be structured so that it is readable. At some point, you or your colleagues will need to edit the web pages and will find it remarkably easier if the HTML is laid out neatly, and with spaces in appropriate, legible and logical places.

Also remember that people may want to look at your HTML from within their browser, and on many occasions copy it. There is unfortunately no simple way to stop this, and you may feel that displaying messy HTML will be a deterrent to potential HTML thieves!

 

html Primer

//www.gla.ac.uk:80/Clubs/WebSoc/primer/

 

 

The content and structure of the pages

  1. Design your content, don't just write it. You must remember that content counts, this is crucial. Most visitors spend less than ten seconds at your site unless you grab their attention straight away. It is a must that you provide solid information, effectively utilised artwork and well-maintained links. Making readers do two extra clicks before they find out what you have to say, will lose you three-quarters of your audience. You need to give your viewers a compelling reason to come back. The web contains millions of sites to see, and you definitely want yours to be one of them.

  2. Make the pages speak for themselves. The title of the page (situated in the <HEAD> tags) should be as self-explanatory as possible. This is the title that appears at the top of the browser window and is also the text that appears in the bookmarks/favourites list. Don't use abbreviations that are obvious to you and not to others; i.e. 'wsp'. Instead, label it fully, such as "Welsh School of Pharmacy Home Page".

  3. Make every page usable out of context. This is important so that a reader isn't lost when he comes in "through the back door". Make the contents of each page clear at the very top of the page, as many viewers will access your pages from search engines, and on many occasions by accident. If the page is untitled, or does not indicate it's content clearly, the reader is likely to exit.

  4. Each page should ideally contain a consistent 'top and tail' style scheme. The page should consist of:
    • A logo, or standard title at the top of each page, which is thematic over all pages.
    • An informative signature at the bottom of each page, signalling a contact name, telephone number, email address, job title and status of the person responsible for the page. e.g.

      This page is maintained by Joanne Woolley

      Multi-media Designer

      WCPPE

      Email:


    2004-01-24 00:31:59
    1556 ¹ø ÀÐÀ½
    ¢Ñ ·Î±×ÀÎ ÈÄ ÀÇ°ßÀ» ³²±â½Ç ¼ö ÀÖ½À´Ï´Ù
     Ä³½Ã¼±¹°





    365ch.com 128bit Valid HTML 4.01 Transitional and Valid CSS!
    ű×