I don't necessarily think that we need a completely static site. What I do think is that most of our information is "rarely changing". So basically, most of it could be static if it was updated relatively often (say even every semester). For archives of talks, the editing should be done when meetings occur. The nature of archiving is static after that.
That's not to say that there couldn't be (for example) an announcements section that was dynamic, so announcements could expire in a timely way. Basically, I look at something like PhpNuke, which is entirely dynamic and it looks like overkill. Big swiss-army knife web solutions are probably going to cause us more trouble and provide stuff we mostly don't use. -- Don Bindner <[EMAIL PROTECTED]>
