gus reiber walked me through how one approaches a website project, and he told me that the important bit to get right is to think of information schema — the data model in which we organize our contents, which covers all the things we want to have on our websites. This problem really belongs to us.
Then we'd go think about how to show which of them in what pages, a process that deeply involves the mythical designer (
Spike Washburn is going to check whether this is something that the designer should be also involved in (or povide us some guidance on), but in the mean time I think we should start thinking about what information we have that we want to carry over, and what information we want to add.
So I think it'd be good to start creating a preliminary catalog of those in a Wiki page, a text file, or something like that.