Foreman Button Proposals

Development
1

Hi, All

Recently I have been looking on the Foreman Action Buttons and created a
proposal for the buttons usability improvement.

The proposals are is the following:

1 - Each page should have one clear call to action, where the primary
action button is always blue, but all others are the secondary
buttons(gray). There is an accessibility reason being that on enter the
primary button should be enacted. It's possible that there could be no
primary action button on a page.

2 - Address inconsistent use of the close icon in modals and other screens.

3 - Change buttons with “New” labels to use the appropriate PF icons + the
“Create” label, as specified by PatternFly.

The detail information is in the PDF file, please have a review.

Before I begin working on fixing these items in the code, I’d love to get
everyone’s feedback.

Thanks

June - UXD Team

foreman button proposal.pdf (11.3 KB)

2

>
>
> Hi, All
>
>
> Recently I have been looking on the Foreman Action Buttons and created a
> proposal for the buttons usability improvement.
>
> The proposals are is the following:
>
>
> 1 - Each page should have one clear call to action, where the primary
> action button is always blue, but all others are the secondary
> buttons(gray). There is an accessibility reason being that on enter the
> primary button should be enacted. It's possible that there could be no
> primary action button on a page.
>
> 2 - Address inconsistent use of the close icon in modals and other screens.
>
> 3 - Change buttons with “New” labels to use the appropriate PF icons + the
> “Create” label, as specified by PatternFly.

I think I do agree with 1 and 3. The 'x' button however at times might
be hard to see, so if you get started with this:

  1. send PRs for each section separately, reviewers will appreciate this
    :slight_smile:

  2. send them across theforeman/foreman, foreman_discovery,
    foreman-docker
    katello/katello and other plugins that form part of the community and
    contain UI sections.

  3. I'm dubious as to whether the single 'x' will make it easier to
    discover, at first glance it looks like something I'd struggle to find
    but let's see on the PRs. You can start by making that change in all
    parts that are non-controversial though!

>
>
> The detail information is in the PDF file, please have a review.
>
> Before I begin working on fixing these items in the code, I’d love to get
> everyone’s feedback.
>

Thanks June, your effort on making Foreman adopt Patternfly is highly
appreciated

··· On 12/21, junzhang@redhat.com wrote:

Thanks

June - UXD Team

–
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

–
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato