Posted by & filed under Content Views, Table View.

It’s time for PatternFly to revisit pagination within data views.  This includes tables, list, and card views. In the past, pagination was part of data tables but we recently wanted to start fresh with data tables and gradually add elements as we go. Pagination seems like a fairly simple and straightforward concept but with multiple pages, it could get messy if not done correctly. We looked at a variety of tables and reviewed how pagination behaves within them for this story


Before we move forward, let’s briefly discuss the persistent elements. Most elements/controls related to pagination would be found on the bottom of the table.  This includes:


  • See the number of items on a page and total number of pages
  • See how many pages of data there is.
  • View which page you are on (current location)
  • Modify how many pages are being displayed.
  • Skip to the next or previous page.
  • Skip multiple pages.
  • Navigate to the first/last page.


Selection info will be shown in the top right of the table. With this story we wanted to add the ability to select all items across multiple pages. Initially, if you select all on a page, it will select all items only on that page. Then it would prompt the user to select all items across the table. Below I came up with two options to address pagination selection across pages along with the pros and cons of each.




The first option above shows a new row appearing within the table under the row headers, in the form of a message. This message informs you of how many items are selected and gives you the ability to select all.  Once all are selected, you have the ability to clear selection from the within the same message.


As you page through the table, all items will remain selected, however the message will not be shown. View below:




Option 1 Pros:  the addition of the message row is obvious and will draw the user’s attention.
Option 1 Cons: Table height would have to adjust to accommodate new message row.  Also, does the placement of the message make sense under the row headers?  Furthermore, it’s redundant to show the number of items shown twice (upper right, and in message)


Option two addresses the cons of option 1.   Selection info will stay persistent in the top right, whether there are none or all items selected.  This way, the user always has the ability to select all or clear selection. They still have the ability to select all items within a single page as well as individual items.




Option 2 Pros: No need for creating a new message row and shifting the table down.  No redundant info. Persistent location and info shown.
Option 3 Cons:  Might not be obvious that you can select all items. Does is seem hidden?


Overall option 2 was preferred. People liked the less obtrusive and simple behavior of it. However there were a couple concerns that surfaced:


  • Language: Does this language make sense? I thought it was helpful to have the “Selected:” label so that way it could stay persistent and we could still show info when none are selected.
  • Selection info shares the row with Filters.  As filters are added, they will appear in the same row to the left (below filter field) and if enough filters are added, they can run int the selection info. Would we then create an additional row for filters or truncate the list of filters and just have a drop down to view all.
  • Move selection info to left so it aligns with selection checkboxes. This makes sense but since filters are of the left, this would require an additional row.  I’m not sure if that’s the best reason to create another row, especially since that would be the only info shown on the row (rest of row would be empty, and thus look unbalanced)


I’ve also quickly mocked up how pagination would appear within the card and list view.




Another thing to note is that filters will work across pages.  I talked with Dan, who has been working on implementing the new data tables, and he confirmed that this will not be a problem, the technology he is using supports this.


Would love to hear your thoughts on option 2, especially concerning that feedback/concerns that we have already received. Next step we will refine this design for the final stages.


Please comment below, thanks!


Posted by & filed under Terminology and Wording.

Base on the document of Terminology and Wording
PatternFly encourages users to adopt much more emotional descriptions to show the time and date in the application. In most cases when users created a blog or document, their activities like attached / updated / followed / commented / liked / unliked…, we can use the following ways to display time:



In some environments, your application may need to show a correct time information, like a meeting time or a event time… Here are some recommended examples to show the correct time.


More information about Date Formats, please check Terminology and Wording of PatternFly


Hi folks,

Please feel free to leave your comments and suggestions. Thank you~

Posted by & filed under Forms.

The PatternFly team is working on the conceptual design for multi column forms. However, this concept is slightly different from other patterns the team has worked on.

We are exploring if there is ever a good use case to use multi-column forms, and if so what are they? 

Forms are a valuable tool because they offer a variety of layouts that can be used to organize your content for users to complete in a meaningful manner.

However, in the case of multi column forms, it’s mostly best practice to avoid their use. The main problem is that using multiple columns within forms could cause the potential for users to interpret the fields inconsistently.  Below are 5 examples of ways multi column forms could be interpreted.


As you can see, multiple columns interrupt the vertical impulse to move down the form. Rather than forcing the users to visually reorient themselves, it’s best to keep them in a consistent  flow by sticking to a single column layout.

However, there are a couple exceptions that seem to be acceptable.



Example 1

The main exception for using multi-column forms that cause the least amount of confusion were for short fields as well as logically related fields.  The most common example are name and address fields (City, State, and Zip Code).



This type of content is standard and easy for users to follow. One suggestion for this format is to align the labels above the fields, rather than to the left. The thought was that this makes the grid stronger and thus, easier to map the fields visually.  Do you agree or disagree? This could be something we could explore for this pattern if we decide to move forward with it. In this case the labels are kept to the left to stay consistent with our general form design.

Another variation is instead of a standard two level format, use various columns. Keep in mind that this will works best for related short input fields.


Example 2

The second exception is when there are to different form choices.  User must choose to fill out one or the other.  In this case, when the forms fields are shown next to each other in a multi column format, there is little confusion as long as the distinction of the two form choices are clear.



There were several thoughts on this use case. First being that this would be considered two single column forms next to each other, rather than a multi column form. The second being that instead of this format, opt for a preselection for new or returning users.  This would then display a single form rather that two side by side.



Because this is the beginning stages of the development of this pattern, we would love to hear your thoughts and input on this topic.  Are there any other scenarios that are acceptable?  Do you agree with the conclusion and the comments received thus far?

Please comment below with your thoughts as they could help shape this pattern as it moves forward along the design process.

Posted by & filed under Web Components.

If you’ve been following the Patternfly mailing list or happened to stumble on our recent post on, “Are Web Components in the future for Patternfly?”,  you’ve probably noticed that we’re doing some thorough research on web components right now.

I’d like to take this opportunity to provide a few updates on our findings and share some context on our recent discussions around web components in Patternfly.

Are web components feasible?

Custom Elements, HTML Imports, Shadow DOM, and HTML Templates are the new specifications heavily influencing web components (you can read a great introduction here if you’re new to these topics), but it’s important to remember that these are mutually independent. Although many examples combine Custom Elements with Shadow DOM CSS techniques, they are not required to be used in conjunction (another trait which adds to their versatility). Custom Elements can stand alone and be styled just like other HTML.

Due to Shadow DOM’s currently minimal browser support, it would not be a stretch to consider a gradual adaptation to implementing new web component standards like the following:


As browser support improves, Shadow DOM can be adopted to improve our CSS encapsulation where necessary. It should also be noted that while HTML Imports may be the most common way to consume web components, Custom Elements can be defined and included as ES6 classes. This alleviates another web component standard and gives options with this specification as well.

Exploring Web Components with Patternfly

Building on our past breakaway sprint efforts with web components, we’ve extended our <pf-tabs> element and tested our approach with some popular new web frameworks gaining traction at Red Hat: ReactJS and Angular2. Utilizing components as “leaf nodes” within other framework components makes them essentially comparable to other DOM nodes used, only much more flexible.

The goal of this research was to integrate a custom element in these frameworks alongside our Patternfly implementations and explore any roadblocks or challenges discovered.

You can see our current work on the <pf-tabs> component here.


(pf-tabs component rendered individually)

A few things to note about this component:

  • The element has been tested in a React context and an Angular2 context. Any differences in element rendering behaviors are noted in the source of the component (to ensure proper behavior in both frameworks).
  • We’ve added some performance tests to analyze rendering speeds with several occurrences of tabs and nested tabs.
  • We’ve chosen to use “Vulcanize”, a build tool for inlining our element’s css and javascript into a single file. This makes the element easily consumed in one import and reduces network requests.
  • It is completely possible to use element attributes to give your element unique behaviors or styles in different contexts (e.g. the class attribute).
  • Shadow DOM initialization and styles have been commented out and appropriate constructs have been added in their place. It is easy enough to add them back if desired.

Notes on Frameworks ReactJS and Angular2

There are too many details to cover in this post, however I encourage you to explore the aforementioned demonstrations. If you run these demos, you will easily notice that our tabs component works as intended in both frameworks and the new frameworks provide adequate contexts to create a Patternfly application.


(Tabs component rendered in a Patternfly/React app)

I should add that our discussions on these frameworks have been fruitful (luckily, there is already an abundance of materials for each to aid in our research). Both frameworks provide exceptional solutions for common problems app developers face like data binding, observing state and inter-component communication, custom events, and optimal rendering. Particularly important, we haven’t found web components causing any barriers in this regard and observed the patterns implemented in these solutions translate quite nicely to web components.


We’ve prepared plenty more to share on this in future posts and will be fine-tuning our strategy in coming weeks. We’ll also be exploring other topics like performance, server rendering, and modular design. So stay tuned to our blog and mailing list all you Patternfliers!

Posted by & filed under Forms.


This blog is to investigate the web form design especially the conditional hidden fields, and give out the possible solutions.

Should we hide fields if user can’t be interacted with? Do we always just keep all fields there and gray them out? Or use progressive disclosure if there are more fields based on a given selection?

When we designing a web form, we should always keep the form easy and simple. We could hide the unnecessary fields in order let users focusing on the present job and show them out when needed.

The picture below is a comparison of the old Apple ID register page and the new one. The difference between the old one and new one is that they remove the mailing address input. Most of the users will register the ID only for downloading the applications or set up a new device. Moving the mailing address part to the buying page and  hiding it in the current page will make the workflow more smoothly.


Old Apple ID register page                                                                              New Apple ID register page                                                                                

apple id1                            appleid1


Back to the question, we could use the progressive disclosure if there are more fields based on a given selection.

We would not rather choose to show the fields that user can’t be interacted with.

In this case, user will spend unnecessary  time to identify what fields they can be interacted with and what they can’t.

We would rather not keep all fields there and gray them out.

The color of Patternfly unclickable field is very light. They can not be seen very clearly on the Linux and Microsoft devices (those devices do not have Retina screen).

Design Options

The Wireframe link is here

Design 1:

This is to define the single level conditional fields.


1.I change the input name from the left to the top in order to help user viewing the form more easier.

In web form design, it is better to use “F” sight line rather than “Z” sight line

屏幕快照 2016-08-10 下午5.48.01

屏幕快照 2016-08-10 下午4.43.16

2.The unchecked field will not be shown unless user clicks it. After clicking the checkbox, the text field will show. The design is to help user focusing only on the present workflow, to avoid him from losing the way. When clicking the first selection checkbox, the text field will all hide.


Design 2:

This is to define the multi level conditional fields.

1.Add a cutting line to distinguish the first level fields and subfields.

2.Unchecked fields will open only until user clicks it. When clicking the sub level checkbox, the text fields will show.



Design 3:

This is to define the conditional fields with dropdown menu.

1.Despite of the first selection fields, the other none selected dropdown menu will hide until user clicks it.

2.When clicking another checkbox, the previous none selected dropdown menu will hide.



Thoughts, comments, concerns? Feel free to comment on this post.

Posted by & filed under Navigation.


We need a responsive design for tabs to handle overflow, which will include a responsive state for the two levels of tabs as well.


Current tabs implementation



Screen Shot 2016-08-18 at 12.03.00 PM

Screen Shot 2016-08-18 at 12.03.08 PM

However, When there are many tabs, it requires significant scrolling to find one of the tabs. Also, it’s not recommended in Material Design guidelines to present tags as a single column


Screen Shot 2016-08-18 at 12.04.01 PM


You can also view this Angular Material demo

2.Responsive Secondary Tabs

Current secondary  tabs
Screen Shot 2016-08-18 at 12.58.52 PM
Screen Shot 2016-08-18 at 1.00.06 PM

It might be better for mobile use cases to scroll horizontal versus displaying all the options. Here are some suggestions to address the problem. ->>

Screen Shot 2016-08-18 at 1.02.18 PM


Screen Shot 2016-08-18 at 1.03.16 PM


Responsive Demo
responsive secondary tabs


Demo is  based on AngularJS ->>

Posted by & filed under Forms.

The red asterisk ( * ) indicating required fields has been around our digital interfaces so long, it’s one of those things you take for granted, like the anachronistic floppy disk for “save”, or the magnifying glass for “search”. It’s easy to forget that somewhere along the line, it was a choice that someone made.

In recent years, people of the internet have been pondering over the use of our spiky little friend, the asterisk, in web forms. They have been asking the question: “do we actually need this thing?”

The alternative to indicating required fields is indicating optional fields. This is commonly indicated by explicitly writing out (optional) for every optional field. Like the asterisk, the (optional) marker has also been around forever as a pattern in web forms; it is similarly ubiquitous.

The arguments for marking only optional fields with (optional) are that:

  • Spelling out the text (optional) makes it more clear for users what they need (or don’t need) to do.
  • Marking required fields may actually subconsciously influence users to skip optional fields.
  • You don’t need a legend describing what (optional) means.
  • There’s less red, which makes for a subjectively calmer form experience.
  • Marking fields (optional) will be cleaner when most fields are required.
  • It forces the designer to consider: do I really need to provide so many extra options?

So, with that in mind, here’s the design proposal for Required Form Fields in PatternFly:


Our recommendation is to mark only optional fields, using the word “optional” (see Design A1 below for how this looks). If a majority of the fields are optional, then you may mark required fields instead (Design B1), but just be aware that if you use both approaches across different forms, it makes for inconsistency in your designs.

If all fields are required, this can be indicated implicitly by disabling the Primary (Submit) action until all fields are filled out (Design A2).

Conversely, if all fields are optional, you have the choice to remove the optional markers, and indicate the fact that the fields are optional implicitly by always enabling the Primary (Submit) action (Design A3).

Design Options

Design A1

Mark only optional fields. Use this approach by default.

Design A1

Design A2

When all fields are required, indicate this implicitly by disabling the Primary (submit) button.

Design B2

Design A3 (Edge Case)

When all fields are optional, you may drop the optional markers and indicate optionality implicitly by always enabling the Primary (submit) button.

Design A2

Design B1 (Alternative approach)

Mark required fields. You may use this approach when a majority of the form fields are optional.

Design B1


Thoughts, comments, concerns? You have the option to comment on this post.

Posted by & filed under UX Research.

As a user experience researcher supporting the PatternFly project, I’m currently researching and developing personas that represent the typical PatternFly user or contributor. Personas are fictional, often alliteratively named, representations of your users. They are based on similarities gleaned from quantitative and qualitative research on users’ habits, motivations, and work contexts.

While I will do more in-depth research by interviewing users in the very near future, I wanted to have an initial draft of the personas available to get a sense of whether actual users see themselves in the descriptions. Digging around in various sources of information about users and roles, I found enough insights to kick off an initial draft. The sources I started with include:

  • Existing personas: Reuse what we have already learned about similar user types.
  • Interview transcripts: A brief, pithy quote direct from the mouth of a user often encapsulates their intentions far better than 1000 words from the interviewer.
  • Mailing list archives: Who is writing to the PatternFly mailing list? What are they asking about or discussing?
  • LinkedIn: Seeing what similar users studied, how long they have been doing their role, what their career path has been like.
  • Job descriptions: What do employers think these types of users should be doing?

Looking through all this information from dozens of actual users shook out three, possibly four, similar roles: front-end developer, a back-end developer who needs to do front-end development, and a designer (which may need to be broken out into interaction designer and visual designer). Personas can include any kind of information, from what kind of laptop they use to what kind of pet they have, but they work best when you focus on areas that help you understand the problem you are solving for that type of user. For each PatternFly persona, I noted points in these categories: background/tools, goals (motivations), pain points, “a day in the life.”



Organization of the persona information


Once the first draft was solid, I ran it by a few teammates to make sure these were heading down the right path. Through these discussions, it became obvious that the idea of “open source contributor” was important to include, but isn’t so much a persona as much as it is a role that each of these personas takes on at various points. Each persona has times when they are consumers of PatternFly (reading content, downloading examples) and times when they are contributors (participating in the mailing list, writing patterns, submitting code), and their actions and motivations in each case would be very different. To date, searches for persona-like research done on open source contributors have proven less than fruitful.

And that, my friends, is where we are today. I invite you to peruse the draft and think on your own PatternFly experiences and those of people you have collaborated with. As you do, ponder these questions as well:

  • Are interaction designer and visual designer separate personas?
  • Are there any personas that are missing?  What about high-level roles like architects?
  • Can you recommend any good articles or research written about what it is like to be an open source contributor?

So, do you see yourself in these personas?  Let me know your thoughts in the comments.


Edited to add a link to the ODP version of the personas. If you use the file to write your own personas, let us know — we’d love to see what you create.