In other applications that have implemented the Patternfly vertical nav it 
is in the top right position of the masthead. 

On Monday, December 19, 2016 at 12:08:42 PM UTC-5, Eric Helms wrote:
>
> In the screenie, I don't see the 'Administer' menu which today lives 
> visually distinct on the right hand side from the non-superuser items. In 
> this new nav, where would that live?
>
> On Mon, Dec 19, 2016 at 9:51 AM, Roxanne Hoover <roho...@redhat.com 
> <javascript:>> wrote:
>
>> I understand, it's certainly worth looking at an alternative position in 
>> the masthead. 
>>
>> On Monday, December 19, 2016 at 9:49:39 AM UTC-5, ohadlevy wrote:
>>
>>>
>>>
>>> On Mon, Dec 19, 2016 at 4:46 PM, Roxanne Hoover <roho...@redhat.com> 
>>> wrote:
>>>
>>>> Are you concerned about the priority or it being in the vertical nav?
>>>>
>>> I guess both, in a way, its a context you "log into" vs an action you 
>>> take, so i feel its similar to how you switch accounts in gmail for example.
>>>
>>>>
>>>> I think there is room to have it located elsewhere. In patternfly the 
>>>> top right hand mast head area allows for additional items. 
>>>>
>>>
>>>>
>>>> On Monday, December 19, 2016 at 9:40:41 AM UTC-5, ohadlevy wrote:
>>>>
>>>>>
>>>>>
>>>>> On Mon, Dec 19, 2016 at 4:38 PM, Roxanne Hoover <roho...@redhat.com> 
>>>>> wrote:
>>>>>
>>>>>> After some reviews with the visual team. I've made some changes to 
>>>>>> the color scheme. The Foreman masthead will remains the same, but I've 
>>>>>> updated the remaining colors to the default patternfly colorscheme. I 
>>>>>> believe this will be better for color-blindness and overall longterm 
>>>>>> visual 
>>>>>> engagement. I met with a user recently who was color-blind - which 
>>>>>> prompted 
>>>>>> me to make some updates. Any feedback welcomed!
>>>>>>
>>>>>>
>>>>>>
>>>>> I see you've folded the org switcher as the main top level entry, is 
>>>>> there another place we could put this context switcher instead ?
>>>>>
>>>>> thanks!
>>>>> Ohad 
>>>>>
>>>>>>
>>>>>> On Monday, November 28, 2016 at 10:14:14 AM UTC-5, Roxanne Hoover 
>>>>>> wrote:
>>>>>>>
>>>>>>> Walden, Yes! The Patternfly vertical nav does have a collapsible 
>>>>>>> feature. If you read the design notes, secondary and tertiary levels 
>>>>>>> can be 
>>>>>>> "pinned" to the left. There is also a version I have seen which is icon 
>>>>>>> only however I'm not seeing the documentation at the moment. 
>>>>>>>
>>>>>>> I also agree with your statement on full width. Reducing the 
>>>>>>> margin/padding will make better use of the space for responsive 
>>>>>>> purposes. 
>>>>>>>
>>>>>>> On Wednesday, November 23, 2016 at 10:55:51 AM UTC-5, Walden Raines 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> > is there an assumption we should move to full width with this 
>>>>>>>> change? 
>>>>>>>>
>>>>>>>> I personally was making that assumption based on the screen in the 
>>>>>>>> patternfly vertical navigation documentation [1] and I support using a 
>>>>>>>> container that is very close to full width (i.e. you'll still want 
>>>>>>>> some 
>>>>>>>> padding so you can easily tell that things aren't appearing off 
>>>>>>>> screen). 
>>>>>>>>
>>>>>>>> Cheers, 
>>>>>>>> Walden 
>>>>>>>>
>>>>>>>> [1] 
>>>>>>>> http://www.patternfly.org/pattern-library/navigation/vertical-navigation
>>>>>>>>  
>>>>>>>>
>>>>>>>>
>>>>>>>> ----- Original Message ----- 
>>>>>>>> From: "Ohad Levy" <ohad...@gmail.com> 
>>>>>>>> To: "Foreman" <forem...@googlegroups.com> 
>>>>>>>> Sent: Tuesday, November 22, 2016 9:05:42 AM 
>>>>>>>> Subject: Re: [foreman-dev] Vertical Navigation 
>>>>>>>>
>>>>>>>> On Tue, Nov 22, 2016 at 3:57 PM, Walden Raines <wal...@redhat.com> 
>>>>>>>> wrote: 
>>>>>>>>
>>>>>>>> > +1 I'm a fan of switching to a vertical navigation but I do have 
>>>>>>>> one 
>>>>>>>> > question. 
>>>>>>>> > 
>>>>>>>> > Is there a pattern for being able to collapse the vertical 
>>>>>>>> navigation?  At 
>>>>>>>> > times you don't need the navigation at all and it takes up 
>>>>>>>> roughly 1/6th of 
>>>>>>>> > the screen (as opposed to roughtly 1/10th with the current 
>>>>>>>> horizontal 
>>>>>>>> > navigation) so it would be nice if it could be minimized to the 
>>>>>>>> side until 
>>>>>>>> > needed. 
>>>>>>>> > 
>>>>>>>>
>>>>>>>> is there an assumption we should move to full width with this 
>>>>>>>> change? 
>>>>>>>>
>>>>>>>> thanks! 
>>>>>>>> Ohad 
>>>>>>>>
>>>>>>>> > 
>>>>>>>> > Thanks, 
>>>>>>>> > Walden 
>>>>>>>> > 
>>>>>>>> > ----- Original Message ----- 
>>>>>>>> > From: "Roxanne Hoover" <roho...@redhat.com> 
>>>>>>>> > To: "foreman-dev" <forem...@googlegroups.com> 
>>>>>>>> > Sent: Tuesday, November 22, 2016 8:24:06 AM 
>>>>>>>> > Subject: [foreman-dev] Vertical Navigation 
>>>>>>>> > 
>>>>>>>> > 
>>>>>>>> > 
>>>>>>>> > Changing Direction... 
>>>>>>>> > 
>>>>>>>> > When the UXD team was tasked with identifying UI improvements for 
>>>>>>>> Foreman 
>>>>>>>> > one of the major improvements we could see was with the 
>>>>>>>> navigation. 
>>>>>>>> > 
>>>>>>>> > As it stands now, Foreman uses the Horizontal Navigation Pattern 
>>>>>>>> > <http://www.patternfly.org/pattern-library/navigation/ 
>>>>>>>> > horizontal-navigation/#_> 
>>>>>>>> > found in PatternFly (see example below). 
>>>>>>>> > 
>>>>>>>> > Our reasons for improving the current UI include better 
>>>>>>>> adaptability for 
>>>>>>>> > additional menu items and a friendlier responsive design layout. 
>>>>>>>> > 
>>>>>>>> > As you can see from the below screen, the current menu does not 
>>>>>>>> react well 
>>>>>>>> > to screen constraints, dropping menu items onto a second line. 
>>>>>>>> > 
>>>>>>>> > 
>>>>>>>> > There are some notes worth addressing when contemplating moving 
>>>>>>>> towards a 
>>>>>>>> > vertical nav from a user experience perspective. 
>>>>>>>> > 
>>>>>>>> > Firstly, though vertical nav supports a tertiary level, currently 
>>>>>>>> no nav 
>>>>>>>> > item is in need of it. It’s nice to know it’s available if 
>>>>>>>> desired. 
>>>>>>>> > 
>>>>>>>> > Secondly, the current vertical nav is at its best when nav items 
>>>>>>>> are given 
>>>>>>>> > groupings and titles for those groups. The current horizontal nav 
>>>>>>>> > inconsistently groups items. Possible solutions could be to 
>>>>>>>> provide 
>>>>>>>> > groupings alternatively you could leave them as is. In the below 
>>>>>>>> mockup we 
>>>>>>>> > can see a secondary nav that has one untitled grouping and three 
>>>>>>>> titled 
>>>>>>>> > groupings (In Bold - Provisioning Setup, Templates, Compliance). 
>>>>>>>> > 
>>>>>>>> > 
>>>>>>>> > 
>>>>>>>> > Additional information about the vertical nav and its 
>>>>>>>> functionality can be 
>>>>>>>> > found on the PatternFly blog 
>>>>>>>> > <
>>>>>>>> https://blog.patternfly.org/vertical-navigation-finding-your-way/>. 
>>>>>>>>
>>>>>>>> > 
>>>>>>>> > An additional note: the idea of a vertical nav was based on our 
>>>>>>>> perspective 
>>>>>>>> > from a user experience team. I know that there will also be 
>>>>>>>> additional 
>>>>>>>> > considerations from a technical perspective. I’m looking forward 
>>>>>>>> to 
>>>>>>>> > everyone's feedback. 
>>>>>>>> > 
>>>>>>>> > -- 
>>>>>>>> > You received this message because you are subscribed to the 
>>>>>>>> Google Groups 
>>>>>>>> > "foreman-dev" group. 
>>>>>>>> > To unsubscribe from this group and stop receiving emails from it, 
>>>>>>>> send an 
>>>>>>>> > email to foreman-dev...@googlegroups.com. 
>>>>>>>> > For more options, visit https://groups.google.com/d/optout. 
>>>>>>>> > 
>>>>>>>> > -- 
>>>>>>>> > You received this message because you are subscribed to the 
>>>>>>>> Google Groups 
>>>>>>>> > "foreman-dev" group. 
>>>>>>>> > To unsubscribe from this group and stop receiving emails from it, 
>>>>>>>> send an 
>>>>>>>> > email to foreman-dev...@googlegroups.com. 
>>>>>>>> > For more options, visit https://groups.google.com/d/optout. 
>>>>>>>> > 
>>>>>>>>
>>>>>>>> -- 
>>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>>> Groups "foreman-dev" group. 
>>>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>>>> send an email to foreman-dev...@googlegroups.com. 
>>>>>>>> For more options, visit https://groups.google.com/d/optout. 
>>>>>>>>
>>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "foreman-dev" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to foreman-dev...@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "foreman-dev" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to foreman-dev...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to foreman-dev...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Eric D. Helms
> Red Hat Engineering
> Ph.D. Student - North Carolina State University
>

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to