View Single Post
  #8   Spotlight this post!  
Unread 15-10-2003, 16:44
KenWittlief KenWittlief is offline
.
no team
Team Role: Engineer
 
Join Date: Mar 2003
Location: Rochester, NY
Posts: 4,213
KenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond repute
I thinkyou are off to a good start. get a clear idea in your head what the purpose of the website is (other than having a cool website)

you can easily apply the engineering design cycle to this project:

1. analysis the problem - what problem are you trying to solve by creating this website? other teams need to be able to reach you? team members need a place to get inforamtion about schedule, dates, important event. promote the team to possible sponsors... once you know what problems you are trying to solve (write them down) then:

2. decide how to solve that problem - what information do you want to communicate? People names? school address? phone numbers? email addresses? Do you want a monthly calender of events or a list of dates and times? do you want a place where your team can post photos? ask questions (forum)? who should be allowed to post and who should be allowed to access? once you have figured out the how then:

3. you can start designing and implementing - this would be where you would start writing HTML and creating pages, and links, putting it up and testing it. As you build your site you can then:

4. test and debug it - ask other people to access the functions, to try to find information, try to post stuff, and provide a way for them to communcate with you when they cant find something, or make it work

BTW, I think usfirst.org has a link page to team websites. Browsing other teams websites is a great way to get ideas for your own. Almost all of them have contact information, so if you see something you want to implement on your site, ask them how they did it. Most people will be glad to tell you.

Last edited by KenWittlief : 15-10-2003 at 16:47.