1 / 23

ÜberBots 2010-2011 Website Proposal

ÜberBots 2010-2011 Website Proposal. ÜberBots Website Team. Goals. 2011 FIRST Website Award Effective Communication Easy to update Easy to access That this will be the last website we need to make for a long time. Focuses. Modular Integrated Compliant Handicap Accessible

drea
Télécharger la présentation

ÜberBots 2010-2011 Website Proposal

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ÜberBots 2010-2011Website Proposal • ÜberBots Website Team

  2. Goals • 2011 FIRST Website Award • Effective Communication • Easy to update • Easy to access • That this will be the last website we need to make for a long time

  3. Focuses • Modular • Integrated • Compliant • Handicap Accessible • Transparent / Simple • Sexy

  4. Modular • Current website, each page is individually coded, code scattered all over • Individually coded › Programmer needed to make new pages • Basically, current system doesn’t work • If pages made from modules (building blocks), “it will be easier to fix bugs, keep compliance, keep uniformity, prevent errors, make editing easier, make coding simpler, and enhance the browsing experience.” - Matt Howard, ÜberBots Forums

  5. Integrated • Integration in forums • One set of credentials • Simplify code, increase efficiency • Force people to use forums • Link calendar events • Integration with different websites and technologies • Help people stay connected with us • Make videos faster by using YouTube servers • YouTube, Twitter, Facebook, RSS, iCal

  6. Compliant • W3C (World Wide Web Consortium) defines web standards • FIRST Website Judges want compliance to standards • 1 + 2 = We need a compliant website • Website needs to look same and function same in IE, Firefox, Chrome, and Safari • RSS and iCal of website need to work

  7. Handicap Accessible • Handicap Accessibility focus of Web 2.0, W3C, and FIRST Judges • Blind, vision-impaired, deaf • Specific things we must do • Text size, captions in video, plain text vs images or Flash • Requires time & effort

  8. Transparent/Simple • Well organized site structure and hierarchy • Site map - helps users and Google • Breadcrumbs - Shows where page is relative to home“Home > Robots > Striker” • Layout should be intuitive and simple • Simple URLs “http://www.uberbots.org/o/robots/striker” Figure 1-1: Simple

  9. Russian Airline Ad

  10. Sexy • Not literally (skimpy clothing, suggestive images) • Website needs to be ascetically pleasing and attractive to user • Help for website award and keep users drawn in • Requires assistance of an “artist” (Matt & other) • Achievable through use of skins

  11. CMS & Maintenance • Re: Management Team • (That’s You)

  12. What is CMS? • CMS - content management system • means a way of editing content on website • current system is very limited and hard to use

  13. Intro to OmniPage™ System • Way of obtaining modularity “building blocks” • Will separate code & scripting from content • Anyone (even Ameya) will be able to edit almost any part of the page • Includes text, calendar, uploading images, Tweets, creating new pages, making users admins, sending out emails, page titles

  14. How do we use it? • If logged in as administrator, just click the edit button in the corner of window, everything becomes editable • To rearrange parts of page (modules), drag and drop • 95% of website will be editable by people with no coding experience

  15. Different Modules • Website will have dozens of types of modules to create interactive, rich content • Simple BBCode module that people are familiar with • Calendar module, picture module, news feed module, html module, php module, etc.

  16. Closings

  17. Other Things We Need to Win • Documentation - a page or section about how the website was made • Basic things - team number, link to FIRST website, sponsors, etc. • Use of newer technologies (html5, twitter, etc.) • Resources for other teams (labVIEW tutorials, other resources) • Uniformity ...

  18. Uniformity • Current website lacks uniformity • Need to create design for main site, forums, and wiki that’s consistent • Will help people while they navigate between parts of website • Makes overall design look better, builds “team identity”

  19. What Else We Need to Include in Website for Team Gain • PayPal donations • User file uploads • “Propaganda” for enlisting new students • SMS meeting updates

  20. Plans for “Construction Zone” • New website will be built parallel to old website • I.E. old website will be 100% functional until the Website Team receives approval for new site from Management • New website will be hidden from public during build season.

  21. Expectations • Little to no budget • Completion by September 2010 • Regional Website Award 2011

  22. Lastly, we would like to thank Ameya for being a good sport.

More Related