A subsite aware CMS is what I want to see as well David. This way each little publishing community can take advantage of OpenACS packages (ticket tracker, time logger, publication forum, etc.) as they prepare and revise content for publication. An option that allows a user to render content to the file system would be nice too. That way we have reliability (pages get served even if the DB connection goes on vacation), scalability (AOLServer can do what it is good at), portability (there is always a hard copy of content that can be moved to whatever platform is in style) and we can use stuff like the static pages package.
