<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by James Mitchell on Medium]]></title>
        <description><![CDATA[Stories by James Mitchell on Medium]]></description>
        <link>https://medium.com/@james_67835?source=rss-29745b1e704c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*w7wML-8HLpiMc7XcaLbuyQ.jpeg</url>
            <title>Stories by James Mitchell on Medium</title>
            <link>https://medium.com/@james_67835?source=rss-29745b1e704c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:41:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@james_67835/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Figma Components: The Frontify Way]]></title>
            <link>https://medium.com/digital-branding/figma-components-the-frontify-way-3fbc7784a655?source=rss-29745b1e704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fbc7784a655</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[brand-management]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[James Mitchell]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 09:50:18 GMT</pubDate>
            <atom:updated>2021-07-13T10:43:34.085Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1wv3qZ81VA82BwQLQrCzdQ.png" /></figure><blockquote>“This design system is flawless!” — No one, ever.</blockquote><p>Components are filthy, wild creatures that we as product designers have collectively set out to tame. Our masochistic tendencies aside, there are obvious reasons to do so. We want to save time and create high-quality, brand-consistent, reliable products.</p><p>Whether you’re just starting out with your first button, or stuck in the mud of a growing component library, bear with me as I explain in painful detail how we do things at <em>Frontify</em>. It’s far from perfect, but perhaps you find an idea or two for your own imperfect system.</p><p>I’ll explain how we structure and name components, our basic versioning workflow, some <em>Figma</em> efficiency-boosting tips, and briefly share how we document our work using <em>Frontify</em> (our own product) to build our <em>Arcade</em> design system.</p><h3>BEM Like a Designer.</h3><p>For those of you unfamiliar with <a href="https://en.bem.info/methodology/quick-start/">BEM</a> (<em>Block</em>, <em>Element</em>, <em>Modifier</em>), it’s essentially a naming format/methodology for front-end components. The <em>Block</em> is the component (e.g. <strong>button</strong>), which contains <em>Elements</em> (e.g. button__<strong>text</strong>) and <em>Modifiers</em> produce the possible variations (e.g. button--<strong>primary</strong> or button__text--<strong>bold</strong>).</p><p>It emerged as a necessity to manage unruly stylesheets and incomprehensible markup. Despite the massive impact of frameworks on component development, this naming pattern and way of thinking is still strong. As our own development team uses it, it formed an excellent basis for structuring components in <em>Figma</em>.</p><p>Enter our <em>Component Frame</em> — this handy helper is the starting point for any new component we design. While it doesn’t strictly follow all the terminology of BEM, it does follow its principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2yIK1_asSC2McCpvmF3iCw.png" /><figcaption>Our beautiful <em>Component Frame</em></figcaption></figure><p>I’ll talk you through how one might build this <em>Slider</em> component using the miraculous <em>Component Frame</em>. If you’d like to follow along you can <a href="https://www.figma.com/community/file/984108010462968918"><strong>grab the demo file</strong></a> for yourself. Note that you need to detach the <em>Component Frame</em> to use it properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BPgJigLRa_2iRBEGv_pRsA.png" /><figcaption>The Slider component we’ll build</figcaption></figure><h4>Name</h4><p>Easily overlooked, we try hard to align at least the name of the component between developers and designers, so that we have a shared language.</p><p>In <em>Figma</em> the name of our <em>Component Frame</em> should match the component followed by the version number. In this case “<em>Slider v1”.</em> We also edit the heading on the <em>Component Frame</em> itself to match.</p><h4>Contains</h4><p>While not strictly part of the BEM methodology, this section can be really helpful for both designers and developers. For designers it acts as a kind of audit; they can get a quick impression of whether they’re making good use of existing components. For developers, it lets them know which dependencies to import when building the component.</p><p>Our first step in building a component is to break it down into its constituent parts. If any of these parts can be covered by an existing component, then we add an instance of the component(s) here. For the rest, we move on to <em>Elements</em>.</p><p>For the <em>Slider</em>, I know that we’ll need our <em>Icon Component</em> (which if you’re curious, uses a <em>Figma</em> hack to maintain the icon’s overridden fill color).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eJWyL5CQH3qSbeA0oXU3Dg.png" /><figcaption>“Contains” section of the Component Frame</figcaption></figure><h4>Elements</h4><p>We don’t have a specific rule for what constitutes an <em>Element</em>. Sometimes it’s a combination of several layers, sometimes it’s a single layer, in some very simple cases, one might skip the <em>Elements</em> altogether. It’s not even a matter of finding what works for your team, but rather for each individual component.</p><p>In the <em>Slider’s</em> case we’ll keep it simple with an <em>Item</em> and a <em>Box</em>. We need the <em>Box</em> because of some limitations with auto-layout, and we’ll group everything else into <em>Item</em> for simplicity.</p><p>For the <em>Box:</em></p><ol><li>Create a frame.</li><li>Style it.</li><li>Make it a component.</li><li>Name it:</li></ol><ul><li><em>“_” — </em>because only the final component should be published to the library</li><li>“<em>Elements/</em>” — so that it’s clearly separated in the component chooser</li><li>“<em>Box” — </em>no need to get verbose, it’s not going to get published anyway</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TYxlBOHe2erAOtntgc4q7Q.png" /><figcaption>Box Element</figcaption></figure><p>Very easy. On to the <em>Item</em>… not so easy.</p><p>When an <em>Element</em> requires variants we use a <em>Master</em> to maintain consistency and ease of editing. Such is the case with the <em>Item</em> in our <em>Slider</em> component. The steps are as follows:</p><ol><li>Add all layers (that are needed by any variant) into one frame.</li><li>Make it a component.</li><li>Name it, just like with <em>Box</em> but adding “<em>MASTER</em>” (i.e. “<em>_Elements/Item MASTER</em>”) so we can distinguish it from the actual <em>Element</em> that we’ll create next.</li><li>Style it to reflect the default state of the <em>Element</em>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uYn13NROZ-xU4VtXWLtVaA.png" /><figcaption>Item Element Master</figcaption></figure><p>Now we need to create variants from that <em>Master</em>, so, here are the first few steps with keyboard shortcuts (Mac OS) so you can do this like a pro:</p><ol><li>Duplicate the <em>Master</em> (⌘ + D).</li><li>Create Component (⌘ + ⌥ + K) — this will create a new component with an instance of the <em>Master</em> as its only child.</li><li>Rename it (⌘ + R) — according to which variant you want to create first e.g. “<em>Active=False</em>”.</li><li>Duplicate this new component (⌘ + D).</li><li>Detach it (⌘ + ⌥ + B).</li><li>Create Component (⌘ + ⌥ + K).</li><li>Rename it (⌘ + R) — e.g. “<em>Active=True</em>”.</li><li>Select both of these new components.</li><li>Combine as variants (no shortcut 😭).</li><li>Name the set (the purple dotted border), in this case, “<em>_Elements/Item</em>”.</li></ol><p>Then you just need to <a href="https://help.figma.com/hc/en-us/articles/360056440594-Create-and-use-variants">create all the necessary variants and name the properties accordingly.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lRvs7caAKeu7nWVrUtP54Q.png" /><figcaption>Item Element</figcaption></figure><h4>Master (Block)</h4><p>The main <em>Component Master</em> should be easy now as it follows the same pattern as an <em>Element Master</em>:</p><ol><li>Take all the possible <em>Elements</em> for the <em>Component</em>.</li><li>Put them in a frame.</li><li>Make it a component.</li><li>Name it:</li></ol><ul><li>“<em>_</em>” — so it’s not published</li><li><em>“Slider”</em> — the name of the component</li><li><em>“MASTER</em>” — to distinguish from the actual <em>Component</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RAOTIsiMgskT2Hup5VIz2g.png" /><figcaption>Component Master</figcaption></figure><h4>Component (Modifiers)</h4><p>This is the only component from this whole frame that we’re actually going to publish (although we break this rule occasionally).</p><p>Similarly to the <em>Element</em>, we take <em>_Slider MASTER </em>and nest it inside each variant, using overrides to create the different compositions and styles. Then we give it the most simple name of all… “<em>Slider”</em>. This is how it will appear in the component chooser when selecting from this library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LKp69OI7sMCqO0AHYyNGuA.png" /><figcaption>Component</figcaption></figure><h4>Bonus Dev-friendliness</h4><p>As mentioned initially, this presents the component in a way that is familiar to our developers (BEM-ish). But there are some additional benefits:</p><ul><li>The <em>Masters</em> (whether for the <em>Component</em> or a particular <em>Element</em>) can often be translated directly into markup (e.g. HTML), before the developer even starts thinking about all the different variants.</li><li>Style inheritance is clear, as everything runs top to bottom. That means that the developer can confidently define the default styling for the <em>Component</em> or its <em>Elements</em>, and use modifiers to create the variants.</li><li>In our case, we only strictly align on the <em>Component</em> name, but if a developer is stuck, or struggles with English, then the names of the elements, properties, states, etc. are already defined for them, and clearly labeled.</li></ul><h3>Versioning — Snap it, Work it, Quick, Erase it.</h3><p>Perhaps we use this component for a while and it starts to reach its limit. We need it to do something that it was never meant to do, or we want to split one of its <em>Elements</em> out into its own component for use elsewhere.</p><p>We follow a very simple workflow for this, and so far it’s been fine.</p><h4>Duplicate the Entire Component Frame</h4><p>Self-explanatory right?</p><h4>Relink the Components</h4><ol><li>Detach (⌘ + ⌥ + B) and (re)Create Component (⌘ + ⌥ + K) for any <em>Masters.</em></li><li>Change any instances from the previous version to the new version. So for example, we have v1 of <em>_Elements/Item</em> in our v2 <em>_Slider MASTER</em>. As we haven’t yet changed the name of the frame they’ll be right next to each other in the component selector. Easy switch. See the “Bulk Editing” section below for a tip on making this step even more painless.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lx5tFEVNiTNFASVl_ecacA.png" /><figcaption>Reassigning Elements from v1 to v2</figcaption></figure><h4>Make Your Changes</h4><p>Now you’re free to adjust or even totally revamp the <em>Component. </em>Don’t forget to increment the version number in the <em>Component Frame’s</em> name and the heading.</p><p>You might be wondering if you’re going to make significant changes to the <em>Component</em> anyway, why bother with all that faff of detaching and reassigning components? Well, it’s just easier to do it all at once so you don’t miss something. Personally, I prefer hitting it with a hammer before I start over picking through it with tweezers when a problem arises.</p><h4>Deprecate</h4><p>This is at the designer’s discretion. We generally make the old version private (add an “<em>_</em>” in front of the name) as a minimum and move the component (with all of its <em>Elements</em> etc.) to a page called “<em>Archived”</em>. That way if there’s work in progress that relies on that component it can still be used, but only the new version will be discoverable.</p><p>At some point of course it’s important to do a cleanup of those archived versions — and we generally do this in the most brutal way of deleting everything on that page when there’s a good opportunity to do so.</p><h3>Plugins &amp; Shortcuts — This is the Way.</h3><p>If you’re yet to be inducted to the <em>Fellowship of Timesavers, </em>let me show you the way, with a few tips &amp; tricks that have been particularly useful in our system.</p><h4>Structuring Variants with <a href="https://www.figma.com/community/plugin/931578032226522167/Simple-Sort-%28Beta%29">Simple Sort</a></h4><p>Some shameless plug(g)in(g) here. I made a <em>Simple Sort</em> to help us organize our variants without too much fuss. While <em>Figma</em> did add auto-layout functionality to variants, this is far from ideal with the more comprehensive components.</p><p><em>Simple Sort</em> organizes variants into a grid, based on some simple configuration options. Just select the variants’ frame (the purple border), and run the plugin. Running “<em>Manual</em>” gives you all the options, and “<em>Auto</em>” applies either the last-used settings for a particular set of variants or the default settings if it hasn’t been used yet. You can read more about that on the <a href="https://medium.com/r?url=https%3A%2F%2Fwww.figma.com%2Fcommunity%2Fplugin%2F931578032226522167%2FSimple-Sort-%28Beta%29">plugin’s page</a>.</p><p>This comes in really handy with theming too, as with some particular manipulations and a special gradient fill set on the variants’ frame, you can achieve something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3znFF69yfr1gdu_xGujqjQ.png" /><figcaption>How we present themes for our Input Label</figcaption></figure><h4>Bulk Editing</h4><p>You can achieve insane bulk-editing efficiency with these 3 tricks, especially when combined.</p><p><strong>⌘ + ⏎ / </strong><em>Shift</em> + <strong>⏎</strong></p><p>After telling a colleague about this one, they were blown away — I imagine others might have missed it too. When you have a layer, or multiple layers, selected hitting ⌘ + ⏎ will select all of the child layers. <em>Shift</em> + ⏎<strong> </strong>will select the parents of all selected layers. The uses of this in bulk editing are endless.</p><p>Most commonly, I use ⌘ + ⏎ for reassigning components when creating a new version (as explained above) — select the variants’ frame (purple border), hit ⌘ + ⏎ to select all variants, ⌘ + ⏎ to select the <em>Master</em> inside of each variant, and voila — you can change them all at once.</p><p><em>Shift</em> + ⏎ comes in really handy for selecting “<em>wrapping elements</em>” such as an auto-layout frame one might put around text and an icon. Use ⌘ + Click to select the text, then <em>Shift</em> + ⏎ to select the parent frame. Really helpful when you want to select several such things at once (for example across a bunch of variants).</p><p><a href="https://www.figma.com/community/plugin/799648692768237063/Select-Layers"><strong>Select Layers Plugin</strong></a></p><p>This plugin is fantastic and has tons of ways of selecting exactly the layers you want. As we are very careful with naming, we’re able to use “<em>Select Layers by Name</em>” quite often.</p><p>Let’s say you want to hide the icon in half of your variants. You select the variants (bonus tip: use ⌘ + Click’n’Drag / ⌘ + <em>Shift</em> + Click’n’Drag), run the command with the query “<em>_Elements/Icon</em>” and hit delete.</p><p><strong>Rename</strong></p><p>Most of you will be aware of this already but for those that aren’t, <em>Figma</em> has an amazing native feature for bulk renaming. Simply select the layers (this is where Select Layers can come in handy), and hit ⌘ + R. You’ll be presented with some really powerful renaming options — most importantly the ability to match and replace a particular string within the names of the layers you’ve selected.</p><p>Perhaps for a particular component, you want the <em>Elements</em> to be published. Select the <em>Elements</em>, hit ⌘ + R, and replace “_” with “”(empty string).</p><h3>Documentation — Keep it Schnitzel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*daTMaGuXNIUbPFnEliii6Q.png" /><figcaption>“<em>Keep it Schnitzel</em>” is <em>Frontify’s</em> take on the classic “<em>Keep it Simple</em>”.</figcaption></figure><p>No design system is really complete without documentation, but it can be overwhelming, and in our case, it turned into a sort of “<em>busy-work</em>” — where the value of all the time we were putting in became less and less clear.</p><p>We’re a small team, so this may not be the case for you, but we recently switched to the leanest of lean documentation and it has been fantastic for us.</p><h4>Component Frame</h4><p>On the <em>Component Frame</em> itself, we have, aside from the component name and version number, a place for notes — a totally free-form area where designers may put relevant pointers for people editing or using the component.</p><h4>Figma Native</h4><p>Figma has two fields for documenting each component. We use the description field for really important notes — that way it really jumps out at you when you use the component. We use the documentation link to point to <em>Frontify</em>.</p><h4>Frontify</h4><p>As a leader in brand management, we know that not only is every brand unique, but the ways in which people manage them are unique.</p><p>In the case of our own product design team, we use <em>Frontify </em>for our super lean documentation. Each component features only:</p><ol><li>A list of synonyms — to aid in search-ability.</li><li>A brief description.</li><li>A preview, either from <em>Figma</em> or <em>Storybook</em>, at the writer’s discretion.</li><li>A table of relevant links (most notably <em>Figma</em> and <em>Storybook</em>).</li><li>Free-space.</li></ol><p>That last one was an important change for us, as previously we had a page template with lots of sections on it that we should fill in for each component.</p><p>Components are wild beasts, each one is unique in its own special way, and trying to cage it in a box using a checklist or template proved to be almost impossible.</p><p>We have the few mandatory fields mentioned above (1–4), and then we’re free to simply put the most pertinent information, so designers and developers can use it effectively without wading through irrelevance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GiqLCAmTThA7ku53Ju_IFg.png" /><figcaption>How the Slider Component we just built might look on Frontify</figcaption></figure><p><em>Frontify</em> acts as a hub for us. <em>Figma</em> and <em>Storybook</em> are incredible tools that we love using — we let them do a lot of the heavy lifting, and <em>Frontify</em> is a simple place in which to bring the work and the people together.</p><h3>“This is great! I’m going to copy it exactly!”</h3><p>Don’t. There’s no one-size-fits-all for design systems.</p><p>If you really like some of the things we’re doing I’d suggest you <a href="https://www.figma.com/community/file/984108010462968918">dig deeper into the demo file</a>, <a href="https://www.frontify.com/en/pricing/essentials/">sign up for a free plan or trial on Frontify</a> and really think about which parts might work well for your team, your components, and your way of working.</p><p>And good luck, we’re rooting for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fbc7784a655" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-branding/figma-components-the-frontify-way-3fbc7784a655">Figma Components: The Frontify Way</a> was originally published in <a href="https://medium.com/digital-branding">Brand Inside &amp; Out</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>