comanage-dev - Re: [comanage-dev] Menu updates (CO-828) and questions that arise from the new navigational paradigm.
Subject: COmanage Developers List
List archive
Re: [comanage-dev] Menu updates (CO-828) and questions that arise from the new navigational paradigm.
Chronological Thread
- From: Benn Oshrin <>
- To:
- Subject: Re: [comanage-dev] Menu updates (CO-828) and questions that arise from the new navigational paradigm.
- Date: Mon, 23 Feb 2015 00:06:32 -0500
On 2/22/15 5:17 PM, Arlen Johnson wrote:
The menus have been changed to look like the following (when a user is
in a CO):
It feels more correct to move the CO selector to the right, even if a
search bar may be over there with it. All three menu items on the left
go together with the CO title, while the "Collaborations" menu is a
global selector. If you disagree, it's trivial to put it back on the left.
I keep going back and forth on this. Why don't we start with it on the right and get some usability experience?
A couple of thoughts arise:
* If a user is in exactly one CO, should that user see the
Collaborations menu at all? ...I don't think so - which means that
the user should be redirected to their CO dashboard on login.
o To do this, I believe we can add a test within the login()
function of the UsersController, setting the URL parameter for
the redirectUrl function so long as other rules (like T&Cs)
don't bubble up.
No, this doesn't go in login. Keep in mind people might "log in" via a deep link, or by reauthenticating when their session expires, in which case they should be sent to the appropriate deep link/page. A better approach is for the beforeFilter() in the appropriate controller to do the check and issue the redirect if needed.
ie: If I go to /registry, I either get a CO chooser menu (or just some text that says to pick from the menubar) or I get redirected to the appropriate landing page. If I visit this page 10 times in a session, I should get the same behavior, even if I logged in just once.
I think this might need to go in PagesController. See also View/Pages/home.ctp.
Thanks,
-Benn-
- [comanage-dev] Proposed changes for provisioning based on status, Benn Oshrin, 02/22/2015
- Re: [comanage-dev] Proposed changes for provisioning based on status, Scott Koranda, 02/22/2015
- Re: [comanage-dev] Proposed changes for provisioning based on status, Benn Oshrin, 02/22/2015
- Re: [comanage-dev] Proposed changes for provisioning based on status, Scott Koranda, 02/22/2015
- [comanage-dev] Menu updates (CO-828) and questions that arise from the new navigational paradigm., Arlen Johnson, 02/22/2015
- Re: [comanage-dev] Menu updates (CO-828) and questions that arise from the new navigational paradigm., Benn Oshrin, 02/23/2015
- Re: [comanage-dev] Menu updates (CO-828) and questions that arise from the new navigational paradigm., Arlen Johnson, 02/23/2015
- Re: [comanage-dev] Menu updates (CO-828) and questions that arise from the new navigational paradigm., Benn Oshrin, 02/23/2015
- Re: [comanage-dev] Proposed changes for provisioning based on status, Benn Oshrin, 02/23/2015
- [comanage-dev] Menu updates (CO-828) and questions that arise from the new navigational paradigm., Arlen Johnson, 02/22/2015
- Re: [comanage-dev] Proposed changes for provisioning based on status, Scott Koranda, 02/22/2015
- Re: [comanage-dev] Proposed changes for provisioning based on status, Benn Oshrin, 02/22/2015
- Re: [comanage-dev] Proposed changes for provisioning based on status, Scott Koranda, 02/22/2015
Archive powered by MHonArc 2.6.16.