Difference between revisions of "Content:Policies"
Jump to navigation
Jump to search
(New page: * Cross-browser support ** prioritize browsers ** operating systems? * Maintability - style sheets, includes ** Documentation *** SVN/trac *** Mediawiki (wiki.cs.earlham.edu) ** Organizin...) |
|||
| Line 7: | Line 7: | ||
*** SVN/trac | *** SVN/trac | ||
*** Mediawiki (wiki.cs.earlham.edu) | *** Mediawiki (wiki.cs.earlham.edu) | ||
| + | **** Changelog rotated every other month (bimonthly) | ||
** Organizing | ** Organizing | ||
*** cgi in one directory | *** cgi in one directory | ||
| Line 16: | Line 17: | ||
** Scripts only available on campus (barndoor) | ** Scripts only available on campus (barndoor) | ||
** Not putting false, compromising, incriminating, inappropriate info | ** Not putting false, compromising, incriminating, inappropriate info | ||
| + | ** Follow campus (ECS?) information policy (does one exist?) | ||
* Reliability (working on staging first) | * Reliability (working on staging first) | ||
** Only put polished and tested pages live | ** 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 | * Usability | ||
| + | ** Users: potential students of CS (or another department of Earlham), people in CS department, Earlham at large | ||
** Clean layout | ** Clean layout | ||
** Navigability | ** Navigability | ||
** No orphaned pages | ** No orphaned pages | ||
| + | |||
| + | * Standards compliance (XHTML) | ||
| + | ** Value ease of use higher than compliance but trying to move toward compliance | ||
| + | ** Keep CSS/HTML separate | ||
Revision as of 13:51, 22 April 2009
- 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
- Documentation
- 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
