<?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[NewsKit design system - Medium]]></title>
        <description><![CDATA[A blog about anything relating to the NewsKit design system by News UK. - Medium]]></description>
        <link>https://medium.com/newskit-design-system?source=rss----4febfdba244f---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>NewsKit design system - Medium</title>
            <link>https://medium.com/newskit-design-system?source=rss----4febfdba244f---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:51:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/newskit-design-system" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Speak to people: How a Nimble Feedback Process Helped Us Understand Our Users]]></title>
            <link>https://medium.com/newskit-design-system/speak-to-people-how-a-nimble-feedback-process-helped-us-understand-our-users-e5f7d02663d5?source=rss----4febfdba244f---4</link>
            <guid isPermaLink="false">https://medium.com/p/e5f7d02663d5</guid>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[interviews-and-insights]]></category>
            <dc:creator><![CDATA[Mike Messina]]></dc:creator>
            <pubDate>Sun, 05 Feb 2023 16:15:54 GMT</pubDate>
            <atom:updated>2023-02-14T17:55:30.834Z</atom:updated>
            <content:encoded><![CDATA[<h4>I spoke at <a href="https://www.meetup.com/design-systems-london-meetup/events/290158276/">Design Systems London #6</a>, about how understanding user concerns is super valuable in helping to shape the direction of a design system in a positive way for consumers.</h4><h4>Here is a video recording from the meetup:</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAJMI_VLj9oc&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAJMI_VLj9oc&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FAJMI_VLj9oc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9233003e1bffeb710884ce38c8b4f62d/href">https://medium.com/media/9233003e1bffeb710884ce38c8b4f62d/href</a></iframe><h4>If you’d prefer to read instead, here’s the transcript:</h4><figure><img alt="Speak to people: how a nimble feedback process helped us understand our users. By Mike Messina" src="https://cdn-images-1.medium.com/max/1024/1*ykWtHGlv-G6H0zJNImCGpg.png" /><figcaption><strong>Speak to people: How a Nimble Feedback Process Helped Us Understand Our Users — by Mike Messina</strong></figcaption></figure><p>I’m going to talk about the feedback-gathering journey we’ve been on at <a href="https://www.newskit.co.uk/">NewsKit</a>, and how feedback is used to inform decisions. How speaking to people has helped us to understand our users, and improve the design system for everyone that uses it.</p><p>…or</p><p>design system therapy</p><figure><img alt="design system therapy" src="https://cdn-images-1.medium.com/max/668/1*7QMUFr1jZVYnsyD0POmyLA.png" /><figcaption><strong>design system therapy</strong></figcaption></figure><h4>👋 Hi, I’m Mike.</h4><p>I live in North Somerset (just south of Bristol), and I’ve been in the NewsKit design system team for coming up on 3 years now.</p><p>My role includes producing specs for components, writing documentation, customer support, and also speaking to people about their experiences using the design system.</p><h4>But first — a bit of background on NewsKit</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YY-gk-fS5Ue9k9apf8Ex4Q.png" /><figcaption><strong>NewsKit is an open source design system built by News UK, for everyone</strong></figcaption></figure><p><a href="https://www.newskit.co.uk/">NewsKit</a> is an open-source multi-brand design system, created for unique media brands across NewsCorp. Active users include teams from News UK and Dow Jones in the US. There are approximately <a href="https://github.com/newscorp-ghfb/newskit/tree/main/src">60 themeable and accessible components available</a>, with more being added all the time.</p><p>The team here aims for high-quality in everything we produce, offering the best possible experience for the consumers of NewsKit. To support that goal, we’ve adapted several methods to gather feedback from active users, so we can understand their specific needs, and listen to their experiences, so we can look to improve the products we offer and the support we provide for everyone.</p><h4>Methods used to gather feedback from users</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fkJZik9ppaFYeoezt9PtFg.png" /><figcaption><strong>Example of the Qualtrics survey, and Slack message we send out to users</strong></figcaption></figure><p>A user survey using the Qualtrics platform is sent quarterly to individuals via our support Slack channels, to track user satisfaction, gauge confidence using NewsKit products, and share thoughts and ideas with the NewsKit team. The survey is kept anonymous so that people feel more comfortable sharing their honest feedback with us.</p><p>We try to keep the survey relatively short, with the average time for completion around 2 minutes. We highlight this in our messages so people know how much time is expected to complete it. We ask a range of questions designed to help us gain insight into how our users view the design system, pitched to help improve the NewsKit for everyone that uses it.</p><p>Some examples of things we found interesting to hear from the survey were that some designers find the handoff of designs to engineers to be a difficult process and that in general, the support available to consumers is well received.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JApl2_q_7aFp29wVnLiZpQ.png" /><figcaption><strong>Q. How likely is it that you would recommend the NewsKit design system to a colleague?</strong></figcaption></figure><p>After a couple of times sending out the survey, questions to gage the Net Promoter Score of the design system, and which department and job role the person filling out the survey, we moved to the top of the survey so that even if someone abandons the survey for some reason, we are at least capturing key information we want to know upfront.</p><p>We also tried reducing the number of questions asked to keep the time to complete shorter and made some questions conditional, which has yielded increased completed surveys and more data as a result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZFBYIzrLRN-KGe3BrU98Lg.png" /><figcaption><strong>Q. Choose 5 words that best describe the NewsKit design system</strong></figcaption></figure><p>This image shows the results of users&#39; responses when asked to choose 5 words to describe NewsKit, which is a more descriptive way for us to track user sentiment, rather than a number scale.</p><p>Tracking sentiment over time allows the team to identify problem areas that can be resolved. The design system constantly improves and evolves based on this feedback. On average, we get approximately ~10–15 completed surveys per quarter, from a range of NewsKit users.</p><h4><strong>All of that sounds great. Job done, right?</strong></h4><p>Obviously, the more people that complete it in full the better, as the data we could get back is genuinely really valuable for understanding user needs and perception. However, surveys can sometimes be a low priority for people to complete due to not having the time to do so, or simply not having anything to share in that particular format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K-9v0O20ervlRu4Ltylcew.png" /><figcaption><a href="https://www.google.com/search?gs_ssp=eJzj4tDP1TfIK8rLNmD04slPS8tMTlUoLkhMTgUAXdoH5g&amp;q=office+space&amp;rlz=1C5GCEM_enGB1012GB1013&amp;oq=office+spac&amp;aqs=chrome.1.0i355i433i512j46i433i512j69i57j0i457i512j0i402j69i64l3.3120j0j7&amp;sourceid=chrome&amp;ie=UTF-8"><strong>Office Space (1999)</strong></a></figcaption></figure><p>Over time, we found that people would on occasion start filling a survey out, and then abandon it at different points — which is nothing new when it comes to asking people to fill out forms generally — even with the best intentions to keep it as succinct as possible (I know I let out an internal groan at times when being confronted with yet another form I’ve been asked to fill out).</p><p>We do try to encourage people to fill out the survey as much as possible, but with the best will in the world, this doesn’t always work to capture more responses.</p><p>There is also more ad hoc feedback that different team members receive directly, in meetings, or over Slack, and this of course can also be very useful for informing decisions. If it’s in a forum like a Slack channel, then other people can benefit from the responses if more people can see it and track updates or resolutions.</p><p>However, ad hoc feedback can get lost quite easily in a continuous Slack feed, and if something is said in person that’s shared in good faith, the original meaning may be taken out of context — which can make the source of truth hard to ascertain, so it is wise to judge each case accordingly.</p><h4>Opportunities for improvements identified</h4><p>We reached a point where didn’t feel that we were getting enough information from just the survey and ad hoc feedback alone.</p><p>What we wanted was to gather information faster, and at a greater frequency as needed, so we could better keep up with the rapidly changing pace of the business and the needs of consumers of NewsKit.</p><p>We wanted to find out more about our user&#39;s concerns and ideas that relate to NewsKit users by reaching out to them in a more direct and proactive way.</p><p>Not relying on consumers to reach out to us, but instead going to them directly with questions, and listening to see if there is something ongoing that can be fed back to the team so more people are in the loop, and action is taken if needed to get address an issue quickly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6OPTilm45TU3UWio-6jshQ.png" /><figcaption><a href="https://www.designbetter.co/design-systems-handbook/putting-design-system-practice"><strong>Quote from Diana Mounter</strong></a><strong> — Head of Design at GitHub</strong></figcaption></figure><p>This is something I wholeheartedly agree with. This sort of approach can help reveal unknown things, that might only come up when having a more informal conversation with someone.</p><h4><strong>Consumer interviews = chats with a purpose</strong></h4><p>Feedback on the NewsKit product is not just encouraged but actively sought. We run regular consumer interview sessions targeting consumers across all disciplines. Any concerns or criticisms can be raised, and feedback and ideas are encouraged.</p><p>Consumer interviews are short, and relatively low effort (for both parties) — meaning we can schedule as many interviews as we want to quickly, and with anyone from across the business.</p><p>The format is a video call (mostly 1-to-1, or sometimes group sessions with an accompanying FigJam board) lasting around 10–15 mins each.</p><p>There is an effort to keep conversations casual, light, and disarming — giving an intro at the beginning of each session introducing myself, and anyone from the NewsKit team that joins, and what we are looking for from a participant.</p><p>They are conducted online over a video call intentionally so that there is a bit of distance for participants, and a more level playing field — so if someone wants to keep their camera off for any reason, they can and there’s no pressure to attend if they change their mind.</p><p>We make a note of anything key in an interview, slowing the conversation down at times when there is a detail important that is captured accurately — which might be a technical issue, or acronym — being sure to clarify specifics to mitigate the need to follow up later.</p><p>Everyone is different, and — they might also be in a rush, on a deadline, or — like me — have a dog wanting to get in on the call — these are the best meetings by far and makes me feel better about my dog sometimes popping up on camera for a hug, as he thinks I’m talking to him.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zOznEhivq_0C_CLU1-3C4g.png" /><figcaption><strong>Oh hi! I’m Mike’s dog, Cooper! 🐶</strong></figcaption></figure><p>We make it a point at the outset to participants that it’s a safe place for them to share honest feedback with the NewsKit team, and we are simply looking for any thoughts they have when using the design system, so we can improve what we offer to consumers — from components to documentation, or support offered, etc.</p><p>Feedback is triaged, and issues can be tracked on an open roadmap so consumers can see when they will be resolved.</p><p>This process helps to build strong relationships between teams and ensures consumers know any concerns are being heard.</p><p>All feedback can be useful, the challenge lies in spotting something worth expanding on, and pulling on a thread to try and get a clear picture.</p><h4><strong>So, have consumer interviews resulted in valuable feedback?</strong></h4><p>The short answer is yes, but it’s an ongoing process that continues to be refined and adapted as business and user needs change.</p><p>I’m not a user research specialist, I just enjoy talking to people and hearing what they have to say. These are some great resources that I recommend checking out, and have been useful guides on the subject:</p><p><strong>🔗 Links from this talk:</strong></p><ul><li><a href="https://rosenfeldmedia.com/books/interviewing-users/">Interviewing Users: How to Uncover Compelling Insights</a> by Steve Portigal | book</li><li><a href="https://zeroheight.com/blog/gathering-feedback-on-your/">Gathering feedback on your design system</a> by Kristen Singh | zeroheight blog</li><li><a href="https://medium.com/agileinsider/build-what-your-customers-want-3f92a56baefe">Build What Your Customers Want</a> by Kareem Mayan | Medium blog</li><li><a href="https://www.designbetter.co/design-systems-handbook/putting-design-system-practice">Design Systems Handbook</a> by Diana Mounter | designbetter.co</li></ul><h4>Some pointers</h4><p>From this experience, I have some things that may help point you in the right direction if you are considering starting to conduct your own consumer interviews.</p><p><strong>Invite other people from your team to get involved</strong></p><p>A single person being the feedback point person is a danger, as they may leave the business. It shouldn’t be left to just one person to gather and manage feedback, it makes sense to share the load around the team.</p><p><strong>Try out different methods and what works for your team</strong></p><p>Change up your methods — as much as you need to, and continue with what works.</p><p><strong>Something is better than nothing</strong></p><p>Don&#39;t worry if time doesn’t allow you to do as much as you planned.</p><p><strong>Focus on active users — and particularly those who share</strong></p><p>Hopefully, the people you choose to speak to are open and come prepared with lots of useful feedback, but it&#39;s worth acknowledging that might not always be the case. Know when to cut an interview short if you feel it isn’t going anywhere — the person might be grateful if they don’t have much to say.</p><p><strong>Keep track of who said what, categorising as you go</strong></p><p>Record all notes in a tool like Airtable so everything is in one place, and can always be referred back to.</p><p><strong>Share key insights with your team</strong></p><p>From surveys or interviews with your team — and the people who make the decisions. At the end of each quarter, there is a meeting where the team goes through the feedback gathered so context can be provided.</p><p><strong>Demonstrate you are listening to your users</strong></p><p>With actions and following up with them, tickets in the backlog, tangible changes with a new release, etc.</p><p><strong>Be sure to thank them for their time</strong></p><p>Show gratitude for people’s time, and that it is valuable — because it is!</p><h4><strong>Do whatever works for you and more importantly the people that consume your DS</strong></h4><p>Surveys or other methods for gathering feedback have their place for sure, and can be just as — or more valuable — it depends on what you find out and from who.</p><p>At the end of the day it doesn’t matter what you try — speaking to consumers and giving people a platform to do so is the important thing.</p><p>Focusing on the people actively using your design system in my experience is what will throw up the most useful insights for your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pxFhPhHlHBUHE-9l4fWHrA.png" /></figure><h4>💬 Get in touch</h4><ul><li><a href="https://www.linkedin.com/in/messinamike/">LinkedIn</a></li><li><a href="https://www.newskit.co.uk/">newskit.co.uk</a></li><li><a href="https://twitter.com/newskitdesign">@newskitdesign</a></li><li><a href="/service/mailto:newskitdesign-sm@news.co.uk">newskitdesign-sm@news.co.uk</a></li><li><a href="/service/mailto:newskit.engineering-sm@news.co.uk">newskit.engineering-sm@news.co.uk</a></li></ul><blockquote><strong><em>📖 </em></strong><a href="https://docs.google.com/presentation/d/1VnJz-irb1GJl1cf5zXmF78KVBL3M0Ftaa6svUsETFQQ/edit?usp=sharing"><strong><em>You can find the slides from my talk here ➡️</em></strong></a></blockquote><blockquote><em>Feel free to reuse and repurpose.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5f7d02663d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newskit-design-system/speak-to-people-how-a-nimble-feedback-process-helped-us-understand-our-users-e5f7d02663d5">Speak to people: How a Nimble Feedback Process Helped Us Understand Our Users</a> was originally published in <a href="https://medium.com/newskit-design-system">NewsKit design system</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How an audio player component tells the story of NewsKit Design System’s changing strategy]]></title>
            <link>https://medium.com/newskit-design-system/how-an-audio-player-component-tells-the-story-of-newskit-design-systems-changing-strategy-8dc99d37ed67?source=rss----4febfdba244f---4</link>
            <guid isPermaLink="false">https://medium.com/p/8dc99d37ed67</guid>
            <category><![CDATA[components]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Nick Dorman]]></dc:creator>
            <pubDate>Mon, 25 Jul 2022 14:23:38 GMT</pubDate>
            <atom:updated>2022-07-25T18:54:34.145Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Contrary to The Buggles’ declaration that <em>Video Killed the Radio Star</em> (the first song ever played on MTV back in 1981), radio is still going strong and is, in fact, having a resurgence. In 2020, <a href="https://www.rajar.co.uk/docs/news/RAJAR_DataRelease_InfographicQ12020.pdf">89% of UK adults</a> listened weekly to the radio. This was the same year The Times and Sunday Times launched <a href="https://www.thetimes.co.uk/radio?gclid=Cj0KCQjwn4qWBhCvARIsAFNAMiiGDratw-mCo4LFJeH7bghMMaDHS1h-N2dJ7l6dSaMsG37tgBbJw5QaAk2eEALw_wcB">Times Radio</a> — a move into digital radio after 200+ years of producing daily newspapers.</p><p>So it fell on us, the <a href="http://newskit.co.uk/">NewsKit design system team</a>, to deliver a radio player — a component that would be reusable across talkSPORT, Virgin Radio and others. This opportunity would allow us to test our early thinking on a real-world product while fulfilling the ambitions of the radio broadcasting teams to reduce reliance on third parties.</p><figure><img alt="The NewsKit radio player, used in Times Radio" src="https://cdn-images-1.medium.com/max/914/1*ldF9-C3aLIEdBLTaJUXsYg.png" /><figcaption>The NewsKit radio player was initially built for Times Radio</figcaption></figure><p>“It can’t be that hard,” we said, continuing with the naivety that was a feature of the early days of NewKit’s development. Needless to say, it was. Not least because it was one of the first components we’d built, and we didn’t have many of the constituent parts. A ‘live’ radio player, streaming audio content, requires a play/ pause button and not much else. But we also needed to provide a player for recorded content, which is more complex; You need to skip forward and back within a track and to the next or previous track. You need to be able to find a particular point in time with a seek bar. There was a lot of logic to be ironed out (such as how to handle the complexities around poor connections) and a lot of discussion about the level of flexibility we should provide.</p><p>Version one of the radio player took three months to build, delaying the Times Radio team. Once their engineers tried to integrate the component, it was clear we hadn’t provided enough flexibility. They found it hard to use, and minor customisation was complex. They ended up abandoning half of the radio player component, only integrating the audio player part.</p><p>It culminated in some intense soul-searching and a loss of morale across the design system team.</p><h3>Flexibility first</h3><p>But don’t worry, it didn’t last. Hours later, we regrouped and set out on a total refactor of everything we’d built, providing a much more flexible and robust theming system that you can read about in detail <a href="https://medium.com/newskit-design-system/evolution-of-theming-in-newskit-design-system-4a35bb83617">here</a>.</p><p>We also reconsidered where we draw the line on what the core system provides. In retrospect, there was little value in us building a radio player. A consumer could more easily cater for their requirements by using our audio player component and combining it with a card. This way, they had much more flexibility over layout options. We agreed that complex compositions of low-level components (what Brad Frost would refer to as ‘<a href="https://bradfrost.com/blog/post/atomic-web-design/#organisms">organisms</a>’) no longer had a place in the core system. Requirements from brands were too varied, and we couldn’t account for every eventuality. Our guidance should be restricted to clear best practices — not layout choices.</p><h3>Composable subcomponents</h3><p>This approach seemed to be doing the trick for a while, and our audio player was adopted across multiple brands. We had some feedback, fixed a few bugs and improved the accessibility of the component.</p><p>But there were still some layout problems. For example, Virgin Radio needed some additional space applied when using the audio player on small mobile screens. We hadn’t included a prop to allow this and fixed it as a bug. But this was symptomatic of a broader issue that also needed addressing (more on this shortly).</p><p>Our audio player component was built to cater for live radio and recorded content (e.g. podcasts), but as we increased adoption across brands with different needs, we started to receive more unanticipated requests: An inline audio player within a news article. A text-to-speech player in a navigation bar. A persistent player anchored to the bottom of a screen.</p><p>The audio player, while managing to fulfil the initial requirements, was <em>still</em> opinionated. A consumer could customise the component extensively (sizes of individual elements, spacing, themes etc.), but the individual elements could not be entirely repurposed for a new use case. We realised our prescriptive layout was never going to serve the needs of all our consumers. This was a harsh realisation after the team had put in so much time and effort to get to this point.</p><figure><img alt="A anatomical diagram of NewsKit’s audio player" src="https://cdn-images-1.medium.com/max/1024/1*CGxtL6ZSJvyuBYBgSEPrlQ.png" /><figcaption>The constituent parts of the audio player can be rearranged to cater for different use cases.</figcaption></figure><p>Taking on board feedback from our users and after some more reflection, we decided to break each element into a separate, exported component. This would free our consumers to compose audio players to meet all manner of edge cases and not be tied to a specific layout.</p><p>Instead of exporting compositions, we started to outline best practices in our documentation and provide scenarios in our Storybook for all common use cases. This allows product teams to access considered best practice solutions out of the box <em>and</em> have ultimate flexibility when needed. It’s the best of both worlds.</p><h3>Space-saving</h3><p>The multitude of minor tweaks to layouts that were required on the original audio player caused us to reconsider how we manage space. In the system’s early days, we took inspiration from <a href="https://medium.com/@nathanacurtis">Nathan Curtis</a>’s excellent post ‘<a href="https://medium.com/eightshapes-llc/space-in-design-systems-188bcbae0d62">Space in Design Systems</a>’. We introduced stack, inline and insets space tokens and applied them to components with overrides for users to configure their required space values.</p><p>It works, and had we only had to concern ourselves with the requirements of a single brand, would have continued to be a robust solution. But again, we couldn’t account for the unexpected requirements consumers would have around the layout of components. They wanted to be able to apply space <em>at will</em>.</p><p>So we recently introduced ‘<a href="https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Logical_Properties">logical props</a>’ to the components, enabling a more fluid approach to space. The addition of these new spacing properties allows users to achieve custom layouts without having to reach for additional layout components — improving ease of use and web performance on the front-end.</p><h3>Embracing evolution</h3><p>Like all design systems, NewsKit caters to specific requirements — this is a system optimised for media. As a multi-brand system, we’ve identified plenty that can be shared across media brands. But there is still a lot that’s distinct. The differences are the brands’ identities — what makes them unique, and our aim for the system is to standardise where practical but never erode the uniqueness of the brands we support.</p><p>Through trial, error and consumer feedback, we’ve gradually increased the system’s flexibility so consumers can more easily achieve their goals. But the edge cases and nuances we’ve come across also have a place in the system. We embrace the unexpected use cases as these can guide and inspire other system consumers, helping to open unexplored avenues and provide richer solutions. The benefits are great — the collaborative exploration and pushing of boundaries offer innovative solutions that can be shared, driving the system forward and allowing us to iterate and innovate with purpose.</p><p><em>Update: I’ve been made aware of another excellent blog post by </em><a href="https://medium.com/u/799c7c7840a"><em>Nathan Curtis</em></a><em> on the </em><a href="https://medium.com/eightshapes-llc/subcomponents-753ce9f6600a"><em>same topic</em></a><em>. It’s like it was meant to be. If that’s not validation, I don’t know what is.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8dc99d37ed67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newskit-design-system/how-an-audio-player-component-tells-the-story-of-newskit-design-systems-changing-strategy-8dc99d37ed67">How an audio player component tells the story of NewsKit Design System’s changing strategy</a> was originally published in <a href="https://medium.com/newskit-design-system">NewsKit design system</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Transition Presets to the NewsKit Design System]]></title>
            <link>https://medium.com/newskit-design-system/introducing-transition-presets-to-the-newskit-design-system-adafc43cbde3?source=rss----4febfdba244f---4</link>
            <guid isPermaLink="false">https://medium.com/p/adafc43cbde3</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[motion]]></category>
            <category><![CDATA[transitions]]></category>
            <category><![CDATA[presets]]></category>
            <dc:creator><![CDATA[Mike Messina]]></dc:creator>
            <pubDate>Thu, 17 Mar 2022 17:35:54 GMT</pubDate>
            <atom:updated>2022-03-21T08:11:49.392Z</atom:updated>
            <content:encoded><![CDATA[<p>by <a href="https://medium.com/@dimova.paola"><strong>Paola Dimova</strong></a>, &amp; <a href="https://medium.com/@mike-messina"><strong>Mike Messina</strong></a></p><p>Motion is an important aspect of a brand. Having consistent motion across a product will create a higher perception of quality for the end user. Motion can be used by brands to appeal to their specific audience. For example, a brand may want to reflect their personality with the motion they use in order to come across as friendly or fun, so fast, snappy motion could influence how they are perceived by their audience.</p><p>To support these varying requirements we have built a standardised and semantic approach for configuring motion into NewsKit.</p><p>In this article, we will go through different approaches and considerations from both design and engineering perspectives, discuss associated challenges, and the solution we have landed on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uE1w-GmGigj61boMNFOTRg.png" /><figcaption>The basics of motion in NewsKit Design System</figcaption></figure><h3>Some context</h3><p>Our original approach to motion in the NewsKit design system was to use our <a href="https://www.newskit.co.uk/theme/motion/">Motion foundation</a> tokens for <a href="https://www.newskit.co.uk/components/overview/">default components</a> that have an aspect of motion (e.g. <a href="https://www.newskit.co.uk/components/button/">Buttons</a>).</p><p>We applied a combination of the following Motion foundations to achieve basic transitions:</p><figure><img alt="Duration foundational tokens" src="https://cdn-images-1.medium.com/max/446/1*nk9TVYT028K_qkdDvOvOzw.gif" /><figcaption>Duration foundational tokens</figcaption></figure><figure><img alt="Timing foundational tokens" src="https://cdn-images-1.medium.com/max/634/1*CC5m2h-YMVGNx_mVusuo6Q.gif" /><figcaption>Timing foundational tokens</figcaption></figure><p>However, when considering additional components with complex motion requirements such as the <a href="https://www.newskit.co.uk/components/modal/">Modal</a> and <a href="https://www.newskit.co.uk/components/drawer/">Drawer</a>, we realised that this approach was too limiting and a more generic reusable approach was needed.</p><h3>Investigation</h3><h4><strong>Getting inspired</strong></h4><p>The first step in the research process was to see how other design systems handle motion, in order to see if we could learn anything or take inspiration from them. We won’t list all of them out here, but there are a few good examples worth mentioning that gave us food for thought:</p><h4>Design Systems</h4><p><strong>Material Design</strong></p><p>One of the most established and comprehensive design systems out there, it goes without saying really that <a href="https://material.io/design/motion/understanding-motion.html#principles">Material</a> was a good solid point of reference — in particular <a href="https://material.io/design/motion/customization.html#applying-customizations">how motion can be customised for different brands</a>. They also have a good <a href="https://material.io/resources/motion-design-kit">motion design kit</a> available.</p><p><strong>IBM Carbon</strong></p><p>The style of motion and how they are categorised in <a href="https://www.carbondesignsystem.com/guidelines/motion/overview/">Carbon</a> were interesting. They have two types of motion styles — productive motion, and expressive motion. This gave us another way to think about how we could structure what we do.</p><p><strong>Adobe Spectrum</strong></p><p>The <a href="https://spectrum.adobe.com/page/motion/">Spectrum</a> motion system has some similarities to our own foundations, and also a clear way of communicating the different effects that combine easing and duration to create animation effects.</p><h4>Tools &amp; Resources</h4><p><strong>Animista</strong></p><p><a href="https://animista.net/">Animista</a> is a useful resource for playing around with different CSS animations, which helped to break down and test certain aspects.</p><p><strong>Headless UI</strong></p><p><a href="https://headlessui.dev/react/menu#transitions">Headless UI</a> is a good reference of transition structure, and how they are applied to components that open/close.</p><p><strong>Motion Figma plugin</strong></p><p><a href="https://www.figma.com/community/plugin/889777319208467032/Motion">Motion</a> is a great animation plugin for Figma that uses a timeline to give more granular control and allows values or gifs to be exported easily.</p><h4>Mapping exercise</h4><p>The next step was to map out existing and potential future components to consider for NewsKit, in an attempt to identify what kind of motion would be required in general across the system, and where motion foundational tokens would need to be combined to form presets to be used in these instances.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fairtable.com%2Fembed%2FshrPxRIBz8EfuR7eK%2Ftbl1tmtEvXDoIXw1F&amp;display_name=Airtable&amp;url=https%3A%2F%2Fairtable.com%2FshrPxRIBz8EfuR7eK%2Ftbl1tmtEvXDoIXw1F&amp;image=https%3A%2F%2Fstatic.airtable.com%2Fimages%2Foembed%2Fairtable.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=airtable" width="800" height="533" frameborder="0" scrolling="no"><a href="https://medium.com/media/19aed34793e494b1e4d1cbc7813b1fab/href">https://medium.com/media/19aed34793e494b1e4d1cbc7813b1fab/href</a></iframe><p>This exercise helped to identify any common characteristics that would need to be reused in a lot of places (e.g. ‘color’ transition was very common). We quickly saw that the required categories of motion were distilled down to a handful of types, with some additional things to consider such as enter and exit motion for surface components that mount and unmount on a screen — like <a href="https://www.newskit.co.uk/components/modal/">Modals</a>, <a href="https://www.newskit.co.uk/components/drawer/">Drawers</a>, or <a href="https://www.newskit.co.uk/components/toast/">Toast</a> notifications.</p><h4>Scalability &amp; Customisation</h4><p>One of the main reasons for having a centralised set of presets that use our foundational motion tokens is that they can be adjusted as required and applied to NewsKit components easily. This level of control allows for brands to tailor motion to their brand. They can control different properties such as timing and curve (easing) at both an individual component level and also at a ‘theme’ level, so that motion applied to components could be controlled centrally and kept consistent.</p><h4>Applying motion in Figma</h4><p>Now that we had a clear idea of which aspects to focus on and what we wanted to allow brands to be able to control, we selected a handful of components to stress test. We wanted to visualise how default motion should look, how it could be adjusted, and also to export some values for a proof of concept to be built and tested in code.</p><p>We chose to use Figma, and its prototype capabilities, to stress test motion applied to components. This was for two main reasons: The first is that Figma has become our standard design tool across all of our product teams. The second reason is that Figma had recently released their smart animate features, so it gave the perfect excuse to try this out.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2Fl1gFmueJndksmc1YFXJ5Zk%2FNewsKit-Interactive-Component-Animations-%28Figma-BETA%29%3Fpage-id%3D119%253A2%26node-id%3D119%253A3%26viewport%3D414%252C48%252C1.1%26scaling%3Dscale-down-width%26starting-point-node-id%3D119%253A3&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2Fl1gFmueJndksmc1YFXJ5Zk%2FNewsKit-Interactive-Component-Animations-%28Figma-BETA%29%3Fpage-id%3D119%253A2%26node-id%3D119%253A3%26viewport%3D414%252C48%252C1.1%26scaling%3Dscale-down-width%26starting-point-node-id%3D119%253A3&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F2b9970a3-dec3-44b6-a6f7-5d23b63fc3ea%3Fheight%3D400%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/85ddcb25d3bbefe18cd83c2d1cbe7bcf/href">https://medium.com/media/85ddcb25d3bbefe18cd83c2d1cbe7bcf/href</a></iframe><p>Once we had some examples of motion applied to our components, we exported some values and examples to be used as references in the build.</p><h3>Engineering perspective</h3><p>The first step in the engineering research process was to carefully examine in detail how CSS animations and CSS transitions work. We made a comparison table between the two methods and noted the similarities and differences between them, which made it easier for us to evaluate the pros and cons of each approach, and how it would fit into our design system.</p><figure><img alt="A comparison table was used to weigh the pros and cons of each approach" src="https://cdn-images-1.medium.com/max/1024/1*TcTruWIUFMpCLMgTw4WLrA.png" /><figcaption>A comparison table was used to weigh the pros and cons of each approach</figcaption></figure><p>CSS transitions and animations are similar in many ways but distinct in terms of how complicated transitions can be, how the CSS code interacts with JavaScript, how loops work, and the methodology that triggers the animation to play. CSS transitions are generally best for simple from-to movements, while CSS animations are for a more complex series of movements.</p><p>The next step was to look at modern animation libraries such as <a href="https://react-spring.io/">react-spring</a>, <a href="https://www.framer.com/motion/">Framer Motion</a>, <a href="https://reactcommunity.org/react-transition-group/">React Transition Group</a>, <a href="https://www.npmjs.com/package/react-motion-animate">React-Motion</a>, among others.</p><p>Over the course of the analysis, we learned that we would need a third-party assisting library to add motion when mounting and unmounting a component in the DOM. Although it is possible to write custom hooks for this, we decided to entrust this functionality to React Transition Group.</p><p>We then looked at several libraries with predefined animations such as Animista and Animate.css. The concept of listed predefined animations fits perfectly into the NewsKit theme, where component styling is achieved mainly through predefined style presets. An already defined animation can be easily converted into a motion preset, so this looked like the right approach for us to take.</p><p>It should be noted that these libraries only use CSS animation.</p><p>Our investigation continued with the consideration of examples from other design systems. Due to the various specifics found in a design system, we saw many different techniques to apply motion — from pure CSS classes, animation strings, to specially crafted animation libraries like Ant’s TweenOne or dedicated for this purpose components such as MUI’s &lt;Fade /&gt;, &lt;Slide /&gt; or &lt;Grow /&gt;.</p><p>Our first interactive NewsKit components to incorporate motion are the Modal and the Drawer. The effects that we wanted to introduce in components were fairly simple and straightforward and could be achieved with both CSS Animations and CSS Transitions.</p><p>In the end, we ended up with mock examples of both of the approaches. This gave us a few insights:</p><ul><li>CSS Animations are easier to embed in the code</li><li>Defining animations with CSS Animations would be neat and more consistent than transitions. But we would have to repeat CSS styles across the code base, something that we’d really like to avoid.</li><li>On the other side of the coin, CSS Transitions are easier to sync with the style presets in the theme.</li></ul><h3>Animations or Transitions — or Both?</h3><p>On one hand, we have more basic animations that allow for movement — sliding, growing, rotating. On the other, we have transitions — such as a background colour change on user interaction. We examined all of our components with an aspect of motion (e.g. buttons), with different types of animations, and came to the conclusion that we wanted small, simple actions in our components and the ability to combine them into more complex effects. The CSS Transitions approach seemed to be the most appropriate method for NewsKit motion.</p><h4>Code examples</h4><p>The NewsKit theme works mostly with preset settings — style, typography, space. It was logical to organise the transitions in presets as well, in order to maintain consistency.</p><p>Here’s what a super simple preset looks like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/38b37d6f1ebb4c1e1447104cbb8c0859/href">https://medium.com/media/38b37d6f1ebb4c1e1447104cbb8c0859/href</a></iframe><p>This backgroundColorChange transition preset consists of a single base object - representing the initial transition state. It is where the transition itself is defined - specifying the name of the CSS property the transition effect is for and the length of time the transition effect takes to complete. All state sub-objects support CSS styles as well.</p><p>As mentioned earlier, our components use style presets to get their look and feel. Here’s what a simple predefined style looks like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d4f8d3d2e0396d271a78932ccbcbdbac/href">https://medium.com/media/d4f8d3d2e0396d271a78932ccbcbdbac/href</a></iframe><p>What is distinctive about this object is that it consists of different states — basic, hover, selected, active, valid, which correspond to different client interactions with the system at a given time. Each state can describe its own styles. These states are transition activators as well.</p><p>Using utility functions, the outcome is CSS, which defines a transition between initial and end state.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/83145fe1728509634f4a94680deb8508/href">https://medium.com/media/83145fe1728509634f4a94680deb8508/href</a></iframe><p>Of course, we can combine several transitions presets in one motion animation:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/57bc3a5bfab2fd0625bbe9c4acda75fc/href">https://medium.com/media/57bc3a5bfab2fd0625bbe9c4acda75fc/href</a></iframe><p>We can also override predefined values in single or multiple transition presets. We can do this both on a theme level by amending the style preset for all components that use it or for a single component:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/01f0ab1dc3b86b7d2a9387180cc43806/href">https://medium.com/media/01f0ab1dc3b86b7d2a9387180cc43806/href</a></iframe><p>Nowadays, responsive web pages are common, so we have implemented the ability for users to set different transition presets according to specific screen sizes:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/21b2776138d847d2f383d851883d4a3a/href">https://medium.com/media/21b2776138d847d2f383d851883d4a3a/href</a></iframe><h3>What we’ve learned &amp; next steps</h3><p>We are continuing to add to our <a href="https://www.newskit.co.uk/theme/presets/transition-presets/">transition presets</a>, and applying default transitions to our components. Now that we have transition presets in the hands of our consumers we can use their requirements and feedback to help us to inform the next evolution of motion in the NewsKit design system.</p><h3>Resources</h3><ul><li><a href="https://www.newskit.co.uk/theme/motion/">Motion foundations in the NewsKit Design System</a></li><li><a href="https://www.newskit.co.uk/theme/presets/transition-presets/">Transition Presets in the NewsKit Design System</a></li><li><a href="https://www.newskit.co.uk/theme/presets/style-presets/#states">Style Presets as they relate to states in the NewsKit Design System</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adafc43cbde3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newskit-design-system/introducing-transition-presets-to-the-newskit-design-system-adafc43cbde3">Introducing Transition Presets to the NewsKit Design System</a> was originally published in <a href="https://medium.com/newskit-design-system">NewsKit design system</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evolution of design system KPIs]]></title>
            <link>https://medium.com/newskit-design-system/evolution-of-design-system-kpis-490f87097473?source=rss----4febfdba244f---4</link>
            <guid isPermaLink="false">https://medium.com/p/490f87097473</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Ellis Capon]]></dc:creator>
            <pubDate>Mon, 29 Nov 2021 10:45:19 GMT</pubDate>
            <atom:updated>2021-11-29T11:43:28.924Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The evolution of KPIs for the NewsKit Design System</strong></p><h3>Introduction</h3><p>Roughly two years old now, the NewsKit Design System is maturing into an industry leader, with adoption increasing sprint by sprint and the system itself being put to the test, increasing the robustness of NewsKit daily.</p><p>If you’d like to read more about the journey we’ve been on, you can do so<a href="https://medium.com/newskit-design-system/introducing-newskit-a-themeable-design-system-for-unique-media-brands-6a2d770e2bbb"> here</a>.</p><p>In this article I’d like to talk you through how the KPIs for the NewsKit design system have evolved over time and, crucially, how what we may have found useful two years ago may no longer be of significance when it comes to tracking our progress. It seems to be an age-old problem for design system teams and, whilst I’m not going to sit here and tell you we’ve cracked it, what I share with you may go some way to helping you demonstrate value to your stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nQ602Oohx-Rl83Zi" /><figcaption>NewsKit mission</figcaption></figure><h3>Why do we need KPIs?</h3><p>“<em>Product key performance indicators (KPIs) are metrics that measure your product’s performance. They help you understand if the product is meeting its business goals and if the product strategy is working. Without KPIs, you end up guessing how your product is performing</em>” — Klipfolio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PyUyZsa2YKfp2w4DUc_Gow.png" /></figure><p>In product development, you need to have a robust set of KPIs available in order to be able to measure the success of what you’re doing — otherwise, you could end up wasting vast amounts of resource moving in the wrong direction. For many technology teams, this is how you demonstrate value to the business and is vital to the success and longevity of your product.</p><p>Setting KPIs and demonstrating business value for a customer-facing product is one thing. However, things get a lot more complicated when you’re attempting to do this for a design system. Your consumers are engineers and designers, and KPIs for the pace and/or efficiency of product development is often much harder to extract than bottom-line revenue or growth metrics</p><p>(if you’re not familiar with design systems, you can get up to speed<a href="https://uxdesign.cc/everything-you-need-to-know-about-design-systems-54b109851969?gi=33a5940604e"> here</a>).</p><p>Within NewsKit, we have adapted our KPIs over time depending on where we are in the product development lifecycle and hope to be capable of demonstrating the value of our design system more accurately as time passes.</p><h3>The beginning</h3><h4>Number of components</h4><p>It’s July 2019. A huge technology team restructure at News UK has just taken place and the NewsKit design system team is born. In the early months of NewsKit, we were aware that no one would be picking up any of our components or our theming system whilst still in their infancy, and it’s for that reason we decided to focus our energy on designing and developing a foundational set of the core components needed to build a typical news website.</p><p>So, to set viable targets for our team, we decided to set the <em>number of components </em>as our primary KPI. A simple measure for the number of supported components made available for product teams to consume and use. But did this demonstrate the true value of our systems? Probably not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZhKqB8HH7Gdl7YNHbbYuNA.png" /><figcaption>NewsKit product development lifecycle</figcaption></figure><h3>Year 2</h3><h4>NPS</h4><p>July 2020. The world is wrestling with Covid-19. Everyone has been ordered to work from home. Our team has now grown and the first product to be built using the NewsKit design system in Times Radio has been launched.</p><p>Once we actually had users for our design system (a big milestone in itself), we needed to understand more about their experience of working with it — warts and all. As an industry-wide measure of customer satisfaction, we decided to use Net Promoter Score (NPS). We began by sending out quarterly surveys, aimed at capturing a whole host of feedback on client perception of the design system i.e. the reality of using NewsKit — with the aim to then action that feedback.</p><p>As part of the survey, we ask the user how likely they would be to recommend NewsKit to a colleague. Depending on what score they answer, this will determine whether they are a promoter, detractor, or a passive user.</p><p>Averaging these responses gives us the NPS score for NewsKit.</p><p>For the first time we were able to track the users’ perception of NewsKit and analyse how this went up or down each quarter, mapping our NewsKit releases to an uptick or downtick in NPS.</p><p>Overall, we have found NPS to be a really valuable KPI to track as we’re now transparently surfacing our users’ sentiment towards the product we are building. As more products adopt NewsKit, this KPI becomes an even more accurate and important tool for demonstrating business value. It helps us cut through the noise all over the place — from prioritising within our tech debt stream to defining our client support strategy</p><p><strong>Year 2 KPIs:</strong></p><ul><li>Number of components</li><li>NPS</li></ul><h3>This year</h3><h4>Pace of development</h4><p>July 2021 brought us into a new (Australian) financial year. Wireless, News UK’s audio arm, launches a brand new Virgin Radio website on their new Wireless Web Platform, built entirely using the NewsKit design system and its sister products, NewsKit API and NewsKit Render.</p><p>This was a big moment for the team and the company as a whole, and represents a further step closer to a future-facing vision of News UK’s architecture, if and when all brands have migrated over to this new technology stack. The core principle is that the Wireless Web Platform will underpin all future radio/tv station website builds, significantly increasing the pace of product development by utilising NewsKit’s innovative theming system to skin the sites to their respective brand colours and styles.</p><p>(To learn more about theming, see this blog by our principal engineer,<a href="https://medium.com/u/27d7f8c88b18"> James Spencer</a>)</p><p>Time and money spent on product development will no doubt become a critical KPI for us in order to demonstrate the true business value of the capabilities we’re delivering. The challenge here lies in our ability to set realistic targets.</p><p>Telling the story <strong>post</strong> product delivery is achievable, presuming the products in question are broadly in the same ballpark in terms of complexity and/or capability:</p><ul><li>Product A took X period of time to build and cost X</li><li>Product B took X% less time to build and saved X cost when compared with Product A</li></ul><p>Setting ourselves viable targets, though, for any given financial-year increment, is very tough. It presumes that we can always compare apples with apples i.e. that all products are similar enough to extrapolate an annual cost/efficiency saving. We can’t.</p><p>It also presumes that entire products will always be built using NewsKit. They won’t. As mentioned further through this article, some products will only adopt NewsKit incrementally, which further dilutes our ability to measure true value and/or set robust targets.</p><p>That said, the more products that are delivered using NewsKit — either in their entirety, or piecemeal — the more ammunition we’ll have to inform realistic annual objectives.</p><h4>Contribution</h4><p>We believe a design system should never be owned solely by the team developing it. Whilst the NewsKit product team are the ‘governors’ of the design system, we aim to become a project that every user, across both design and engineering, has a stake in — and encourage contribution at every opportunity.</p><p>In July we began to capture the number of items contributed to the design system. Component contribution in code is the north star but this can be a lengthy and challenging process, so we include other forms of contribution too, such as;</p><ul><li>Patterns</li><li>Component specifications in design</li><li>Component contribution in Figma</li><li>Bug fixes in code</li></ul><p>These incremental calls for contribution are helping to establish ownership (and enthusiasm) amongst engineers and designers across the wider technology team.</p><h4>Performance</h4><p>Some brands using NewsKit are incrementally adopting, rather than taking on wholesale platform rebuilds, and replacing key components on their pages only when there’s demonstrable business value on the table — with a high-level goal to have a fully NewsKit-supported site over time.</p><p><a href="https://medium.com/u/d17e82adb7e1">Cristiano Rastelli</a> (formerly of Badoo) wrote a brilliant piece on measuring the impact of a design system. You can find it<a href="https://didoo.medium.com/measuring-the-impact-of-a-design-system-7f925af090f7"> here</a>.</p><p>Taking what we learned from<a href="https://medium.com/u/d17e82adb7e1"> Cristiano</a>, we are looking into how we can track the adoption of our components over time, in each of our brands’ codebases. News UK is a large organisation with multiple brands. Each brand has its own (or sometimes multiple) codebases, which makes extracting an accurate figure as a percentage quite challenging. However, only tracking the adoption of the design system still does not prove out any business value. We need to dig a little deeper for this…</p><p>All of our NewsKit components and subsystems are designed and built to be as performant, accessible, and flexible as possible. From the live products that have used NewsKit and the various proof of concepts carried out using our components, we know that <a href="https://web.dev/vitals/">Google Core Web Vitals</a> metrics are improved when our components are used over other, legacy components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/0*JD0Fl508hZm5h-Th" /><figcaption>Google Core Web Vitals</figcaption></figure><p>We are working towards capturing a KPI that will allow us to correlate the adoption of NewsKit as a % against the Core Web Vitals scores. We would expect to see an improvement in the CWV scores as the adoption of NewsKit increases, however, we are only at the beginning of the journey to get to the bottom of this metric, so expect to see another blog post in the not too distant future.</p><h3>Summary</h3><p>Whilst I don’t have a definitive answer to the age-old question of which KPIs are the right ones to track, I hope I’ve highlighted some of the areas that could demonstrate the value of a design system. We will no doubt update these KPIs again in the coming months, but that’s ok. As the system evolves, so does our means of tracking our progress. What’s most important is ensuring our focus is always on providing value to our consumers.</p><h3>KPIs moving forward:</h3><ul><li><strong>Number of component</strong>s — Useful to see the growth of a design system</li><li><strong>The pace of development</strong> (£ saved) — A real diamond for proving out business value. This is what your CFO will care about</li><li><strong>NPS</strong> — How likely are our consumers to recommend the design system to a peer?</li><li><strong>Contributions</strong> — A good way to measure the buy-in to the design system from other product, design, or engineering teams</li><li><strong>Adoption % in code </strong>— Nice to see how well adopted the system is</li><li><strong>Adoption vs Core Web Vital score</strong> — A useful way to prove the value of the system through tangible numbers</li></ul><p><em>Thanks to </em><a href="https://medium.com/u/b8733d2d4d5a"><em>Joe Cooke</em></a><em> &amp; </em><a href="https://medium.com/u/b79fbc3e4d01"><em>Nick Dorman</em></a><em> for their collaboration on this piece.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=490f87097473" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newskit-design-system/evolution-of-design-system-kpis-490f87097473">Evolution of design system KPIs</a> was originally published in <a href="https://medium.com/newskit-design-system">NewsKit design system</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we improved our design system delivery]]></title>
            <link>https://medium.com/newskit-design-system/how-we-improved-our-design-system-delivery-f0306a385a6d?source=rss----4febfdba244f---4</link>
            <guid isPermaLink="false">https://medium.com/p/f0306a385a6d</guid>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Gill Bennet]]></dc:creator>
            <pubDate>Thu, 07 Oct 2021 08:59:38 GMT</pubDate>
            <atom:updated>2021-10-07T08:59:38.462Z</atom:updated>
            <content:encoded><![CDATA[<p>Our journey on understanding how to build out a Design System has had many twists and turns. Through each learning, we have continuously reviewed, refined and streamlined how we work to provide components as quickly as possible while increasing the quality. If you’re not up to speed with what a design system is you can read one of our previous blog posts<a href="https://medium.com/newskit-design-system/introducing-newskit-a-themeable-design-system-for-unique-media-brands-6a2d770e2bbb"> here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ppExadtsky0m-8tCx-vy8A.png" /></figure><p>We have learned a lot; from understanding the complexities in getting our<a href="https://medium.com/newskit-design-system/evolution-of-theming-in-newskit-design-system-4a35bb83617"> theming</a> and foundations right and implementing<a href="https://medium.com/newskit-design-system/cross-browser-visual-testing-picking-the-right-tool-for-newskit-design-systems-20531018c0"> cross-browser visual testing</a>, to our approach to building out components.</p><p><strong>Early Engagement</strong></p><p>As a multi-brand design system, our components need to be flexible enough for any one of our brands to use them for multiple use cases. To achieve this, we ensure that all of the brands are involved in the specification stage, giving us more confidence that we’re future-proofing our components as more brands adopt NewsKit.</p><p>Even if a brand has no immediate plans to use the component, we still engage with them early on so that we have recorded their input and ensured they are bought-in to the approach if they decide to integrate later on.</p><p>Despite this, we still need to ensure we’re delivering progressive enhancements. Initially, we tried to deliver a fully-fledged component in the first release, but we changed our thinking and now deliver what is needed first, even when we have a good idea of where a component should end up. Through trial and error, we now have a greater understanding of how to define what the MVP is for any new component we work on.</p><p>We also have a better understanding of which components need to be prioritised. In the early days, we took the approach of auditing the most common components and building those first. However, through close collaboration with the product teams that we support, we instead respond to what’s required based on their roadmaps. This allows us to deliver direct business value as we build out the system.</p><p>Engaging early has been a key learning for our Design and Engineering teams. For designers, engaging our Engineering teams in the specification stage of the design process and reviewing ongoing work before writing up the tickets significantly reduced back and forth; streamlining our development process.</p><p><strong>The Right Tools</strong></p><p>The <a href="https://www.youtube.com/watch?v=UwEbKtia_HE">introduction of Figma</a> across our design teams improved collaboration, communication and workflow efficiencies. As well as consolidating multiple tools, we found<a href="https://www.figma.com/blog/how-news-uk-developed-a-multi-brand-design-system/"> Figma</a> provided us with the flexibility to manage the UI libraries from a single location, cutting down maintenance overhead.</p><p>Figma’s Jira integration gives our engineers easy access to designs from the ticket they are working on and we’ve developed our own plugin, in-house, to manage different themes across our brands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3x6ACnQox9D8CrFaUbg5Q.png" /></figure><p><strong>Similar ways of working</strong></p><p>From the moment we came together as a team, we all agreed that our designers and engineers would need to work closely together. By bringing the Design team into the Scrum framework with our engineers, our collaboration and communication constantly flow. The design team have also introduced design ceremonies throughout the week to gain feedback on their work regularly.</p><p>Another area we focused on was improving our release process. When we started our journey, we had a lot to learn to understand the complexities of a Design System for multiple brands. Due to the number of breaking changes in our early releases we were reluctant to release regularly. However, over time we have become more stable, allowing brands to upgrade to the latest version of NewsKit more easily. The design team mirrors the code release cycle, releasing design changes to the UI Kit every two weeks.</p><p><strong>Standardisation</strong></p><p>Our initial time in design and engineering for delivering components took longer than we first hoped. However, with more experience in the team and better collaboration with our brands, we have seen the overall delivery time of our components reduce.</p><p>Over time, we have built up our codebase and domain experience within the team. Areas such as accessibility and SEO now require far less time spent upfront on investigations to understand the approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QYoTReznj8bDGqXTBNDVzw.png" /><figcaption>Checklist created by the Design team to ensure that nothing is missed and we meet the standards we have set for ourselves.</figcaption></figure><p>Checklists also now play a vital role in ensuring we meet the standards we have set and provide a starting point for anyone picking up a new piece of work.</p><p>To ensure we are not approaching our graphs and designs ad hoc in our UI library, our designers work through a checklist. Including having engineering design peer review, saving time on both sides going back and forth. Our engineers also use a checklist in their PR process which they constantly review and update when needed.</p><p>We have also improved through re-using other components. The Tab and Menu items we were able to base off the Button component. By doing so, it meant we didn’t have to build these again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FoxW5wke4UJgGB6L5Ci1VA.png" /><figcaption>We have become quicker in the design and build process with each component we have worked on</figcaption></figure><p>Initially, we didn’t have any of the foundational components, but as we have progressed we have been able to reuse simple components to build more complex ones. For example, we can take our button off the shelf when building a component like the drawer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*ay7t8u2WeZfWIm73F2KqaQ.png" /><figcaption>Subsequent delivery of closely related components is significantly quicker</figcaption></figure><p>Another example of this is the banner, toast, and inline message. The banner was one of the first components built that required common functionality. By the time we built out the toast and inline message components our turnaround time significantly reduced.</p><p><strong>Feedback</strong></p><p>Finally, continuous feedback has been important to ensure that we have the right approach. The more frequently we gain feedback, the easier it becomes to resolve any issues promptly.</p><p>As brands started to pick up NewsKit we introduced regular drop-in sessions with our brands in the design and engineering teams. That two-way feedback has helped us to understand any issues they have using our Design System. We have also used those sessions to demonstrate any new components in the pipeline, allowing any feedback from our users before we release the initial MVP version.</p><p>There are other ways we have tracked feedback. We have introduced surveys with the users of the design system, setting product KPIs and<a href="https://didoo.medium.com/measuring-the-impact-of-a-design-system-7f925af090f7"> NPS scores</a>. We now set targets around components built, adoption and reviewing regular feedback from surveys — enabling us to ensure Newskit is as user friendly as possible.</p><p>We have put significant effort into understanding and improving our processes. The results are already showing in delivering key projects across NewsUK and NewsCorp. With more brands onboarding to use our design system, we are continuing to review areas such as:</p><ul><li>How documentation fits into our overall delivery process.</li><li>Providing support without impacting the delivery of new components or enhancements.</li><li>Balancing delivery across multiple brands</li><li>Which KPIs are the right ones for us to demonstrate business value to our stakeholders.</li></ul><p>If you would like to see what’s coming up, our high-level roadmap can be found on the<a href="https://www.newskit.co.uk/about/roadmap/"> NewsKit Website</a>.</p><p>#designsystems #delivery #figma #react #publishing</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0306a385a6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newskit-design-system/how-we-improved-our-design-system-delivery-f0306a385a6d">How we improved our design system delivery</a> was originally published in <a href="https://medium.com/newskit-design-system">NewsKit design system</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Resilience Testing in NewsKit API]]></title>
            <link>https://medium.com/newskit-design-system/resilience-testing-in-newskit-api-cefe61ac9c17?source=rss----4febfdba244f---4</link>
            <guid isPermaLink="false">https://medium.com/p/cefe61ac9c17</guid>
            <category><![CDATA[chaos-engineering]]></category>
            <category><![CDATA[resilience-engineering]]></category>
            <category><![CDATA[resilience-testing]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Stoyan Z Yanev]]></dc:creator>
            <pubDate>Fri, 23 Apr 2021 15:44:40 GMT</pubDate>
            <atom:updated>2021-04-23T15:44:40.744Z</atom:updated>
            <content:encoded><![CDATA[<p>NewsKit API is the News UK data service that consolidates different data sources across the business and provides a single federated GraphQL endpoint to the applications powered by NewsKit Components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eV9OjY-Vd6tICwx-L211_Q.png" /></figure><p>The idea of NewsKit API is based on <a href="https://en.wikipedia.org/wiki/Federated_architecture">federated architecture</a> and <a href="https://www.apollographql.com/docs/apollo-server/federation/introduction/">Apollo Federation</a>. It brings the benefits of federated architecture and the flexibility of GraphQL together.</p><p>The architecture for the NewsKit API is laid out below. Each data source is accessed via a GraphQL wrapper or a service. The difference between a service and a wrapper is that a wrapper acts as a transformer between two data entities ( models ), while a service is responsible for serving the data directly.</p><p>This distinction doesn’t bear any significance to our clients and we use them interchangeably in this document. These services/wrappers translate data into well-defined GraphQL schemas which are federated by the NewsKit API Gateway.</p><p>The Gateway’s responsibility is solely to federate the individual services. The services in NewsKit API will resolve the Graph requests passed down from the Gateway respectively and return the data to clients in a coherent GraphQL schema. The approach also enables NewsKit API to future-proof the data contract against changes in the underpinning data sources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*17doIPU81ABn_Aj_r_h4Rw.png" /></figure><h3>Why did we build NewsKit API?</h3><p>We built a Design System to make our front-end composable. In order to provide a seamless development experience for the engineering teams in other business units, we also needed a composable back-end.</p><p>GraphQL solves the challenge for dynamic data fetching from front-end applications. Clients can now get all of the required data to construct complex UI components via a single query.</p><p>Introducing GraphQL into an established tech stack is no mean feat. Over the years, some of our existing products have grown organically, both in complexity and size. In order to construct a single web page, one team had to make over 20 requests to different REST API endpoints. Worse, only a tiny portion of the fetched data is used, with most of it discarded. This is inefficient and expensive.</p><p>We took an incremental approach for our GraphQL adoption, through GraphQL federation and the idea behind <a href="https://en.wikipedia.org/wiki/Federated_architecture">Federated architecture</a> (FA). This enabled us to iteratively expand our Graph schema to make the API usable immediately, delivering value to the business. The discoverability of the data in GraphQL schema reduces the risk of different teams building the same things in isolation.</p><h3>What is Resilience Testing ?</h3><p>Software testing, in general, involves many different techniques and methodologies to test every aspect of the software regarding functionality, performance, and bugs.</p><p>Resilience is the ability of a system to minimise the impact of failure. Failure happens, all the time. Resilient systems take progressive steps to allow the most useful parts of the system to still serve their purpose.</p><p>The tests aim is not only to provide information regarding failures of the system — resilience, but also to improve performance and observability.</p><p>When we consider resilience we mainly focus on the availability — are the services available during the stress testing, is there any downtime in our service etc. We have to analyse the results and decide if our infrastructure reacts as we hoped/planned, and what would be the potential improvements.</p><p>When we talk about performance — this is where we think about stressing resources — spikes in : CPU, Memory and other resource constraints.</p><p>And there is also the benefits of observability — the least talked about benefit, but it is really important one. Being able to check if we have the right alarms in place, are they triggered when they were supposed to. If those alarms are in place, is the team ready to react to them effectively.</p><p>The product that we are building is a GraphQL federation (Newskit API) deployed on EKS. Due to the complex infrastructure and the high traffic, we rely on a thorough testing strategy, which includes resilience tests,</p><h3>What is AWS Fault Injection Simulator ?</h3><p>According to AWS:</p><blockquote><em>Fault Injection Simulator is a fully managed chaos engineering service that makes it easier for teams to discover an application’s weaknesses at scale in order to improve performance, observability, and resiliency. Chaos engineering is the process of stressing an application in testing or production environments by creating disruptive events, such as server outages or API throttling, observing how the system responds, and implementing improvements.</em></blockquote><blockquote><em>With Fault Injection Simulator, teams can quickly set up experiments using pre-built templates that generate the desired disruptions, such as server latency or database error. Fault Injection Simulator provides the controls and guardrails that teams need to run experiments in production, such as automatically rolling back or stopping the experiment if specific conditions are met. With a few clicks in the console, teams can run complex scenarios with common distributed system failures happening in parallel or building sequentially over time, enabling them to create the real world conditions necessary to find hidden weaknesses.</em></blockquote><h3>Benefits of using AWS FIS</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9jrCBfOlB1ymgLYbTQHz0A.png" /><figcaption>(Diagram from AWS re:Invent)</figcaption></figure><ul><li>Improve application performance, resiliency, and observability</li><li>Validate how your application performs on AWS — Amazon EC2, Amazon EKS, Amazon ECS, and Amazon RDS</li><li>Safeguard chaos experiments — AWS Fault Injection Simulator provides the fine-grained controls that teams need to define the specific conditions under which they want to stop an experiment or roll back to the pre-experiment state.</li><li>A fast and easy way to get started with chaos engineering — AWS Fault Injection Simulator provides prebuilt templates that enable teams to set up and run high quality experiments in minutes. Fault Injection Simulator structures the chaos engineering process so that teams can quickly run chaos engineering experiments by following the step-by-step process in the console and selecting from a predefined list of actions.</li><li>Get superior insights by generating real-world failure conditions</li><li>Integrated security model — AWS Fault Injection Simulator is integrated with AWS Identity and Access Management (IAM) so that you can control which users and resources have permission to access and run Fault Injection Simulator experiments, and which resources and services can be affected.</li><li>Visibility throughout an experiment — AWS Fault Injection Simulator provides visibility throughout every stage of an experiment via the console and APIs. As an experiment is running you can observe what actions have executed. After an experiment has completed you can see details on what actions were run, if stop conditions were triggered, how metrics compared to your expected steady state, and more.</li></ul><p>The conditions during the tests will be real — it is not false metrics or manipulated envs. The described events in the templates will really be happening. Example — Memory utilisation tests — the memory described will actually be used during the testing, and not just have false alerts.</p><h3>Use Cases:</h3><ul><li>Periodic Game Days — This is a completely hands-on opportunity for technical professionals to explore AWS services, architecture patterns, best practices, and group cooperation.</li><li>Continuous Delivery Pipeline Integration — You can integrate AWS Fault Injection Simulator into your continuous delivery pipeline. This will enable you to repeatedly test the impact of fault actions as part of your software delivery process.</li></ul><h3>In Practice what experiments can we run ?</h3><p>It is a flexible framework that can be used for pretty much every type of chaos engineering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KsjOdVLd-KAASLDOSLRp-w.png" /><figcaption>(Diagram from AWS re:Invent)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HFzIbsSIZJgBFJl-krDbEQ.png" /><figcaption>(Diagram from AWS re:Invent)</figcaption></figure><p>There are 3 CORE Components of each experiment:</p><ul><li><strong>Action</strong> — the fault injection, data being lost from DB, container resources being constraint, certain services being unavailable, latency problems etc. We can combine several simple actions into some much more complicated scenarios (several performance degrading events at once). We can build or timeline of events (in sequel or parallel) and test scenarios which are very hard to mimic in real life.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rHRMJVrOPCH-ZtFcOQEYOg.png" /><figcaption>(Diagram from AWS re:Invent)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEed171_x-Oof9gGdfB5rA.png" /><figcaption>(Diagram from AWS re:Invent)</figcaption></figure><ul><li><strong>Targets — </strong>A target is one or more AWS resources on which an action is performed during an experiment. You define targets when you create an experiment template. You can use the same target for multiple actions in your experiment template. To identify your target resources, you can specify resource IDs, filters and tags.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBicuoXr7O_Gdb8SVL3KfA.png" /><figcaption>(Diagram from AWS re:Invent)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wvT0X7pN-5Yzcysn4wk8jA.png" /><figcaption>(Diagram from AWS re:Invent)</figcaption></figure><ul><li><strong>Stop Condition — </strong>stop condition is a mechanism to stop an experiment if it reaches a threshold that you define as a Amazon CloudWatch alarm. If a stop condition is triggered during an experiment, AWS FIS stops the experiment, and in some cases rolls back the state of the target resources.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lbf-rQpJ6pOD77SLq9RM4g.png" /><figcaption>(Diagram from AWS re:Invent)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iwhHUesyH0K8JEFIzCUXcA.png" /><figcaption>(Diagram from AWS re:Invent)</figcaption></figure><p>Other alternatives for chaos engineering include the open-source Chaos Monkey, and the paid offerings from Gremlin, but after a thorough research we decided to choose AWS FIS. The main goal is to test Kubernetes clusters, deployed using AWS EKS.</p><p>In Newskit API we plan to test our resilience by terminating EKS node groups, throttling our API and many custom actions. By running experiments on a regular basis that simulate outage, we want to able to identify any systemic weaknesses early and fix them.</p><p>We are still working on our implementation, hence why there is an example template provided, and not a particular implementation. We will share our progress and potential findings in the near future.</p><h3>Useful Resources</h3><ul><li><a href="https://www.youtube.com/watch?v=yoNeMLj3CHc">AWS Fault Injection Simulator: Fully managed chaos engineering service</a></li><li><a href="https://www.youtube.com/watch?v=0UXKrEXSDIE">AWS Fault Injection Simulator</a></li><li><a href="https://www.youtube.com/watch?v=sQZhSL9NkQM">AWS Fault Injection Simulator</a></li><li><a href="https://www.youtube.com/watch?v=OlobVYPkxgg">Chaos Engineering</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cefe61ac9c17" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newskit-design-system/resilience-testing-in-newskit-api-cefe61ac9c17">Resilience Testing in NewsKit API</a> was originally published in <a href="https://medium.com/newskit-design-system">NewsKit design system</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cross browser visual testing — Picking the right tool for NewsKit design systems]]></title>
            <link>https://medium.com/newskit-design-system/cross-browser-visual-testing-picking-the-right-tool-for-newskit-design-systems-20531018c0?source=rss----4febfdba244f---4</link>
            <guid isPermaLink="false">https://medium.com/p/20531018c0</guid>
            <category><![CDATA[visual-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[visual-testing-tools]]></category>
            <dc:creator><![CDATA[Denitsa Kulezich]]></dc:creator>
            <pubDate>Fri, 26 Feb 2021 15:42:25 GMT</pubDate>
            <atom:updated>2021-02-26T15:47:56.373Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cross browser visual testing — Picking the right tool for NewsKit design system</h3><p>In a world where most IT products are fighting for a bigger audience, it’s becoming increasingly important to have a visually pleasing and smooth user experience.</p><p>Here at NewsKit, one of our products is a Design System which enables different NewsUK titles to build better products, faster. One of our goals from a quality perspective is to deliver multiple components that render correctly. But how can that be achieved, especially in a reality where we have a variety of devices, browsers, resolutions and capabilities, across various platforms? It looks like an impossible mission. But is it, though?</p><h3>Where do we start?</h3><p>Let’s face it, we need to do cross browser testing. We can hear some of you saying: “Not another layer of tests, no!” and completely understand this frustration. When you have a complex software solution, with many integrations, putting more effort into creating yet another test suite is a real pain. You start thinking of the time and costs you need to invest in creating the tests, then the maintenance, also upskilling the testers and the developers — there are a lot of considerations.</p><p>And what is cross-browser testing? It’s a non-functional type of testing, designed to verify how your website and/or web components will work on different browsers and devices with different capabilities. The focus is not on the functional side (you should test that with the functional end-to-end tests) but, instead, on how your software is rendered on these platforms.</p><figure><img alt="Cross Browser Testing diagram" src="https://cdn-images-1.medium.com/max/1024/0*aYbxjlC80xbYDXYH" /><figcaption>Cross browser testing lets us test our application in various browsers and devices</figcaption></figure><p>So, if you need to support Chrome, IE, Mozilla Firefox, Safari browsers and latest iOS versions, as well as Android that runs on different devices, you will need to execute your visual testing suite on these platforms to ensure that your software runs flawlessly. As you can imagine, doing that manually will take a lot of time and testing effort, and you will need to do it every time there is a visual change. So, to reduce effort it’s a good idea to automate your cross-browser tests.</p><h3>Here come the visual testing tools!</h3><p>Visual testing tools assist us in our testing activities. They help us tremendously in our ambition to achieve a slick user interface that works smoothly on a large majority of devices and browsers. They also save a huge amount of time investment in testing.</p><p>But, then again, there are so many options here. A quick online search about visual testing tools will lead you to a number of results — which is a good thing, as you have the opportunity to pick the right one for you. But how do you pick the right tool? Choosing the “trial and error” path will likely waste time and effort.</p><h3>How to pick the right one?</h3><p>In our opinion this is the hardest part. You don’t want to pick a tool that you will have to change in six months when you realise it’s not suitable for your product.</p><p>So, what should you consider when picking a visual testing tool?</p><ol><li>What problems with the visual aspects of your product(s) are you facing?</li><li>Keep in mind the technologies you are using.</li><li>Who’s going to maintain the visual tests?</li><li>And don’t forget the budget and time constraints</li></ol><p>Analysing all of the above will help you get oriented in the vast universe of cross browser visual testing tools.</p><p>And to help you with your journey, we have prepared a short list of tools that we evaluated based on our requirements and their advantages and disadvantages.</p><h3>Applitools</h3><p>Unlike other visual tools from our list, <a href="https://applitools.com/">Applitools</a> uses AI comparison algorithms so images are compared in such a way a human would. By using different comparison algorithms (exact, strict, content and layout comparison) you have different options to compare images, reduce false positives and cater for different scenarios, such as dynamic data or animations.</p><p>They support various versions of most browsers and device emulators via <a href="https://applitools.com/docs/topics/sdk/using-the-visual-grid.html">Visual Grid</a>. Another nice functionality is that they integrate easily with most of the functional testing frameworks. You name it; Selenium, Cypress, Appium, WebdriverIO, Espresso, XCUITest, even Storybook!. They also have Github and integrations to different Continuous Integration (CI) tools.</p><p>Test maintenance is also significantly reduced. If there are any tests that are failing due to new code changes, Applitools provide a dashboard to accept and reject the comparisons easily.</p><figure><img alt="Applitools Dashboard" src="https://cdn-images-1.medium.com/max/1024/0*gpTziI8heaSJOiyu" /><figcaption>Applitools Dashboard</figcaption></figure><p>In terms of cost, Applitools is the most expensive out of all the tools we evaluated so consider your budget constraints and discuss with your entire team.</p><h3>Happo</h3><p>If you are searching for a nice, cheaper visual tool, <a href="https://happo.io/">Happo</a> could be the right choice.</p><p>Happo uses pixel-by-pixel comparison, however you have an option to tune it, so it doesn’t strictly compare the snapshots to your baseline. Again, they support the latest versions of most browsers and emulators. Their speed of image comparison is impressive — they use bitmap hashing and compare the hashes. They also have Github and CI integration and plugins to support Storybook and Cypress directly. Alternatively, you can use their javascript library directly. Their dashboard provides an easy way to view all the snapshots and any visual differences.</p><figure><img alt="Happo Dashboard" src="https://cdn-images-1.medium.com/max/1024/0*8BILhsa0bhf4bZ3-" /><figcaption>Happo Dashboard</figcaption></figure><p>On the downside they only have support for pixel-by-pixel comparison and, even if you tune it, you still may have false positives. They have, however, written some tips on <a href="https://docs.happo.io/docs/spurious-diffs">how to avoid spurious differences on your images</a> which you might find useful.</p><h3>Percy</h3><p>Another nice option, especially if you don’t necessarily need to support a lot of browsers, is <a href="http://percy.io/">Percy</a>. Recently acquired by <a href="https://www.browserstack.com/">Browserstack</a>, Percy supports only the latest versions of Chrome and Firefox, so far.</p><p>It is a pixel-by-pixel comparison tool which has 1px tolerance when comparing your snapshots with the baseline. Similar to Applitools and Happo, they also have Github and CI integrations.</p><p>Sadly, Percy is missing some features, which at least in our case was important. They only have support for two browsers so far — Chrome and Firefox. Hopefully, they will add more browsers to the list. They are also missing the option to change the comparison tolerance. In addition, we found out that if you have some big resources like audio files on your page (as we do) Percy cannot process the snapshots and your build will fail. Last, but not least, sometimes they don’t have enough time to take the full snapshot of a page or component, causing false positives — and they don’t provide you with delays out of the box, so you need to implement those explicitly.</p><figure><img alt="Percy dashboard, showing visual differences" src="https://cdn-images-1.medium.com/max/1024/0*yyer_vt7GMHqDeZB" /><figcaption>Percy Dashboard showing visual differences</figcaption></figure><h3>Chromatic</h3><p>If the focus of your visual testing effort will be Storybook only, this may be a suitable tool for you.</p><p><a href="https://www.chromatic.com/">Chromatic</a> is another pixel-by-pixel tool and you have the option to change the pixel tolerance. They also have Github and CI integrations and support Chrome, Firefox and IE 11.</p><p>On the downside they only work for Storybook, which in our case wasn’t enough. They don’t support devices and browsers other than those listed above.</p><h3>Screener</h3><p>Yet another pixel-by-pixel comparison tool, <a href="https://screener.io/">Screener</a>, now acquired by <a href="https://saucelabs.com/">Saucelabs</a>, supports a variety of browsers, has Github and CI integrations and can also integrate with Storybook and Selenium frameworks.</p><p>On the other hand, they currently do not have support for Cypress which is important for us. But if you use Selenium this may be the tool for you.</p><h3>Loki</h3><p><a href="https://loki.js.org/">Loki</a> is a very lightweight pixel-by-pixel comparison tool for your Storybook components which also gives you the option to change the pixel tolerance. And it’s free!</p><p>Our enthusiasm about this tool was waned by the fact that Loki supports only Chrome and is only specific for Storybook. You would also need an external tool to do the snapshot comparisons.</p><h3>Comparison Table</h3><figure><img alt="Table showing the comparison between the reviewed visual tools" src="https://cdn-images-1.medium.com/max/1024/0*AgwNDXlNlf1j4hw8" /><figcaption>Table showing the comparison between the reviewed visual tools</figcaption></figure><h3>So, what now?</h3><p>Take some time to analyse your requirements and plan the testing effort around it. It’s very important to not forget your budget and deadlines, as they are the cornerstones of every project.</p><p>Finally, we hope that our visual testing tool findings will help you take an informed decision around your tooling, and ease your job in the process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20531018c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newskit-design-system/cross-browser-visual-testing-picking-the-right-tool-for-newskit-design-systems-20531018c0">Cross browser visual testing — Picking the right tool for NewsKit design systems</a> was originally published in <a href="https://medium.com/newskit-design-system">NewsKit design system</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evolution of theming in NewsKit design system]]></title>
            <link>https://medium.com/newskit-design-system/evolution-of-theming-in-newskit-design-system-4a35bb83617?source=rss----4febfdba244f---4</link>
            <guid isPermaLink="false">https://medium.com/p/4a35bb83617</guid>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[emotionjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[theming]]></category>
            <dc:creator><![CDATA[James Spencer]]></dc:creator>
            <pubDate>Fri, 05 Feb 2021 13:49:30 GMT</pubDate>
            <atom:updated>2021-08-12T15:52:46.980Z</atom:updated>
            <content:encoded><![CDATA[<p>Since we started NewsKit we’ve learnt a thing or two about theming, in this article we will go through different approaches, discuss associated trade-offs and how we’ve solved these challenges. It’s fair to say we were a little naive on how complex building a multi-brand design system would be when we started this journey! If you’re embarking on a design system project or looking to adopt NewsKit in your teams this article should help to get you up to speed on the different approaches available.</p><p>Theming is a core cross-cutting concern of a multi-brand design system, without a standardised approach, we would end up with a collection of components with potentially very little in common. It’s taken many iterations to get to where we have, whilst the journey isn’t over, we believe we do have a solid foundation in place to support the growing requirements for our diverse set of brands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5He71Cc3w96B9LtvrIFo1g.png" /><figcaption>The basics of theming in NewsKit Design System</figcaption></figure><h3>A bit of context</h3><p>Using a simplified version of our <a href="https://www.newskit.co.uk/components/action/button">button</a> as an example let’s looks at how this can be styled and the trade-offs associated with each approach</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*VeSg36FYygClBuf8Da0Plg.png" /><figcaption>NewsKit primary button</figcaption></figure><p>Imagine a webpage that only makes use of Inline styling.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/69edcb0623518f5ab7e728df10b87377/href">https://medium.com/media/69edcb0623518f5ab7e728df10b87377/href</a></iframe><p>First of all, it’s not that easy to read, and that is with a heavily redacted set of attributes. If we have multiple buttons on a page, it becomes a pain to update them all, it’s easy to miss an instance, even more so when we have multiple pages. We are quickly going to end up with inconsistencies across our UI, damaging product fidelity and brand perception. No sane person will want to maintain this at any scale.</p><p>A solution to this is to use CSS classes that can be shared across our site.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2bd27d76d545d1cead46132bd4ef7e1e/href">https://medium.com/media/2bd27d76d545d1cead46132bd4ef7e1e/href</a></iframe><p>If our team is disciplined and uses the correct button class on every element we can easily update all the buttons in the application from a single place. <a href="http://www.csszengarden.com/">CSS Zen Garden</a> is the definitive example of how powerful this can be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*hWu5DUnd2DTu6GxkExnR_g.png" /><figcaption>NewsKit outline button</figcaption></figure><p>However as our system evolves we’ll want to introduce new button types, such as our outline button above. This button shares many attributes with our default button. The problem we run into now is if we want to change our primary button colour we need to find the value and update multiple places in our CSS, not as bad as everything being inline, but still a pain and potentially difficult to manage in larger solutions that have many components relying on the same values. CSS variables allow us to sort this mess out, we can centralise the important parts of the theme in these variable declarations to build a <strong>simple theme.</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/97837671a73aa863fdaf1ebe390cf687/href">https://medium.com/media/97837671a73aa863fdaf1ebe390cf687/href</a></iframe><p>The important takeaway here is the manner in which we organise relationships between these variables and classes can have a dramatic impact on the future maintainability and consistency of our application. In the design system world, the parlance for these variables is design tokens. These tokens can be a mapping to raw values like above, a mapping to another token, or an aggregation of several tokens, more on this later.</p><p>Over the last few years, CSS in JS libraries have continued to gain traction, it’s outside the scope of this article to discuss all the associated trade-offs, but what’s important to us is it allows us to componentize our CSS and makes it easy to get render critical CSS out of the box, which in the world of publishing is important not only for our readers but also it’s increasing impact on search rank with Googles incoming <a href="https://web.dev/cls/">CLS changes</a>. It should be highlighted that the theming concepts described herein should be possible with vanilla CSS but they will be much harder to manage.</p><h3>Initial Theming solution</h3><p>In the very early days of NewsKit, our button was similar to the following. We have helper functions getting values from the theme. The getTypePresetFromTheme function gets several CSS attributes at once.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ef855810e7251a1c40fdedbf34098a09/href">https://medium.com/media/ef855810e7251a1c40fdedbf34098a09/href</a></iframe><p>This has a few issues.</p><ul><li>Not all values are tokens, not everyone wants an 8px border, this is however easily fixed by just tokenising additional values. There is however a cost to tokenising each new property as a scale should be defined for the underlying value range.</li><li>Our initial intention was to rely on the emotion <a href="https://emotion.sh/docs/theming#themeprovider-reactcomponenttype">theme provider</a> to change the tokenised values. However, creating a new theme each time you need a new button style is tedious, and managing that many themes will become an issue in itself.</li><li>Values that needed to be overridden inline could be done by exposing additional props, the problem with this is your component interfaces quickly become very cluttered. Additionally, it’s hard to predict how consumers are going to use the component, deciding what belongs on the component quickly becomes guesswork.</li></ul><p>This is mostly an example of a <strong>contextual theme</strong>, by this we mean our UI is going to behave differently depending on where it is placed, We can develop features such as dark mode or sub-brands on the same page provided we tokenise the attributes.</p><p>It’s worth noting that for many organisations this contextual theme is all they will need. However, we have a lot of different brands with varied requirements, overriding components at both an individual level and theme level in a consistent manner is required.</p><h3>Solutions</h3><h4>Expanding Preset Usage</h4><p>As we saw above, we grouped typographic styles in a single group, which we refer to as presets. Essentially a preset is just a group or an object of CSS properties that can be reused through reference to a token. This grouping makes it easier for consumers as our APIs become more consistent. It also helps us by meaning we don’t have to anticipate every single property a consumer might want to bring to a component.</p><p>At the time of writing, we have the following presets in NewsKit</p><ul><li><a href="https://www.newskit.co.uk/theming/presets/typography-presets"><strong>Typographic</strong></a><strong>:</strong> where text styles live, headlines, subheadings, paragraphs, etc.</li><li><a href="https://www.newskit.co.uk/theming/presets/style-presets"><strong>Style</strong></a><strong>:</strong> colour, backgrounds, borders. It’s worth noting that these support pseudo-states such as hover, active, etc. in addition to custom ones such as valid and selected.</li><li><a href="https://www.newskit.co.uk/theming/presets/space-presets"><strong>Space</strong></a><strong>:</strong> provides padding and margins.</li></ul><p>Adding presets to our button example we get the following.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fe4f659b8bb4b12c1c37af639b3ff8f0/href">https://medium.com/media/fe4f659b8bb4b12c1c37af639b3ff8f0/href</a></iframe><h4>Overrides</h4><p>A problem that our button example doesn’t really make apparent, is even with presets, we end up with a significant amount of properties on our components; take our <a href="https://www.newskit.co.uk/components/media/audio-player">audio player</a> for example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*D0DGuSmR3lk8EjGBE9ijdg.png" /><figcaption>NewsKit light theme audio player</figcaption></figure><p>This is exposed to the developer as a single component, yet it’s constructed of buttons, sliders, and text elements. Giving our consumers access to change each of these underlying elements is going to require introducing a significant amount of props onto the root of the component. Whilst this could feasibly work it’s not a great experience to be overwhelmed with theming options for nested elements. It also has a maintainability issue because each time we introduce a property on the button we would need to introduce it on the audio player as well, discrepancies will slip in.</p><p>The solution to this is simple, we have single overrides prop on each component that is used to override the theme for that instance, this can be thought of as being equivalent to inline styling. The object structure can be nested meaning we can extend indefinitely. If we add new props on an underlying component we get this for free on the parent because it will be passed straight through.</p><p>Our code ends up looking like so:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9b752ccabd478e9fee8cdf5199bca74a/href">https://medium.com/media/9b752ccabd478e9fee8cdf5199bca74a/href</a></iframe><h4>Component Defaults</h4><p>One thing overrides don’t allow us to do easily is modify all our button instances from a single location. This is where <a href="https://www.newskit.co.uk/theming/component-defaults/overview">component defaults</a> come in, in a way they are very similar to overrides but they are applied at a theme level, conceptually similar to updating our button class in the earlier CSS examples.</p><p>Every component in NewsKit comes with defaults that are set on the base theme, each component holds references to their respective defaults. When setting up the base theme we’ve made opinionated decisions around how these defaults relate to underlying token sets, for instance, we have a system-wide default border. If a user only wants that border to be applied on half their components, they can change this through the defaults. This is an example of a <strong>reference theme</strong> and hopefully demonstrates the level of flexibility baked into NewsKit.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9c41dbe94f3b69b17490962eac5d5e3b/href">https://medium.com/media/9c41dbe94f3b69b17490962eac5d5e3b/href</a></iframe><p>A currently unrealised goal of this is to generate these defaults as part of our Figma export process, allowing developers to simply drop a generated theme into their website to achieve that brand’s look and feel.</p><h3>Recap</h3><p>we’ve covered 4 types of themes, the definitions of which I’ve borrowed from this <a href="https://gos.si/blog/full-featured-themes-in-figma/">excellent article</a>.</p><ul><li><strong>Simple:</strong> If we change tokens we can propagate change through the application</li><li><strong>Contextual:</strong> Are will render differently depending on where they are placed, think sub-brands and dark mode.</li><li><strong>Reference:</strong> We have a level of indirection allow us to change the token the component is referencing and not just the value of the token itself.</li><li><strong>Full-featured:</strong> When we have all of the above combined. If it’s not clear by now this is what NewsKit is 😉.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s-slrCHM6BPNMvlZ-jyQoA.png" /><figcaption>figure detailing different types of themes</figcaption></figure><h3>Wrapping Up</h3><p>Hopefully, that gives you a good idea of the journey we’ve been on and why we’ve made some of the architectural choices we have. We believe we have a comprehensive base on which to build the numerous components that our diverse set of different brands across News require. Building components in this way comes at a significant upfront cost and if your organisation is embarking on a similar journey you should weigh up what level of theming you actually require.</p><p>The journey for us is far from over, here are some of the ways we’re looking to enhance our theming system in the future:</p><ul><li>Media queries on all overrides &amp; defaults. Currently support is a bit patchy as to where you can apply these, it makes sense to open this up further to give consumers more flexibility.</li><li>Component overrides, for example allowing you to bring your own buttons to the audio player.</li><li>Automated theme export from Figma to code.</li></ul><p>Additionally, our high-level roadmap can be found on the <a href="https://www.newskit.co.uk/about/roadmap">NewsKit website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a35bb83617" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newskit-design-system/evolution-of-theming-in-newskit-design-system-4a35bb83617">Evolution of theming in NewsKit design system</a> was originally published in <a href="https://medium.com/newskit-design-system">NewsKit design system</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing NewsKit: A themeable design system for unique media brands]]></title>
            <link>https://medium.com/newskit-design-system/introducing-newskit-a-themeable-design-system-for-unique-media-brands-6a2d770e2bbb?source=rss----4febfdba244f---4</link>
            <guid isPermaLink="false">https://medium.com/p/6a2d770e2bbb</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ellis Capon]]></dc:creator>
            <pubDate>Thu, 17 Dec 2020 17:22:28 GMT</pubDate>
            <atom:updated>2020-12-18T13:54:57.445Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m going to tell you a quick story about why <a href="https://www.news.co.uk/">News UK</a> decided to build a design system and why what we’ve ended up creating is so much more…</p><p>(if you’re not familiar with design systems, you can get up to speed <a href="https://uxdesign.cc/everything-you-need-to-know-about-design-systems-54b109851969?gi=33a5940604e">here</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JaRwV_vAdGyHGr_2ZLJQyQ.png" /></figure><h3>Why a design system?</h3><p>News UK is one of the largest publishing companies in the UK. We own big news brands and publishers;<a href="https://www.thetimes.co.uk/"> The Times</a>,<a href="https://www.thetimes.co.uk/"> The Sunday Times</a>,<a href="http://thesun.co.uk/"> The Sun</a>, and <a href="https://www.the-tls.co.uk/">Times Literary Supplement</a> and we’re increasingly investing in broadcasting, since the acquisition of <a href="https://www.wirelessgroup.co.uk/home/">Wireless Group</a> in 2016 (<a href="https://www.thetimes.co.uk/radio">Times Radio</a>, <a href="https://talksport.com/">talkSPORT</a>, <a href="https://talkradio.co.uk/">talkRADIO</a> and <a href="http://Virgin Radio UK | The Chris Evans Breakfast Show and the ...virginradio.co.uk">Virgin Radio</a>). In recent years the shift towards the digital media space has become even more rapid and traditional newspaper sales have fallen amidst the general move towards ‘online everything’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0FYkq8-m_KFTFl14gYFOzg.png" /><figcaption>Card component anatomy</figcaption></figure><p>As one might imagine, these huge publishing operations are underpinned by a number of technology teams. Each publisher requires a number of performant, stable and customer friendly websites, built using a collection of interface components. When The Times decide they want to build an index page, that page will be constructed using a variety of article cards (see a card example on the left). The same need exists for The Sun, or indeed, any other of the many News UK publications. In the current world, multiple product teams will spend resources on building an article card component in their own unique way, to satisfy the needs of their business stakeholders. These components have traditionally looked and behaved a little differently but, in essence, are variations of a common, base component.</p><p>Auditing the sites and seeing how much was shared led to a simple question — “why don’t we build one, agnostic, themeable, high-quality component that will satisfy all of the requirements?”. And so the NewsKit Design System was born.</p><figure><img alt="NewsKit logo" src="https://cdn-images-1.medium.com/max/1024/1*TDVA_FcKGVnj854Lwtr0Yw.png" /></figure><h3>NewsKit</h3><p>NewsKit, roughly 18-months old, is now maturing into a robust design system, adopting some of the latest technology to enable News UK brands to <em>build better products, faster</em>. We currently have around 29 high quality<a href="https://reactjs.org/"> React</a> components available to consumers with <a href="https://airtable.com/shrbFPJXN4tVA0Yye/tblCID6rEnixia79p">many more to come</a>.</p><p>Our design system is much more than a component library. NewsKit is a family of toolkits that supports the whole process of building beautiful, scalable digital products. Like many others, we’ve recently migrated all of our design teams to Figma. This provides us with a collaborative space to help design and grow News UK’s offering, enabling us to keep our components in sync across multiple projects and simplifying the customisation of themes and components.</p><p>Using design tokens, our theming system allows designers to take an agnostic NewsKit component, apply a theme created in Figma, hand it off to an engineer and, in doing so, provide a fully publication-themed component ready to be used to build a product!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*HXO5FT9RGbPgE9OOTQDzsg.gif" /><figcaption>With our theming system and the <a href="https://www.figma.com/community/plugin/731176732337510831/Themer">Themer</a> plugin, we can switch from wireframes to multiple high-fidelity brand themes</figcaption></figure><p>As we head towards the end of 2020, a momentous year for many reasons, the NewsKit team’s focus is gradually shifting. Our 2021 priorities can be outlined as follows:</p><ul><li>Support the adoption of our design system across News UK and, potentially, wider News Corp brands</li><li>Build upon our component library and continue to drive efficiency for product teams in our technology department</li></ul><p>Please do follow us for more, as we begin to tell you about the many technologies, successes, failures and pivots from our design system journey.</p><p>Forthcoming topics include:</p><ul><li>The story behind our unified content API and how we’re integrating that with our design system</li><li>Taking the NewsKit ecosystem to the next level with our core render package, allowing prospective clients to spin up a highly performant, scalable and themeable website rendering solution</li></ul><p>You can also take a look at exactly what we’re building by visiting our documentation site at <a href="http://www.newskit.co.uk/">NewsKit.co.uk</a>.</p><p>If you have any questions for us or would like to share learnings, we’d love to hear from you. Follow us here, leave a comment below and we’ll get in touch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a2d770e2bbb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newskit-design-system/introducing-newskit-a-themeable-design-system-for-unique-media-brands-6a2d770e2bbb">Introducing NewsKit: A themeable design system for unique media brands</a> was originally published in <a href="https://medium.com/newskit-design-system">NewsKit design system</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>