Posted by & filed under PatternFly.

Don’t wanna miss a thing? Get caught up on major PatternFly happenings and give some thanks to the design community members who reached new heights this quarter.

In this edition:

What’s new

A lot’s happened since our last contributions post in September. Let’s talk about it.

We added JS implementation on

PatternFly is all about consistent design that’s easy to implement. With that in mind, code pages on now link to available javascript implementations of our design patterns.

We built new login pages

Login Page

We like to make a good first impression. The new login has an updated look and feel, responsive design, and supports a whole bunch of use cases like:

  • Login from a social media or third party account (like Google or GitHub)
  • Single sign-on (SSO)
  • Multi-factor login scenarios

The design document provides guidance on how to handle common errors that might occur during the login process. Check out all the new login pages on our website here: Login Page, Multi-Factor Login, Single Sign-On.

We revised the Filter pattern

The new and improved Filter pattern is more modular and flexible. The basic interaction model for filtering content from a toolbar remains unchanged, but the new pattern explains how you can use a variety of filter triggers to support different use cases. We also introduced two new filter trigger patterns:

We’re using new hover colors for List Views

We changed the hover color for rows in a List View from light gray to light blue. “But why?” you might ask. Two reasons:

  • Better consistency between hover styles for lists and tables
  • To avoid confusion between a hover state and an expanded state for lists that support row expansion

More consistency and less confusion? Double yes!

We improved the recommendations form validation

We updated the Errors and Validation pattern to clarify how and when we should validate the information users enter on forms. The updated recommendations cover how to handle the differences between client-side and server-side validation and when to disable submit buttons.

And so much more!

We made tons of incremental updates and small additions since last fall to improve the quality and consistency of the pattern library and generate new patterns.

“Tell me more!” you say? Take a look at the new Slider pattern and the standard loading state for dashboard cards for some examples of this work.

Thanks and high fives

We want to give a special shout out to all of the designers who contributed to the work we’ve featured here.

A hearty PatternFly thank you to Kyle Baker, Michael Coker, Jenny Haines, Colleen Hart, Leslie Hinson, Chris Shinn, Haley Wang, June Zhang, Melody Zhong, and Tao Zhu.

Our goal is to recognize all of the contributors who keep PatternFly moving forward. If there’s anyone we missed, please forgive us! And then let us know so we can make a big fuss about them in our next Wrap-Up.

Help wanted (in case you missed it)

Help Wanted

The PatternFly design library is packed with reusable patterns that help designers and developers build consistent and usable product experiences. But it would be nothing without contributions from community members like you!

Like a hand without a glove, we have a growing list of common use cases that aren’t yet covered by a design pattern.

Check out the list of new design patterns we need help with right now, and learn more about how you can contribute to PatternFly.

Design templates for agility and speed

We have PatternFly design templates available for Balsamiq Mockups 3 and for Sketch. You can download these template files from our GitHub design repo.

These templates will help you quickly create PatternFly compatible wireframes and design mockups, so please download and use them.

Suggestion box

This is our first installment of the Wrap-Up, and nobody is perfect. If there’s something you’d love to see here that we’re missing, please let us know!

Want helpful tips from the community? What about a fun facts about the team? Puppy pictures?

Fill out this form to submit your ideas, or just send an email to [email protected].

Posted by & filed under PatternFly.

PatternFly relies on the contributions of designers and developers like you to grow and improve the content of our design pattern library. When you make a design contribution, you help improve product usability and consistency with reusable solutions for common use cases.

How can you help?

Check out the list of new design patterns we need help with right now. If you have related designs to contribute or an interest in getting involved, reach out to Matt Carrano at [email protected] or find him on the PatternFly Slack channel.

New pattern requests

File Upload pattern

Add a pattern that will enable a user to upload files in two ways:

  • Browse for and select a file to upload
  • Drag and drop files into the web app

See patternfly-design issue #506 for more details.

Tab Usage pattern

Provide guidelines and examples that outline how to use different tab styles in a page.

See patternfly-design issue #526 for more details.

Session Timeout pattern

Specify how to inform a user that a session has timed out.

See patternfly-design issue #498 for more details.

Loading states for content views

Define the appropriate feedback to provide a user while loading data into any content view, including List, Card, and Table views.

See patternfly-design issue #467 and related issues #468 and #469 for more details.

Date and time selection

Enhance the documentation for Datepicker and Timepicker with guidelines on using these components together or independently and working with different date and time formats.

See patternfly-design issue #459 for more details.

Bug fixes

Help keep PatternFly design documentation up to date and relevant by addressing small bug fixes. View a complete list of issues that are up for grabs.

Did you know?

We have PatternFly design templates available for Balsamiq Mockups 3 and for Sketch. You can download these template files from our GitHub design repo.

These templates help you quickly create PatternFly compatible wireframes and design mockups, so please download and use them.

As always, we welcome your questions, comments, and ideas about how to make PatternFly Design better!

Posted by & filed under PatternFly.

We’d like to officially announce that support for Sass has been added as a core feature of PatternFly and is now available in the 3.31.0 release. Many in the community had already been using the PatternFly-Sass package and the concepts behind that repo have been brought into PatternFly core.

We are doing this because many products found that they preferred using Sass instead of LESS for their CSS preprocessor and the community provided PatternFly-Sass needed official support so it wouldn’t fall behind.

How will this impact you?

For Consumers of PatternFly:

If you are using PatternFly css in your website only, this shouldn’t impact you at all. If you are using the less partials instead of patternfly.less or patternfly-additions.less, the mixins file had to be broken into two separate files (mixins.less and bootstrap-mixin-overrides.less) so you’ll need to add a second reference to the bootstrap-mixin-overrides.less file.

Contributors to PatternFly:

Supporting Sass as part of our release means that each contributor to PatternFly core css needs to make sure they build the Sass and include it with their PR for review. The readme explains how to do this here: Any code reviewers should also ensure that any less changes are accompanied by corresponding Sass changes.

As always, we appreciate feedback on this and any other PatternFly features that have been provided and please either use the mailing list or our slack channel ( to join) to ask questions. To learn more about how to contribute to PatternFly or how to use it in your project, please see the readme at: or view our website at

Posted by & filed under PatternFly, PatternFly Design.


One of the biggest challenges with web design is understanding typography. Font choice, weight, size, and spacing are all important things to consider when you are setting up type for your website or application.

If you aren’t familiar with the term vertical rhythm, simply put, it’s what keeps vertical spaces, between elements on a page, consistent with each other.

Having a hard time with type?

If you look at this article and you get warm fuzzy feelings from the type, but don’t understand why, vertical rhythm might be for you.

I am a core contributor to PatternFly, a design system for enterprise web applications. We are really excited about our next big CSS release and we’ve been working on a bunch of great new features for it.

One feature we are building out is vertical rhythm.

With PatternFly our goal is to offer a consistent design that is easy to implement. We want our users to feel confident that the overall style is well thought out and considers things they may not have an eye for.

Let’s talk about our PatternFly type

By default PatternFly makes the font choice of Overpass for you, we also consider things like line height, weight and size for paragraphs, lists, and a bunch of other type elements.

Often users will use heading tags based on the style they want, rather than the semantic meaning of the tag. In order to avoid this, we’ve stripped all the styles from the headings and offer classes to style them instead. So you can use that <h1> at the top of your page and apply the .h3 class to get the style you want.

This results in a scenario that is not ideal because our users have to apply classes to all headings for pages that are full of content.

That’s where vertical rhythm comes in.

Using our .pf-vertical-rhythm utility class you can apply it to a wrapper and any encompassing headings will get the weight, size and margin that we’ve defined.

Let’s take a look at some examples.

Below you will see and example of an pretty standard page full of content. I’m sure some of you look at this and don’t know where to start.

Now, let’s look at the same page with a class of .pf-vertical-rhythmapplied to its wrapper:

By adjusting a few styles, we now have a page that looks much better.

Vertical rhythm is not complicated, but it can easily be overlooked if you don’t have an eye for it. We wanted to offer something to our users who would rather rely on a set of predefined rules than come up with something on their own.

By implementing vertical rhythm through out the application you ensure a consistency that your users will be grateful for, wether they know it or not.

This is still a work in progress, we’d love to hear your feedback and suggestions.

Posted by & filed under Forms, PatternFly.


Problem Solving

Toggle filter addresses the problem of a user frequently accessing filters, repeatedly, and having to select them over and over again. It will allow a user to quickly toggle, an individual filter criteria on and off, and immediately see the results, without having to relocate the filter criteria, via the drop down. It also addresses users knowing or discovering the existing filters and learning what data will be returned when selecting a filter.

Use Case(s)

User of an application, repeatedly uses, common filtering criteria, and wants to be able to frequently vary the return results of the criteria, without having to open and close a filter and relocate the same filters over and over again.


The requirements  stemming from the product that some users comp up with the requirement and send email to the [email protected].

  • Toggle filter can be used with or without other filter patterns, but the filters cannot be active at the same time.
  • An application will pre-define the toggle filters.
  • Toggle filtering will not offer the ability for an end user to define which individual filters are used.
  • There is a finite number of toggle filters.

Products already using this UI

Currently, customer portal is using similar UI as below:





Toggle filter is a component that enables a user to quickly access a common, singular filter criteria. It is displayed as a toggle button group. The application can use up to 4 quick filter criteria.


Toggle filter used Filter

The toggle filter can be used with or without Filter pattern, however, the filters cannot be active at the same time. When using together with the Filter, the results of the two filters are separate. Toggle filter results are not dependent on the Filter.  When a user clicks the toggle filter, after getting a result from the Filter, the previous filtering criteria (pill) and criteria results will be cleared, and replaced by the new results, based on the toggle filter criteria.


Design Interaction

1.Toggle filter attributes:The attributes are single select buttons. The toggle filters are not representative of multiple filtering criteria per button. Each toggle button is an “or” command. Only one button can be chosen at a time.The widget style is using the style of the current Patternfly Button Group. See Patternfly button group.


2.Toggle filter used with Filter pattern,  toggle filter not in use: When using together with Filter, The filtering results are independent. The widget style will be the same as the current filter UI. Current filter pattern can be found here


3.Toggle filter used with Filter, toggle filter in use: When a user clicks the toggle filter after Filter activated, the previous filtering result will be clear and replaced by the new result.


4.Toggle filter used before Filter : When a user clicks the toggle filter after Filter pattern activated, the previous filtering result will be clear and replaced by the new result.


5. Toggle filter used Filter: In the case that user uses the Filter after having a result from the toggle filter, the filter result will be replaced by the Filter when the Filter is activated.


Please feel free to leave comments on Github:

Posted by & filed under PatternFly, UX Research.

by Melody, Tao & Haley

List views have been used widely across products. After we did some research about the applications list view (Research could be found here) , we find out that we could update and create some new guidelines for PatternFly. Summarized as following:


1. New Content Layout Template

Currently we don’t have a content layout template for Pattenfly list view pattern. Following is a new layout template to clarify the content order of the list view pattern.

2.  Alignment rule and Responsive Rule Improvement

Currently Patternfly have two different list view status:

1. Standard List View

2. Stacked List View ( list-view-pf-stacked)

We redesigned the alignment and responsive rule based on the two above situation:
1. Standard list view alignment – The default alignment for the list view row is vertical center aligned. When the screen size is less than 992px, the list view row will change to top aligned ( the same as stacked list view).
2. Stacked list view alignment – The list view row is top aligned in all screen sizes.

List View Row Change Based On the New Alignment Rule

The second and the third row will change form vertical aligned to top aligned.

3. New List View Row Template

“Date” and “Lable” are common element in application, so we try add some new template to PatternFly.

Please feel free to leave comments and suggestions.

Posted by & filed under Navigation, PatternFly, UX Research, What's New on

As the design of PatternFly becomes more modular, a project has been kicked off within the community to update the website’s information architecture (IA) to better align with the new framework architecture to better meet user needs. To guide the decision making process for the re-design we’ve decided to employ the Open Decision Framework (ODF), a tool developed within Red Hat for making project decisions based around open source principles.

Open Decision Framework

According to the ODF, “open decision making is transparent, inclusive, and customer-centric. It involves clearly sharing problems, requirements, and constraints with affected parties; collaborating purposefully with multiple stakeholders to secure diverse opinions and comprehensive feedback; and managing relationships and expectations across competing needs and priorities.” [1]  The four main phases of the ODF process include:

  1. Ideation
  2. Planning and research
  3. Design, development, and testing
  4. Launch

How We’re Using the Open Decision Framework

Our plan is to use ODF principles to guide the design decisions made in re-architecting the PatternFly website. We will:

  • Create and maintain a common fact base where important facts and information about the project will be shared with all PatternFly stakeholders.
  • Engage the PatternFly community to participate in the UX research activities that will feed the design process.
  • Publish a project plan with roles, dates, constraints and proposed activities in the common fact base.
  • Provide regular updates through the PatternFly blog and @patternfly_des on Twitter.
  • Publish and solicit feedback from the community on all research findings.  
  • Communicate the decision factors and provide opportunity for community feedback when key design decisions are made.
  • Evaluate, acknowledge, and incorporate the feedback and highlight any design changes made in response to that feedback.

What’s Been Done So Far

Over the past several months, some background UX research has been completed in preparation for the project.  In March 2016, a baseline usability test of the PatternFly website was completed to identify issues with the existing website information architecture and design. As a result of this test, minor updates were made to the website’s Home, Patterns and Blog pages. In January 2017, interviews were conducted with 10 experienced PatternFly users (both designers and developers) to identify concerns with the current PatternFly website IA and determine requirements for a new IA. A summary of results from that activity is available here.

Next Steps

In the coming weeks and months, we will conduct additional research to guide the design of the new PatternFly website. Two activities are currently being planned.

  1. A tree-testing exercise to test the usability of a newly proposed taxonomy for PatternFly website that would reflect Modular Design principles. Participants will be given a series of tasks in which they will need to navigate the PatternFly site-map to find specific pieces of information. The time taken and number of steps to complete each task will be recorded.
  2. An online card sorting activity to help understand users mental models of the new taxonomy  and how different content should be organized.

We plan on leveraging the PatternFly mailing list and social media to solicit volunteers to participate in and possibly help facilitate these activities. We look forward to leveraging the PatternFly community and ODF to help improve the user experience of the PatternFly website.



Posted by & filed under PatternFly.

As the application landscape evolves, design resources must also evolve. The PatternFly community has rapidly grown and technology has evolved so we are now able to push the boundaries. PatternFly was originally designed with a utilitarian mindset, focused on supporting data dense management applications. This mindset shaped the design of the PatternFly we see today.


With the growth of PatternFly, we now have a more diverse community. This diverse audience brings a much more diverse set of applications and use cases. Specifically, they have brought consumer facing applications, which have a marketing focused aesthetic that is missing from our current design. These new consumer style applications bring different styling expectations such as, bold, colorful graphics which help them stand out from their competition.


In an effort to support these new consumer style applications, we have taken a few steps to evolve our current design to meet these needs. Our goals are to create new graphically bold styling. The focus of this effort is on the look and feel – color, sizing, positioning, imagery, type, icons and will not affect content or interactions.


Since styling can be subjective, it is important to gather quantifiable data to inform design decisions. We conducted a desirability study to compare our current design against two new designs. All three concepts used the same content and interactions to easily compare.


Measuring Look and Feel


Desirability studies are designed to measure participants’ emotions by giving them a vocabulary of positive and negative word pairs that they can assign to each design. Additionally to ensure we received a definitive result, we also asked each participant to choose which design best described one of a series of positive attributes.


Twenty-two participants were lead through an identical workflow foreach concept.  Then, they were asked to rate each concept, based on the provided vocabulary, and encouraged to share any additional thoughts for each. We also gathered additional information about the participants, such as company, occupation and their role.


The Concepts


Using the sample application content and Red Hat branding as a base, we designed three concepts. The control design uses our current PatternFly design styles. The new concepts use two different styling techniques to display content. The dark design relies on heavier graphics and imagery whereas the light design utilizes typography and color to establish hierarchy. We purposefully exaggerated each concept with the intent of generating a distinct reaction to more easily compare the desirability of each concept. These are just concepts, specifically designed to get a reaction, to validate a new visual direction.



The Results


We calculated the total number of positive and negative words associated with each design concept. A majority of the feedback was positive for each concept. The control design receiving majority of the negative word associations and the Light receiving a majority of the positive.


We broke down the words associated with each concept and arranged them by frequency. The saturation of the color is associated is scaled to reflect the frequency.

The control design received 44% of the total negative words associated with the concepts. As stated above, this concept reflects the current PatternFly styling, which was created with a utilitarian approach. The study reflects this strategy with the highest associated terms being “Useful” (20) and “Conservative” (9).



The dark design received neither the most positive or negative responses.  The highest associated terms were “High Quality” (21) and “Confusing” (8). This concept was rated highly for ‘Unwelcoming’, potentially a result of the dark black and red values, which people tend to associate with evil.



The light design received 36% of the total positive words associated with the concepts. The highest associated terms were “Interesting” (22) and “Conservative” (5). Every participant rated this concept as “Interesting”.



We compared each design across the total positive and negative word counts. You can see in each design how we improved or regressed as you look at the frequency across terms.


Overall Performance


Lastly, we asked users to choose between each design based on the positive terms above. For example, which design is the ‘highest quality’? You can see in the results below, participants rated the new concepts higher than the current PatterFly design by a margin of at least 50%. The darker design rated highest for “High Quality” and “Easiest” to use while the lighter design rated highest for “Innovative” and “Satisfying”.



We also examined the data by role. There was a distinct preference between participants with business and design backgrounds. The business participants preferred the dark while the designers preferred the lighter design. One theory could be that  participants with a sales background prefer the more bold and impactful designs because it helps their products stand-out from the crowd whereas designers prefer a more nuanced and subtle approach.


In summary, the data shows that users prefer the newer designs three times as much as the control.



What’s Next?


Since these designs are just concepts to test a direction, there is still a lot of design decisions and work left to be done. There are many considerations that these designs do not address.


This is only the starting point. It will take time to create a great solution to fit the PatternFly community’s needs. As we progress, we will continue to keep you updated.

Posted by & filed under PatternFly.

Hello friends!  I recently gave a talk at the first annual PatternFly conference on some easy ways to take the writing you do for PatternFly from good to great.  In it, I shared a few items that would comprise a short checklist that you can refer to as you write.  Those items, and some others, are included here.

For patterns:

  • Does this address Faith the front-end developer’s main questions and concerns?
    • Does it give her what she needs to know to build a UI that impresses her team?
    • Does it give her design guidance and info without lots of jargon?
    • Is it written clear and completely enough that a beginner can be successful?
  • Does this address Ron the reluctant front-end developer’s main questions and concerns?
    • Does it include all the details he needs to plug-and-play?
    • Is it written concisely without a lot of detail (backstory, implementation details, etc.) that won’t help him achieve his goals?
    • Have I described how all the pieces work together, in case he wants to reverse-engineer it?
  • Does this address Inga the interaction designer’s main questions and concerns?
    • Have I described the use cases that this pattern addresses well?
    • Have I described use cases that this pattern is NOT suited for?  Did I include links to other patterns that might fit those other cases?
    • Are the differences in the variations clear?  Is it clear when to use one vs. another?
    • Was this pattern tested with users?  Is there a link to the findings?
  • Have I addressed outstanding issues (i. e. incomplete information) and questions?  Is there upcoming work on this pattern that I should mention?
  • Is the writing style straightforward but not formal?  Does it have a tone that sounds neutral and not like I’m telling you about it personally?

For blog articles:

  • Can I break this into multiple posts?
  • Is my call-to-action clear?
  • Did someone who is like one of the personas read this?  (For bonus points, have someone like each of the personas read it and give you feedback.)
  • Did I run this through Grammarly to check spelling, punctuation, and grammar?
  • Did I read it out loud?
  • Does this sound like something I would say?  In other words, is this written in my voice?

This list is not complete and should be considered a living document.  If you have suggestions for additions, please let me know if the comments.  If you use it for your writing, comment on how it worked for you.

Finally, if you attended my talk, I appreciate it!  Let’s keep the conversation going — let me know your thoughts below about any writing you’ve done (or would like to do) for PatternFly.