Tips for Having Everything You Need.

Web Site Development Timeline
- from: http://www.coyotecom.com/webdevo/steps.html
by: Jayne Cravens, owner of Coyote Communications, a consulting service for not-for-profit and public sector organizations.

Overview of steps to get a simple, workable site up within just a few weeks; once this basic site is up and regularly maintained, advanced features, such as interactive or automated features can be developed and implemented.

1. Before your organization starts its Web development, most of its staff that deals directly with the public in any capacity (development, marketing and public relations, education and outreach services) needs access to the Internet. This means the organization needs:

- an Internet Service Provider (ISP)
- a main email address
- at least one computer in these departments that has access to this service provider (however, I would encourage you to get as many computers online as possible)

This may not mean that each staff member has an email address, but it should mean that anyone can access the agency'sWeb site, and other Web sites that relate to the organization's work. Also, make sure all staff understands the Web page approval process.

I strongly advise against proceeding on your Web development until after this minimal Internet access has been established. It would also be preferable, but not totally necessary, for all of agency's computers to be networked to one another before proceeding as well.

2. The appropriate staff member(s) should convert all available/appropriate information to .txt (text only) format, gather all available graphics, and store this information in a centralized place on the agency'scomputer system. Gathering the graphics for online use may mean calling whomever designed or printed the agency's publications and asking them to send you the graphics on disk (.gif format would be most preferred, but with the right software, you should be able to read any graphic file regardless of the computer system it was created on).
Estimated timing: 60 hours

3. When the majority of information has been download or gathered and converted to text, initial Web page construction could begin. Information should drive the design, so its best to create graphic-less pages during initial construction, to see how the information flows.
Estimated timing: 40 hours

4. After several text-only web pages have been completed, artwork design could begin (buttons, page headers, etc.). I advise fully designing 15 pages of the overall Web site (the 3timeless2 pages LINK would be best to start with), and then submit these pages to the appropriate staff for feedback.
Estimated timing: 40 hours

5. Once artwork and overall style is agreed upon, it could be added to the rest of the pages as they are developed, and the entire Web site could be completed. I recommend that all .gif files go into their own directory as well (see page 6 for suggested directory structure).
Estimated timing: 60 hours

6. Once the Web site is complete and approved, it should be uploaded to the chosen server.
Estimated timing: 5 hours

7. When the Web site is fully functioning from the server, the Web site address should be released to the staff and the board for "beta" testing for one week; staff and board should use the site and forward corrections/changes to the appropriate the agency's staff person to make.
Estimated timing: 5 working days

8. After the week of beta testing, the Web site should be marketed online to appropriate audiences LINK. Estimated timing: 10 - 20 hours 9.Also after the week of beta testing, the Web site should be marketed offline
Estimated timing: ongoing