> On 11/15/2012 07:57 PM, Jaromír Coufal wrote: > > Good morning/afternoon/evening to all > > (you can choose your time-zone) > > > > On our Aeolus Developer Conference I introduced new concept of > > Conductor > > UI. When I wanted to use versioning to distinguish it from current > > one, > > I realized that it would be better just to call it "new generation" > > :) > > > > With this e-mail I would like to follow up with more details to the > > first stage of our change - navigation restructuring. > > > > ==== > > Goals > > ==== > > - Make user oriented in the system > > - Allow user to quick navigate through the system > > - Show to user as much as possible within at least steps as > > possible > > (but don't overwhelm him) > > - Don't get user lost (at least not easily) > > - If user gets lost recover him fast > > > This is good stuff Jaromir. My only concern, as you alluded to, is > it's > a bit of a "start from scratch" approach. If we can do that, > wonderful! > But if it's too big a hill to climb then could we make these changes > more iteratively? > > I recently posted some possible approaches[1]. The concepts are much > less specific than yours. (I'm not a designer!) > 1. Is it really a navigation problem or rather not taking advantage > of > our table widget model? It seems we don't display enough information > so > we end up with many page views, therefore confusing the user. Your > solution addresses this nicely and my proposal is to apply this > throughout the site.
Just to address this particular question - in my opinion, it is absolutely a navigation problem. I agree that the table widget is nice, but that fixes specific pages. Jaromir's point (which I agree with) is that it's hard to even navigate to that specific page right now. If a first time user started up Conductor, he'd have no instinctive way to know where to manage providers. Mainn
