Nick ran this by me in IRC earlier today. Here's the gist of my response:
The big concern I have is revising markup and styling the LSN stuff (profile pages / wiki / groups) - basically all the stuff within openplans. I have yet to have any task pertaining to openplans be easier / faster than expected. That's the only iceberg issue I see on my plate.
For instance, the LSN project blog stuff may need heavy revision - especially admin screens. I also don't see any listings for StreetsWiki markup changes or styling. I don't know if anyone from the Design team has looked at any of those pages (I have not), but we should expect there to be at least some integration / revision work on that front.
I spent some time looking at blogs within projects today, and I think this is one area where we can scale back as necessary, possibly/probably going with the no-treatment option as we currently do on nycstreets.org. Phil's mockups show moving blog sub-navigation to within the main navigation, which is a detail we should probably punt on for the first round. Assuming we do that, there might not be very much work in the blog admin at all.
It's true that there aren't any mockups for streetswiki. The assumption, at this point, is that it can inherit most of its style from wikis within groups. Non-group pages (profiles, search results), can also be treated in a very vanilla manner, as they were on previous versions of livablestreets.com (like what's currently up at stage.livablestreets.com). These pages can mostly stand on their own with the base opencore styles, taking some cues from the site wrapper.
I'll do what I can to get the full first-draft of sblog / sfilms done ahead of next week's milestone, to see whether I can buy us any extra time.
In terms of pipelining the markup & CSS work, I probably will need some help, and that most-likely will mean some combination of Rollie / Nick / Phil. Given how tight the deadline is, it might make most sense to have Phil pair with Rollie or Nick to ramp up, unless Phil's needed on pressing design stuff for OpenGeo or other internal clients.
Yeah, Rollie and I spoke briefly about this this morning. To start, he's going to spend some of his own time implementing the new Project Summary page in HTML. But he will also be working with Phil to balance his time between this project and OpenGeo work. I might also spend some night/weekend time pitching in, heh heh :) Regardless, we'll make sure you get the help you need.
So basically, I'm optimistic that we'll be able to hit this timeline, but it may be a bit of a rough month. It'll be pretty critical that we have good communication within the team, as well as clear requirements for any development changes we need to make for launch.
Yes, definitely. To start, we should put our heads together (you, me, phil), before embarking on any new sections of the site, to review the mockups and get on the same page re: details, especially since the various mockups are not always 100% synced up. I'll also continue to add notes to the Production Status page, including annotating skitches. Let's really try to use that page as our staging ground.
Nick