Changes

Most of the services on WSO's site were written by students in a framework called [http://www.pagekit.org Apache PageKit]. Applications written for it take advantage of WSO's log-in system. Current examples are the [http://wso.williams.edu/facebook WSO Facebook], the old [http://wso.williams.edu/blog blogs], and [http://wso.williams.edu/PhotoShare PhotoShare], and anything else on the WSO site that has the look and feel of http://wso.williams.edu. If you have an idea for a new web service and want to know what it takes to make it happen, you came to the right page.

Finally, the Content is a bullet lodged into the back of PageKit's brain, the kind you can't pull out or else you'll bleed to death. The Content makes me hate PageKit. A Content file is required for every web page. Now in theory, Content is supposed to be XML files with information that doesn't change much, like a policy or a static list, which is interpolated into the View templates. But XML is probably the least human-friendly data encoding language I know, so in reality everybody just sticks their "Content" straight into the View templates. But even if a page does not use anything from the XML file, ''it still has to have an XML file or else the site will break.'' If you learn that principle, if you write it on the ceiling above your ceiling bed and memorize it, you will save yourself much suffering.