Planning A Website

Where Do I Start?

Creating a website can be a daunting proposition when you are looking at the whole process at once. The purpose of this page is to present guidelines that will help you break that process into these manageable tasks: Planning, Developing, and Deploying.

Resources

• ATUS Web Services can assist at the beginning of your project to determine the best technology for your needs.
• Templates provided by ATUS will allow you to focus on your content rather than design.
• Web Resources – There are numerous sites on the internet that give advice on how to create websites. Two sites that ATUS recommends are:
  • Web3 Schools
  • Web Style Guide

Planning The Site

First, look at other sites that have a similar purpose. Focus on the content, and how easy or difficult it is to find information. Does the navigation make sense? Is the content relevant? From this evaluation you can learn what does and does not work in a website.

Your Website Blueprint

A website blueprint is a set of documents, including drawings, that describe all of the essential information about the site.

One of the keys to success in developing a website is to document the results of all of your tasks. We recommend keeping a directory on your computer for everything related to your site. This directory should contain, at a minimum, the documents described below.

Blueprint Document 1- Requirements Specification

• What are your goals in creating this website, what overall information do you want to convey?
• Who is your audience? Students, prospective students, faculty, staff, community, or a combination of two or more of these? What will be their goals in using your website?
• Are there different goals for different audiences? If so, what are the goals for each?
• Does the written content for your site already exist, or will someone be creating it?
• If the content exists, how and where is it currently stored?
• How often does the content change?
• Are there constraints on the information you want to display? For example, a page on this website should only be visible to students enrolled in a specific course.
• What interaction do you need between your site and its users? Do you have a database from which you want to extract and display information? Do you have forms that site visitors will need to complete?

Blueprint Document 2 - Site Specification

• What technology is available, and how will it be used?
• Who will manage the project?
• Who will create the pages?
• Who will maintain the site?
• What will happen if one of these people above is no longer available?
• What will be the approval and upload process for future changes?
• What is the time frame for development?
• What special allocations are needed so you have a realistic timeframe? Example: If you have students working on a project, remember finals week and breaks.

Blueprint Document 3 - Site Layout

• Gather all of your content, and organize it into categories. Determine the primary topics your website will cover and how your content fits into those topics.
• Look over your content with the eye of a user. If you were a user, where would your expect to find each piece of information?
  • Standard Content Areas. Most sites have standard content (About Us, Contact Us)
  • General Content Areas. Divide your content into broad general areas. These areas will become the secondary pages on your site.
  • Miscellaneous. Some content does not fit into general areas. Often this content is placed into a catch-all area, or you may need to review your general areas.
• Create a drawing using pencil and paper, or a visual tool such as MS Visio, to lay out all of the content within your site.
• When your layout is complete, sketch in any images and major page elements that your want to use to enhance your pages.
  • Keep images small and visually effective. Images take up space, which can mean longer download time for people using your site. Be sure your images contribute to both the look and the information of your site. For tips in using graphics, see ATUS Web Graphics page or our tips on using photoshop.
  • IMPORTANT NOTE: You must have the rights to any images that you use on your site. Copyright law requires that you obtain permission to use any images that are not in the "public domain." There are many ways of obtaining free, non-copyright images. If you have questions about image rights, start with the image information here

Developing The Site

Once you have finished the planning phase, it is time to create the pages that will make up the site.

If you do not currently have a website space, contact ATUS Web Services to have space set up for you. Your content will determine the server on which your site is located.

The recommended tools for development are Adobe Dreamweaver or Adobe Contribute. ATUS Web Services will help you determine which is best for you to use. Contact ATUS Software Services to obtain licenses and software at your desktop.

If you are not experienced in the authoring tool(s) that are recommended, check the WWU Training Site for upcoming classes on Dreamweaver and Contribute.

No matter which server hosts your site, we highly recommend developing your site on your local computer drive. You can store completed pages on the local hard drive, or your University U: Drive (MyWeb) . Once the site is completed, it can then be deployed to the server.

Western strives to assure that web sites are accessible to all. Please review the pages on accessibility and compliance to be sure you follow the guidelines that will enable all users to benefit from your site.

There are common elements that should be on every page of your site.

• Specify the title of each page in your site. This is done within the <title></title> tag in the header of the page, and is displayed in the blue bar at the very top of the window.
• Every page must have, at a minimum, a link to the home page of the site. Because of the way search engines (such as Google) work, a user is very likely to enter your site at a low level page. If there is no way for the user to get into the rest of your site, they are lost.
• A contact name and email or phone, should be visible on every page. In the ATUS Templates, this is part of the footer.
• Provide a clearly visible date that the page was last updated. If you save your files as .shtml the date can be automatically placed on your page with the following code:

  <!--#config timefmt="%m.%d.%Y" -->
  <!--#echo var="LAST_MODIFIED"-->

• Within the Header Section of the page, the following information should be placed in a commented area:
  • The person, department, or entity that owns the site.
  • The author, or contact person for the site.
  • An email or phone number for the author.
  • The date the page was created
• Each page should have a link to Western's Home Page. If a user comes in at a low level page, and finds this is not where she wants to be, an easy link to both the home page of your site and the home page of the University will be helpful.

Deploying The Site

How to deploy (publish) your site will depend on the server that has been assigned. Contact ATUS Web Services if you have any questions on how to publish your site to the server.