Hi Stefan, all, On Thu, May 13, 2010 at 5:36 AM, Stefan Taxhet (sonews) <[email protected]> wrote: > Hi, > > Ivan M wrote: > [...] > >> In short, as we all know, it's time for a redesign. >> >> The question is: when does the redesign begin? The Kenai migration >> project has not really presented opportunities for contribution yet, >> and we still don't have a very clear roadmap about when it's going to >> happen. > > That's mildly put ;-) > At this point of time it's stalled.
OK, let's look on the positive side: that gives us time to come up with a new design :) >> If we can have a design ready before the migration to Kenai, >> maybe we can reduce the effort required (i.e. we don't have to port >> the existing design over). >> >> That also leads to another question: what are the constraints? i.e., >> what kind of system will we be working with when we do migrate? What >> kind of content management system will it have? Will there be better >> localization support for menus, etc? These things are still not clear, >> and they will be important factors to be considered when creating the >> design... > > It depends a bit on how drastic a redesign would be, or whether it's a > refresh... Personally, I would suggest something moderately drastic :) 1) For the header, a re-evaluation of all the links (8 links max?). The wiki and planet would be two good candidates for inclusion. My Pages could go to the top-right side of the page with all the user login stuff for now, and then its future depends on Kenai's functionality with respect to user pages. 2) New, modern layouts for all core pages (i.e., those linked to from the main menu) 3) For the footer, an expanded array of links like the footer of Mozilla.com 4) A new tableless layout 5) The left hand project navigation will depend on Kenai functionality so I won't comment on that... same goes for other nice dynamic stuff that has been mentioned in the recent "Clean up the OOo Template thread). Javascript for localization is the worst case scenario; we need to do much better for our NLC projects. For now we can focus on the basics which are achievable on the current infrastructure. Anything relating to CollabNet-specific implementation can be left as-is. >> which brings me back to the main question: when does the >> redesign begin? :) > > Now? ;-) > > Seriously, I don't think we should create a dependency on an infrastructure > change but go ahead. We should wait for the branding project logo guidelines to be finalized and then I would like to propose that we take active steps toward a redesign. Some pages, like Support, which need revamping could be taken care of before migration. We could also evaluate the action statements and how they fit into the rest of the site (eg ensure consistency), prune out / archive obsolete pages to make migration easier, etc. By working within the existing system we can avoid creating a dependency on infrastructure change; when we do actually change infrastructure, then we can add all the fancy extras it allows. And by working within the restrictions of the existing system we don't set ourselves up for disappointment. What do you think? Regards, Ivan. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
