On 12/04/2012 11:30 AM, Tzu-Mainn Chen wrote:
From: "Aaron Weitekamp" <[email protected]>
To: "Tzu-Mainn Chen" <[email protected]>
Cc: "aeolus-devel" <[email protected]>, "Jaromír Coufal"
<[email protected]>
Sent: Tuesday, December 4, 2012 11:05:08 AM
Subject: Re: RFC: Navigation restructuring
On 12/04/2012 10:27 AM, Tzu-Mainn Chen wrote:
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
Yes, navigation is broken, but just fixing the site map is not a very
difficult problem. Jaromír's wireframes address a deeper issue which
is
solved by leveraging a widget model (soon to be part of
Converge-ui/Alchemy?[1]). Along the way, as my post suggests, we're
able
to simplify navigation.
We might just be arguing over approach here. I'm no usability expert, but I think that
taking a step back and asking: "how does a user want to use Conductor?" makes
sense. And when asking that question, I think it makes sense to start with site
navigation and clearly define how it should work. The page content is definitely an
issue as well, but I don't think it's a deeper issue than our navigation.
Mainn
I think you're right. And you make a great point about first considering
use cases: defining workflows and modeling our UI against that. Personas
-> use cases -> wireframes/nav
-Aaron
-Aaron
[1] https://fedorahosted.org/katello/wiki/Server%20Containers
https://fedorahosted.org/katello/wiki/Organization
