<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Erin Donehoo on Medium]]></title>
        <description><![CDATA[Stories by Erin Donehoo on Medium]]></description>
        <link>https://medium.com/@edonehoo?source=rss-4b549ba96527------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*f_fea7nxubA4Wt9xQwSW6Q.jpeg</url>
            <title>Stories by Erin Donehoo on Medium</title>
            <link>https://medium.com/@edonehoo?source=rss-4b549ba96527------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:10:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edonehoo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Harmonizing the Red Hat experience]]></title>
            <link>https://medium.com/patternfly/harmonizing-the-red-hat-experience-f5dc5c52e1be?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5dc5c52e1be</guid>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[theming]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Wed, 03 Jun 2026 15:13:25 GMT</pubDate>
            <atom:updated>2026-06-05T13:29:36.790Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our new theme is built for Red Hat journeys</h4><figure><img alt="A split screen image of dark theme, lo-fi UIs. On the left is the Default theme, with blue accent colors, and on the right is the Project Felt theme, with red accent colors." src="https://cdn-images-1.medium.com/max/1024/1*KYvrm8V0w7ThnpNc8iO_Gw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p>Design systems bridge brand identity to the end user experience, but when a brand identity spans marketing experiences, a product marketplace, and complex enterprise software user interfaces, that bridge needs active maintenance.</p><p>Whether users are shopping for a product on a marketing website or using a complex dashboard user interface to get work done, our goal is always the same — to make the user journey look unified and feel continuous.</p><p>To that end, we are introducing a new theme variant with familiar Red Hat visuals.</p><p>This new theme is part of Project Felt, which is an ongoing cross-team initiative to encourage greater unity between the Red Hat brand, marketing experiences, and product user interfaces. Built on our design token system, the Project Felt theme ships as a non-breaking release and is fully ready for use in your products.</p><p>Here is how it came together and where we are taking it next.</p><h3>Envisioning a seamless Red Hat journey</h3><p>This theming effort started as a cross-team workshop between maintainers of PatternFly and the <a href="https://ux.redhat.com/">Red Hat Design System (RHDS)</a>, and the <a href="https://www.redhat.com/en/about/brand/standards">Red Hat brand</a> team. Together, we tackled this shared challenge:</p><p><strong>How do we create a more seamless experience for users as they move through the full Red Hat journey?</strong></p><p>To start, we leveraged the “See, Buy, Use” flow as our experience map. We created mock experiences as part of this flow in order to visualize:</p><ul><li>A visitor first encountering Red Hat through social ads or marketing experiences;</li><li>Then, a prospect navigating to our product marketplace to start a trial or make a purchase;</li><li>Finally, a daily active customer using the features included in a product interface.</li></ul><p>We know these unique contexts have not always been in sync, so our goal was to find a shared visual language that makes the Red Hat journey feel consistent while still preserving intentional differences as needed.</p><p>The result of this workshop laid the groundwork for many of the styles we are shipping today. While unity and cohesion are the goals, we do not want to apply one single look and feel to everything yet. Rather than changing the default look of our systems, we created a separate option — the Project Felt theme — so teams can choose the visual language that best fits their needs</p><h3>Our updated Default theme</h3><p>Our Default theme largely maintains the classic PatternFly look, with PatternFly blue as a brand color. But, we’ve made a few refinements to bring it into closer alignment with RHDS:</p><ul><li>Links now use a dotted underline, which becomes a solid active color on hover and focus.</li><li>Active navigation items get a vertical accent marker for clearer visual emphasis.</li><li>Icons are now aligned with the <a href="https://github.com/RedHat-UX/red-hat-icons/tree/main/src/ui">Red Hat icon set.</a></li><li>Borders are now higher contrast for better visibility, and toggle groups use a more subtle brand color for clearer distinction.</li></ul><figure><img alt="A “before and after” image is shown to overview the subtle changes added to the Default theme. On the left is the previous state of components like toggle groups, navigation, and links, and on the right is the new version of the same components." src="https://cdn-images-1.medium.com/max/1024/1*OXHFTKgcyNFlNWhtjwd8Lg.png" /></figure><p>These changes are intentionally subtle and are meant to feel like natural polish for our Default appearance, rather than a disruption. As soon as you upgrade to PatternFly 6.5, these changes apply automatically across your components.</p><h3>Our new “Project Felt” theme</h3><p>The Project Felt theme is our first theme variant and a step towards a unified Red Hat identity. Named after the material of<a href="https://www.redhat.com/en/about/brand/standards/the-hat"> the iconic Red Hat fedora</a>, our new Project Felt theme is Red Hat through and through. It replaces PatternFly blue with<a href="https://www.redhat.com/en/about/brand/standards/color"> Red Hat “Red”</a> as an accent color and introduces<a href="https://www.redhat.com/en/about/brand/standards/hybrid-style-handbook#base-shapes"> pill-shaped borders</a> for buttons, controls, and containers.</p><p>The result is a product UI that feels recognizably Red Hat. For teams building products where that continuity matters more, Project Felt makes it easier to deliver that familiarity for your users.</p><figure><img alt="A split screen comparing tabs in the Default theme to tabs in the Project Felt theme. On the left, the Default theme shows a blue underline for active items and square shapes for hover and focus states. On the right, the Project Felt theme shows a red underline instead of blue and rounded shapes instead of squares." src="https://cdn-images-1.medium.com/max/1024/1*Ikf58Gjp_BizRH7V3Y9eFg.png" /></figure><p>Because Project Felt is built entirely on our design token system, you can adopt it without breaking changes. To enable it, add .pf-v6-theme-felt to your application’s &lt;html&gt; tag. You can preview it alongside our other theming options on <a href="http://patternfly.org/">PatternFly.org</a> via the masthead theme switcher.</p><h3><strong>New components and layouts</strong></h3><p>This theming work also motivated a few new building blocks, designed to support the visual direction and use cases these themes are aimed at. All three are available regardless of which theme you use:</p><ul><li><a href="https://www.patternfly.org/components/hero"><strong>Hero:</strong></a> Inspired by<a href="https://www.redhat.com/en/about/brand/standards/hybrid-style-handbook#base-shapes"> Red Hat’s hybrid style</a> shapes, this card-like component is for high-impact callouts at the top of pages. It features rounded corners that echo the silhouette of Red Hat’s fedora.</li></ul><figure><img alt="A card with an asymmetrical shape. It has a gray background and shows an abstract background image on one side." src="https://cdn-images-1.medium.com/max/1024/1*EuV_IhNU1Nyh58grWhWWPg.png" /></figure><ul><li><a href="https://www.patternfly.org/components/page/react-demos#docked-nav"><strong>Docked navigation:</strong></a> A space-saving navigation that collapses page names to icon representations, saving space in the UI while remaining expandable for full context.</li></ul><figure><img alt="Navigation collapsed into a compact, icon-based menu bar." src="https://cdn-images-1.medium.com/max/1024/1*7T8a1EGPKg75Fi72jyAmog.png" /></figure><ul><li><a href="https://www.patternfly.org/ai/generative-uis/overview"><strong>Compass layout:</strong></a> A “conversational-first” layout for generative UI experiences, with a ChatBot message bar below page content and surrounding action toolbars.</li></ul><figure><img alt="A UI screen with controls and navigation flanking page content, with a chatbot message bar at the bottom." src="https://cdn-images-1.medium.com/max/1024/1*RP5EBcRVPwQqEgn3akRt_A.png" /></figure><h3>Also new in theming</h3><p>Our 6.5 release also added two new contrast options that are available across themes and light/dark color schemes: <a href="https://medium.com/patternfly/designing-with-depth-c5d11a2c2449">glass mode</a>, which adds transparency and depth to your UI, and <a href="https://medium.com/patternfly/designing-for-clarity-949379dee820">high contrast mode</a>, which supports users who need stronger contrast.</p><h3>What’s Next: Toward one system</h3><p>This release is the first phase of a larger, long-term effort to unify the PatternFly and Red Hat design systems, making it easier for every Red Hat team to build and maintain consistent experiences across websites and products. The Project Felt theme is our first step toward a future where Red Hat websites and products have a shared foundation, and “Red Hat” is consistently recognizable across every touchpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p><em>Have a story of your own?</em><a href="https://medium.com/p/af90715e556d"><em> Write with us</em></a><em>! Our community thrives on diverse voices — let’s hear yours.</em></p><p><strong><em>Disclaimer: </em></strong><em>This story was drafted with AI assistance. All insights and final edits are the author’s own.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5dc5c52e1be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/harmonizing-the-red-hat-experience-f5dc5c52e1be">Harmonizing the Red Hat experience</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing with depth]]></title>
            <link>https://medium.com/patternfly/designing-with-depth-c5d11a2c2449?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5d11a2c2449</guid>
            <category><![CDATA[glass]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[visual-design]]></category>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Thu, 28 May 2026 14:11:02 GMT</pubDate>
            <atom:updated>2026-06-05T13:29:22.069Z</atom:updated>
            <content:encoded><![CDATA[<h4>A closer look at glass mode</h4><figure><img alt="A semi-transparent lo-fi UI placed on a light blue background." src="https://cdn-images-1.medium.com/max/1024/1*4mqelPEQXN2Xd3fR2oLfsA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p>Glass mode is a new contrast option for PatternFly that adds transparency, blur, and depth to your UI. Semi-transparent containers let brand-approved background imagery subtly show through, adding layers to your products that make them feel more “alive”.</p><p>Because transparency can add legibility risks, we validated glass with user research and a comprehensive accessibility audit before shipping it.</p><p>Here’s a look at how glass works, how to use it, and what informed our decisions along the way.</p><h3>How do I explore glass mode?</h3><p>Glass mode is available in both the light and dark versions of the Default and Project Felt themes.</p><p>To enable glass, add .pf-v6-theme-glass to your application’s &lt;html&gt; tag, as outlined in the <a href="https://www.patternfly.org/foundations-and-styles/theming/glass-mode-handbook">glass mode handbook</a>. You can preview glass mode (alongside all other theming combinations) on PatternFly.org using the masthead theme switcher.</p><h3>How does glass change the UI?</h3><p>Glass mode adjusts transparency, borders, and shadows on surface-level containers to create the appearance of glass panes. Content below shows through subtly, adding a sense of depth and content hierarchy without obscuring what’s underneath. Under the hood, glass is powered by a set of design tokens that work together to create the base fill, overlay tint, and boundary highlights of the glass effect.</p><p>When enabled, glass automatically applies to four components: login page, masthead, navigation, and page. It can also be manually extended to card, drawer, hero, and panel via the isGlass prop. Additionally, we’ve added the isPlain prop to many components, which removes the default borders and solid background colors, so that they can sit directly on a glass-enabled component without obscuring the intended effect.</p><h3>Glass-specific component variants</h3><p>Two new component variations work together to help anchor the glass experience. When glass is enabled, these component variants are automatically used in place of their standard counterparts:</p><ul><li><strong>Banded masthead:</strong> A masthead option that adds transparency, blur, and a shadowed border to help set it apart as a solid, persistent dock above the rest of the page.</li></ul><figure><img alt="A default masthead beside a banded masthead. The banded masthead is elevated by the glass effect." src="https://cdn-images-1.medium.com/max/1024/1*kCshG2wZi9DCcGc34DEkLQ.png" /></figure><ul><li><strong>Floating side navigation: </strong>A side navigation option that adds transparency, blur, and a shadowed border to make the nav more visually separate and elevated, so that it reads clearly as a navigation resource within the glass context.</li></ul><figure><img alt="A default side nav beside a floating side nav. The floating nav is elevated by the glass effect and placed in a separate, inset container." src="https://cdn-images-1.medium.com/max/1024/1*T6xnNlkxkKHpyTZhddJu5Q.png" /></figure><h4>Background imagery</h4><p>Rather than a solid background color, page backgrounds can use brand-approved imagery that lets brand-colored shapes show through any glass containers. We developed a set of images in collaboration with the Red Hat Brand team that offer abstract, subtle visuals for general use, with additional product-specific options for teams that want them.</p><figure><img alt="Four thumnails of background images with abstract shapes, including a light blue options, light gray, and two dark options that are black with dark purple imagery." src="https://cdn-images-1.medium.com/max/1024/1*X2HkhXNzVPWzGDxvDorAWw.png" /></figure><p>Background images are available to download from the <a href="https://redhat.brand-portal.adobe.com/mediaportal.html/content/dam/mac/redhat/brand/brand-engagement-kit/wallpapers/product-interface-backgrounds?disableExpiredRedirect=true">Red Hat brand portal</a>. In development, default images are automatically applied when you pull in PatternFly styles. For more details, refer to the <a href="https://www.patternfly.org/foundations-and-styles/theming/glass-mode-handbook#background-images">glass mode handbook</a>.</p><h3>How do I use glass mode?</h3><p>While full implementation guidance lives in the <a href="https://www.patternfly.org/foundations-and-styles/theming/glass-mode-handbook">glass mode handbook</a>, here are the high-level details:</p><h4><strong>1. Use brand-approved background images</strong></h4><p>To ensure proper accessibility, images should be non-distracting and chosen from the options provided by the Red Hat Brand team. Text should never be placed directly on top of a background image and should instead live within a container. Titles or headings with stronger font weights can be placed directly on background images only if they pass specific brand and contrast requirements.</p><h4><strong>2. Avoid glass-on-glass layering</strong></h4><p>Glass objects that are inside a glass container can become illegibly blurred themselves, so we don’t currently support or recommend layering glass-enabled containers. Our background token opacity values are intentionally set to simulate depth without requiring nested blur.</p><h4><strong>3. Allow users to opt out</strong></h4><p>Any product using glass mode must give users a clear way to switch to default contrast or high contrast via a theme switcher or preferences menu. When high contrast is enabled (manually or via the OS-level prefers-reduced-transparency or prefers-contrast media queries) glass effects must be automatically disabled or replaced with a solid background to prioritize functional accessibility.</p><h3>Validating through research and testing</h3><p>Before shipping glass mode, we conducted a user research study and accessibility audit, both aimed at ensuring our aesthetic choices didn’t compromise usability or accessibility.</p><h4><strong>User research findings</strong></h4><p>We tested glass across four variations with enterprise professionals, comparing task performance and user sentiment across light and dark themes.</p><p>Click task success and speed were consistent across all four variations, in both light and dark. Glass layering and background imagery did not measurably hinder users’ ability to identify and interact with UI elements. Ratings for perceived clarity, aesthetic appeal, and ease of use showed no meaningful differences across variations either.</p><p>User preferences varied. Those who favored the full background and layered effect described the look and feel as “premium”, “professional”, and “attractive.” Users who preferred a more subdued background found it more “open,” and were concerned that red in the background might signal errors or critical failures in an IT context. A few users noted that flatter layering helped readability, while others didn’t register the subtle transparency differences at all.</p><p>These findings informed the more abstract, subdued background images we ultimately shipped and reinforced our requirement that products always give users a way to opt out.</p><h4><strong>Accessibility audit findings</strong></h4><p>Our primary challenge was maintaining WCAG AA (4.5:1) and AAA (7:1) contrast ratios across both color schemes. The audit found that accessibility failures were more than twice as likely in dark themes, with danger and error text posing the most significant risk.</p><p>To account for this, we carefully selected the default opacity to balance visual appeal with legibility. Both light and dark modes use 50% opacity, with the accessibility findings informing our choice of background colors and imagery to support contrast across both schemes. If your team overrides these values, you’re responsible for verifying WCAG compliance for your specific implementation.</p><h3>Looking ahead</h3><p>As you begin to use glass mode in your products, we’ll keep updating our documentation with patterns that emerge. We’re also eager to hear about your experiences and how glass works for you–<a href="https://join.slack.com/t/patternfly/shared_invite/zt-1npmqswgk-bF2R1E2rglV8jz5DNTezMQ">reach out to us on Slack</a> with any questions or feedback!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p><em>Have a story of your own?</em><a href="https://medium.com/p/af90715e556d"><em> Write with us</em></a><em>! Our community thrives on diverse voices — let’s hear yours.</em></p><p><strong><em>Disclaimer: </em></strong><em>This story was drafted with AI assistance. All insights and final edits are the author’s own.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5d11a2c2449" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/designing-with-depth-c5d11a2c2449">Designing with depth</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for clarity]]></title>
            <link>https://medium.com/patternfly/designing-for-clarity-949379dee820?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/949379dee820</guid>
            <category><![CDATA[high-contrast]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Wed, 27 May 2026 17:49:05 GMT</pubDate>
            <atom:updated>2026-05-27T17:50:17.435Z</atom:updated>
            <content:encoded><![CDATA[<h4>High contrast mode supports a wider range of needs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oiCuGfSNE2S2ize2Ngg2ug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p>PatternFly is committed to accessibility and ensuring every user can navigate products effectively. Our standard light and dark modes meet WCAG AA contrast standards (4.5:1 for text), but meeting the minimum requirement isn’t the same as being accessible for everyone. For users with low vision or other visual impairments, higher contrast isn’t a preference, it’s a necessity.</p><p>High contrast mode is now out of beta and fully released. It works across both the Default and Project Felt themes, in light and dark color schemes, and targets WCAG AAA text contrast ratios to give users who need stronger contrast a reliable, supported option.</p><h3>Beyond a color swap</h3><p>Creating a true high contrast experience required more than just swapping colors–we needed to revisit our design token architecture and make changes at its foundations. Designer Lucia Boehling and Developer Michael Coker led the work, collaborating with the Red Hat Brand and Ansible teams to ensure the result was both accessible and consistent with Red Hat’s visual identity.</p><p>The work focused on three areas:</p><h4><strong>Palette expansion</strong></h4><p>We evaluated our existing palette against WCAG AAA requirements and worked with the Brand team to add stricter shades where needed. For text, we targeted the AAA ratio of 7:1, and for non-text elements (where WCAG AAA doesn’t specify enhanced requirements) we chose to match the AA text standard and raise contrast to 4.5:1, so interactive elements and boundaries are more legible.</p><h4><strong>Global border rules</strong></h4><p>We worked with the Ansible design team to explore high contrast product screens and identify design patterns we could standardize. This helped us establish global border rules that define clear boundaries in place of shadows and subtle background fills, which often disappear in high contrast.</p><h4><strong>Token evolution</strong></h4><p>We updated our entire token set, mapping semantic tokens to both light and dark high contrast modes. We also added new color and border width tokens to enable global styling without manual overrides.</p><h3>User choice is an accessibility feature</h3><p>To guide and validate our work, we conducted moderated and unmoderated research with participants across a range of visual needs and preferences. This research revealed a key insight: there is no one-size-fits-all.</p><p>While some participants gravitated toward high contrast mode, others found that our standard dark mode provided better readability for them. When it comes to UI appearance, choice matters as much as any single setting. By providing multiple theming options, users can pick the experience that works best for them.</p><h3>Navigating system preferences</h3><p>One technical challenge was distinguishing between PatternFly’s theme styles and user-defined settings, such as browser-level forced colors (for example, Windows High Contrast Mode).</p><p>We designed our system to honor system preferences above all else. Browser-level configurations override PatternFly settings, so users who’ve already configured their OS or browser for high contrast get a consistent experience without any conflict.</p><h3>High contrast and glass mode</h3><p><a href="https://www.patternfly.org/foundations-and-styles/theming#glass">Glass mode</a> adds transparency that can compromise legibility in the UI. To account for this, we’ve built high contrast precedence into our architecture: when a user enables high contrast mode manually or via the OS-level prefers-reduced-transparency media query, all glass effects are automatically disabled. Functional accessibility always takes priority over aesthetics.</p><h3>Getting started</h3><p>Because high contrast mode is built on our design token system, enabling it requires a single class with no performance impact. To enable high contrast, apply the <strong>pf-v6-theme-high-contrast</strong> theme class to your application’s root element:</p><p>&lt;html class=”pf-v6-theme-high-contrast”&gt;</p><p>For more detailed guidance, explore the <a href="https://www.patternfly.org/foundations-and-styles/theming/high-contrast-handbook">high contrast developer handbook</a> for best practices and implementation instructions, and our <a href="https://www.patternfly.org/foundations-and-styles/theming">theming foundations</a>, to learn how high contrast fits into our theming system.</p><h3>What’s next?</h3><p>High contrast is now supported across all PatternFly components and extensions. Looking ahead, we’re exploring ways to expand our token system to support other accessibility needs, like different types of color blindness.</p><p>This feature exists because of community input–try enabling it in your projects and let us know what you think about the ease of implementation and the visual experience. <a href="https://join.slack.com/t/patternfly/shared_invite/zt-1npmqswgk-bF2R1E2rglV8jz5DNTezMQ">Share your thoughts with us on Slack</a>.</p><p><em>A special thanks to the team behind this epic: Lucia Boehling, Michael Coker, Andrew Ronaldson, Sarah Rambacher, Eric Olkowski, and the Ansible and Red Hat Brand teams for their collaboration.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p><em>Have a story of your own?</em><a href="https://medium.com/p/af90715e556d"><em> Write with us</em></a><em>! Our community thrives on diverse voices — let’s hear yours.</em></p><p><strong><em>Disclaimer: </em></strong><em>This story was drafted with AI assistance. All insights and final edits are the author’s own.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=949379dee820" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/designing-for-clarity-949379dee820">Designing for clarity</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A new path for PatternFly.org]]></title>
            <link>https://medium.com/patternfly/a-new-path-for-patternfly-org-b3536f514f2f?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3536f514f2f</guid>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[navigation]]></category>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Thu, 14 May 2026 13:50:50 GMT</pubDate>
            <atom:updated>2026-05-14T13:50:50.990Z</atom:updated>
            <content:encoded><![CDATA[<h4>A look at our community-guided navigation redesign</h4><figure><img alt="A white map is placed atop a dark gray background. On the map is a dotted line leading to a red X. Beside the map is a lo-fi image of a navigation menu." src="https://cdn-images-1.medium.com/max/1024/1*L3CtrJqE9TyypMVqYQR_3g.png" /></figure><blockquote><strong><em>Note:</em></strong><em> The changes described in this article are currently available for preview at </em><a href="http://staging.patternfly.org/"><em>staging.patternfly.org</em></a><em>. Links in this blog will be updated when they go live on PatternFly.org.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p><a href="https://medium.com/patternfly/welcome-to-patternfly-6-5c372f2fd5de">Since we launched PatternFly 6</a>, we’ve continued to expand our website to keep pace with new product patterns and technologies. But as we released more documentation, it became clear our navigation was struggling to keep up. With dozens of new guidelines needing homes on <a href="http://patternfly.org/">PatternFly.org</a>, our information architecture wasn’t just making it harder to place new content — it was becoming a barrier to the efficiency and consistency we strive to provide.</p><p>As PatternFly’s content designer, I knew we needed a strategic change, but that change couldn’t happen in isolation. To ensure our new direction was driven by data rather than my own assumptions, I led a multi-phase research study to uncover how our website could better serve our community.</p><p>After months of iteration and analysis in 2025, our new navigation is more effective and scalable. Here, I’ll share my research findings, the specific changes I’ve made, and the four core principles that guided our redesign.</p><h3>Research approach and results</h3><p>To build a more user-focused navigation, I led a study with 23 total participants who identified as a designer or developer. I used a mix of methods to ground decisions in how Flyers actually use PatternFly:<strong> card sorting </strong>to understand mental models and explore new ways to group content, and <strong>tree testing</strong> to measure how successfully and confidently participants could find information using only the navigation menu.</p><h4>Testing and iteration</h4><p>My research followed a multi-step process to move from our baseline to a new design, involving both experienced and fresh perspectives:</p><ul><li><strong>Tree test 1 (the baseline): </strong>13 participants completed 10 tasks using the existing navigation menu. This first step identified exactly where people were getting lost and established our starting metrics for success and confidence.</li><li><strong>Card sorting:</strong> I worked with 4 PatternFly maintainers through 3 rounds of card sorting. This revealed how maintainers closest to the system think about content organization.</li><li><strong>Refining the path: </strong>I ran two additional rounds of tree testing (with 12 and 19 participants respectively) to iterate towards a final design. I rephrased tasks to reduce bias and tested new navigation areas. To ensure the new system worked for everyone, I invited back original participants to measure improvement and also recruited novice PatternFly users (recent team hires) to see how the site performed for those less familiar with our system.</li></ul><h4><strong>Findings</strong></h4><p>The results showed that a new direction was a clear win. While our existing navigation had a solid <strong>70.7%</strong> success rate, the new design raised that to <strong>76.4%</strong>.</p><p>What stood out even more was the jump in user confidence–on a 5-point scale, average ratings increased from <strong>3.62 to 4.15</strong> between our baseline and final tree tests. While some findability gaps remained — particularly around terminology for core concepts — the data confirmed I was on the right track. I used the final round of qualitative feedback to make one last set of refinements, ensuring the experience felt simplified but stayed functional.</p><figure><img alt="A side-by-side comparison of the previous PatternFly website navigation and the new navigation. The new navigation most notably uses horizontal dividers and bolded headings to separate navigation items into 3 sections." src="https://cdn-images-1.medium.com/max/1024/1*B-e8pJybSGAPsZE-MUIc9w.png" /><figcaption>The before/after comparison of our nav shows how my changes translate visually.</figcaption></figure><h3>The “Why”: 4 principles that guided the design</h3><p>The numbers only tell part of this story. Qualitative feedback from our participants uncovered 4 clear principles to drive the final design. Not every insight lent itself to a clean before/after metric, but all shaped what you see today.</p><h4>1. Clear labels drive confidence</h4><p>When a navigation label describes a distinct destination, users feel confident. When it’s vague, they hesitate. Regarding our “Accessibility” heading, one user noted: <em>“This feels very forward and clear!”</em> In contrast, conceptual headers like “Foundations” and “Guidelines” often felt indistinguishable to users.</p><h4><strong>The changes:</strong></h4><ul><li><strong>I made key entry points action-oriented</strong> — like Get started, Get help, and Get involved — to put the user’s goal first.</li><li><strong>I elevated help resources from behind generic headers</strong> and created dedicated pages for Contact us, FAQs, Bug reports, and Contribution guides.</li></ul><figure><img alt="2 website nav items are shown expanded: “Get help”, which contains “FAQs”, “Contact us”, and “Report a bug”, and “Get involved”, which contains “Community” and “Contribute”." src="https://cdn-images-1.medium.com/max/1024/1*GtaVnoCBq513cxNwnbMpkA.png" /><figcaption>The new “Get involved” and “Get help” sections contain important support resources.</figcaption></figure><h4><strong>The results:</strong></h4><ul><li>Removing guesswork from top-level labels was a major driver of our overall success rate increase.</li><li>Participants navigated to help/support resources (like bug report and contact information) much faster than in our baseline test.</li></ul><h4>2. Structure breaks down complexity</h4><p>This study confirmed that long, unstructured navigation can be overwhelming. To fix this, I applied a UX principle called “<a href="https://www.nngroup.com/articles/chunking/">chunking</a>” to break content into smaller, related groups. This helps our users recognize the right path rather than trying to memorize a list.</p><h4><strong>The changes:</strong></h4><ul><li><strong>I organized items into three labeled, non-clickable groups</strong>–Learn, Design and develop, and Connect–separated by horizontal dividers.</li><li><strong>I moved items into their logical categories. </strong>For example, Topology and Component groups moved into Extensions, and Layouts and Tokens moved into Foundations and styles.</li></ul><figure><img alt="The new PatternFly navigation menu is shown, with labeled, blue annotation markers pointing to the dividers and group headers." src="https://cdn-images-1.medium.com/max/1024/1*iY4ViL5ls1FiUloc9-1hag.png" /><figcaption>Organizing navigation items into conceptual groups makes it easier to find what you need.</figcaption></figure><h4><strong>The results:</strong></h4><ul><li>Participants appreciated the breathing room. As one put it: <em>“Classifying the menu items makes the number of options seem less overwhelming.”</em></li><li>Across the redesign, top-level navigation items decreased from 16 to 13 — even as four new destinations were added.</li></ul><h4>3. Our design language weakens confidence</h4><p>PatternFly is a robust system, but our language for core concepts — like components, patterns, and extensions — isn’t always self-explanatory. One participant admitted: <em>“I don’t understand the difference between Component groups, Extensions and Patterns.”</em></p><h4><strong>The changes:</strong></h4><ul><li><strong>I ensured that every major nav section has an updated Overview page</strong>. While we aren’t renaming our core features right now, these pages provide concise definitions and use cases to help users navigate our system’s complexity.</li></ul><figure><img alt="The “Foundations and styles” section is shown expanded, with the nested “Design tokens” section also expanded. Both the parent and child items have their own “Overview” page." src="https://cdn-images-1.medium.com/max/1024/1*nqjnvJHThxqwEvz74FY_jA.png" /><figcaption>Overview pages are standard across the site and provide introductory info about major sections, while cross-linking to related resources.</figcaption></figure><h4><strong>The results:</strong></h4><ul><li>Because this study focused on navigation-only interactions, I didn’t specifically test the effectiveness of this new page content. We’ll monitor the success of these changes through Google Analytics and user feedback surveys as our team continues to explore how users perceive our core concepts.</li></ul><h4>4. “Irrelevant” content creates noise</h4><p>I observed participants mentally filtering our navigation based on their roles. If a navigation item felt like a <em>“designer thing,”</em> developers would often ignore it as noise–even when the content was relevant to both roles. The issue isn’t the content itself, but the perception of who it’s for based on how it’s labeled.</p><h4><strong>The changes:</strong></h4><ul><li><strong>I organized all functional design and development documentation into its appropriate core concept</strong> like Components, Extensions, or Foundations and styles. By using these clear, conceptual “buckets,” I hope to reduce the feeling that any part of our system is job-specific.</li></ul><figure><img alt="The “Design and develop” navigation section is shown, which contains the core features of PatternFly, like “Components”, “Patterns”, “Accessibility”, and more." src="https://cdn-images-1.medium.com/max/1024/1*D5lFnQOsWrpIgVfJORYX_Q.png" /><figcaption>The “Design and develop” section is streamlined to organize pages into their proper parent item.</figcaption></figure><h4><strong>The results:</strong></h4><ul><li>Some of these role-based assumptions are deeply rooted, so this work goes hand-in-hand with efforts to clarify design language. This insight has also opened doors for future exploration, such as role-based personalization or a site-wide context selector, to help users find exactly what they need for their specific job.</li></ul><h3><strong>A snapshot of key changes</strong></h3><p>Here’s a consolidated view of every change I made — for full URL-level detail, <a href="https://docs.google.com/spreadsheets/d/e/2PACX-1vTnt7Muq-AJ2cJEl_wJGzgIeg50FThFtDa5OlVi7GT7Suh3SD8PY2TltE6hgnKlnCcyG5V5q-DlcGjb/pubhtml">refer to this Google Sheet.</a></p><h3><strong>Top-level navigation updates</strong></h3><h4><em>Renamed:</em></h4><ul><li>Design foundations → Foundations and styles</li><li>PatternFly AI → AI</li><li>UX writing → Content design</li><li>Developer resources → Developer guides</li></ul><h4><em>Relocated:</em></h4><ul><li>Charts is now under Components</li><li>Component groups &amp; Topology are now under Extensions</li><li>Tokens, Layouts, &amp; Utility classes are now under Foundations and styles</li><li>Training is now under Get started</li></ul><h4><em>New:</em></h4><ul><li>About us, Releases, Get help, and Get involved are new top-level items, surfacing content that was previously buried under Get started</li></ul><h3><strong>Standardization and consistency</strong></h3><ul><li>“About [Section]” pages (like those in AI, Charts, and Patterns) are now simply called Overview</li><li>Several pages were renamed for immediate clarity: Upgrade → Upgrade guide, Tokens → Design tokens, Writing for all audiences → Accessibility and localization</li><li>Content design gained a more structured organization, with Grammar and Writing guides as distinct sub-sections replacing the previous flat list</li></ul><h3>Explore the new design today</h3><p>Redesigning our navigation has been a collaborative, iterative journey — and you can experience it right now. The new navigation is available for preview at <a href="http://staging.patternfly.org/">staging.patternfly.org</a>!</p><p>We invite you to explore our new site structure and see how these changes affect your workflow. While the research phase is complete, navigation is never a one-time project. As you use the new navigation, we want to hear from you in our <a href="https://www.feedback.redhat.com/jfe/form/SV_9MKBjq8H7muINMy">user feedback survey</a>–your insight keeps PatternFly flying.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p><em>Have a story of your own?</em><a href="https://medium.com/p/af90715e556d"><em> Write with us</em></a><em>! Our community thrives on diverse voices — let’s hear yours.</em></p><p><strong><em>Disclaimer: </em></strong><em>This story was drafted with AI assistance. All insights and final edits are the author’s own.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3536f514f2f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/a-new-path-for-patternfly-org-b3536f514f2f">A new path for PatternFly.org</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PatternFly Medium submission guidelines]]></title>
            <link>https://medium.com/patternfly/patternfly-medium-submission-guidelines-af90715e556d?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/af90715e556d</guid>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Wed, 27 Aug 2025 16:08:42 GMT</pubDate>
            <atom:updated>2025-08-27T16:19:21.354Z</atom:updated>
            <content:encoded><![CDATA[<h4>Rules, tips, and tricks to writing with us</h4><figure><img alt="Two slightly rounded rectangles atop a split-color background, with a black background on one side and light gray on the other. One rectangle is white, with a blue PatternFly logo in the middle. The other rectangle is dark blue, with a black Medium logo in the middle. From both rectangles there are radiating lines to draw attention." src="https://cdn-images-1.medium.com/max/1024/1*ZMlmAiRnX0g85rhfOYZ1vw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p>PatternFly is an <strong>open source design system</strong>, dedicated to building consistent, usable enterprise software. We operate on principles of transparency and community contribution, making PatternFly accessible to everyone. Our primary goal is to empower designers and developers, enabling them to work more efficiently and build better user experiences together.</p><p>We demonstrate these core principles here on our Medium publication, where we publish medium-to-long format articles with project details and the stories behind new features. We also empower members of our community to share their experiences in the field of UX.</p><p>Our community thrives of diverse voices — we welcome and encourage anyone interested to write with us! Here are some guidelines to help you create PatternFly’s next great article.</p><h3>Requirements</h3><ol><li>In order to submit an article, you must <a href="https://help.medium.com/hc/en-us/articles/115004915268-Sign-in-or-sign-up-to-Medium">have a Medium account</a> and be following our publication.</li><li>By submitting your article, you agree to collaborate with PatternFly editors to ensure that your story aligns with our publication style.</li><li>Ensure your story is appropriate for our publication:</li></ol><ul><li><strong>Audience</strong>: UX industry professionals, PatternFly users, Red Hatters, and anyone interested in UX or open source design.</li><li><strong>Content focus</strong>: To share expertise, educate readers, and start conversations with the community about UX, open source design, and PatternFly</li></ul><h3>Writing your article</h3><p>Generally, a story should focus on one of the following topics:</p><ul><li><strong>PatternFly: </strong>A story about your thoughts, ideas, research, or tips for using PatternFly. This includes details about how you’re using PatternFly, as well as PatternFly-related updates.</li><li><strong>Open source:</strong> Your perspective on the world of open source design and development.</li><li><strong>UX thought leadership:</strong> Insights on design, research, development, writing, or other UX fields.</li></ul><p>To get a better idea of how an article should flow, we recommend first reading some of our recently published pieces.</p><h4><strong>A note on AI-assisted writing</strong></h4><p>Please <strong>do not use AI to generate your entire story. </strong>While it’s a great tool for brainstorming and polishing your draft, we want your unique voice and experience to be front and center.</p><p>Even if you don’t consider yourself a writer, we want to hear <em>your</em> story in <em>your</em> words. Our editors are here to help with the rest!</p><h3>Formatting your article</h3><p>All PatternFly articles share a few consistent design aspects:</p><ul><li><strong>Title and subtitle: </strong>Each article needs an attention-grabbing title and a short, descriptive subtitle.</li><li><strong>Header image: </strong>Articles begin with a header image that also serves as the story’s thumbnail. This image will be created by the PatternFly team to ensure visual consistency. To request an image, please leave a bracketed comment in your draft with a clear description. For example, <em>[Image: A Figma blueprint-style image, with a button at the center that a mouse is hovering over. The button has a ripple design to indicate the animation.]</em></li><li><strong>Structure:</strong> Format your article with an introduction, a body with multiple sections, and a conclusion.</li><li><strong>Introduction: </strong>Preview<strong> </strong>the story you’re going to tell and let the intro lead into the first body section.</li><li><strong>Body: </strong>Add a subtitle that describes the content. Include relevant screenshots and images that help tell your story.</li><li><strong>Conclusion:</strong> Summarize your story and include any next steps or calls to action that you have.</li></ul><h3>Submitting your draft</h3><p>Once you’ve written your article, <a href="https://help.medium.com/hc/en-us/articles/213904978-Submit-a-story-to-a-publication">follow Medium’s guidelines to submit your draft</a> to our publication.</p><p>After you submit your draft, the PatternFly, our editors will do their best to review it within two weeks. You’ll be notified of any requested changes or feedback from our editors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p><em>If you have questions about the process, or run into any issues, please </em><a href="https://join.slack.com/t/patternfly/shared_invite/zt-1npmqswgk-bF2R1E2rglV8jz5DNTezMQ"><em>reach out to us on Slack</em></a><em>. We can’t wait to read what you have to share!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af90715e556d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/patternfly-medium-submission-guidelines-af90715e556d">PatternFly Medium submission guidelines</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Motion with purpose]]></title>
            <link>https://medium.com/patternfly/motion-with-purpose-7ac3bd08efba?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ac3bd08efba</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Thu, 31 Jul 2025 13:44:09 GMT</pubDate>
            <atom:updated>2025-09-08T15:53:39.725Z</atom:updated>
            <content:encoded><![CDATA[<h4>Building a motion system that’s true to our values</h4><figure><img alt="A design “blueprint” places a blue, pill-shaped button on a white background with a light gray grid. There’s a finger pointer over the button, with a ripple of shades of blue coming from the center of the button, to the edge of the button border. There’s a thin, outlined rectangle surrounding the button and pointer that’s reminiscent of a Figma design." src="https://cdn-images-1.medium.com/max/1024/0*f2KRU4Bw2ZmoOSOy" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p>When you think of animation in UIs, what comes to mind?</p><p>It’s easy to dismiss motion as a pretty decoration, something that simply brings excitement to otherwise dull interactions. And while there’s value in livening up our software experiences, what if the most effective animations were the ones you barely noticed? What if motion, like typography and color, was simply another tool to make complex products more clear and usable?</p><p>On the PatternFly team, this is a question we’ve been exploring since 2022.</p><p>As we’ve worked to integrate motion into our design system, we knew it had to be more than just a fun addition. It needed a purpose, and it needed to be true to our principles and values.</p><p>By meticulously researching and observing animation implementation in other design systems, we deliberately chose a path that prioritized the performance and stability that our users expect from PatternFly. After years in the making, we’re excited to dive into our new motion system — one that is intentional, consistent, engaging, and, above all, inclusive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VIDkdSOnvw2EfG-GtwkQcg.png" /></figure><h4>Designing for everyone with an accessibility-first approach</h4><p>Even when it’s used intentionally and carefully, motion in UIs isn’t for everyone.</p><p>For some users, animation is a distraction. But for others, it’s more than just distracting–it’s harmful. Motion-based effects can trigger <a href="https://alistapart.com/article/accessibility-for-vestibular/">debilitating vestibular disturbances</a>, and certain types of flashing <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/Seizure_disorders">can induce seizures</a> in individuals with <a href="https://www.epilepsy.org.uk/info/photosensitive-epilepsy/web-design">photosensitive epilepsy</a>. Our intention for adding motion to PatternFly was always to help our users, not hurt them, so we took the responsibility of accessible design incredibly seriously.</p><p>Initial research, led by Sarah Rambacher, uncovered a set of strict, safety-first considerations. We learned that parallax effects and movement that runs contrary to a user’s scroll direction are highly likely to be problematic. We learned that flashing content poses specific risks, especially flashes between 5 and 30Hz and saturated red flashes.</p><p>With these clear considerations, our motion system prioritizes accessibility at its core.</p><ul><li>We follow the <a href="https://www.w3.org/TR/WCAG21/#seizures-and-physical-reactions">W3C accessibility guidelines</a> to enforce a limit of either using less than three flashes per second, or ensuring that the flash is below the <a href="https://www.w3.org/TR/WCAG21/#dfn-general-flash-and-red-flash-thresholds">general flash and red flash thresholds</a>.</li><li>We keep our animations minimal and reduce their contrast to avoid potential triggers.</li><li>Most importantly, we embrace the prefers-reduced-motion media query as a clear path to let users reduce the presence of animations. To ensure consistent functionality for animated components, we often reduce the animation duration to be imperceptible, rather than completely disabled. This approach prioritizes user safety without inadvertently breaking the experience.</li></ul><figure><img alt="A gif shows an error message that populates as improperly formatted text is entered into a text input. The user is shown turning on reduced motion settings in an OS menu and triggering an error once again. Prior to reduced motion, the error appears with a fade-in and slight side-to-side jiggle. In reduced motion, there’s only the face-in." src="https://cdn-images-1.medium.com/max/800/0*gk0ckXs2DZ-83iQd" /><figcaption>To further solidify our research findings and technical decisions, we crafted our motion design principles that provide a clear and easy-to-understand framework for our approach to motion.</figcaption></figure><h4>Motion with a mission</h4><p>At the foundation of our motion design philosophy is our declaration that motion in PatternFly must always serve a purpose. Well-designed animations can be powerful tools for improving usability. They can guide a user’s focus to what’s important, clarify the relationship between UI elements, and provide immediate, reassuring feedback that the system is responding to their actions.</p><p>This led us to our four guiding principles:</p><ul><li><strong>Intentional:</strong> Motion should guide our users without being a distraction. It must be purposeful and simple, helping users complete their tasks and focus only on what is most important.</li><li><strong>Consistent:</strong> Motion should create a familiar and predictable experience. It should be applied uniformly to unify interactions and connect the user’s journey across different products.</li><li><strong>Engaging:</strong> Motion should captivate users and add character to the interface. It can celebrate user accomplishments and make common interactions more expressive and interesting.</li><li><strong>Inclusive:</strong> Motion must empower users by respecting their preferences. It must always be optional and accommodating to ensure a comfortable and accessible experience for all.</li></ul><p>Take our expansion animations, for example. When a user opens an accordion or an expandable section, the content doesn’t just pop into view. Instead, a gentle fade and slide transition draws their eye to the newly revealed information. It’s a subtle effect, but it aligns with our principle of being intentional by guiding the user’s focus and making the new content easier to process.</p><figure><img alt="A gif is shown, where a mouse pointer clicks a navigation menu item to expand sub-nav items. The sub-nav items come into view with an animation that slides and fades the items into view from the direction of the parent item." src="https://cdn-images-1.medium.com/max/800/0*OEf3XGyw6WcUIqxc" /><figcaption>By guiding focus with a gentle fade and slide transition, expansion animations draw your eyes to newly revealed information.</figcaption></figure><h4>Anatomy of a PatternFly animation</h4><p>To ensure our animations will be consistent and scalable we developed a system of semantic motion tokens for duration, delay, and easing.</p><figure><img alt="Semantic design tokens are set up within Figma. They outline a range of options for motion duraction, from “xs” to “2xl” duration lengths." src="https://cdn-images-1.medium.com/max/1024/0*iXyW71xnOdYz7w-1" /><figcaption>Our motion tokens fit right into the semantic token system of PatternFly 6.</figcaption></figure><p>Under the hood, we chose a CSS-first approach. By prioritizing CSS transitions and animations over JavaScript-based solutions, we’re able to benefit from better performance. Because browsers are highly optimized to handle CSS animations, our animations will have smoother rendering and less technical overhead. We also focus on animating only the most performant properties, like transform and opacity, avoiding less efficient properties like height and margin that can negatively impact the animation quality.</p><figure><img alt="A gif shows a mouse pointer hovering over a hamburger menu navigation icon and clicking the icon. On hover, the middle of three horizontally stacked bars turns to a right-facing arrow. When clicked, the associated menu opens, and the arrow faces to the left, indicating that subsequent clicks will close the menu." src="https://cdn-images-1.medium.com/max/800/0*w81OAk2w0X_nyRTc" /><figcaption>A new arrow indicator in our hamburger menu icon signals to users what will happen next.</figcaption></figure><p>Our decision to use a CSS-first approach was informed by a careful analysis of other major design systems, where we saw a variety of philosophies. Some relied more heavily on JavaScript, while others used less performant properties.</p><p>By analyzing the different methods being used, we could solidify our path and focus on prioritizing performance and stability.</p><figure><img alt="A comparison table contains an assessment of animation implementation in 4 design systems, including PatternFly. The table contains checkmarks and x’s for different features. Only PatternFly’s column contains all features outlines: docs, css-only animations, most performant animation usage, accessibilty docs, and documented support for prefers-reduced-motion." src="https://cdn-images-1.medium.com/max/1024/0*MBIMDByS5Z3YpGw7" /></figure><ol><li><strong>Most performant actions used:</strong> Refers to using CSS properties like transform and opacity that don’t force the browser to recalculate page layouts, resulting in smoother animations and better overall performance.</li><li><strong>Orchestration:</strong> Describes how an animation is triggered. MUI uses JavaScript to manage the start and end states and orchestrate CSS transitions.</li><li><strong>Generally performant:</strong> While MUI might favor performant properties, some components animate height and can still lead to less smooth animations.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VIDkdSOnvw2EfG-GtwkQcg.png" /></figure><h3>Now we’re movin’ and groovin’</h3><p>Bringing purposeful motion to PatternFly has been a multi-year, highly collaborative marathon. The foundational system we’ve built demonstrates how animation, when treated with care, can make an interface more intuitive, accessible, and engaging.</p><p>With our initial phase of micro-animations complete, we can look toward the next horizon, like assessing performance and usability, understanding user sentiment, or even exploring more complex animations. We also look forward to ensuring that all animations are supported by default in a future breaking change release, removing the need for any opt-ins.</p><p>See the result of this multi-year effort:</p><ul><li>Dive into the details in our<a href="https://www.patternfly.org/design-foundations/motion"> motion guidelines and developer documentation</a>.</li><li>Interact with the different animations in <a href="https://www.patternfly.org/design-foundations/motion/demo">our guided animations tour</a>.</li><li>And let us know what you think.</li></ul><p>Your experience will help us define what comes next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p><em>Have a story of your own? </em><a href="https://medium.com/p/af90715e556d"><em>Write with us</em></a><em>! Our community thrives on diverse voices — let’s hear yours.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ac3bd08efba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/motion-with-purpose-7ac3bd08efba">Motion with purpose</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why PatternFly?]]></title>
            <link>https://medium.com/patternfly/why-patternfly-26f65e21bdbd?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/26f65e21bdbd</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[patternfly]]></category>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Fri, 20 Jun 2025 13:01:47 GMT</pubDate>
            <atom:updated>2025-09-08T15:54:06.834Z</atom:updated>
            <content:encoded><![CDATA[<h4>Defining Red Hat’s commitment to enterprise design</h4><figure><img alt="A PatternFly logo sits in the middle of a web of interconnected icons, including Red Hat product logos, a code branch icon, and an icon representing multiple people, all of which have dotted lines connecting to the PatternFly logo. There is a light blue background with clouds." src="https://cdn-images-1.medium.com/max/1024/1*xohZjJ1XyTwNP4lvjCBGbA.png" /></figure><figure><img alt="A blue horizontal divider with a centered PatternFly logo in the middle." src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p>Believe it or not, PatternFly just turned 11! It snuck up on us too, but it’s a moment to reflect on our journey. PatternFly started as a way to bring consistency to Red Hat’s diverse product lineup. While our community has grown beyond Red Hatters over the past decade, our core mission of keeping Red Hat products consistent remains.</p><p>Lately, the PatternFly team has been focused on streamlining and optimizing our team structure and processes to clarify responsibilities and build a stronger foundation for future growth. Amidst big plans on PatternFly’s horizon, we found this moment to be perfect for a bit of reflection. It felt right for us to consider why we’re <em>still</em> here and why PatternFly is <em>still</em> the go-to design system for Red Hat.</p><p>So we took that step back, and as a team, we put our heads together to craft an updated message for PatternFly. Here’s what we settled on.</p><figure><img alt="A horizontal divider made of three blue ellipses." src="https://cdn-images-1.medium.com/max/1024/1*VIDkdSOnvw2EfG-GtwkQcg.png" /></figure><h3><strong>PatternFly is tailored for Red Hat’s unique needs</strong></h3><p>PatternFly isn’t a generic design system; it’s purpose-built to meet the complex demands of Red Hat’s enterprise software and its technical users. We offer a robust design kit for creating mockups that quickly translate to code.</p><p>Unlike other systems, PatternFly offers highly customized components and extensions to support large data sets, complex workflows, and real-time insights — including unique solutions like <a href="https://www.patternfly.org/topology/about-topology">Topology</a>, <a href="https://www.patternfly.org/extensions/quick-starts">quick starts</a>, and <a href="https://www.patternfly.org/patternfly-ai/chatbot/overview">ChatBot</a>. This tailored approach enables us align Red Hat’s brand across many unique user experiences. It helps us advance the look and feel of our products while prioritizing accessibility, and drive cross-product consistency by elevating UI patterns.</p><p>PatternFly is built <em>for</em> Red Hat needs, not simply adapted, ensuring the best flexibility and functionality for our diverse product portfolio.</p><h3><strong>PatternFly’s philosophy is inherently open source</strong></h3><p>PatternFly’s philosophy is inherently open source, aligning with Red Hat’s foundational perspective. As an MIT-licensed project, we actively encourage collaboration and promote transparency in our development practices. This not only builds a unified “open source” brand across Red Hat products, but also directly facilitates access and contribution, empowering product teams and the wider community to submit issues, feature requests, and solutions.</p><p>This open collaboration is <em>essential</em> for supporting complex enterprise workflows across Red Hat’s diverse portfolio. It has enabled us to deliver tailored solutions for data-heavy dashboards in Red Hat Insights, intricate multi-level navigation in Red Hat Advanced Cluster Management, robust enterprise tables and charts in Red Hat Satellite, and seamless terminal integrations in Red Hat OpenShift Platform. Our direct design-engineering integration, built with widely adopted React implementations, further ensures efficiency and alignment with industry standards within our open framework.</p><h3><strong>PatternFly is engineered for speed and control</strong></h3><p>PatternFly operates independently, a practice that is crucial to our efficiency and responsiveness. This allows us to set priorities based on timely Red Hat product needs, avoiding dependency on external roadmaps and delivering custom solutions when they’re most needed. Our React implementation also ships with built-in accessibility features, making accessibility integral to our development process rather than an afterthought.</p><p>By maintaining this level of control over our development, we can ensure strong security and compliance and predictably manage breaking changes, providing more stability and confidence for products built with PatternFly.</p><p>This unified approach to speed and control enables rapid iteration, ensuring PatternFly consistently evolves in alignment with Red Hat’s strategic direction.</p><h3><strong>PatternFly empowers developers, designers, and project managers</strong></h3><p>PatternFly provides a foundation and shared language between designers, developers, and product managers, supporting better communication, understanding, and collaboration.</p><p>PatternFly is designed to be a powerful ally for front-end developers, with comprehensive documentation, native accessibility support, and the flexibility of multiple libraries (React <em>and</em> HTML). Even entry-level developers can build effective, beautiful, and inclusive interfaces.</p><p>Both designers and developers get to benefit from our extensive design guidelines. From simple components to more complex UI solutions, PatternFly expedites the work of product teams by providing well-documented shortcuts that save time and effort.</p><p>Our open source approach directly empowers product teams to easily contribute or request changes, fostering a truly collaborative environment where designers and developers can actively shape the very system they build with.</p><figure><img alt="A horizontal divider made of three blue ellipses." src="https://cdn-images-1.medium.com/max/1024/1*VIDkdSOnvw2EfG-GtwkQcg.png" /></figure><p>Reflecting on “Why PatternFly?” reinforces a powerful truth: our design system is deeply interwoven with Red Hat’s commitment to open source, delivering robust enterprise experiences, and developer empowerment. With tailored features, independent development, and a collaborative foundation, PatternFly directly provides the consistency, control, and agility demanded by Red Hat’s diverse product portfolio. It’s a testament to what we can achieve when we build together.</p><p>For the PatternFly team, the next steps involve actively integrating this defined narrative into our core documentation, onboarding materials, and internal training. This perspective will also inform an upcoming team-wide workshop, focused on more deeply defining and understanding our users. As PatternFly matures and we continue to meet our community where they are, we’ll continually refine and evolve this message to keep our story and purpose clear and relevant.</p><p>We invite you to explore <a href="http://patternfly.org/">PatternFly.org</a> to dive deeper into its capabilities and strategic impact. More importantly, we encourage you to <a href="https://www.patternfly.org/get-started/about-patternfly#join-the-community">join our vibrant community</a>, <a href="https://www.patternfly.org/get-started/contribute">contribute to our evolution</a>, and help shape the future of enterprise user experiences the open source way.</p><figure><img alt="A blue horizontal divider with a centered PatternFly logo in the middle." src="https://cdn-images-1.medium.com/max/1024/1*4W1_9uAO6Wyvv-0lJYvPFg.png" /></figure><p><em>Have a story of your own? </em><a href="https://medium.com/p/af90715e556d"><em>Write with us</em></a><em>! Our community thrives on diverse voices — let’s hear yours.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26f65e21bdbd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/why-patternfly-26f65e21bdbd">Why PatternFly?</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to PatternFly 6]]></title>
            <link>https://medium.com/patternfly/welcome-to-patternfly-6-5c372f2fd5de?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c372f2fd5de</guid>
            <category><![CDATA[releases]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Mon, 28 Oct 2024 18:28:02 GMT</pubDate>
            <atom:updated>2025-09-08T15:55:10.246Z</atom:updated>
            <content:encoded><![CDATA[<h4>OPEN SOURCE</h4><h4><em>Our modern makeover is all about consistency, clarity, and cohesion</em></h4><figure><img alt="Low-fidelity PatternFly 6 graphics." src="https://cdn-images-1.medium.com/max/1024/1*FOVVqeJPmsoM6uJqsZHXZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*awiWEJtcb8sVTcor" /></figure><p>The moment we’ve all been waiting for is finally here! Say “hello” to PatternFly 6. Our next era introduces several significant changes that enhance consistency, clarity, and cohesion across PatternFly.</p><p>We’re excited to unveil what’s new:</p><ul><li>An updated visual design</li><li>Our new design token system</li><li>The release of PatternFly AI</li><li>And much more!</li></ul><p>As always, <a href="https://patternfly.org/get-started/release-highlights">our release highlights</a> contain extra detail, but let’s take a look at the key changes.</p><h3>PatternFly’s new look and feel</h3><p>Your eyes don’t deceive you: PatternFly 6 has a brand new visual theme.</p><figure><img alt="Collage of high-fidelity PatternFly 6 components." src="https://cdn-images-1.medium.com/max/1024/0*AobO1O-dh79ghVtn" /><figcaption>Updated colors and shapes create a simplified and lightweight visual experience.</figcaption></figure><p>This is the first time in <em>4 years</em> that we’ve changed the look of PatternFly to this extent. We’ve updated our color palettes, typography, spacing, borders, and more, to create a look that is more modern and lightweight. This new look also aligns with <a href="https://www.redhat.com/en/about/brand/standards">Red Hat styles</a>, to help users enjoy a more seamless experience between Red Hat websites and applications.</p><p>More than just good looks, our new visuals create more inclusive experiences by integrating familiar Red Hat styles and improving accessibility scores.</p><p><a href="https://www.figma.com/@patternfly">All PatternFly 6 styles are available for you to use in Figma →</a></p><h3>A whole new world of design tokens</h3><p>Our design overhaul was made possible through our new, robust design token system. Design tokens lay the foundation for easier maintenance, scalability, and consistency across products. When you use tokens, you’ll gain immediate access to future PatternFly style changes, ensuring your users receive the newest features as they’re released.</p><p>Plus, design tokens make it easier to complete future migrations!</p><p><a href="https://www.patternfly.org/tokens/about-tokens">We’ve added tokens documentation to the website </a><a href="https://www.figma.com/@patternfly">→</a></p><figure><img alt="Design tokens used in a warning alert." src="https://cdn-images-1.medium.com/max/1024/0*8rMBmBKJ1gK3YXOL" /><figcaption><em>Our semantic tokens make your design choices more clear and consistent.</em></figcaption></figure><h4>Custom theming</h4><p>While light and dark theming has previously been possible, PatternFly 6 makes it easier for you to add support in your products. Now, both light and dark themes ship with PatternFly by default. To enable dark theme support, you can simply use our new class. Visit <a href="http://patternfly.org/developer-resources/dark-theme-handbook">our dark theme handbook</a> for the latest implementation guidance.</p><p>Thanks to design tokens, it also becomes possible to implement flexible, custom themes using PatternFly. After migrating to PatternFly 6, you can easily adjust your product’s styles to create a visual theme that strengthens your brand and supports your users.</p><h4>Motion design</h4><p>Tokens have also enabled us to begin adding micro-animations to our components. This work is still in progress, but you can read about <a href="http://patternfly.org/design-foundations/motion">our guiding principles and processes for motion design</a> now. We’ll continue to provide updates as this project advances.</p><h4>A note about pixels</h4><p>To improve our documentation accuracy, we’ve updated many pixel references on our website to instead mention rems, which are relative units that are based on the font size of a webpage’s `&lt;html&gt;` element. Using rems instead of pixels improves accessibility and better supports a wider range of users.</p><p><a href="https://blog.hubspot.com/website/css-rem#what-is-rem-css">Learn more about rem units and their benefits</a><a href="https://www.figma.com/@patternfly"> →</a></p><p>While many of our CSS variables have used rems in the past, our design and documentation resources often referred to the pixel equivalents instead. By updating our documentation to also use rems, designers can have a more accurate understanding of the implementation of design decisions.</p><p>PatternFly expects the `&lt;html&gt;` element size to be 16px, so 1rem would be 16px, 2rems would be 32px, and so on.</p><figure><img alt="Comparison of rem units to equivalent pixel sizes." src="https://cdn-images-1.medium.com/max/1024/1*a2dCpLAKlPcpcfenTWSNbA.png" /></figure><p>As part of PatternFly 6, we did convert our breakpoint tokens to use rems. As a result, you may need to make updates to your codebase where you refer to breakpoint values. This is an important step that we mention in<a href="http://patternfly.org/get-started/upgrade#3.-update-any-pixel-based-logic"> our upgrade guide</a>.</p><h3>Introducing PatternFly AI</h3><p>AI has been the talk-of-the-town recently — and with good reason. When used intentionally and strategically, AI can better empower your users to complete their goals. We put careful thought into how AI can be leveraged to support your users.</p><p>PatternFly 6 introduces the initial release of PatternFly AI, featuring <a href="http://patternfly.org/patternfly-ai/chatbot/about-chatbot">our new chatbot extension</a>.</p><figure><img alt="Basic chatbot window." src="https://cdn-images-1.medium.com/max/1000/0*nG74wEQpXFEkfLI-" /><figcaption>Our chatbot extension uses PatternFly styles to neatly integrate into your products.</figcaption></figure><p>Chatbots can provide your users with personalized support that boosts their efficiency and improves their experience with your product. Our chatbot is <em>only</em> available with PatternFly 6.</p><p><a href="http://patternfly.org/patternfly-ai/about-ai">The PatternFly AI documentation</a> includes our AI principles and ethical guidelines, as well as conversation design guidelines that help you write for AI.</p><h3>Component groups overhaul</h3><p>Our <a href="https://medium.com/patternfly/introducing-component-groups-dbe054cac726">component groups extension has been growing since its release</a>, so we took a step back to enhance documentation, update component names, and restructure the information architecture.</p><p>As a result, you can now find <a href="http://patternfly.org/component-groups/about-component-groups">component groups</a> at the top level of our navigation. To help you explore the different options, we’ve also organized the components into functional categories.</p><figure><img alt="Component groups navigation section, expanded." src="https://cdn-images-1.medium.com/max/1024/1*b7korV3i3SZCtp5-pRCb_g.png" /><figcaption>Conceptual grouping makes it easier to find what you need.</figcaption></figure><p>We are always continuing to evolve our component groups and documentation. If you notice a bug or have a suggestion for a new component group, feel free to file an issue in our <a href="https://github.com/patternfly/react-component-groups/issues">GitHub repository</a>! If you have any general feedback, <a href="https://patternfly.slack.com/archives/C293LQ36J">let us know on Slack.</a></p><h3>React component changes</h3><p>Of course, we’ve continued to involve our standard React component library to adapt to your users’ needs.</p><h4><strong>Deprecated components</strong></h4><p>When we need to make significant design or code changes to a component, we may deprecate one implementation in favor of another. This helps with consistency and maintenance efforts.</p><p>In PatternFly 6, we’ve deprecated the following:</p><ul><li><a href="http://patternfly.org/components/chip"><strong>Chip</strong></a><strong>:</strong> Instead, use <a href="http://patternfly.org/components/label">label</a>.</li><li><a href="http://patternfly.org/components/tile"><strong>Tile</strong></a><strong>:</strong> Instead, use <a href="http://patternfly.org/components/card#cards-as-tiles">card</a>.</li><li><strong>Text:</strong> Not quite a deprecation, but text has been renamed <a href="https://patternfly-org-pr-4317-site.surge.sh/components/content">“content.”</a></li></ul><h4><strong>Promoted components</strong></h4><p>We’ve promoted these beta components to be official implementations:</p><ul><li><a href="http://patternfly.org/components/button#button-with-count">Buttons with count label</a></li><li><a href="http://patternfly.org/components/label#editable-labels">Editable labels</a> and <a href="http://patternfly.org/components/label#editable-label-group">editable label groups</a></li><li><a href="https://medium.com/components/menus/menu#with-drilldown">Drilldown menus</a></li><li><a href="http://patternfly.org/components/navigation#flyout">Flyout navigation</a></li><li><a href="http://patternfly.org/components/navigation#drilldown">Drilldown navigation</a></li><li><a href="http://patternfly.org/components/spinner#inline-size">Inline spinner</a></li><li><a href="http://patternfly.org/components/timestamp">Timestamp</a></li></ul><p>We also promoted the “Next” versions of the following components:</p><ul><li><a href="http://patternfly.org/components/dual-list-selector">Dual list selector</a></li><li><a href="http://patternfly.org/components/modal">Modal</a></li><li><a href="http://patternfly.org/components/drag-and-drop">Drag and drop</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LEMlLQcHBMqfgmOQ" /></figure><h3><strong>Ready, set, go!</strong></h3><p>PatternFly 6 is ready for you now — don’t hold your users back from the latest and greatest! You can <em>only </em>take advantage of our exciting new features when you upgrade.</p><p>The <a href="http://patternfly.org/get-started/upgrade">PatternFly 6 upgrade guide</a> is available to support and guide your migration journey.</p><p>We know that migrating your codebase can be a <em>significant</em> undertaking that requires careful consideration, but it’s work that benefits both you and your users. This is an opportunity to rethink product experiences, starting with research and design.</p><p>If you have any questions or need support as you migrate, don’t hesitate to <a href="https://patternfly.slack.com/archives/C293LQ36J">reach out to the PatternFly team on Slack.</a> We’re here to help you!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KB6Fd2owhNiheLd6" /></figure><p><em>Have a story of your own? </em><a href="https://medium.com/p/af90715e556d"><em>Write with us</em></a><em>! Our community thrives on diverse voices — let’s hear yours.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c372f2fd5de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/welcome-to-patternfly-6-5c372f2fd5de">Welcome to PatternFly 6</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the PatternFly 6 beta]]></title>
            <link>https://medium.com/patternfly/introducing-the-patternfly-6-beta-364952dba6ba?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/364952dba6ba</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Thu, 22 Aug 2024 13:24:52 GMT</pubDate>
            <atom:updated>2024-08-22T13:24:52.787Z</atom:updated>
            <content:encoded><![CDATA[<h4>OPEN SOURCE</h4><h4>All about our next big step towards PatternFly 6</h4><figure><img alt="Low-fidelity image of the PatternFly dark theme website, covered by a blue “beta” label" src="https://cdn-images-1.medium.com/max/1024/1*-xS5YU2yAEwZSXFF_xjgow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CT4tw1PpPrkvtA_S" /></figure><p>New month, new milestone!</p><p>By now, <a href="https://medium.com/patternfly/welcome-to-the-patternfly-6-alpha-6d6f64de5a73">our alpha release for PatternFly 6</a> has been available for a few months. The feedback from our alpha participants has allowed us to keep enhancing and evolving as we move towards the full release of PatternFly 6. Today, we’re excited to share the next big step in our journey–our beta release!</p><p>The PatternFly 6 beta introduces more improvements and refinement, containing all major features planned for the final release. This beta period is all about testing our first draft of the final details. Your continued participation, support, and feedback helps ensure that PatternFly 6 is as well-tested and bug-free as possible before the full release.</p><p>This blog covers the most top-level highlights — <a href="https://staging-v6.patternfly.org/get-started/release-highlights">check out our full release highlights for more details.</a></p><h3><strong>What’s new?</strong></h3><p>Here’s what we’ve been up to since April:</p><ol><li>We fixed the bugs that were reported throughout the alpha period.</li></ol><p>2. We made more updates to our website docs to reference our token system.</p><p>3. We applied PatternFly 6 styles to our charts, extensions, patterns, and Topology. These have been added to <a href="https://www.figma.com/@patternfly">our Figma kit</a> as well!</p><p>4. We promoted some of our beta components to become standard components in PatternFly 6. These will be fully-supported features going forward:</p><ul><li>Buttons with count label</li><li>Editable labels</li><li>Flyout and drilldown menus and navigation</li><li>Menu toggle with status indicator</li><li>Modal title with status indicator</li><li>Inline spinners</li><li>Timestamp component</li></ul><p>5. We’ve continued developing more codemods to support your upgrade process. Since our initial alpha launch, we’ve added around 30 additional codemods, bringing our current total count to 66. As we keep working towards the full release, this number is likely to increase even further, to ensure that we’ve got you covered.</p><p>6. We changed the API for our class-name-updater codemod to make it more consistent with pf-codemods: both now use a --v6 flag. We updated our upgrade guide to reflect this change.</p><h3><strong>What’s next?</strong></h3><p>The full release of PatternFly 6 is tiptoeing closer, but there are still some final touches that we’ll add to our documentation throughout the beta. And, of course, we’ll fix any bugs that you share with us along the way.</p><p>Please continue to <a href="https://github.com/orgs/patternfly/discussions">share your feedback</a>, <a href="https://github.com/patternfly/patternfly-org/issues/new/choose">open a GitHub issue</a>, or <a href="https://join.slack.com/t/patternfly/shared_invite/zt-1npmqswgk-bF2R1E2rglV8jz5DNTezMQ">reach out to us on Slack</a>. We can’t wait to release PatternFly 6 into the wild!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Pub-6BFpqfWqh9zq" /></figure><p><em>Have a story of your own? </em><a href="https://medium.com/patternfly/submitting-to-patternflys-medium-publication-d809a75b4ea2"><em>Write with us</em></a><em>! Our community thrives on diverse voices — let’s hear yours.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=364952dba6ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/introducing-the-patternfly-6-beta-364952dba6ba">Introducing the PatternFly 6 beta</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to the PatternFly 6 alpha]]></title>
            <link>https://medium.com/patternfly/welcome-to-the-patternfly-6-alpha-6d6f64de5a73?source=rss-4b549ba96527------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d6f64de5a73</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[alpha]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[releases]]></category>
            <dc:creator><![CDATA[Erin Donehoo]]></dc:creator>
            <pubDate>Tue, 02 Apr 2024 15:57:28 GMT</pubDate>
            <atom:updated>2024-04-02T20:47:08.530Z</atom:updated>
            <content:encoded><![CDATA[<h4>OPEN SOURCE</h4><h4>Everything you need to know about our alpha release</h4><figure><img alt="Image of the new PatternFly homepage." src="https://cdn-images-1.medium.com/max/1024/0*tc9YA_4LEFm1AZm9" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0J4SU9MuilqgLZvg" /></figure><p>Flyers, welcome to the alpha release of PatternFly 6!</p><p>For the first time, we’re pulling back the curtains to let you in on the next major PatternFly update — <em>months in advance</em>.</p><p>We’re excited to finally share <a href="https://staging-v6.patternfly.org/"><strong>the alpha website</strong></a> with you.</p><p>The full release of PatternFly 6 is still under development and won’t happen until later this year, but this open alpha gives you a sneak peek at our upcoming redesign and invites you to test out the changes we’re making.</p><h3><strong>How to participate in the alpha</strong></h3><p>To view the alpha website, click the link in the banner on our website’s homepage:</p><figure><img alt="The new homepage banner that redirect users to the alpha website." src="https://cdn-images-1.medium.com/max/1024/1*tB_fhkJTHn-NZZsSUgJaFA.png" /><figcaption>Click “Go to PatternFly 6” to be redirected to our alpha website</figcaption></figure><p>You can also select “PatternFly 6” from the release toggle in the PatternFly.org masthead.</p><figure><img alt="The release menu offers PatternFly 6 as an option." src="https://cdn-images-1.medium.com/max/1024/1*PyoCyyyAAp6gIlSEx7AEhA.png" /><figcaption>The alpha release has its own link in our release dropdown menu</figcaption></figure><p>Once you’ve switched to the alpha website, you’ll see the site update with our new PatternFly 6 visual theme. You’ll also be able to find updated alpha-specific documentation across the site.</p><p>If you previously upgraded from PatternFly 4 to PatternFly 5, then the alpha onboarding process will be familiar. Like with our last major release, we’ve created an <a href="https://staging-v6.patternfly.org/get-started/upgrade">upgrade guide</a> to outline the major changes and provide instructions to help you upgrade your product’s codebase.</p><h3><strong>What’s included in the alpha?</strong></h3><h4><strong>Design tokens</strong></h4><p>We <a href="https://www.patternfly.org/get-started/design#figma-library">moved our design library from Sketch to Figma</a> this year to facilitate better communication and collaboration for designers and developers alike. Soon after, we got to work building a design token system. These style variables introduce a more straightforward, semantic naming structure to our variables, making it easier for you to make consistent design decisions. Plus, our token system is easier to maintain, meaning that you’ll have quick access to any updates to the PatternFly design system.</p><p><a href="https://staging-v6.patternfly.org/tokens/about-tokens">We’ve added documentation to the alpha website</a> to provide more details and context about tokens.</p><p>Design tokens reimagine the way that UIs can be built with PatternFly and pave the way for additional visual theming support, just like our brand new theme…</p><h4><strong>New visual theme</strong></h4><p>Our token system was created to support PatternFly’s new visual theme. This new look is what you can see across the PatternFly alpha website. It’s more modern, lightweight, and refined so that you can build the best UIs. Take a look through our updated design for our components, patterns, and charts.</p><p>We’ve also <a href="https://staging-v6.patternfly.org/get-started/design">updated our design onboarding guide</a> with instructions for the PatternFly 6 Figma design kits.</p><blockquote><strong>Note: </strong>The PatternFly 5 design library is not built with tokens. To take advantage of our token system, you <em>must</em> upgrade your product to PatternFly 6 and its new theme.</blockquote><h3><strong>What’s next?</strong></h3><p>We’re continuing to tinker, refine, and smooth out details to prepare for the full release of PatternFly 6, later this year. We’ll have a beta release between now and then, which we’ll share with you as soon as it’s ready. For now, we hope you enjoy this alpha!</p><p>We ask you to <a href="https://github.com/orgs/patternfly/discussions">share all feedback</a> and/or <a href="https://github.com/patternfly/patternfly-org/issues/new/choose">open a GitHub issue</a> if you find any bugs as you participate in this release. Your welcome support will help strengthen PatternFly ahead of its next major release!</p><p>As always — please <a href="https://join.slack.com/t/patternfly/shared_invite/zt-1npmqswgk-bF2R1E2rglV8jz5DNTezMQ">reach out to us on Slack</a> if you’d like to chat about this release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iuMuvsaQnsCk-EJ_" /></figure><p><em>Have a story of your own? </em><a href="https://medium.com/patternfly/submitting-to-patternflys-medium-publication-d809a75b4ea2"><em>Write with us</em></a><em>! Our community thrives on diverse voices — let’s hear yours.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d6f64de5a73" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/welcome-to-the-patternfly-6-alpha-6d6f64de5a73">Welcome to the PatternFly 6 alpha</a> was originally published in <a href="https://medium.com/patternfly">PatternFly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>