Content:Policies

• Cross-browser support
  • prioritize browsers
  • operating systems?

• Maintability - style sheets, includes
  • Documentation
    • SVN/trac
    • Mediawiki (wiki.cs.earlham.edu)
      • Changelog rotated every other month (bimonthly)
  • Organizing
    • cgi in one directory
    • php includes on directory
    • css in one directory
    • images in a directory

• Security/Integrity - don't make security holes :P
  • Scripts only available on campus (barndoor)
  • Not putting false, compromising, incriminating, inappropriate info
  • Follow campus (ECS?) information policy (does one exist?)

• Reliability (working on staging first)
  • Only put polished and tested pages live
  • Major changes should be run by users and tested by users, and given a specific release date ahead of time

• Usability
  • Users: potential students of CS (or another department of Earlham), people in CS department, Earlham at large
  • Clean layout
  • Navigability
  • No orphaned pages

• Standards compliance (XHTML)
  • Value ease of use higher than compliance but trying to move toward compliance
  • Keep CSS/HTML separate