aardvark wrote: > > From: Ron Dorman <rwd at csi1st.net> > > > > I agree with rudy on this. Seems to me that we first need to decide > > what functionality is needed. Choose the components best suited to > > deliver the needed functionality. Then design a layout that provides > > the best accessibility, usability and visual appearance of the > > selected components. > > that's a given... you don't think that's where we are? have we identified all the functionality we need to add from the results of the survey? if I have missed it I apologize for asking. are we considering javi's IA work in the design? I don't want us to run past something important and later say "OOPS". I don't want to delay things either. > we know: > - we want to keep all existing capability > - we want to bring the other sites into the home page more > - we want to explore trreating news differently > - we want to keep the same goals of standards/accessibility > > however, some of this is easier to discuss when we can prototype > to get ideas on the table... for instance, if two people are debating > a feature, sometimes the best way for them to understand one > another is to go to their corners, prototype, and come back... I agree with this, and what I was referring to in my statement below. Yes we need the concepts to look at and change and tweak. My point being that the final design be built around the needs (now and expected in the future) instead of the needs being adapted to fit a design. > my fear is that if we don't prototype, this discussion will become > another '"what's a member" discussion and we'll never get > anywhere, just swirling around a few points... many of us are > visual, so i plan to accentuate my ideas with prototypes when i > have the time... I do not wish to see this bogged down either. I like what issac has done to this point and want to see more concepts. Maybe just a reminder to consider all the information collected to date and review occasionally because there is a lot of information in the survey results and IA documents in addition to what we have learned over the last 3 years. > > Having some design concepts to think about is good in that they will > > stimulate creativity and guide us toward a better site. But we do not > > need the horse (design / layout) pushing the cart (functionality / > > accessibility / usability). > > i don't think we're there yet... I don't either. Want to keep us from getting there. Ron D.