<?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 Zack Allen on Medium]]></title>
        <description><![CDATA[Stories by Zack Allen on Medium]]></description>
        <link>https://medium.com/@zallen_78045?source=rss-793b7ea7ccd0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*7A8sek7FGasW4bwdlPRc7g.png</url>
            <title>Stories by Zack Allen on Medium</title>
            <link>https://medium.com/@zallen_78045?source=rss-793b7ea7ccd0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:01:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zallen_78045/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[Component changes [2020 major release update]]]></title>
            <link>https://medium.com/patternfly/component-changes-2020-major-release-update-7b93eb4ec02c?source=rss-793b7ea7ccd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b93eb4ec02c</guid>
            <category><![CDATA[major-release]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Zack Allen]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 13:01:01 GMT</pubDate>
            <atom:updated>2020-08-17T16:04:34.005Z</atom:updated>
            <content:encoded><![CDATA[<h4>From new names to new additions, let’s walk through PatternFly’s updated components.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4uHLa6_vjQ-Puepg" /><figcaption>Photo by <a href="https://unsplash.com/@kaleidico?utm_source=medium&amp;utm_medium=referral">Kaleidico</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><figure><img alt="PatternFly’s branded divider, our logo centered between two lighter lines." src="https://cdn-images-1.medium.com/max/1024/1*XmM91Yc3Be0Kqc7FxtOwFw.png" /></figure><p>When we first create components, we have no idea just how many use cases they’ll cover or new creative ways they’ll be used. Sometimes components change so much that we rename them. And sometimes, like in the case of <strong>label</strong>, they just fall flat and need a visual overhaul to be useful again.</p><p>We’re on a constant mission to grow and evolve with you. Updating our components is a key part of that process. Let’s start off with the heavy hitters if you’re a PatternFly consumer: our renamed components.</p><h3>Renamed components</h3><p>We know no one likes going back to change variable names in their code, but we felt the benefits of simpler and cleaner names outweighed the cost of this change.</p><h4><a href="https://github.com/patternfly/patternfly/pull/2937">Expandable to ExpandableSection</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>Our components are things, and things are nouns. All of our component names are nouns — except <strong>expandable</strong>. Expandable is an adjective, and adjectives describe states and variations. Therefore we renamed the expandable component to expandable section to better align with our naming convention.</p><h4><a href="https://github.com/patternfly/patternfly/pull/3035">Card Component Renaming</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>You can put some pretty complex components in the header of our cards. Our card headers used to be structured rather confusingly:</p><pre>&lt;Card&gt;</pre><pre>  &lt;CardHead&gt;</pre><pre>    &lt;CardHeadMain&gt;Header&lt;/CardHeadMain&gt;</pre><pre>  &lt;/CardHead&gt;</pre><pre>  &lt;CardHeader&gt;Title&lt;/CardHeader&gt;</pre><pre>&lt;/Card&gt;</pre><p>You’ll notice the “Title” is in a <strong>CardHeader</strong> component… that’s rather confusing! We renamed CardHeader to <strong>CardTitle</strong> and made the rest of the names fall in line:</p><pre>&lt;Card&gt;</pre><pre>  &lt;CardHeader&gt;</pre><pre>    &lt;CardHeaderMain&gt;Header&lt;/CardHeaderMain&gt;</pre><pre>  &lt;/CardHeader&gt;</pre><pre>  &lt;CardTitle&gt;Title&lt;/CardTitle&gt;</pre><pre>&lt;/Card&gt;</pre><h4><a href="https://github.com/patternfly/patternfly/pull/3046">DataToolbar to Toolbar</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>We built the <strong>data toolbar</strong> component to replace our less functional toolbar component. Once the data toolbar was promoted to an official component, we decommissioned the old toolbar to free up its name. Continuing the toolbar’s legacy, the data toolbar was renamed to toolbar, and the rest is history.</p><figure><img alt="Our new toolbar component, featuring drop-down selection, sorting options, and toolbar actions" src="https://cdn-images-1.medium.com/max/1024/0*9dVE4m1Bs5L8W8vF" /><figcaption>Goodbye old toolbar component. You won’t be missed.</figcaption></figure><h4><a href="https://github.com/patternfly/patternfly-react/pull/4223">Toolbar to PageHeaderTools</a> by <a href="https://github.com/jschuler">@jschuler</a></h4><p>As it turns out, the default implementation for page headers in React was the old toolbar component. Our HTML library had a better solution for this since 2019 called <a href="https://www.patternfly.org/2020.04/documentation/core/components/page#usage"><strong>PageHeaderTools</strong></a>. When killing the old toolbar, we replaced it with PageHeaderTools.</p><h3>Refactored components</h3><p>We’re sure you’re familiar with procrastination. Historically, we’ve had the perfect excuse to procrastinate refactoring components: we didn’t want to break existing usages or surprise consumers. Unfortunately for this release we couldn’t lean on that excuse anymore…</p><h3>Label</h3><h4><a href="https://github.com/patternfly/patternfly/pull/2943">Refactored label component</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>We refactored and redesigned the <strong>Label</strong> component. It now supports multiple color variations, icons, a close button, an alternate “outline” design, and interactivity when used as a link.</p><p>Sizing also changed. Instead of a normal and compact size, the label component has a single size that works for all applications.</p><p>These changes make the label component not only easier to use, but also easier to differentiate from buttons, which was an issue with the previous design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/0*_MhB-LXg1a0C41a5" /><figcaption>Our old labels looked a lot like buttons (left).</figcaption></figure><figure><img alt="Our new labels without outlines, so they no longer look like buttons" src="https://cdn-images-1.medium.com/max/1024/0*AxnZlm6TJV8vKIjm" /><figcaption>Our new labels support more functionality and no longer look like buttons (right).</figcaption></figure><h4><a href="https://github.com/patternfly/patternfly/pull/2823">Widen chip group labels</a> by <a href="https://github.com/christiemolloy">@christiemolloy</a></h4><p>Sometimes you just need a little bit more space. Previously, our chip label max width truncated chip labels expanding beyond `120px`, making them difficult to read.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/0*WtBn5hSBK4R0dot-" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/0*LTZDc-MwUgKWkJJk" /><figcaption>To solve <a href="https://github.com/patternfly/patternfly/issues/2765">this issue</a>, we just needed to give our chip group labels a few more characters of elbow room!</figcaption></figure><p>We increased the width of chip group labels from `120px` to `160px` to allow more space to accommodate longer label names.</p><h4><a href="https://github.com/patternfly/patternfly/pull/2766">Refactor of form label and control sections</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>Sometimes simple problems require complex solutions. One of our Flyers just wanted to add a popover to a form’s label text:</p><figure><img alt="A popover added to Phone Number label text on a form" src="https://cdn-images-1.medium.com/max/436/0*S-6q6jW7tSaVlQ2F" /><figcaption><a href="https://github.com/patternfly/patternfly/issues/2703">Adding a popover</a> seemed simple enough.</figcaption></figure><p>Unfortunately, our markup wasn’t quite up to snuff to support this, so we introduced new sections for form component layouts: .pf-c-form__group-label and .pf-c-form__group-control.</p><p>While we addressed this issue, we cleaned up some unused modifiers, moved padding around, and made the component’s CSS more consistent with others, given the new HTML. We also modified some styling for radios and checkboxes.</p><p>We added the requested form field level help feature, too. When clicked, the button triggers a popover with more information to help users complete the form. We added support for all of this to React.</p><figure><img alt="A clickable popover button beside a Name field. Clicking opens the popover text." src="https://cdn-images-1.medium.com/max/506/0*oAUqASC52u7YnOTB" /><figcaption>It may look the same, but that icon is now a clickable button!</figcaption></figure><h3>Chip</h3><h4><a href="https://github.com/patternfly/patternfly/pull/2941">Chip redesign</a> by <a href="https://github.com/christiemolloy">@christiemolloy</a></h4><p>We redesigned the <strong>chip</strong> component to be sleeker and less boxy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/488/0*1zvhko9mP9jgFfA_" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/0*C0i0nnb6IkDD9dpJ" /><figcaption>Old chips were tall and had a grey outline (left). New chips are shorter and have no outline (right).</figcaption></figure><h4><a href="https://github.com/patternfly/patternfly/pull/3058">Chip group structure</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>We refactored the chip group for improved accessibility. The new structure makes user customization easier too.</p><figure><img alt="Previously, a stacking issue was caused by a negative margin. Chips look cramped and crowded." src="https://cdn-images-1.medium.com/max/1024/0*iLeAmOZdCgI2ooHp" /><figcaption><a href="https://github.com/patternfly/patternfly/issues/2990">Stacking issue</a> caused by negative margin.</figcaption></figure><figure><img alt="Chip groups eliminate the stacking issue. Now, these chips are categorized and stacked neatly." src="https://cdn-images-1.medium.com/max/1024/0*Ljq3aoEjb8Mqh38O" /><figcaption>Proper markup means proper stacking!</figcaption></figure><p>In React, this allowed us to remove the concept of <strong>ChipGroupToolbar</strong>. Instead you can just add a category to a chip group!</p><h3>Modal</h3><h4><a href="https://github.com/patternfly/patternfly/pull/2969">Modal gets its own title</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>As part of our effort to have Wizard using Modal under the hood, our <strong>modal</strong> component now has its own built-in title. Don’t worry, you can still use the title component for your modal title if you’d like. Whither shall you modal?</p><h4><a href="https://github.com/patternfly/patternfly/pull/2881">Left-align modal footer actions</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>We set the modal footer actions to be left-aligned by default, to align with action placements across PatternFly. This approach improves consistency across the system and makes it easier to scan from top to bottom when forms are used inside a modal.</p><figure><img alt="Now, modals appear with all text left-justified by default to improve scannability" src="https://cdn-images-1.medium.com/max/1024/0*AyvujtXSCZ-czZNr" /><figcaption>🎵 To the left, the left, the left, the leftttttt… 🎵</figcaption></figure><h3>Tab</h3><h4><a href="https://github.com/patternfly/patternfly/pull/2757">Tab redesign</a> by <a href="https://github.com/mattnolting">@mattnolting</a></h4><figure><img alt="The vertical variation of our tabs component" src="https://cdn-images-1.medium.com/max/266/0*6C23VgqRlVT2oxml" /><figcaption>Boxy vertical tabs are in!</figcaption></figure><p>We redesigned the <strong>tabs</strong> component. The new tabs design offers both horizontal and vertical variations. It also supports an inset feature that adds padding to the tabs container, repositioning the start and end point of the tabs list. This adds flexibility to the tabs design so it can be used in custom layouts to match the padding of surrounding components and layouts. You can now use icons in tabs.</p><p>We also improved scroll button design and UX. The scroll buttons now appear inline with (as opposed to on top of) the tabs list, and both scroll buttons are always visible when overflow content exists on either side.</p><p>Here’s another example of our new tabs in action:</p><figure><img alt="The horizontal configuration of our tabs component, including sub tabs" src="https://cdn-images-1.medium.com/max/1024/0*Rfrx8hd2zRbHk3QB" /><figcaption>You can now spam click those scroll buttons with confidence. We also added sub tabs!</figcaption></figure><h3>Alert</h3><h4><a href="https://github.com/patternfly/patternfly/pull/2921">Refactor for better accessibility</a> by <a href="https://github.com/christiemolloy">@christiemolloy</a></h4><p>We redesigned the <strong>alert</strong> component for improved usability and accessibility. By placing the actions below the content, we don’t have to worry about lengthy action buttons competing for content space. We gave the close action its own unique styling to match the design.</p><p>In addition, this refactor is more usable for mobile viewport sizes. The design now extends more cleanly to that size.</p><p>Your alerts might take up an extra vertical line of space, but we think it’s worth it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7k2kBcUxfenJiHy6" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xwCId0fcfSAwyz6v" /><figcaption>Old alerts were rather crowded when the description or actions took longer than a single line (left).</figcaption></figure><p>At the cost of an extra line, we gain a whole lot, including changed colors which you can read about in our <a href="https://medium.com/patternfly/global-changes-2020-major-release-update-a108a13486e9">2020 major release update</a></p><h3>Navigation</h3><h4><a href="https://github.com/patternfly/patternfly/pull/2978">Vertical nav defaults to dark theme</a> by <a href="https://github.com/mattnolting">@mattnolting</a></h4><p>We made the dark vertical navigation theme the default. Our user research revealed a user preference for the dark themed navigation. If you prefer the light theme, it still works just fine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/0*D1E8kUR57ZG1xy7h" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c8iN2-yHbWZlxFP6" /><figcaption>The light theme (left) is being replaced by the dark theme (right).</figcaption></figure><h3>Table</h3><h4><a href="https://github.com/patternfly/patternfly/pull/2868">Improve table text wrapping</a> by <a href="https://github.com/mattnolting">@mattnolting</a></h4><p>We made the text wrapping behavior in table cells less aggressive, resulting in improved text wrapping in most <strong>table</strong> component use cases.</p><p>However, some situations may call for aggressive wrapping, so we introduced a modifier class variation for table cells (.pf-m-break-word) to re-enable aggressive wrapping.</p><h4><a href="https://github.com/patternfly/patternfly/pull/2965">Better table text styling</a> by <a href="https://github.com/mattnolting">@mattnolting</a></h4><p>We added a set of classes that serve as tools to better control the way table cells display text:</p><ul><li>.pf-m-nowrap keeps text from wrapping to multiple lines</li><li>.pf-m-truncate truncates overflowing text with an ellipsis when the text overflows the width of the cell</li><li>.pf-m-wrap allows text to wrap to multiple lines if it doesn’t wrap by default</li><li>.pf-m-fit-content fits text within the existing column/cell width instead of expanding it</li><li>.pf-m-break-word enables aggressive word wrapping, for use with very long strings, such as URLs</li></ul><p>In React, the <strong>Table</strong> now has a <strong>TableText</strong> component to improve text displays in a grid layout. New decorators (nowrap, truncate, fitContent, breakWord) have also been added.</p><figure><img alt="The TableText component in action. Text in grid layouts wraps accordingly, for a neater appearance." src="https://cdn-images-1.medium.com/max/1024/0*Y_82XyKOXyoROR1v" /><figcaption>The impossible text struggle is now solved.</figcaption></figure><p>We’ve made considerable additions and modifications to our components in our 2020 major release. We hope these changes streamline and improve your PatternFly experience! For more materials on our 2020 major release, check out our <a href="https://medium.com/patternfly/major-release-update-patternfly-4-june-2020-c90deec8f84b">major release update</a>.</p><figure><img alt="PatternFly’s branded divider, our logo centered between two lighter lines." src="https://cdn-images-1.medium.com/max/1024/1*XmM91Yc3Be0Kqc7FxtOwFw.png" /></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=7b93eb4ec02c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/component-changes-2020-major-release-update-7b93eb4ec02c">Component changes [2020 major release update]</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[Global changes [2020 major release update]]]></title>
            <link>https://medium.com/patternfly/global-changes-2020-major-release-update-a108a13486e9?source=rss-793b7ea7ccd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a108a13486e9</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[major-release]]></category>
            <category><![CDATA[ux-development]]></category>
            <dc:creator><![CDATA[Zack Allen]]></dc:creator>
            <pubDate>Mon, 22 Jun 2020 12:57:08 GMT</pubDate>
            <atom:updated>2020-08-17T16:02:44.839Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Miniature globe with a model airplane on top" src="https://cdn-images-1.medium.com/max/1024/0*VX6tdZeCheZGzztr" /><figcaption>Photo by <a href="https://unsplash.com/@frankvex?utm_source=medium&amp;utm_medium=referral">Frank Vessia</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><figure><img alt="PatternFly’s branded divider, our logo centered between two lighter lines." src="https://cdn-images-1.medium.com/max/1024/1*XmM91Yc3Be0Kqc7FxtOwFw.png" /></figure><p>For over a year now, we’ve just been itching to make global changes to PatternFly. What would a breaking change release be without major upgrades to fonts, colors, and viewports?</p><p>We’re stoked to elect Red Hat Text as our default font of choice everywhere. We also changed some of our colors to provide better contrast and made smaller viewports first-class citizens in the traditionally desktop-driven PatternFly world.</p><p>Let’s take a closer look at these changes.</p><h3>Font</h3><h4><a href="https://github.com/patternfly/patternfly/pull/2955">Make redhat font default, add opt-in for overpass</a> by <a href="http://github.com/mcoker">@mcoker</a></h4><p>PatternFly faced long-lasting browser compatibility issues with Overpass, so we made the decision to switch to the official Red Hat font family once it was completed. Red Hat’s brand team and type designer helped ensure this new font met all product and digital marketing needs. Not to mention, we think it looks nice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/0*uAcvU0jGUdr_QGSN" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*AulO1HSmq_MRdkBRghsfaA.png" /><figcaption>Overpass is our old font. We think Red Hat Text looks much better.</figcaption></figure><p>Not a fan? No problem. You can still opt out of this change and continue using Overpass instead.</p><h3>Colors</h3><p>With PatternFly’s sharp new font, we had to spruce up our color palettes as well. Not only do the new colors look better, but they also provide better contrast for accessibility. Who said functional design can’t look good too?</p><p>You can check out the new palettes on PatternFly’s revamped <a href="https://www.patternfly.org/v4/design-guidelines/styles/colors#color-palette">Colors page</a> (thanks to <a href="https://github.com/gdoyle1">@gdoyle1</a> for the design!).</p><h4><a href="https://github.com/patternfly/patternfly/pull/2906">Add new cyan, gold, green, and red colors, updated blue</a> by <a href="http://github.com/mcoker">@mcoker</a></h4><p>Alerts have a fresh look with PatternFly’s new colors. Now you can create alert messages that are easier to read and a bit nicer to look at.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/0*mfAHilSI2WKVlzjA" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*b9nUCH9dPLFIeCH3QSlhwA.png" /><figcaption>The previous alert colors were a bit dull. Thanks to @mceledon, PatternFly’s alerts are now modern and vibrant.</figcaption></figure><h4><a href="https://github.com/patternfly/patternfly/pull/2832">Update blue and cyan 600/700 color variables</a> by <a href="https://github.com/christiemolloy">@christiemolloy</a></h4><p>Some of PatternFly’s unused blue and cyan colors didn’t get updated in March 2019 for <a href="https://github.com/patternfly/patternfly/pull/1600">brand</a> purposes. In August 2019 we missed updating them again when <a href="https://github.com/patternfly/patternfly/pull/2107">adding a default alert variant.</a> Rather than retire these colors, we decided to update them to align nicely with the rest of the color palette.</p><figure><img alt="Blue and cyan color palette" src="https://cdn-images-1.medium.com/max/904/0*wSvpi4Hd8gPDpVnX" /><figcaption>The 6th and 7th columns are the updated blue and cyan colors. They’re rather dark, but potentially usable!</figcaption></figure><h4><a href="https://github.com/patternfly/patternfly/pull/2817">Update success-100, success-200, and green-500</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>To improve accessibility and consistency across PatternFly’s portfolio, we updated some of the green colors. Now you can build more unified interfaces that everyone — regardless of visual ability — can enjoy.</p><p>But that’s not all! This update beautifies things quite a bit. In the words of our designer <a href="https://github.com/mceledonia">@mceledonia</a>, “It just changes greens to better greens.”</p><p>Some of the components that use the new #3E8635 value are alert, form, form control, label, notification drawer, and progress.</p><figure><img alt="Before/after success green" src="https://cdn-images-1.medium.com/max/325/0*zKHG28mzD5ixr8LG" /><figcaption>The old success color didn’t provide sufficient contrast compared to the new lighter green.</figcaption></figure><h4><a href="https://github.com/patternfly/patternfly/pull/2818">Update black global and background global/component vars</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>Accessibility didn’t end with the green color updates. PatternFly’s primary and secondary text colors have been widely used to display text on white (` — pf-global — BackgroundColor — 100`) and light gray (` — pf-global — BackgroundColor — 200`) backgrounds, but the contrast ratios were not quite reaching the required <a href="https://www.w3.org/TR/WCAG20-TECHS/G18.html">W3C 4.5:1 contrast ratio</a> in some components, such as forms and empty states.</p><p>To achieve the ratio, we updated our secondary text color ` — pf-global — Color — 200` and replaced ` — pf-global — BackgroundColor — 150` and ` — pf-global — BackgroundColor — 300` with ` — pf-global — BackgroundColor — 200`. This way, you can build forms and empty states that more of your users can easily interact with.</p><figure><img alt="Old empty state" src="https://cdn-images-1.medium.com/max/1024/0*sHLM1Us3-kPa3Igx" /></figure><figure><img alt="New empty state" src="https://cdn-images-1.medium.com/max/1024/0*FOBE_SQwwPEB3Dqb" /><figcaption>The new empty state now meets color contrast standards.</figcaption></figure><h3>Mobile first</h3><p>Speaking of accessibility, PatternFly needed some work in the mobile-first design area. More and more enterprise applications are using smaller viewports, so it’s important that our patterns can easily support design for mobile screens.</p><p>We changed PatternFly’s CSS across the board and addressed a few components specifically to make sure they support the mobile experience. This way, mobile users can enjoy the same PatternFly-quality consistency and accessibility across viewports.</p><h4><a href="https://github.com/patternfly/patternfly/pull/2962">Hide vertical navigation at 1200px and update spacing</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>Perhaps the most impactful mobile-first change is that we now hide the vertical navigation at 1200px instead of 768px. At 768px the page’s main content area was very narrow and difficult to work with, causing tables, data lists, card layouts, and more to be cramped at that viewport.</p><figure><img alt="Old sidenav breakpoint" src="https://cdn-images-1.medium.com/max/772/0*XhuDxSpJ3DnJsp13" /><figcaption>The old sidenav breakpoint left data lists rather cramped.</figcaption></figure><p>Now that the vertical navigation is hidden at 1200px, page content layouts should flow smoothly above and below the navigation breakpoint at 1200px. Additionally, the chrome spacing is now more compact at 1200px, resulting in additional space for an application’s content at a greater viewport width.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*q7LkvaOz5elDgnFn" /><figcaption>The new breakpoint gives data lists plenty of space.</figcaption></figure><h4><a href="https://github.com/patternfly/patternfly/pull/2816">Change components to be mobile first</a> by <a href="https://github.com/christiemolloy">@christiemolloy</a></h4><p>We updated all components (except table grid modifiers) to have a mobile-first approach to the CSS. `min-width` is now used in all media queries, and we updated CSS variables so that a base variable always refers to the mobile-first design.</p><p>This change provides greater consistency in the way CSS is authored and makes the CSS easier to customize. It also creates a common approach for structuring component CSS and writing media queries.</p><h4><a href="https://github.com/patternfly/patternfly/pull/3091">Remove `pf-m-mobile/icon/user` and add `pf-m-hidden/visible` in PageHeaderTools</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>We removed a limited subset of CSS classes used to hide and show elements in the masthead and enabled a full suite of `.pf-m-hidden` and `.pf-m-visible` variables that can be used at specific breakpoints.</p><p>These tools give you full control over what elements are hidden or visible in the masthead at various device widths. They also align better with the tools that the React masthead previously offered to hide and show elements.</p><h4><a href="https://github.com/patternfly/patternfly/pull/2964">Allow wizard to be used in modal</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>You’ll now have an easier time using the wizard in the modal component, especially when designing for the mobile experience. We removed the “wizard modal” styling that existed previously and made the “in page” variation the default behavior. This changes the wizard into a normal block element that takes up the height and width of the element it’s placed in. Now there’s only a single variation instead of two, and you can simply place the wizard in the modal component.</p><h4><a href="https://github.com/patternfly/patternfly-react/pull/4140">Make wizard inPage</a> by <a href="https://github.com/nicolethoen">@nicoletheon</a></h4><p>Since our HTML/CSS supported placing the wizard in the modal component, we removed the `inPage` prop in React. But don’t worry — we have you covered if you would still like to use the modal variation of the component without writing additional code. You can just specify the `isOpen` prop, and the wizard will be placed in a modal for you.</p><h4><a href="https://github.com/patternfly/patternfly/pull/2866">Empty state: Center content and adjust secondary margin</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>Originally, PatternFly’s empty states often had a container with full width and some sort of layout to center the contents like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yJtsuU1SpqiVdXIx" /><figcaption>Who wants a small off-center empty state?</figcaption></figure><p>But did you really want your empty state off to the left side like that? We didn’t think so.</p><p>Now you don’t have to put in the work to widen and center your empty states — the component does it for you. You can even make it fill the height of its container by adding the class `.pf-m-full-height` or passing the `isFullHeight` prop in React (thanks to <a href="https://github.com/patternfly/patternfly-react/pull/4031">#4031</a> by <a href="https://github.com/seanforyou23">@seanforyou23</a>).</p><h4><a href="https://github.com/patternfly/patternfly/pull/3050">Update bottom pagination design</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>The bottom pagination is now specifically designed for mobile by sticking to the bottom of the viewport. To align with the React component naming, we renamed the bottom pagination from “footer” to “bottom.”</p><h4><a href="https://github.com/patternfly/patternfly/pull/2916">Breadcrumb: Add word-break, display link, and inline icon</a> by <a href="https://github.com/mcoker">@mcoker</a></h4><p>Breadcrumb trails are also a bit more mobile-friendly. We changed the structure and white space behavior in the breadcrumb component so that the items adapt better with different types of content. This is particularly useful in more narrow viewports where space is limited and breadcrumb items begin to stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/0*MqapD3Auj_E60HsK" /><figcaption>I think we have a text wrapping problem…</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/0*GT0jF-hQnNRC_pNe" /><figcaption>Problem solved!</figcaption></figure><h3>React</h3><h4><a href="https://github.com/patternfly/patternfly-react/pull/4076">Use tsc instead of babel for build</a> by <a href="https://github.com/redallen">@redallen</a></h4><p>Since PatternFly 4 started as a JavaScript library, we have been using <a href="https://www.npmjs.com/package/@babel/preset-react">Babel’s preset-react</a> along with a few other presets to build components. However, now that the <a href="https://github.com/patternfly/patternfly-react">patternfly-react</a> repo is 96.8% Typescript (and we already run the Typescript compiler to Typecheck code!) we replaced Babel’s output with the Typescript compiler’s output.</p><p>This speeds up builds and improves the quality of our transpiled code. Another added advantage is that the Typescript compiler supports incremental builds out of the box and does a much better job than our custom incremental build script, which had issues in the past.</p><p>Babel also injected helpers at the top of each file to do things like implement the spread operator. The Typescript compiler can take care of these by importing a common <a href="https://www.npmjs.com/package/tslib">tslib</a> package, which helps bundle sizes.</p><p>But it didn’t come for free. We lost support for UMD builds (consider using the <a href="https://unpkg.com/@patternfly/react-core@3/dist/umd/react-core.umd.js">react-core.umd.js</a> bundle) and for propTypes (consider using an editor with Typescript support).</p><h4><a href="https://github.com/patternfly/patternfly-react/pull/4144">Upgrade React peer dependency to ^16.8.0</a> by <a href="https://github.com/redallen">@redallen</a></h4><p>We upgraded our peer dependency from react@¹⁶.4.0 (2 years old) to react@¹⁶.8.0 (1 year old). This change allows our library code to use <a href="https://reactjs.org/docs/hooks-intro.html">React hooks</a> moving forward. Contributions can now use hooks, and some of our developers are already excitedly adding code with hooks. In the future, we may expose state management to you through hooks.</p><h3>Check back soon</h3><p>That’s all for global changes. Check back for more articles on the <a href="https://medium.com/patternfly/major-release-update-patternfly-4-june-2020-c90deec8f84b">update post</a>.</p><figure><img alt="PatternFly’s branded divider, our logo centered between two lighter lines." src="https://cdn-images-1.medium.com/max/1024/1*XmM91Yc3Be0Kqc7FxtOwFw.png" /></figure><p><em>Have a story of your own? Write with us! 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=a108a13486e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/global-changes-2020-major-release-update-a108a13486e9">Global changes [2020 major release update]</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[Major release update: PatternFly 4, June 2020]]></title>
            <link>https://medium.com/patternfly/major-release-update-patternfly-4-june-2020-c90deec8f84b?source=rss-793b7ea7ccd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c90deec8f84b</guid>
            <category><![CDATA[major-release]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-development]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Zack Allen]]></dc:creator>
            <pubDate>Mon, 22 Jun 2020 12:01:01 GMT</pubDate>
            <atom:updated>2020-08-17T20:03:55.958Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Partially opened laptop with multiple colors emerging from the screen" src="https://cdn-images-1.medium.com/max/1024/0*ZJEi7hDBHxU1SMDM" /><figcaption>Photo by <a href="https://unsplash.com/@tma?utm_source=medium&amp;utm_medium=referral">Tianyi Ma</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><figure><img alt="PatternFly’s branded divider, our logo centered between two lighter lines." src="https://cdn-images-1.medium.com/max/1024/1*XmM91Yc3Be0Kqc7FxtOwFw.png" /></figure><p>Hey, Flyers! As you might know, PatternFly has gone through some major changes. We’ve been busy squashing bugs and packing new features for the past 3 months, but our <a href="https://www.patternfly.org/v4/documentation/react/overview/upgrade-guide">upgrade</a> <a href="https://www.patternfly.org/v4/documentation/core/overview/upgrade-guide">guides</a> don’t quite cover everything we’ve improved or our reasons for changes in the first place. So we decided to create a series of articles that walk through it all.</p><p>Here’s a recap of the major changes. Keep an eye on this page as we release articles to cover each change in more detail.</p><ul><li><a href="https://medium.com/patternfly/global-changes-2020-major-release-update-a108a13486e9"><strong>Global changes</strong></a>: We’ve made global changes to our color palette, default font, and React packages. Components’ CSS is now mobile-first for a less cramped experience on smaller viewports.</li><li><a href="https://medium.com/patternfly/component-changes-2020-major-release-update-7b93eb4ec02c"><strong>Components</strong></a>: We’ve made numerous changes to our components, including redesigning the chip, alert, and tab components.</li><li><a href="https://medium.com/patternfly/cleanup-and-miscellaneous-changes-2020-major-release-update-2e4b88360709"><strong>Modifiers, spacers, and naming changes</strong></a>: We’ve taken the chance to clean up CSS variables and BEM elements in Core as well as renamed and cleaned up props in React.</li></ul><p>We hope this series not only better informs you of what changes are coming your way, but also gives you insight into our design and implementation processes. Enjoy!</p><figure><img alt="PatternFly’s branded divider, our logo centered between two lighter lines." src="https://cdn-images-1.medium.com/max/1024/1*XmM91Yc3Be0Kqc7FxtOwFw.png" /></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=c90deec8f84b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/major-release-update-patternfly-4-june-2020-c90deec8f84b">Major release update: PatternFly 4, June 2020</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[How MDX unified PatternFly’s documentation]]></title>
            <link>https://medium.com/patternfly/how-mdx-unified-patternflys-documentation-e68fb29411d6?source=rss-793b7ea7ccd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e68fb29411d6</guid>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Zack Allen]]></dc:creator>
            <pubDate>Fri, 14 Feb 2020 13:01:01 GMT</pubDate>
            <atom:updated>2020-02-14T13:01:01.385Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="3 stacked white binders full of paper" src="https://cdn-images-1.medium.com/max/1024/0*aAOzjkBlNQarj73t" /><figcaption>Photo by <a href="https://unsplash.com/@beatriz_perez?utm_source=medium&amp;utm_medium=referral">Beatriz Pérez Moya</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Documentation is never completely seamless. Everyone aims for helpful, efficient, and — of course — consistent content. But with so many content creators and file formats, stuff gets clunky.</p><p>At one time, we had that problem with PatternFly documentation. Our HTML/CSS community was writing documentation in a different format than our React community, and maintaining consistency was tricky when trying to create our combined documentation site, <a href="https://www.patternfly.org/v4/">patternfly.org</a>.</p><p>But we found a way. Here’s how we unified our documentation with MDX.</p><h3>Documentation problems</h3><p>PatternFly comes in two major offerings: <a href="https://www.npmjs.com/package/@patternfly/patternfly">HTML</a> and <a href="https://www.npmjs.com/package/@patternfly/react-core">React</a>. Until recently, these offerings used two completely different systems for their documentation and were hosted on two completely different websites. Merging the two systems together into patternfly.org was error-prone for a lot of reasons:</p><ul><li>Patternfly.org required copied code that would have to be updated whenever either documentation system changed.</li><li>Each build of patternfly.org would build our entire React library. This was because our documentation system expected to be able to import directly from source code rather than just downloading our own released build.</li><li>CSS issues always arose since we were importing our own styles in a variety of ways across multiple HTML and React versions.</li><li>Bug fixes or features made to our patternfly.org docs couldn’t easily be copied back to the HTML or React workspaces.</li></ul><p>Yikes!</p><p>Despite all these errors, keeping the documentation separate wasn’t an option. We needed to find some way to unify both the CSS and React documentation for a unified user experience complete with full text search.</p><h3>Finding common ground</h3><p>Luckily, both the CSS and React workspaces were using a common build system called Gatsby. CSS had a whole host of Markdown (MD) files, while React had Javascript (JSX) files. We had multiples of these files for each example.</p><figure><img alt="Two examples for PatternFly’s HTML badge component" src="https://cdn-images-1.medium.com/max/1024/0*pOpLcHSh0TDW820r" /><figcaption><em>Two examples for our </em><a href="https://www.patternfly.org/v4/documentation/core/components/badge"><em>HTML Badge component</em></a><em>. Their content used to be kept in </em><a href="https://github.com/patternfly/patternfly-next/tree/25f1fb9662d9c4d60931f7d30376cc41a8df1496/src/patternfly/components/Badge/examples"><em>Handlebars files</em></a><em>, a </em><a href="https://github.com/patternfly/patternfly-next/blob/25f1fb9662d9c4d60931f7d30376cc41a8df1496/src/patternfly/components/Badge/examples/index.js"><em>JSX file</em></a><em>, </em><a href="https://github.com/patternfly/patternfly-next/tree/25f1fb9662d9c4d60931f7d30376cc41a8df1496/src/patternfly/components/Badge/docs"><em>some MD files</em></a><em>, and a boilerplate JSX file.</em></figcaption></figure><figure><img alt="Two examples for PatternFly’s React Badge component" src="https://cdn-images-1.medium.com/max/1024/0*REJfEdBZ1OoSW_qb" /><figcaption><em>Two examples for our </em><a href="https://www.patternfly.org/v4/documentation/react/components/badge"><em>React Badge component</em></a><em>. Their content used to be kept in </em><a href="https://github.com/patternfly/patternfly-react/tree/710577890b72668a46b3e34037142c3b8b797cf6/packages/patternfly-4/react-core/src/components/Badge/examples"><em>two separate JSX files</em></a><em>, with an additional </em><a href="https://github.com/patternfly/patternfly-react/blob/710577890b72668a46b3e34037142c3b8b797cf6/packages/patternfly-4/react-core/src/components/Badge/Badge.docs.js"><em>boilerplate JSX file</em></a><em> to render the entire documentation page.</em></figcaption></figure><p>There’s quite a bit of overlap in the design of these docs! Yet they were stored in completely different formats. This is where MDX comes in: a new Javascript-enabled MD format.</p><p>By converting all of our docs to MDX files (where each MDX file maps to a page), we could easily load them into our site generator <a href="https://www.gatsbyjs.org/">Gatsby</a> to create consistent documentation pages. Here’s an example of an MDX file for HTML, which uses <a href="https://handlebarsjs.com/">Handlebars</a> (denoted by ```hbs code blocks).</p><pre> — -</pre><pre>title: Badge</pre><pre>section: components</pre><pre>cssPrefix: pf-c-badge</pre><pre> — -</pre><pre>## Examples</pre><pre>```hbs title=Read</pre><pre>{{#&gt; badge badge — modifier=”pf-m-read”}}</pre><pre>...</pre><pre>{{/badge}}</pre><pre>```</pre><pre>```hbs title=Unread</pre><pre>{{#&gt; badge badge — modifier=”pf-m-unread”}}</pre><pre>...</pre><pre>{{/badge}}</pre><pre>```</pre><pre>## Documentation</pre><pre>### Overview</pre><pre>Always add a modifier class. Never use the class `.pf-c-badge` on its own.</pre><pre>### Usage</pre><pre>| Class | Applied to | Outcome |</pre><pre>| — | — | — |</pre><pre>| `.pf-c-badge` | `&lt;span&gt;` | Initiates a badge. **Always use with a modifier class.** |</pre><pre>| `.pf-m-read` | `.pf-c-badge` | Applies read badge styling. |</pre><pre>| `.pf-m-unread` | `.pf-c-badge` | Applies unread badge styling. |</pre><p>Our docs were given a fresh new syntax that includes all the content rendered on the page thanks to <a href="https://github.com/patternfly/patternfly-next/pull/2242">this pull request</a>. No more digging around in multiple files to change content.</p><pre> — -</pre><pre>title: ‘Badge’</pre><pre>section: components</pre><pre>cssPrefix: ‘pf-c-badge’</pre><pre>typescript: true</pre><pre>propComponents: [‘Badge’]</pre><pre> — -</pre><pre>import { Badge } from ‘@patternfly/react-core’;</pre><pre>## Examples</pre><pre>```js title=Read</pre><pre>&lt;Badge&gt;<br>  Read badge<br>&lt;/Badge&gt;</pre><pre>```</pre><pre>```js title=Unread</pre><pre>&lt;Badge isUnread&gt;<br>  Unread badge<br>&lt;/Badge&gt;</pre><pre>```</pre><p><a href="https://github.com/patternfly/patternfly-react/pull/1753">React followed suit</a> with a similar format. Now the way we store docs is consistent, and each documentation page maps 1:1 with a MD file.</p><h3>No more copying code</h3><p>Even after converting the docs to a common format, the code that used to build our three documentation sites had to be stored in three separate repositories.</p><p>Luckily, another new technology, <a href="https://www.gatsbyjs.org/docs/themes/what-are-gatsby-themes/">Gatsby themes</a>, allowed for sharing configuration across projects. By moving shared code into a Gatsby theme, we can now make sweeping changes to our <a href="https://pf4.patternfly.org/">HTML</a> and <a href="https://patternfly-react.surge.sh/">React</a> developer workspaces, or our official documentation site <a href="https://www.patternfly.org/v4/">patternfly.org</a>. We can change any part of the site layout, how fullscreen pages are created, or how examples are rendered without having to copy code between repositories!</p><h3>Pitfalls</h3><p>Gatsby isn’t perfect, and neither is MDX. While turning our Gatsby projects into first-class documentation websites, we hit a few roadblocks with our developer workspace:</p><ul><li>MDX takes time to first be converted to Javascript (whereas before it started as Javascript), and Gatsby needs to handle a new file node for each MDX file.</li><li>The plugin we use for Gatsby and MDX called <a href="https://www.gatsbyjs.org/packages/gatsby-plugin-mdx/">gatsby-plugin-mdx</a> has a bug where changing the imports for an existing MDX file might require restarting the dev server.</li><li>Gatsby renders hundreds of more pages than it used to for a consistent documentation experience at the cost of 10–30 seconds more to start up.</li><li>Gatsby has to process and watch 10,000+ files to properly generate documentation, whereas before it needed to watch only around 1000.</li><li>We have our own system for how to render Handlebars templates tied to Gatsby lifecycle methods that don’t always hot-reload properly.</li></ul><p>As we make our documentation better, we face a few challenges like these. So this is a good area for future work.</p><h3>A better documentation experience</h3><p>Flyers can now expect unified content with a consistent look and feel across PatternFly’s HTML and React offerings. On top of that, things are more efficient. Combined with Gatsby themes, our documentation code is only written in one place, and it’s easier to maintain.</p><p>The end result? A better PatternFly documentation experience for the community.</p><p><em>Have a UX story of your own? </em><a href="https://docs.google.com/forms/d/e/1FAIpQLSenoFuNp_GoW9gDxA5s8uklvZuGcYRMpwTfiTc0nXaG3Z3tEQ/viewform?usp=sf_link"><em>Send your ideas our way</em></a><em>. More writers and fresh perspectives can only make PatternFly’s Medium publication stronger.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e68fb29411d6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/how-mdx-unified-patternflys-documentation-e68fb29411d6">How MDX unified PatternFly’s documentation</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>