Re: [foreman-dev] Re: [UX] Facets and Host UI - roadmap discussion.

[Roxanne Hoover]

ke adding a new tab to
>> the
>> >> >>> host form or host show page. Currently, the only way to do this is
>> >> >>> using
>> >> >>> deface.
>> >> >>> But this feels pretty hacky to me and isn't good to maintain. I'd
>> >> >>> really
>> >> >>> appreciate if there were easy and tested hooks for common areas
>> like
>> >> >>> the
>> >> >>> host show page.
>> >> >>>
>> >> >>> In my opinion, we are already too late on finishing the facets (and
>> >> >>> Pagelets) integration. Personally, I don't have a strong opinion on
>> >> >>> either
>> >> >>> option. But prefer the second approach as well.
>> >> >>>
>> >> >>> In regards to widening the feature gap for a host ux redesign: We
>> have
>> >> >>> to
>> >> >>> provide extension points anyways. The Foreman community gains a
>> lot of
>> >> >>> value from the rich plugin ecosystem and the possibility to extend
>> >> >>> Foreman
>> >> >>> fairly easy.
>> >> >>> When we redo the host ux pages, we have to provide extension
>> points.
>> >> >>> This
>> >> >>> is not a nice-to-have feature, but a must-have in my opinion.
>> >> >>>
>> >> >>> - Timo
>> >> >>>
>> >> >>> --
>> >> >>> 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+unsubscr...@googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> Have a nice day,
>> Tomer Brisker
>> Red Hat Engineering
>>
>> --
>> 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.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "foreman-dev" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/foreman-dev/oqbkuOAkISc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

ROXANNE HOOVER

VISUAL & INTERACTION DESIGN

Red Hat

<https://www.redhat.com/>

rohoo...@redhat.comM: 919-609-5300
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

-- 
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.

Re: [foreman-dev] Re: [UX] Facets and Host UI - roadmap discussion.

[Roxanne Hoover]

Thanks for the screenshots! 

I like that the information is grouped together. I think that this could 
easily be integrated into the host designs that were done.


On Sunday, November 12, 2017 at 1:36:08 PM UTC-5, ssh...@redhat.com wrote:
>
>
> OK, I have managed to create some screenshots of the before and after 
> state. Please don't judge the styling - it's more about the technical 
> abilities than the styling.
>
> I will take Puppet as an example. Let's say we have puppet facet that has 
> the following data: puppet environment, puppet proxy and puppet ca proxy 
> fields plus a list of puppet classes assigned to the host.
>
> Before: 
> The information is spread on multiple screens:
> Take a look at this screenshot: https://ibb.co/bsXT8G it shows where this 
> information is currently located on the main tab.
> This screenshot: https://ibb.co/ksuaoG shows the detailed puppet classes 
> view.
>
> After:
> Everything related to puppet is presented on a single tab. This tab can be 
> enabled and disabled based on user's preference - the user can decide to 
> turn puppet management on or off for this host.
> https://ibb.co/bNnd8G shows the tab when the fields are enabled, and 
> https://ibb.co/eCJ72b shows all the fields disabled.
>
> I hope it helps to visualize both options.
>
>
> On Wednesday, November 8, 2017 at 12:08:06 AM UTC+2, Walden Raines wrote:
>>
>> Hey Shim,
>>
>> Can you please include screenshots (or, even better, a quick video or 
>> gif) of the new UI to make it easier for people to visualize who don't have 
>> the code checked out?
>>
>> Assuming I'm understanding your description of the two options, I would 
>> also vote for option #2 as option #1 sounds like it would be very difficult 
>> to ensure a good UI since some other plugin could just put whatever they 
>> want wherever in the UI.  
>>
>> Thanks,
>> Walden
>>
>>
>>
>> On Tue, Nov 7, 2017 at 5:38 AM, Timo Goebel  
>> wrote:
>>
>>> I have been playing with Facets the last few weeks and must say, that 
>>> they are really great. It's pretty easy to add dedicated functionality to 
>>> the host model and I want to use that for some of my plugins (Omaha, 
>>> Monitoring, something new, ...).
>>> Everything is great so far except for the missing UI hooks Shim mentions.
>>>
>>> What I want to do are mostly easy thing, like adding a new tab to the 
>>> host form or host show page. Currently, the only way to do this is using 
>>> deface.
>>> But this feels pretty hacky to me and isn't good to maintain. I'd really 
>>> appreciate if there were easy and tested hooks for common areas like the 
>>> host show page.
>>>
>>> In my opinion, we are already too late on finishing the facets (and 
>>> Pagelets) integration. Personally, I don't have a strong opinion on either 
>>> option. But prefer the second approach as well.
>>>
>>> In regards to widening the feature gap for a host ux redesign: We have 
>>> to provide extension points anyways. The Foreman community gains a lot of 
>>> value from the rich plugin ecosystem and the possibility to extend Foreman 
>>> fairly easy.
>>> When we redo the host ux pages, we have to provide extension points. 
>>> This is not a nice-to-have feature, but a must-have in my opinion.
>>>
>>> - Timo
>>>
>>> -- 
>>> 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Icon Feedback

[Roxanne Hoover]

Thanks for all the great feedback. I'm going to pass this on to the visual 
team and see what they come up with.

On Tuesday, August 15, 2017 at 4:20:26 AM UTC-4, Ivan Necas wrote:
>
>
> On Tue, 15 Aug 2017 at 09:47, Lukas Zapletal <lz...@redhat.com 
> > wrote:
>
>> Hey,
>>
>> nice, but content and infrastructure is a bit weird to me. The folded
>> paper icon is overused in many software and its meaning is blurry to
>> me.
>>
>> Infrastructure is more like support software/hardware, smaller
>> servers, forklift or network icon would be better fit. Something like:
>>
>>
>> http://icons.veryicon.com/ico/System/iOS7%20Minimal/Computer%20Active%20directory.ico
>
>
> +1
>
>>
>> <http://icons.veryicon.com/ico/System/iOS7%20Minimal/Computer%20Active%20directory.ico>
>>
>> For content, I'd go with a book or library icon or something like
>> that. The key idea is we handle lot of content, not a sheet of paper.
>>
>> LZ
>>
>>
>>
>> On Mon, Aug 14, 2017 at 9:10 PM, Roxanne Hoover <roho...@redhat.com 
>> > wrote:
>> > Visual Design took a pass at the icons in vertical nav. Anyone have any
>> > thoughts? They seem straightforward to me, some were unaltered from the
>> > original chosen.
>> >
>> > --
>> > 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.
>>
>>
>>
>> --
>> Later,
>>   Lukas @lzap Zapletal
>>
>> --
>> 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] Icon Feedback

[Roxanne Hoover]

Visual Design took a pass at the icons in vertical nav. Anyone have any 
thoughts? They seem straightforward to me, some were unaltered from the 
original chosen.

-- 
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.

[foreman-dev] Weekly Dev/Design Meeting: Smart Capsules and Proxies.

[Roxanne Hoover]

https://docs.google.com/document/d/1o5Y01knvsL60Fduk_807RxsAkg-t3KebOMZy7koTutQ/edit

Smart Proxies & Capsules

Presented Ivan Necas



   - 
   
   Internal vs. external proxy indicator
   



   - 
   
   Change active features to bullet list for easier readability
   - 
   
   Row Labels should be bold.
   - 
   
   Change refresh icon to button.
   - 
   
   Title case for row labels.
   - 
   
   When no Failed Features, display “No Failed Features” or redo layout to 
   have that information integrated into card (if they are related - demo did 
   not show failure state)
   - 
   
   Change Pulp Storage to Donut
   - 
   
   Evaluate if Red Delete is necessary here.
   



   - 
   
   Show date for “CA Certificate Expiry Date” instead of estimate
   - 
   
   Title case on cards
   - 
   
   Auto-assign Entries should use a button (icon optional) vs. icon only
   - 
   
   Host Managed change to card.
   


   - 
   
   Make table standard with other tables.
   - 
   
   Search Field is unlabeled.
   - 
   




   - 
   
   When in empty state, say “No Results” vs. current text. If current text 
   is required, change title to “Search Suggestions” (in bold), left justify 
   text with bullets properly spaced to text.
   

   - 
   
   The delete buttons are different. Are they required to be red?
   - 
   
   I would change the “New” button to be more specific… “New INSERT WORD”.
   - 
   
   Search should have a label.
   

   - 
   
   Highlighted text is unreadable.
   - 
   
   Search has no label.
   

   - 
   
   Remove all caps from level, make sure this matches dropdown
   - 
   
   Highlighted table column header “Time”, is not aligned with other labels.
   


   - 
   
   Non-standard scroll and scroll is showing when it’s not needed.
   - 
   
   Row highlight color differs from other table in same section.
   


   - 
   
   Page is okay, but for a more aesthetic layout, each item could be put in 
   a card vs. list style (as shown). It would make the items easier to read 
   since the gaps can difficult to follow from left to right.
   



   - 
   
   Errors need to be laid out better.
   

-- 
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.

[foreman-dev] Weekly Dev/Design Meeting: Provisioning

[Roxanne Hoover]

https://docs.google.com/document/d/16163KPzlYlCv_kaV62mHres6_-UnTTwWhpHMSivvcKI/edit

Provisioning

Presented by Ivan




   - 
   
   This form is within another div (see grey line box). Can we remove it 
   from that?
   



   - 
   
   Move help text to help icon.
   

   - 
   
   For provisioning, there is no flow. A user must go through separate 
   screens and back again in order to set something up. Let’s review the 
Creation 
   Wizard 
   
   


   - 
   
   Provisioning a Host, integrate Template set up
   

   - 
   
   Move info help before field but below tabs.
   


   - 
   
   Check out RHEV and Cockpit for networking layouts.
   

   - 
   
   Should the build button be red?
   - 
   
   This could probably use further design changes to better display info. 
   I’m not sure opening up a model that then displays inline errors is the 
   best way to communicate. 
   
Pending Installation is the only status. More granular statuses would be 
helpful.

-- 
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.

[foreman-dev] Weekly Dev/Design Meeting: Bookmarks and Search

[Roxanne Hoover]

https://docs.google.com/document/d/18RiZASVbRuh9Iuz2OBvzJc4e8H1243IVmhNneBYNsPw/edit



Search and Bookmarks

Presented by Tomer




   - 
   
   Ensure what you can filter by is relevant to the user to reduce items in 
   list that will have no value.
   


   - 
   
   I’ve seen alternate operators… such as in the screen below. Ensure that 
   none are duplicates. I’m not an expert on these operators but if one 
   standard language of operator could be used, that would be better.
   - 
   
   

   - 
   
   Change error to “Architecturs” not recognized. It is redundant to 
   mention searching since they are already in in a search field.
   


   - 
   
   I have a proposed design for search that would be more consistent with 
   patternfly and add additional functionality here depending on permission. 
   See below, feel free to provide feedback.
   




   - 
   
   Perhaps have Public not be default and also add inline help to define 
   what Public is.
   - 
   
   Is there any checking to see if duplicate names or searches are entered?
   - 
   
   Gray line bounding box should be removed within modal.
   






-- 
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.

Re: [foreman-dev] Weekly Dev/Design Meeting: Discovered Hosts

[Roxanne Hoover]

Another icon question... is the red icon actually an error or warning? 
Using red usually mean an error has occurred. However, if it's perhaps 
normal or okay for a user to have been inactive for 7 days, then red is 
probably not the correct color. 

On Friday, July 7, 2017 at 11:53:27 AM UTC-4, rahul bajaj wrote:
>
>
>
> On Friday, July 7, 2017 at 7:31:24 PM UTC+5:30, Roxanne Hoover wrote:
>>
>>
>>
>> *Hello Roxanne,Can you please mention which icons are you talking about 
>> here ? *
>>
>> Those found in the name column (old icon:new icon)
>>
>> blue check mark
>> green circle plus
>> red circle warning
>>
>> I'm sure we have existing icons we can use, I would just need to know the 
>> meaning behind the green + vs. the blue checkmark.
>>
>> The icons indicate whether the user has been active within 7 days(green 
> icon), has not been active for last 7days(blue) and has not been active for 
> more than 7 days(red icon).
> It would be really helpful if you could suggest the icons :) 
>
>
>> *can you please provide me a example of bread crumb that would be valid 
>> here ?Should it be like : Hosts / Discovered Hosts / user  ? * 
>>
>> I think here it would be Discovered Hosts >> Name of Item they are on.
>>
>> PatternFly has an existing breadcrumb but we are working on a new style 
>> to allow additional functionality.
>>
>> So should i wait until it is been developed ? 
>
>>
>>
>> <https://lh3.googleusercontent.com/-jCcKoJWpiGg/WV-UKPUGWsI/Atw/oDrl2mwuOFUwRciCqDhwKWDAniuTYSEugCLcBGAs/s1600/Mockup_D1_v4.jpg>
>>
>>
>>
>> On Friday, June 30, 2017 at 10:25:09 AM UTC-4, rahul bajaj wrote:
>>>
>>>
>>>
>>> On Friday, May 26, 2017 at 6:15:55 PM UTC+5:30, Roxanne Hoover wrote:
>>>>
>>>> Thanks! If additional work is needed from me including mockups, etc. 
>>>> please do not hesitate to reach out!
>>>>
>>>> On Friday, May 26, 2017 at 6:58:28 AM UTC-4, Lukas Zapletal wrote:
>>>>>
>>>>> Thanks Roxanne,
>>>>>
>>>>> I've created a tracking ticket for the changes: 
>>>>> http://projects.theforeman.org/issues/19681
>>>>>
>>>>> LZ
>>>>>
>>>>> On Thu, May 25, 2017 at 9:32 PM, Roxanne Hoover <roho...@redhat.com> 
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> https://docs.google.com/document/d/1BNxtczgB2_C6-rzdBwP7Mq3bwbUK7J6__qZe_EGGjE4/edit
>>>>>>
>>>>>>
>>>>>> Discovered Hosts 
>>>>>>
>>>>>> Presented by Izap
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>- 
>>>>>>
>>>>>>Icon use and color does not comply with PatternFly or with other 
>>>>>>uses in the application
>>>>>>- 
>>>>>>
>>>>>>Org/Location is not tracking the context selected by the user for 
>>>>>>Org/Location
>>>>>>
>>>>>>
>>> Hello Roxanne,
>>>
>>> Can you please mention which icons are you talking about here ? 
>>>  
>>>
>>>>
>>>>>>- 
>>>>>>
>>>>>>Reboot All, Auto Provision All should be added to Select Action 
>>>>>>button
>>>>>>
>>>>>>
>>>>>>  
>>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>- 
>>>>>>
>>>>>>Redundant info on the Highlight -  IP address, maybe change to 
>>>>>>Primary IP
>>>>>>- 
>>>>>>
>>>>>>Expand All button should be grouped with accordion, not with 
>>>>>>actions.
>>>>>>- 
>>>>>>
>>>>>>Remove Back button, implement bread crumb.
>>>>>>- 
>>>>>>
>>>>>>Change Delete from Red to Grey
>>>>>>- 
>>>>>>
>>>>>>Move Highlights next to Interfaces with the Accordion below both 
>>>>>>of those that can take up the entire width of the page reducing 
>>>>>> truncation 
>>>>>&

Re: [foreman-dev] Weekly Dev/Design Meeting: Discovered Hosts

[Roxanne Hoover]

*Hello Roxanne,Can you please mention which icons are you talking about 
here ? *

Those found in the name column (old icon:new icon)

blue check mark
green circle plus
red circle warning

I'm sure we have existing icons we can use, I would just need to know the 
meaning behind the green + vs. the blue checkmark.


*can you please provide me a example of bread crumb that would be valid 
here ?Should it be like : Hosts / Discovered Hosts / user  ? * 

I think here it would be Discovered Hosts >> Name of Item they are on.

PatternFly has an existing breadcrumb but we are working on a new style to 
allow additional functionality.


<https://lh3.googleusercontent.com/-jCcKoJWpiGg/WV-UKPUGWsI/Atw/oDrl2mwuOFUwRciCqDhwKWDAniuTYSEugCLcBGAs/s1600/Mockup_D1_v4.jpg>



On Friday, June 30, 2017 at 10:25:09 AM UTC-4, rahul bajaj wrote:
>
>
>
> On Friday, May 26, 2017 at 6:15:55 PM UTC+5:30, Roxanne Hoover wrote:
>>
>> Thanks! If additional work is needed from me including mockups, etc. 
>> please do not hesitate to reach out!
>>
>> On Friday, May 26, 2017 at 6:58:28 AM UTC-4, Lukas Zapletal wrote:
>>>
>>> Thanks Roxanne,
>>>
>>> I've created a tracking ticket for the changes: 
>>> http://projects.theforeman.org/issues/19681
>>>
>>> LZ
>>>
>>> On Thu, May 25, 2017 at 9:32 PM, Roxanne Hoover <roho...@redhat.com> 
>>> wrote:
>>>
>>>>
>>>> https://docs.google.com/document/d/1BNxtczgB2_C6-rzdBwP7Mq3bwbUK7J6__qZe_EGGjE4/edit
>>>>
>>>>
>>>> Discovered Hosts 
>>>>
>>>> Presented by Izap
>>>>
>>>>
>>>>
>>>>
>>>>- 
>>>>
>>>>Icon use and color does not comply with PatternFly or with other 
>>>>uses in the application
>>>>- 
>>>>
>>>>Org/Location is not tracking the context selected by the user for 
>>>>Org/Location
>>>>
>>>>
> Hello Roxanne,
>
> Can you please mention which icons are you talking about here ? 
>  
>
>>
>>>>- 
>>>>
>>>>Reboot All, Auto Provision All should be added to Select Action 
>>>>button
>>>>
>>>>
>>>>  
>>>>
>>>
>>>>
>>>>
>>>>- 
>>>>
>>>>Redundant info on the Highlight -  IP address, maybe change to 
>>>>Primary IP
>>>>- 
>>>>
>>>>Expand All button should be grouped with accordion, not with 
>>>>actions.
>>>>- 
>>>>
>>>>Remove Back button, implement bread crumb.
>>>>- 
>>>>
>>>>Change Delete from Red to Grey
>>>>- 
>>>>
>>>>Move Highlights next to Interfaces with the Accordion below both of 
>>>>those that can take up the entire width of the page reducing truncation 
>>>> of 
>>>>information.
>>>>
>>>>
> can you please provide me a example of bread crumb that would be valid 
> here ?
> Should it be like : Hosts / Discovered Hosts / user  ?  
>
>>
>>>>
>>>>- 
>>>>
>>>>Priority counter should use patternfly touchspin, 
>>>>http://www.patternfly.org/pattern-library/widgets/#bootstrap-touchspin
>>>>
>>>>
>>>>
>>>>
>>>>- 
>>>>
>>>>This combo select button users find confusing and are prone to 
>>>>click error… just a note that a long term strategy should be identified 
>>>> to 
>>>>fix it. I’m specifically referring to buttons that utilize the small 
>>>>chevron box on the right as the drop down action.
>>>>
>>>>
>>>>
>>>>- 
>>>>
>>>>Style of modal doesn’t follow PatternFly (
>>>>http://www.patternfly.org/pattern-library/widgets/#modal)
>>>>- 
>>>>
>>>>Change “Close Button” to “Cancel” 
>>>>- 
>>>>
>>>>“Create Host” - name is inaccurate, possibly change to “Customize”
>>>>- 
>>>>
>>>>Determine which button is more common, “Quick Create” or “Create 
>>>>Host” and color the more common action blue.
>>>>
>>>>
>>>> Fixed this : https://github.com/theforeman/foreman_discovery/pull/357 
>
>>
>>>>- 
>>>>
>>>>Warning be placed at the top. 
>>>>
>>>>
> Fixed this : https://github.com/theforeman/foreman_discovery/pull/357 
>
>>
>>>>
>>>>
>>>>- 
>>>>
>>>>Discovered Hosts empty state should be similar to empty state of 
>>>>Hosts.
>>>>
>>>>
> On it :)
>
> Thanks, 
> Rahul Bajaj.
>
>> -- 
>>>> 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.
>>>>
>>>
>>>
>>>
>>> -- 
>>> Later,
>>>   Lukas @lzap Zapletal
>>>
>>

-- 
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.

[foreman-dev] Weekly Dev/Design Meeting: Ansible Plugin

[Roxanne Hoover]

https://docs.google.com/document/d/1ThdUib-UMsY8bQaSy2YlmzrUNzt8gtp6Ah3eDaa8F4Q/edit

Ansible Plugin

Presented by Daniel

 


   - 
   
   No Bulk actions available, include checkboxes of bulk actions. Though 
   bulk actions may not be appropriate for all tables, this might be one.
   - 
   
   Future feature - be able to click on role to see parameters. Integrate 
   terminal options into UI.
   - 
   
   Improve table column width and column sorting.
   - 
   
   Order by name on default
   - 
   
   There is no help on this page
   
 


   - 
   
   Is saying “Import from..” needed? Would a user assume that since it’s 
   the import button it would be importing from the selected source. If so, 
   drop down options could include the name only, “Import from Foreman host” → 
   “Forem host”
   - 
   
   Make “Import” blue as it is the only and primary action on the page
   
   

   - 
   
   Toggle icons are redundant and probably unnecessary. 
   - 
   
   I think it’s possible a new layout with iconography added to Add or 
   Remove would be more visually appealing
   
 

 


   - 
   
   Break out report by Ansible, Puppet, etc.
   - 
   
   Those with color blindness would not find the color boxes helpful.
   

   - 
   
   “Ansible Roles” button is not clear what action is performing. Consider 
   renaming to “Run Ansible Roles” or whatever Ansible references in their 
   documentation, remove icon. We have been keeping button actions icon free 
   (or aiming to).
   
   
 

 

   - 
   
   Text is not easily read. Users must scan excessively to find results: Is 
   it possible to remove unnecessary syntax and redo formatting to make more 
   readable? If not, would a search be helpful? How can we make this more like 
   the puppet output.
   
 

 

 


   - 
   
   Level indicators 
   
 

 

 

-- 
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.

Re: [foreman-dev] Weekly Dev/Design Meeting: Discovered Hosts

[Roxanne Hoover]

Thanks! If additional work is needed from me including mockups, etc. please 
do not hesitate to reach out!

On Friday, May 26, 2017 at 6:58:28 AM UTC-4, Lukas Zapletal wrote:
>
> Thanks Roxanne,
>
> I've created a tracking ticket for the changes: 
> http://projects.theforeman.org/issues/19681
>
> LZ
>
> On Thu, May 25, 2017 at 9:32 PM, Roxanne Hoover <roho...@redhat.com 
> > wrote:
>
>>
>> https://docs.google.com/document/d/1BNxtczgB2_C6-rzdBwP7Mq3bwbUK7J6__qZe_EGGjE4/edit
>>
>>
>> Discovered Hosts 
>>
>> Presented by Izap
>>
>>
>>
>>
>>- 
>>
>>Icon use and color does not comply with PatternFly or with other uses 
>>in the application
>>- 
>>
>>Org/Location is not tracking the context selected by the user for 
>>Org/Location
>>
>>
>>- 
>>
>>Reboot All, Auto Provision All should be added to Select Action button
>>
>>
>>
>>
>>
>>
>>- 
>>
>>Redundant info on the Highlight -  IP address, maybe change to 
>>Primary IP
>>- 
>>
>>Expand All button should be grouped with accordion, not with actions.
>>- 
>>
>>Remove Back button, implement bread crumb.
>>- 
>>
>>Change Delete from Red to Grey
>>- 
>>
>>Move Highlights next to Interfaces with the Accordion below both of 
>>those that can take up the entire width of the page reducing truncation 
>> of 
>>information.
>>
>>
>>
>>
>>
>>- 
>>
>>Priority counter should use patternfly touchspin, 
>>http://www.patternfly.org/pattern-library/widgets/#bootstrap-touchspin
>>
>>
>>
>>
>>- 
>>
>>This combo select button users find confusing and are prone to click 
>>error… just a note that a long term strategy should be identified to fix 
>>it. I’m specifically referring to buttons that utilize the small chevron 
>>box on the right as the drop down action.
>>
>>
>>
>>- 
>>
>>Style of modal doesn’t follow PatternFly (
>>http://www.patternfly.org/pattern-library/widgets/#modal)
>>- 
>>
>>Change “Close Button” to “Cancel” 
>>- 
>>
>>“Create Host” - name is inaccurate, possibly change to “Customize”
>>- 
>>
>>Determine which button is more common, “Quick Create” or “Create 
>>Host” and color the more common action blue.
>>
>>
>>
>>- 
>>
>>Warning be placed at the top. 
>>
>>
>>
>>
>>- 
>>
>>Discovered Hosts empty state should be similar to empty state of 
>>Hosts.
>>
>> -- 
>> 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.
>>
>
>
>
> -- 
> Later,
>   Lukas @lzap Zapletal
>

-- 
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.

[foreman-dev] Weekly Dev/Design Meeting: Discovered Hosts

[Roxanne Hoover]

https://docs.google.com/document/d/1BNxtczgB2_C6-rzdBwP7Mq3bwbUK7J6__qZe_EGGjE4/edit


Discovered Hosts 

Presented by Izap




   - 
   
   Icon use and color does not comply with PatternFly or with other uses in 
   the application
   - 
   
   Org/Location is not tracking the context selected by the user for 
   Org/Location
   

   - 
   
   Reboot All, Auto Provision All should be added to Select Action button
   





   - 
   
   Redundant info on the Highlight -  IP address, maybe change to Primary IP
   - 
   
   Expand All button should be grouped with accordion, not with actions.
   - 
   
   Remove Back button, implement bread crumb.
   - 
   
   Change Delete from Red to Grey
   - 
   
   Move Highlights next to Interfaces with the Accordion below both of 
   those that can take up the entire width of the page reducing truncation of 
   information.
   




   - 
   
   Priority counter should use patternfly touchspin, 
   http://www.patternfly.org/pattern-library/widgets/#bootstrap-touchspin
   



   - 
   
   This combo select button users find confusing and are prone to click 
   error… just a note that a long term strategy should be identified to fix 
   it. I’m specifically referring to buttons that utilize the small chevron 
   box on the right as the drop down action.
   


   - 
   
   Style of modal doesn’t follow PatternFly 
   (http://www.patternfly.org/pattern-library/widgets/#modal)
   - 
   
   Change “Close Button” to “Cancel” 
   - 
   
   “Create Host” - name is inaccurate, possibly change to “Customize”
   - 
   
   Determine which button is more common, “Quick Create” or “Create Host” 
   and color the more common action blue.
   


   - 
   
   Warning be placed at the top. 
   



   - 
   
   Discovered Hosts empty state should be similar to empty state of Hosts.
   

-- 
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.

[foreman-dev] Weekly Dev/Design Meeting: Dashboard

[Roxanne Hoover]

https://docs.google.com/document/d/1aNQKd66ghhk9MKg35q0-BXqlUDKKhdymyzA1hI1nXp8/edit


Dashboard

Presented by Tomer




   - 
   
   Consider having widgets Save positions automatically without having to 
   click button.
   - 
   
   Auto Refresh button - not clear that this was turning off/on auto 
   refresh. I assumed it was manual. Change button to text -- “Auto Refresh”, 
   perhaps use a switch.
   - 
   
   Consider letting widgets refresh on their own vs. the entire page 
   reloading.
   - 
   
   Documentation button should go to page about widgets
   

Overall comment - Evaluate which widgets are most popular by user role.


Search is not ideal for all widgets. Considering grouping widgets by 
category then grouping search for that category so the user understands the 
context. Short term solution would be to change “Filter…” to be more 
descriptive of what you’re actually searching.




   - 
   
   These two charts could be combined into one chart. Perhaps using the 
   Stacked Horizontal Bar Chart.
   

Change charts over to patternfly visualizations.

http://www.patternfly.org/pattern-library/data-visualization/bar-chart/



Switch to icon/text, or icon. Not just color (fails color blind standards)

Group red items at the top or only show errors.

Overall Comment: Where appropriate - offer quick link to corresponding 
widget main page.



   - 
   
   Offer status of host
   - 
   
   Make items within table clickable.
   


Overall Comment: Not all widgets need to use tables. For example Host 
Subscription status could be put in a donut or other visually appealing 
layout. This will make the page more “exciting”, and also allow a visual 
memory of which widget they are looking for that differentiates it from the 
other widgets.

Other tables that could be converted (not a complete list as this is based 
on what is available in my environment):

Content Host Subscription Status

Current Subscription Status

Task Status/Latest Warning Error Tasks

Virt-Who Configuration Statistics

Current Subscription Totals




   - 
   
   Subscription widget items should be clickable.
   

Potentially combine Task Status and Latest Warning/Error Tasks into one 
multi-faceted widget.


   - 
   
   Add date to this table. Also not clear what is applicable.
   




   - 
   
   This is more of a call to action piece than a widget. It would lend 
   itself well to a landing page.
   



   - 
   
   Unusual display of status/date. Break status out into icon next to title 
   (in same column, front of title), change “Status” to Date”, display date.
   


Overall Comment: Are all widgets fixed height? Can we change this?


-- 
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.

[foreman-dev] Weekly Dev/Design Meeting: Smart Class Parameters

[Roxanne Hoover]

https://docs.google.com/document/d/1H_2feb4MkuZobk6gXvYSGpnXl4Vxp5MgUSyfMbgsraA/edit


Smart Class Parameters

Presented by Ori





   - 
   
   Switch order of buttons 
   (http://www.patternfly.org/pattern-library/forms-and-controls/forms/)
   


   - 
   
   Put help text in inline help
   - 
   
   Remove entire link on “Reset Puppet Environment….” to Reset Puppet 
   Environment to match selected Content View.
   



   - 
   
   Omit inline help icon should not be blue.
   




   - 
   
   Tooltip for overriden flag icon so users know what it means
   - 
   
   Searching within specific environments, this is a greater problem of 
   consistency with search interaction. Some search criteria dropdowns appear 
   before the input box, and in this instance after.
   - 
   
   User Title Case for all labels… such as “ Key type” = “Key Type”
   




   - 
   
   Change help icons to black
   - 
   
   New Documentation button solution coming soon!
   - 
   
   Remove blue from Add Matcher
   - 
   
   Lines probably not needed in Specify Matchers table
   




   - 
   
   Add error icon and remove red text.
   




   - 
   
   When items are removed - remove error.
   - 
   
   Add Error icon to tab
   


   - 
   
   Remove lines, use spacing to create rows because fields are already 
   boxed in.
   


   - 
   
   Have full screen button remain in the top right.
   









-- 
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.

[foreman-dev] Weekly Dev/Design Meeting - Parameters and Overrides

[Roxanne Hoover]

https://docs.google.com/document/d/17d6dlTJzg4pCNXRnlRQ4w89UR7IOdAR94AFLRp58E9w/edit

Parameters and Overrides
Presented by Ori

Override error says it can’t be blank, but it’s already blank.

Override functionality is different for puppet class vs. global parameters. 
This should be the same.

Overridden Global Parameters move to Host Parameter… making Global 
parameters function like Puppet Class Parameters may reduce the list growth 
that occurs on overrides



Hide icon for puppet class could be exchanged for something for indicative 
of the action.

Marek “I’d like to see the OS clickable in the tooltip”

User doesn’t know why fields are disabled… let user know they lack 
permissions.

Determine rules around hiding buttons for users who do not permission. It 
is currently inconsistent. Consider showing but disabling actions. 

-- 
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.

[foreman-dev] Weekly Dev/Design Meeting - Smart Class Parameters

[Roxanne Hoover]

https://drive.google.com/drive/u/1/folders/0B5KC3vr5EkgmX0tWVmJ2LTNSWTg


Smart Class Parameters

Presented by Ori





   - 
   
   Switch order of buttons 
   (http://www.patternfly.org/pattern-library/forms-and-controls/forms/)
   


   - 
   
   Put help text in inline help
   - 
   
   Remove entire link on “Reset Puppet Environment….” to Reset Puppet 
   Environment to match selected Content View.
   



   - 
   
   Omit inline help icon should not be blue.
   




   - 
   
   Tooltip for overriden flag icon so users know what it means
   - 
   
   Searching within specific environments, this is a greater problem of 
   consistency with search interaction. Some search criteria dropdowns appear 
   before the input box, and in this instance after.
   - 
   
   User Title Case for all labels… such as “ Key type” = “Key Type”
   




   - 
   
   Change help icons to black
   - 
   
   New Documentation button solution coming soon!
   - 
   
   Remove blue from Add Matcher
   - 
   
   Lines probably not needed in Specify Matchers table
   




   - 
   
   Add error icon and remove red text.
   




   - 
   
   When items are removed - remove error.
   - 
   
   Add Error icon to tab
   


   - 
   
   Remove lines, use spacing to create rows because fields are already 
   boxed in.
   


   - 
   
   Have full screen button remain in the top right.
   









-- 
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.

Re: [foreman-dev] Weekly Design/Dev MeetingL Content Views

[Roxanne Hoover]

 Placement of buttons poor
>
> http://projects.theforeman.org/issues/19166
>
> > This wizard doesn’t have steps, introduce new wizard.
>
> http://projects.theforeman.org/issues/17345
>
> > Table scrolls which is unusual instead of pagination or longer page 
> scroll
>
> This is fixed now in master, all tables now use pagination.
>
> > Date is not handled consistently in tables (I know this is being 
> addressed)
>
> I am unaware of and date consistency work, maybe in Foreman?
>
Marek is doing work around this. 

>
> > Add additional information to bar, lets see the numbers especially on 
> failure. Do we want to keep mimicking dynaflow?
>
> What additional information should we add here?
>
Perhaps things like percentage complete, or x out of x. I think just the 
green bar isn't super informative.  

>
> > Number of column headers and columns do not match.
>

Thanks Walden! 

>
> http://projects.theforeman.org/issues/19283
>
> On Wed, Apr 12, 2017 at 2:39 PM, Roxanne Hoover <roho...@redhat.com 
> > wrote:
>
>>
>> https://docs.google.com/document/d/1Oqh0o676iS6ME9gGBPGCs-ToL8yDM882bIJZNNYcfOo/edit
>>
>>
>>
>> Dev/Design Weekly Review - Content Views
>>
>> Presented by Brad Buckingham
>>
>>
>>
>>
>>
>>
>> Create New Version button should be blue.
>>
>> Sync Status should be icon - When blue hover is active you cannot see 
>> status
>>
>>
>>
>>
>> List/Remove/Add -- Can these be added together? Will work on some design 
>> concepts.
>>
>> Also - second row tabs are usually line style, not box style. (
>> http://www.patternfly.org/pattern-library/widgets/#tabs)
>>
>>
>> Reduce redundancy of always use latest and specific version. Filtering 
>> for use latest?
>>
>> Space between tabs… too crowded. 
>>
>> Security icon should be red with capitalized S
>>
>> Can Affected Repositories be included into building a filter?
>>
>>
>>
>> Use PF Calendar. (
>> http://www.patternfly.org/pattern-library/forms-and-controls/datepicker/)
>>
>> Success item should have icon
>>
>> If Publish New Version is main item, make blue and break out other items. 
>> Otherwise relabel actions with drop down (I believe this is what we are 
>> moving forward with in other parts of the UI).
>>
>>
>> “De” and “dev-2” are serif typeface. Change to match other step typefaces
>>
>> This life cycle graphic breaks frequently… I will work on an alternate 
>> design.
>>
>>
>> User Help icon for help text on Composite View.
>>
>>
>> Can we use this same “Always Use Latest” drop down on the previous 
>> content views
>>
>> -Edit view is the same as previous content view?
>>
>>
>> If there is no data, put statement that there is no content, do not use 
>> inline message box.
>>
>>
>> Grey box should be error and appear on checkbox click. Change button to 
>> Cancel or Submit
>>
>>
>>
>>
>>
>>- 
>>
>>Organization dropdown doesn’t match patternfly
>>
>>
>>
>>- 
>>
>>New layout that communicates changes better. This is too generic.
>>- 
>>
>>Placement of buttons poor
>>- 
>>
>>This wizard doesn’t have steps, introduce new wizard.
>>
>>
>>
>>- 
>>
>>Table scrolls which is unusual instead of pagination or longer page 
>>scroll
>>- 
>>
>>Date is not handled consistently in tables (I know this is being 
>>addressed)
>>
>>
>>
>>- 
>>
>>Add additional information to bar, lets see the numbers especially on 
>>failure. Do we want to keep mimicking dynaflow?
>>
>>
>>
>> Number of column headers and columns do not match.
>>
>>
>> -- 
>> 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] Weekly Dev/Design Meeting: Management of Repositories

[Roxanne Hoover]

https://docs.google.com/document/d/1IoF--pWXXqjrAXSgBLVY3dRC-PeDcPZZxhCnl0wlaP8/edit

Management of Repositories

Presented by Brad Buckingham



For Sync Selected button - I think we were discussing buttons changing to 
Actions with drop down. 

Create Sync Plan - Button is not stylized to standard, and sync plan is not 
in line.

Day and time switcher is not patternfly 
(http://www.patternfly.org/pattern-library/forms-and-controls/timepicker/#/api)

Once sync plan is created you are left at the product page -- not at Create 
Product Page.. suggest putting in modal since the process is not multi-step 
and short.


Error messaging is not standard.



No products, should not be in a messaging box.

Action Button only has two options. Either change to “Action” with 
remaining to options or breakout into two buttons.

Remove dividing line after search


Upload vs. Save… original create GPG Key has different buttons than edit 
mode. Make the same to reduce confusion. I would recommend removing the 
upload button and sticking with Save since that pattern is also found in 
product creation.


Move help text to help icon/tooltip.

Form field label should be to the left of form.

Additional thought: If the form wasn’t limited to this area the text could 
be expanded more and this would reduce the length of this form.

On highlight text is not visible in Content column.

Blue Upload button vs. Sync now?

Fix layout here.  I can provide a layout for this.


Add Repository Column instead of drop down. 



Help icon should be moved to Upgradeable and be visible all the time.

Application help icon doesn’t follow the help icon for other tooltips.

-- 
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.

[foreman-dev] Weekly Design/Dev MeetingL Content Views

[Roxanne Hoover]

https://docs.google.com/document/d/1Oqh0o676iS6ME9gGBPGCs-ToL8yDM882bIJZNNYcfOo/edit



Dev/Design Weekly Review - Content Views

Presented by Brad Buckingham






Create New Version button should be blue.

Sync Status should be icon - When blue hover is active you cannot see status




List/Remove/Add -- Can these be added together? Will work on some design 
concepts.

Also - second row tabs are usually line style, not box style. 
(http://www.patternfly.org/pattern-library/widgets/#tabs)


Reduce redundancy of always use latest and specific version. Filtering for 
use latest?

Space between tabs… too crowded. 

Security icon should be red with capitalized S

Can Affected Repositories be included into building a filter?



Use PF Calendar. 
(http://www.patternfly.org/pattern-library/forms-and-controls/datepicker/)

Success item should have icon

If Publish New Version is main item, make blue and break out other items. 
Otherwise relabel actions with drop down (I believe this is what we are 
moving forward with in other parts of the UI).


“De” and “dev-2” are serif typeface. Change to match other step typefaces

This life cycle graphic breaks frequently… I will work on an alternate 
design.


User Help icon for help text on Composite View.


Can we use this same “Always Use Latest” drop down on the previous content 
views

-Edit view is the same as previous content view?


If there is no data, put statement that there is no content, do not use 
inline message box.


Grey box should be error and appear on checkbox click. Change button to 
Cancel or Submit





   - 
   
   Organization dropdown doesn’t match patternfly
   


   - 
   
   New layout that communicates changes better. This is too generic.
   - 
   
   Placement of buttons poor
   - 
   
   This wizard doesn’t have steps, introduce new wizard.
   


   - 
   
   Table scrolls which is unusual instead of pagination or longer page 
   scroll
   - 
   
   Date is not handled consistently in tables (I know this is being 
   addressed)
   


   - 
   
   Add additional information to bar, lets see the numbers especially on 
   failure. Do we want to keep mimicking dynaflow?
   


Number of column headers and columns do not match.


-- 
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.

[foreman-dev] Weekly Dev/Design Meeting: Facts and Trends

[Roxanne Hoover]

https://docs.google.com/document/d/1tQvpYYzPRoIwlWEGa5oaB248gD-zSs7IwLlG31Xzfo0/edit

Facts and Trends

Presented by Marek


Title of Fact Values|Host name is inconsistent, but also inconsistent 
throughout the application. A global solution should be brainstormed.

Can the nested items all be floated to the top in the table instead of 
forcing a user to drill down or perhaps a different layout to accommodate 
the nested items (folder icon, chevron, etc.)

Use chevron instead of colons for breadcrumbs

Action icon - convert to word button instead of icon. 


Load for chart does not use spinner. Legend text is small.

Empty page should follow PatternFly start page. This page looks like they 
(the user) did something wrong.

Is there an action that can be given on this page or craft a more detailed 
message.



Move towards new PatternFly Datavisualization charts. 
(https://rawgit.com/patternfly/patternfly/master-dist/dist/tests/area-charts.html)

“Trends for the last 30 days” layout can be improved to be more consistent 
with the other UI’s.

-- 
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.

[foreman-dev] Dev/Design Weekly Meeting - Remote Execution

[Roxanne Hoover]

https://docs.google.com/document/d/1StSf6700dvKMXLpgFsxQrq8yv3CI6MH_VI_8ucjs4og/edit

Remote Execution

Presented by Ivan



   - 
   
   Remove blue from documentation button
   
- Could Search input field be converted to standard search query

- Resolves to buttons are just icons without words… use word buttons, 
preview and reload. 

- Title case for labels, move help text to tooltip/icon help


Activation Keys. 


- Removal of two-pane view would fix the inline messaging error found in 
the left hand nav.

Providers and template - “ Providers and Templates

- “Manual Selection using Static Query -- change name to reflect previous 
search input.

- In instances when the donut is not present the remaining text above the 
donut is not obvious.




- Time stamps - Past a certain amount of days, just use the time stamp vs. 
“5 days ago”.

- Succeeded blocks are blue - They should be green, Pending could be dark 
grey, Total to remain blue.

- Change heading to “Job Invocations”

- Toggle buttons into one multi-select, separate Task Details and Cancel 
job. WIth breadcrumb interaction “Back to Job” will no longer be needed.

- Console grows as more lines are added. Limit growth area and add in 
scroll vs. having the page grow uncontrollably.




   - 
   
   Add status for last occurrence
   - 
   
   Change Cancelled icon to “pficon-error-circle-o” in red, Finished to 
   “pficon-ok” in green and Active to “fa-repeat” in blue.
   - 
   
   Change heading to “Recurring Logics”
   

- Change these both to grey or choose which one is more important and only 
have 1 blue button.

   - 
   
   Change “Effective user” to “Effective User”
   
- Capitalize “F” in “failed” and make red.

- Perhaps a larger discussion: See PatternFly Active Filters for handling 
to status filters below search bar: 
http://www.patternfly.org/pattern-library/forms-and-controls/filter/#/design

   - 
   
   Move help to label and remove blue explanation text next to icon.
   - 
   
   Change X for Template Input to “Remove” button
   - 
   
   Change “Template input” to “Template Input”
   - 
   
   Ensure title casing is used for all headers.
   

-- 
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.

[foreman-dev] Dev/Design Weekly Meeting - Organizations and Locations

[Roxanne Hoover]

https://docs.google.com/document/d/1kYpDUvcOikK6dShvN556MI1RtWLrYSyqDDp6YjUvAls/edit

Organizations and Locations 

Presented by Daniel

Login first time with no organization or locations

  - Setting up a new location or organization is using the old wizard, in 
the future convert to new PatternFly wizard, or reduce to one form if the 
fields are not numerous.

   - 
   
   Label field needs an info tip explaining what it is
   - 
   
   Names do not have to match
   - 
   
   Cancel/Submit buttons are touching
   

   - 





Managing organizations and locations

- Help brings you back to Organization set up -- remove help button, not 
helpful. Perhaps replace with documentation.



   - 
   
   Help text “This certificate…” should be moved into field level help.
   - 
   
   Is there a better way to organize the Edit view? (left hand nav/ twopane 
   view)? This also seems stylistically different than the other two-pane 
   views.
   





What happens for objects that are imported into Satellite (assigning 
organizations)

   - 
   
   Setting location and organizations for import are in different tabs
   

When you’re trying to edit hosts, org and location are disabled because the 
host is registered in subscription manager. 

Fail on mismatch isn’t clear, doesn’t allow trouble shooting, error is too 
generic



Setting user group to own host is not restricted by organization or 
location. 


Tasks for an admin user show all tasks even those outside of selected 
organizations.

-- 
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.

Re: [foreman-dev] Dev/Design weekly meeting notes: Subscription.Next

[Roxanne Hoover]

Ohad - Yes, agreed on point #4... this seems like the type of content that
would be ideal for the notification drawer.

On Thu, Feb 23, 2017 at 9:46 AM, Ohad Levy <ohadl...@gmail.com> wrote:

>
>
> On Wed, Feb 22, 2017 at 5:44 PM, Roxanne Hoover <rohoo...@redhat.com>
> wrote:
>
>> Link to Google Docs: https://docs.google.com/
>> document/d/1IsylCDVXl7_CiMEO5dCofhqcOReX4l9-Tv-jXcWG1y4/edit
>>
>>
>> Subscription.Next
>>
>> Presented by Thomas McKay
>>
>> Subscriptions through Content
>>
>>
>> Product> Detailed page
>>
>>
>> Products page requires the user to enable a repo but the user is left
>> with no clear direction to do so. Potential to link directly to Repo page
>> with filtered results?
>>
>>
>> May be a bug - Products page - Highlighted rows with blue link text is
>> unreadable. Would fail visual impairment tests.
>>
>>
>>
>> Repository page>
>>
>> Needs full redesign
>>
>>-
>>
>>Visual design is outdated.
>>-
>>
>>   How useful is the accordion set up?
>>   -
>>
>>   Are the tabs useful to the user?
>>   -
>>
>>   Lack of filter or search
>>   -
>>
>>   Content within accordion is inconsistent with the rest of the
>>   application
>>   -
>>
>>   Multiple bugs
>>
>>
>>
>> Sync Status>
>>
>>
>>-
>>
>>Needs complete redesign if not removal.
>>
>>
> a few points to consider:
> 1. Ideally, sync status page should also show sync status across
> proxies/capsules.
> 2. currently when using bulk actions and sync across multiple products, I
> am left without knowing the real state (I'm redirected to a task, which UI
> is simply not useful any form and shape) - I think most users want to know
> if their operation succeed and if its in progress how longer / progress
> indication of sort.
> 3. because sync uses tasks behind the scenes, many times tasks are locked,
> paused or in error state so the plus side is that the current page actually
> link to the specific task that failed or might need resume/retry etc. I do
> have a rant in general about using tasks with locks / pause etc for syncing
> content (especially for content with a sync schedule).
> 4. I would really want to see how sync status indication find its way to
> use the notification toast/drawer.
>
>
>>-
>>
>>   Sync status is inconsistent with other status’s,
>>   -
>>
>>   Difficult to differentiate status
>>   -
>>
>>   The combination of both an accordian and a table is not fine tuned
>>   -
>>
>>   Active checkbox could be it’s own column
>>   -
>>
>>   No filter or search
>>   -
>>
>>   Since this page seems to be used with a singular purpose, it may
>>   be best to integrate this functionality into the product page.
>>
>>
>>
>>
>>
>>
>>
>> Monitor> Dashboard
>>
>>-
>>
>>Sync overview widget -  convert status to icon.
>>
>>
>>
>>
>>
>> --
>> 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.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "foreman-dev" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/foreman-dev/xWTsMBingRY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> foreman-dev+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] Dev/Design weekly meeting notes: Subscription.Next

[Roxanne Hoover]

Link to Google 
Docs: 
https://docs.google.com/document/d/1IsylCDVXl7_CiMEO5dCofhqcOReX4l9-Tv-jXcWG1y4/edit


Subscription.Next

Presented by Thomas McKay

Subscriptions through Content


Product> Detailed page


Products page requires the user to enable a repo but the user is left with 
no clear direction to do so. Potential to link directly to Repo page with 
filtered results?


May be a bug - Products page - Highlighted rows with blue link text is 
unreadable. Would fail visual impairment tests. 



Repository page>

Needs full redesign

   - 
   
   Visual design is outdated.
   - 
  
  How useful is the accordion set up?
  - 
  
  Are the tabs useful to the user?
  - 
  
  Lack of filter or search
  - 
  
  Content within accordion is inconsistent with the rest of the 
  application
  - 
  
  Multiple bugs
  


Sync Status>


   - 
   
   Needs complete redesign if not removal.
   - 
  
  Sync status is inconsistent with other status’s,
  - 
  
  Difficult to differentiate status
  - 
  
  The combination of both an accordian and a table is not fine tuned
  - 
  
  Active checkbox could be it’s own column
  - 
  
  No filter or search
  - 
  
  Since this page seems to be used with a singular purpose, it may be 
  best to integrate this functionality into the product page.
  






Monitor> Dashboard

   - 
   
   Sync overview widget -  convert status to icon.
   




-- 
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.

[foreman-dev] Dev/Design Weekly Demo Notes - OpenSCAP

[Roxanne Hoover]

Google Doc can be found here:

https://docs.google.com/document/d/1HI64SEpDTDOa65amZof9SW9pEVZW2SjQZE7xCLxnDSg/edit


Notes here:

Openscap - Presented by Ondrej Prazak

Openscap items under Hosts> Compliance

Main Hosts Page> SCAP Contents

   - 
   
   Primary Button color - Help should be grey, “Upload New SCAP Content” 
   should be blue.
   - 
   
   Table headers are not sortable edit table header has no text. I believe 
   in other tables the header was “Actions”
   - 
   
   Table row items are not clickable unlike other tables
   

Details of item>

   - 
   
   Info tip for upload text.
   - 
   
   Spacing between uploaded text and upload button
   - 





   - 
   
   Error formatting including error on tab. Remove “No File Chosen” because 
   this is not true, they choose a file just not an acceptable file type. 
   Place error messaging in it’s place. “Upload SCAP Datastream file” should 
   be in an info tip. Tab needs error icon
   


   - 
   
   New Scap Content page and Edit page launch the same page however one is 
   two pane and one is not. Conversion to full pane would remedy this.
   

Hosts>Policies

   - 
   
   New policy wizard does not follow patternfly standard.
   - 
   
   Depending on the length of this process, a wizard may not be needed.
   
Main page - Help button is dark blue? It should not. “New compliance 
policy” is primary button

Host>Policies>Details

   - 
   
   Layout of tiles is not efficient. This is probably not a low level of 
   effort to fix. Additional thought would be needed on better layout.
   
Host>Policies>Details>View Report

   - 
   
   Delete button is red, it should be grey unless it is ultra destructive. 
   Also which button would be considered the primary action? It should be blue.
   - 
   
   Considering changing “Result” text to icons. 
   

-- 
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.

[foreman-dev] Dev/Design Weekly Demo Notes - Roles and Permissions

[Roxanne Hoover]

https://docs.google.com/a/redhat.com/document/d/1GA9aHkr3DGVzCan36EWcVORuC8g4gdyG527NxJKzrKE/edit?usp=sharing


Roles and Permissions presented by Marek

Main Roles page has two different colored buttons. Documentation button 
should be grey (I will double check this).


New Role> 


   - 
   
   General Role description not needed
   - 
   
   Inline messaging has two icons… second icon is an inline help and should 
   be moved next to labels
   

   - 
   
   FYI - New dual pane selector coming soon!
   

Role tab>

   - 
   
   Errored Tab - I believe there was a recent github story around styling 
   for this, and that an icon would be present as users with color blindness 
   cannot see the errored tab.
   
This is from github 



Filters on main table (single pane view result) >

Then click on filter - Warning text is not within a box… it should be. 
Driven by resource type.

Filter checkboxes have inline help that should be next to the label, not 
the checkbox

Error on Permission required field - text is not aligned - error on tab is 
not standard.


Click on item> Filter tab

No way to know it’s related to which left hand item


Users>


   - 
   
   Delete button is not standard
   


   - 
   
   Permission denied error formatting can be improved. Back button shoudl 
   be outside the box, increase box width, remove horizontal line. Remove 
   search.
   


Other Notes:


   - 
   
   Marek suggestion - ship with more default roles. Some would not be 
   editable. Would need to notify user why or visually indicate that. Perhaps 
   a new column indicating its source, or listing that in the details of a 
   role. Templates show a lock in a new column.
   


   - 
   
   The Filters Tab and the Filters page (see compared screenshots below) 
   are very similar if not nearly identical in content. Is it possible to 
   combine them into one screen. Clicking on either the row, or the filter 
   button would take you to the same page.
   

-- 
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.

[foreman-dev] Dev/Design Weekly Demo Notes - Tasks

[Roxanne Hoover]

Foreman Tasks Demo - Presented by Ivan



Content> Products> Repository>

Edit fields icon too far away from fields. With multiple rows it can be 
difficult to determine which edit icon goes with which row. In the event of 
no item in the row, there is a large gap between the edit and field label. 
This problem can be found throughout the application. Additional research 
should be done to determine best solution/placement or if it is needed at 
all being that there is a highlight - and an inline edit is available.


Tasks> Table

   - 
   
   Icons for visual state for status 
   - 
   
   PatternFly Listview might be beneficial, we would have to look at the 
   content.
   - 
   
   Notification drawer would be helpful in letting users know the task 
   status
   - 
   
   Sort column headers - This issue has been bugging our customers.
   

Tasks> Table> Click an item>

   - 
   
   Notification drawer would be helpful in letting users know the task 
   status
   - 
   
   Start at vs Started at…. better define labels better.
   - 
   
   Spinner + pending + status bar… two visual elements displaying the same 
   progress.
   - 
  
  Perhaps “100% Complete” could show Completed items out of Total 
  items, which the bar displays the % complete. 
  - 
  
  Only show percentage as a whole number.
  - 
   
   The arrangement of the content could be improved to group related items 
   and buttons together. I’ve made a note to look into this.
   

   - 
   
   Perhaps show the details of statuses from Running steps tab near the 
   status.
   - 
  
  Upon additional thought. Is there enough content in each of the tabs 
  to warrant their own tab? It seems like the tabs are heavily 
inter-related 
  and it may be helpful to have some of that information grouped together. 
  Moving from two-pane view would offer more screen space to potentially 
fit 
  content together.
  

Tasks> Table> Click an item>Errors Tab>

   - 
   
   I do not think an inline notification box is needed here.
   



New Repository>General Information>

Required fields such as name, should be marked as required.



Other Notes:

Make Tasks more integrated into the workflow

Ivan Necas wants tasks in a table screens from other products.

dLobatog - “which proxy executes which task?”

-- 
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.

[foreman-dev] Re: Is this the new UI style from patternfly?

[Roxanne Hoover]

I've not seen this style of table before either...

On Thursday, January 19, 2017 at 8:06:08 PM UTC-5, Tom McKay wrote:
>
> I was making a role filter and see that the UI table is very different 
> than other pages[1]. Is this what we should update the katello pages to as 
> well? I couldn't find equivalent on patternfly.org.
>
> [1] 
> http://www.awesomescreenshot.com/image/2080169/0a330d7663bc9617fbe28e2ac49b
>

-- 
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.

[foreman-dev] Dev/Design Weekly Demo Notes - Users, User Groups

[Roxanne Hoover]

Sharing my notes from the weekly Dev/Design Demo. This week Marek presented 
on Users, User Groups, Roles.


These are my notes and thoughts only from a UX/UI perspective, they are not 
mandates and are open to feedback/discussion.



General Comments - issues found throughout the application:


   1. 
   
   Button color, placement and style - Buttons appear outside of standard 
   color, stylization and layout expectations.
   2. 
   
   Title case for forms and buttons - Some form labels and buttons do not 
   follow title case. For example in the Users section: Authorized by 
   (incorrect) vs. Authorized By (correct).
   3. 
   
   Inline Messaging Stylization and placement - layouts are inconsistent as 
   well as placement on the page.
   4. 
   
   Documentation Button - This needs to be evaluated for best placement and 
   color. It varies throughout the application.
   5. 
   
   Infotips - many fields have additional description text that should be 
   placed in an infotip. Occasionally the description text is redundant to the 
   form label.
   6. 
   
   There is the occasional tooltip on a button. I find it intrusive.  A 
   good rule of thumb is that if a button isn’t self-explanatory, then there 
   is something wrong with the button or the process.
   
   
Notes:


   1. 
   
   Password authorization - Weak/Normal/Strong visualization would not pass 
   528 compliance for those visually impaired. The colors associated with each 
   strength level seems mismatched. For example: Normal is red. A red status 
   as well as form field highlight indicates an error. Weak is grey, and also 
   possibly not high enough contrast for the visually impaired. The solution 
   may be to simplify the password strength to text only, “Weak Password, 
   Strong Password”. Also - greater thought or discussion could be had around 
   “Normal” or “Strong”. If a “Normal” indicator is shown, does this actually 
   change user behavior in the same way “Weak” does? Perhaps only “weak” is 
   needed.
   


   1. 
   
   Inline messaging regarding email notification should be moved above 
   content but within the content box.
   


   1. 
   
   Login button changes to loading. I believe this is not standard 
   patternfly behavior.
   


   1. 
   
   Users > Email settings
   1. 
  
  Search drop down has a find field. It doesn’t seem like this is 
  practical given the limited number of choices and the inability to make 
  more options. 
  1. 
 
 I believe an alternate layout and input method could be used that 
 would make choices more obvious at first glance.
 2. 
  
  Order of fields changes on submit. They should remain in the same 
  order.
  3. 
  
  Test Email button seems misplaced and not patternfly standard button.
  
  2. 
   
   Admin/Administrator check boxes - Text labels should be consistent. 
   Consider using infotip to better describe the role. A better layout may 
   also make it feel less out of place when placed alongside the dual 
   pane/shuttle selector. 
   
   3. 
   
   Edit User Page:
   1. 
  
  Description (box description is generic and most likely not needed).
  2. 
  
  Re-login Permission denied box layout is not correct. Filter field is 
  touching masthead.
  
  4. 
   
   User Group Main page -  Delete button, text is red. A default grey 
   button should be used. Perhaps confirmation of deletion in terms of 
   extended implications could be displayed?
   
   5. 
   
   New Authorization Source Create page does not follow patternfly.
   
   6. 
   
   LDAP Authentication Page > Account:
   1. 
  
  Group Base field is shorter than LDAP Filter.
  2. 
  
  LDAP filter should be larger to accommodate multiple line filters 
  (common)
  
  7. 
   
   User Groups > External groups:
   1. 
  
  External groups = External Groups
  2. 
  
  I believe the table functionality could be improved to show more 
  details/actions with potential inline editing. This would remove the 
“show 
  linked external user groups” button whose results displayed could be 
  extraordinarily long. 
  3. 
  
  As an additional note - moving away from two-pane view would allow 
  detailed pages like this to take advantage of additional screen real 
estate.
  









-- 
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.

Re: [foreman-dev] Vertical Navigation

[Roxanne Hoover]

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 
> > 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

Re: [foreman-dev] Vertical Navigation

[Roxanne Hoover]

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! 
>>>>>

Re: [foreman-dev] Vertical Navigation

[Roxanne Hoover]

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!



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). 
>> > 
>&g

Re: [foreman-dev] Vertical Navigation

[Roxanne Hoover]

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/optou