Developers Agenda


Published on

Agenda for first meeting of Web Developers Group at Idaho State University. Offers general guidelines and suggestions to improve coordination of university web work between central WebComm office and "embedded" web developers throughout campus.

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Developers Agenda

  1. 1. Web Developers Meeting Office of Web Communications Idaho State University 15 November 2007
  2. 2. ABOUT: Office of Web Communications  Formed in late November 2006  One director: Graham Garner  One full-time senior web developer: Laird Duncan  Three student positions (one filled)  Derek Aitken  Oversee the entire ISU Web site  Take direct responsibility for “The Commons”
  3. 3. PURPOSE: of WebComm  Create consistent design and function of ISU’s Web presence  Reinforce branding image of the University  Maintain best practices at both front and back ends of the site (design view vs. coding)  Enforce usability standards; W3C and ADA
  4. 4. SPIDERS: on the Web  Different types of spiders  Work on different parts of the Web  Still part of one Web  Your work can strengthen or weaken the whole  Coming up with new ideas to apply to the whole can be beneficial  Doing your own pattern in your own section just makes you stand out – and not in a good way
  5. 5. ADDRESS: Compliance XHTML CSS SSIs Templates
  6. 6. ADDRESS: Security Who has access/belongs to publishing groups Cease using these directories as storage spaces Y-drive exposure Deleting web sites
  7. 7. ADDRESS: Server Access Other servers, i.e. Pharmacy, Business, Education, Physics Contact information for server administrators Grant WebComm access
  8. 8. UNITE: As a Campus-wide Force Everyone aware of current standards and efforts WebComm acts as clearinghouse and focal point Collective experience and goal
  9. 9. STOP: Doing These Things  Grabbing things from “View Source” and pasting them in  Using web space as a storage space
  10. 10. START: Doing These Things  Using the templates  Use the server-side includes  Use the style sheets  Recommending changes to the templates
  11. 11. ACCEPT: What You Cannot Change  Wordmark  Global navigation  Placement of local navigation  Text styles (h1, h2, h3, h4, p)
  12. 12. EXPLORE: Things You Can Change  Images  The content area  Types of pages  Contact Us, Forms, Downloads, Galleries, Slideshows, Video, Audio/Podcasts  Template schemes (future plans)  Colors  Divs; columns or sections
  13. 13. INFLUENCE: Global Change  If you have a great idea … propose it  If you have a problem … share it  If you have a question … discuss it  If you find a solution … bring it  Open communication will help us all know where we have been, where we are, and where we are headed
  14. 14. Upcoming Issues  Search engine replacement  Exploring events calendar options  Redesign timeline (flexible) Started Oct. 15 Templates by Feb. 1 Beta site by Spring Break (March 24) New site goes live (July 1)
  15. 15. Support  WebComm School   Survey/Audit