<?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 Leslie Hinson on Medium]]></title>
        <description><![CDATA[Stories by Leslie Hinson on Medium]]></description>
        <link>https://medium.com/@iamlesliehinson?source=rss-9e6129d9083d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rursZD3qokqO9fkR.jpg</url>
            <title>Stories by Leslie Hinson on Medium</title>
            <link>https://medium.com/@iamlesliehinson?source=rss-9e6129d9083d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:44:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iamlesliehinson/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[A tale of teamwork and toolbars]]></title>
            <link>https://medium.com/patternfly/a-tale-of-teamwork-and-toolbars-2bc8bf1fe4a4?source=rss-9e6129d9083d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bc8bf1fe4a4</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[flyer-stories]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Leslie Hinson]]></dc:creator>
            <pubDate>Wed, 01 Apr 2020 16:08:33 GMT</pubDate>
            <atom:updated>2020-04-01T18:02:21.840Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Leslie Hinson and Matt Carrano</em></p><figure><img alt="Two designers collaborating using a whiteboard" src="https://cdn-images-1.medium.com/max/1024/0*YGiv9GHwXbB6jwfI" /><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><p>Building components for the PatternFly design system isn’t easy. More often than not, the first solution isn’t the perfect one, but it’s a starting point and a chance for us to collaborate with our users to figure out how to improve.</p><p>This is the story about the <a href="https://www.patternfly.org/v4/documentation/react/demos/toolbardemo">PatternFly toolbar</a> and how it evolved based on input from designers and developers from the Red Hat Cloud Services team.</p><h3>Defining the toolbar: It’s complicated</h3><p>So what exactly is a toolbar? Depends on who you ask! When we say “toolbar,” we’re referring to a set of elements that sit on top of a list or table. It provides access to common functions like filtering or performing actions against selected data.</p><p>But from a design perspective, it’s complicated. Applications can differ drastically, and there is not a specific set of functions that work for everyone and everything.</p><p>So we created a flexible system (packaged as the data toolbar component) that allows the user to construct any toolbar they want by combining various components.</p><p>The data toolbar component ensures proper spacing and handles responsive behaviors. Beyond that, PatternFly would not be opinionated about what went inside this toolbar.</p><h3>Toolbar rolls out, feedback rolls in</h3><p>The first version of the data toolbar was introduced to PatternFly, and the Red Hat Cloud Services team was one of the first to adopt. But, this version didn’t quite meet their needs. They proposed a number of enhancements.</p><p>First, they needed a way to select multiple items and give the user a clear understanding of what is selected. The result? <a href="https://www.patternfly.org/v4/documentation/react/demos/bulkselecttable">Bulk selection</a> was added as a new feature that could be used with the toolbar.</p><p>Second, the pagination component was taking up too much space, so we worked together to introduce <a href="https://www.patternfly.org/v4/documentation/react/components/pagination#compact">a compact version of the pagination component</a>. This allowed all the toolbar elements to fit on a single line.</p><p>What makes this type of feedback great? It has a broad impact, meaning more than one product or project benefits. This is important to PatternFly because we are always aiming to make components flexible and scalable.</p><h3>Using PatternFly as a foundation for product-specific needs</h3><p>At this point, the Cloud Services team had all the parts they needed. The PatternFly components can be arranged in any way based on what the user needs. The possibilities are endless. From a design system perspective, this is ideal because our system can be used by many.</p><p>But from the product suite perspective, this flexibility can be a challenge — especially when you need consistency across multiple applications. Here’s a Slack conversation between two of the designers that highlights why:</p><blockquote><strong>Kendra:<em> </em></strong>Why do all these apps have their own toolbar implementation that differs for no good reason? We have to lock some of the toolbar down, but offer some flexibility.</blockquote><blockquote><strong>Katie: </strong>I’m reworking the toolbar for my apps. Want to work together to try and create a standard?</blockquote><blockquote><strong>Kendra: </strong>Yes, 1000x yes.</blockquote><p>Katie and Kendra reviewed the toolbars across the set of applications and created a pattern based on PatternFly that was specific to their needs. Next, it was coded by product developers as a shared component for Cloud Services, making it easy to use across development teams.</p><blockquote>We had a solid foundation to work with (PatternFly toolbar), but we needed to pick some of the specific options that PatternFly offered, while letting others remain optional across apps.</blockquote><blockquote>— Kendra Marchant, Principal Interaction Designer at Red Hat</blockquote><p>In the end, the cloud services team used their toolbar across nine separate applications. This means that nine different teams were able to benefit from one collaborative effort to design and develop a toolbar that would work in that product suite. And this improves the user experience across these applications since it’s consistent across.</p><h3>The future is teamwork</h3><p>If PatternFly components could talk, they would reveal many stories like the toolbar component. PatternFly is built on teamwork, and we Flyers need this collaboration to push our designs forward. So the next time you think one of your designs is “done,” consider sharing with others first. Trust us: The end result will be that much better.</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=2bc8bf1fe4a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/a-tale-of-teamwork-and-toolbars-2bc8bf1fe4a4">A tale of teamwork and toolbars</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 2020 roadmap]]></title>
            <link>https://medium.com/patternfly/patternfly-2020-roadmap-a2a5464881c5?source=rss-9e6129d9083d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2a5464881c5</guid>
            <category><![CDATA[ux-developer]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[patternfly]]></category>
            <dc:creator><![CDATA[Leslie Hinson]]></dc:creator>
            <pubDate>Wed, 29 Jan 2020 13:01:01 GMT</pubDate>
            <atom:updated>2020-01-29T13:01:01.468Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Leslie Hinson, Jan Wright, Dana Gutride, Jessie Huff, and Michael Celedonia</em></p><figure><img alt="PatternFly logo" src="https://cdn-images-1.medium.com/max/700/1*R0iu6tYiy2002GrxSmU3Gg.png" /></figure><p>PatternFly has a lot of moving parts, and there is never a lack of things to do. Honestly, it’s easy to get wrapped up in all the demands of the present, but we wanted to press pause to reflect back on what’s been accomplished and look forward to what’s to come.</p><h3>Reflecting back on 2019</h3><p>In 2019, the PatternFly team released the first stable and production version of PatternFly 4. This gave development teams confidence to adopt the new system. Over the course of the year, adoption spiked from two known products to over forty known products actively using the newest version of PatternFly.</p><p>Comparing the NPM downloads from 2018 to 2019 for <a href="http://patternfly/react-core">PatternFly4-React</a>, you can see a 950% increase from 30k to over 315k. <a href="http://patternfly/patternfly">Patternfly4-Core</a> increased 525% from 40k to 250k in the same time frame.</p><p>And as a result of the hard work and efforts in 2019, the PatternFly system is more mature than ever with:</p><ul><li>Over 60 components and counting for building a front-end UI.</li><li>Over a dozen <a href="https://www.patternfly.org/v4/documentation/react/overview/training">training modules</a> to teach PatternFly implementation best practices.</li><li><a href="https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&amp;levels=aaa">WCAG 2.1</a> accessible components and guidance to meet accessibility standards.</li><li>Documentation to cover all versions of PatternFly, as well as <a href="https://www.patternfly.org/v4/documentation/react/overview/release-notes">release notes</a> to show exactly what was delivered.</li><li>A new <a href="https://sketch.cloud/s/7do0P">PatternFly Sketch symbol library</a> to expedite the PatternFly design process.</li></ul><h3>Looking forward into 2020</h3><p>Now 2020 is here, and we’re continuing to focus on new components and enhancements. Our main goal is to provide as much value as possible to the community, so we’re refining as well as expanding what PatternFly offers today.</p><h3>Refining PatternFly</h3><h4>Accessibility</h4><p>The PatternFly community believes in inclusive product experiences that everyone can use. That’s why accessibility is so important to us—it’s at the forefront of our design and development.</p><p>PatternFly aims to provide accessible components that meet level AA in the <a href="https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&amp;levels=aaa">Web Content Accessibility Guidelines 2.1</a>. The <a href="https://www.patternfly.org/v4/get-started/accessibility-guide">PatternFly Accessibility guide</a> offers guidance and examples to help create accessible products with PatternFly. We are leveraging both automated and manual testing through Axe tooling, integration tests, keyboard and screen reader testing, and more. PatternFly is continually improving our accessibility to provide the best possible experience. This year, our objective is to:</p><ul><li>Audit all the components and address any regressions.</li><li>Improve our test coverage.</li><li>Scale a11y expertise across the community by conducting workshops.</li></ul><h4>Visual design</h4><p>As components have been adopted, we’ve noted a number of visual improvements that can be made based on observation and community feedback. These changes aren’t a visual refresh, but they certainly move the components toward visual maturity. Some specifics include making better use of white space and tightening up drop shadows.</p><h4>The designer and developer experience</h4><p>PatternFly’s community is predominantly a mix of designers and developers — and we want to make their experience the best it can be. So we’re planning on continuing to improve the tools and resources that are available. Here’s what we have in mind for 2020:</p><ul><li>Evaluate and revamp documentation on the website.</li><li>Continue to build out starter projects.</li><li>Integrate with Red Hat Developer tooling to provide quick starts for PatternFly.</li><li>Keep the PatternFly Sketch library up to date.</li></ul><h3>Expanding PatternFly</h3><h4>Website use cases</h4><p>Since PatternFly started in 2014, the focus has been on web applications use cases. Therefore, design patterns have been specific to task-oriented workflows or views with a lot of data.</p><p>But this isn’t always enough for all teams.</p><p>So we’ll begin expanding PatternFly with components and documentation that address the requirements of website-specific use cases. The end result? A more robust PatternFly for teams that need a broader solution for apps, SaaS offerings, and/or websites.</p><h4>Web components</h4><p>Web components have matured over the last few years, so it’s a good time to revisit the idea of a framework-agnostic solution for PatternFly.</p><p>This year, the team is committed to investing time for research and development in the area. The goal is to define a web component architecture that uses the existing PatternFly styles (CSS/HTML) and achieve complete alignment with the PatternFly design system. This engineering investment is future looking, and the PatternFly React components will continue to be the supported component reference architecture for PatternFly interaction.</p><h3>Stay connected</h3><p>There’s so much to come, and all these improvements wouldn’t be possible without feedback from the community. We hope you continue to work with us so that we create a better PatternFly together. There are plenty of ways to stay connected:</p><ul><li><a href="https://twitter.com/patternfly_des?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">Follow us on Twitter.</a></li><li><a href="https://slack.patternfly.org/">Reach out on Slack.</a></li><li><a href="https://www.redhat.com/mailman/listinfo/patternfly">Join our mailing list</a>.</li><li><a href="https://medium.com/patternfly">Follow PatternFly’s Medium publication</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2a5464881c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/patternfly/patternfly-2020-roadmap-a2a5464881c5">PatternFly 2020 roadmap</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 football taught me about teamwork]]></title>
            <link>https://medium.com/@iamlesliehinson/what-football-taught-me-about-teamwork-974ac258f16c?source=rss-9e6129d9083d------2</link>
            <guid isPermaLink="false">https://medium.com/p/974ac258f16c</guid>
            <category><![CDATA[sports]]></category>
            <dc:creator><![CDATA[Leslie Hinson]]></dc:creator>
            <pubDate>Wed, 05 Jul 2017 20:22:50 GMT</pubDate>
            <atom:updated>2017-08-18T14:14:53.757Z</atom:updated>
            <content:encoded><![CDATA[<p>Teamwork was a consistent theme in my upbringing, largely in part, because my father is a football coach. I would like to share with you his key lessons about teamwork.</p><p>Lesson #1: Never hurt the team. This requires practicing three things:</p><ul><li>Try your best.</li><li>Be loyal.</li><li>Communicate.</li></ul><p>Lesson #2: Play the next play. This is not only a lesson that he teaches his “kids” but would also consider it a family motto. Play the next play means to never get too crushed about prior defeats, but also never get too cocky about prior wins. The most important play is always the next.</p><p>I wanted to share examples that helped to demonstrate these two lessons.</p><p>Jake was my dad’s quarterback at a small school in Texas. He was a fantastic athlete that shattered all sorts of records over the course of four seasons.</p><p>However, Jake did have a challenge with his speech in that he sometimes stuttered. This was exacerbated when he was nervous. The letter “s” was particularly troublesome.</p><p>Now, my dad implements a no huddle offense. As a quick technical explanation, this is just a way to speed up the game offensively, in hope of catching the defense off guard. The quarterback has the option to yell out a play call to his teammates as he sees weaknesses on the defense.</p><p>The need for speed and responsibility to call out the plays that, at times, started with the letter “s” proved difficult for Jake. So he had to come up with a solution.</p><p>At first it was profanity. He found if he could start by getting the s’s rolling that was helpful. He would say ”shit, shit, shit” and then 62 would come out more fluidly. He also start creating hand signals to help him to communicate to the team.</p><p>Upon reflecting on this story, my dad commented that it was amazing the improvement that Jake had made when comparing freshman year to senior year. By senior year, he no longer needed the profanity.</p><p>I love this story because it involves profanity, which I enjoy more than I should, but more importantly I think it touches on the three key points of lesson 1.</p><p><strong>Try your best: </strong>Jake never came crying to my dad to slow down the game. He found a solution that would address the problem. Practice also helped him to refine and improve his approach.</p><p><strong>Be loyal: </strong>I know I’ve spent a majority of the time talking about Jake, but one really big piece missing is all of his teammates. Jake had a challenge that required other team members to adjust. They had to work with their QB to learn additional signals, so that he was able to quickly get them the information they needed. Jake would have never been able to conquer this feat alone. It required the support and loyalty from his teammates.</p><p><strong>Communicate: </strong>The point about Jake’s communication is obvious and touched upon in my last point. Jake had to communicate with his team members to work together to make a solution that worked for them. However, Jake also communicated with my dad, his coach, to identify the struggles he was having. My dad once overheard, “Jake is the most foul mouthed player I’ve ever heard!” from someone passing by. Because of my dad’s understanding of the problem, this comment was met with a smile and an honest explanation.</p><p>Last but not least, lesson 2 is <strong>play the next play</strong>. I will apply this football motto to some UX design scenarios.</p><p>Let’s say, I’ve spent a ton of time and energy creating a design that, after sending to development, realize has gaps or doesn’t work as well as intended. Play the next play. It doesn’t matter the mistakes you’ve made. It only matters what you plan to do about it.</p><p>So, I spend time ensuring that all those gaps are filled. Design and development work together to create a solution that works. In the end, we receive high praise from management for the work completed. Again, play the next play. Take some time to pat yourself on the back, but this single victory shouldn’t be your defining one. Apply the lessons learned to the next task at hand.</p><p>While I try to subscribe to this approach in life and work, I’m certainly guilty of getting caught up in a moment at times, usually the bad ones. However, I can look back on various moments where someone in my life has jumped in to remind me to “play the next play”. It’s in their own words and usually sounds something more like “It’s ok, let’s work on this together to solve it”. So thank you to everyone that have given me these reminders and reassurance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=974ac258f16c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Community events help recruit new contributors]]></title>
            <link>https://medium.com/open-source-communities/community-events-help-recruit-new-contributors-178615409d91?source=rss-9e6129d9083d------2</link>
            <guid isPermaLink="false">https://medium.com/p/178615409d91</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[patternfly]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Leslie Hinson]]></dc:creator>
            <pubDate>Thu, 13 Apr 2017 23:07:59 GMT</pubDate>
            <atom:updated>2017-04-17T20:42:44.548Z</atom:updated>
            <content:encoded><![CDATA[<p>Seven months ago, the idea for a <a href="http://www.patternfly.org/">PatternFly</a> conference was introduced during a discussion about growing our community. At that point in time, a PatternFly conference was just a twinkle in our eyes.</p><p>PatternFly is sponsored by <a href="http://redhat.com/uxd">the Red Hat User Experience Design team</a>. In June, the 50+ members of the UXD team will be traveling from all over the world to Raleigh, North Carolina to take part in various team activities and workshops.</p><p>This provided the perfect opportunity to schedule <a href="http://www.patternfly.org/conference/2017/">The PatternFly Conference</a> as it would allow community members, many of which are designers and developers on the UXD team, to participate in the event.</p><p>But how do events help the community and why are they important for new contributors?</p><h3>Generate excitement</h3><p>Events can help to attract new contributors that may not have previously known about a project or how to get involved. While the initial promotion and the actual event bring the project recognition, the residual buzz generated by the attendees can have on-going benefits that outlive the event itself.</p><p><strong>TIPS</strong></p><ul><li>Submit talks to related events.</li><li>Plan your own event for your community.</li><li>Share what you’ve learned at an event by blogging and tweeting about your experience.</li><li>Send shout-outs or kudos to speakers or other attendees.</li></ul><h3>Make connections</h3><p>Events are a great place to meet someone new or get to know the person behind the avatar. Either way, having the opportunity to meet face to face, outside of the daily grind, can provoke interesting connections that can spawn into future opportunities.</p><p><strong>TIPS</strong></p><ul><li>Reach out to someone with less experience and offer your expertise and support on a subject.</li><li>Look for opportunities to learn from others and don’t be afraid to ask questions. People love to share about their experiences.</li></ul><h3>Get inspired</h3><p>Events are a place where thought leaders come together to share and promote ideas. Whether it’s learning about a new opportunity or discovering a new way to tackle a problem, you never know what will strike your fancy.</p><p><strong>TIPS</strong></p><ul><li>Take advantage of being surrounded by industry thought leaders to grow your own ideas.</li><li>Venture out and introduce yourself to others.</li></ul><p>The PatternFly Conference is on June 8 from 12–6PM. To learn more, register for the event, or submit a talk, visit <a href="http://www.patternfly.org/conference/2017.">http://www.patternfly.org/conference/2017.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=178615409d91" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-source-communities/community-events-help-recruit-new-contributors-178615409d91">Community events help recruit new contributors</a> was originally published in <a href="https://medium.com/open-source-communities">Open Source Communities</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>