<?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[Brand.ai Blog - Medium]]></title>
        <description><![CDATA[Brand.ai provides tools to help teams share a visual language, and create more consistent, cohesive customer experiences. - Medium]]></description>
        <link>https://medium.com/brand-ai?source=rss----b925bcd35eed---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Brand.ai Blog - Medium</title>
            <link>https://medium.com/brand-ai?source=rss----b925bcd35eed---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:28:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/brand-ai" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[We’re joining InVision and building the future of design systems together]]></title>
            <link>https://medium.com/brand-ai/were-joining-invision-and-building-the-future-of-design-systems-together-b0889abd3eef?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/b0889abd3eef</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Brand.ai]]></dc:creator>
            <pubDate>Wed, 29 Nov 2017 19:07:23 GMT</pubDate>
            <atom:updated>2017-10-25T20:49:09.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zcu99Hs4maHvJh5nvSlUsg.png" /><figcaption>Brand.ai + InVision</figcaption></figure><p>It’s official! We’re so excited to announce that we’re joining the InVision team.</p><p>We’re incredibly grateful for the support of our customers, investors, and for the incredible team that helped build Brand.ai over the past two years. This extended team made it possible for us to build one of the leading design systems tools anywhere.</p><p>We’ve integrated our product and customer insights into the ultimate design system technology — InVision Design System Manager. You can learn more about this exciting new tool <a href="https://www.invisionapp.com/blog/announcing-invision-design-system-manager">here</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FXEf1RnbZ4ZQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXEf1RnbZ4ZQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FXEf1RnbZ4ZQ%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8507e6f75a58b8c5695e65dc8436fa28/href">https://medium.com/media/8507e6f75a58b8c5695e65dc8436fa28/href</a></iframe><p>What does this mean for existing Brand.ai customers? For the moment, nothing at all. We will be in touch with more information as InVision Design System Manager rolls out.</p><p>We’re excited about the problems we can solve as part of the InVision team — and about the promising products we’re building together.</p><p>With all our thanks,</p><p>Ehud &amp; the Brand.ai team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0889abd3eef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/were-joining-invision-and-building-the-future-of-design-systems-together-b0889abd3eef">We’re joining InVision and building the future of design systems together</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sharing an Atomic Design Library in Sketch (and beyond) with Brand.ai]]></title>
            <link>https://medium.com/brand-ai/sharing-an-atomic-design-library-in-sketch-and-beyond-with-brand-ai-cd12e29e15c9?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/cd12e29e15c9</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[atomic-design]]></category>
            <dc:creator><![CDATA[Ehud Halberstam]]></dc:creator>
            <pubDate>Wed, 05 Apr 2017 08:05:34 GMT</pubDate>
            <atom:updated>2017-04-05T08:11:30.796Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR</strong> Sharing and maintaining an <a href="https://medium.com/p/cabe65426ab0">Atomic Design</a> system across Sketch files is close to impossible. Brand.ai fixes that.</p><p>One key premise of atomic design is that a change in an atom propagates to molecules, organisms, templates, and pages.</p><p>In Sketch, components such as atoms and molecules are represented with symbols. Updating a symbol master will update its instances in other symbols where it’s nested (i.e. molecules, organisms), and in artboards where it’s used. So, symbols provide the propagation mechanism we’re after. Except, changes in symbols don’t propagate outside the boundaries of a Sketch file.</p><p>If you’ve ever tried updating a symbol across different files, you must have noticed that a change doesn’t propagate to your design. Instead, you get a duplicate of the symbol, and the old version of the symbol is still nested in other symbols and artboards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/403/1*9O9k4TPU9DA6gIwTuIxIRg.png" /><figcaption>Pasting a new version of the same symbol in a new file creates a duplicate instead of updating the symbol.</figcaption></figure><p>Of course, this issue is not unique to teams using Atomic Design, but it’s easy to see how it’s difficult to maintain an Atomic Design system given this limitation.</p><p>Fortunately, the Brand.ai Sketch plugin provides the missing sync mechanism. It lets you share your atomic design system with your team. It will keep symbols (and nested symbols) connected across files so changes propagate through.</p><p>Here it is in action:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6hsK2rtdZAE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6hsK2rtdZAE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6hsK2rtdZAE%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d83df7c33c51d8cff08e68ee020b52e0/href">https://medium.com/media/d83df7c33c51d8cff08e68ee020b52e0/href</a></iframe><p>Brand.ai also makes it easy to sync text styles and layer styles across files in a similar manner.</p><h4>From Sketch to Front-End Code</h4><p>Brand.ai stores design data in the cloud, and helps sync styles outside of Sketch files altogether. All text styles, colors, and icons you upload to your design library in Brand.ai are available in Sass, Less, iOS, Android and other formats.</p><p>Here’s an example web view of a design library (see a live version <a href="https://brand.ai/acme-demo-new/style">here</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cPcvaKMceZsxiecpCfBhvw.png" /><figcaption>Web view of your design library in Brand.ai. You can update the library directly from Sketch.</figcaption></figure><p>And here is the corresponding Sass output in the Data Export page of the same library:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hIqBdZ5pcYPLwn_YSY6SqA.png" /><figcaption>Data export page for your design library.</figcaption></figure><p>Developers can integrate the Sass file in the example above into apps through a build script, and automatically keep apps up-to-date with the latest design.</p><p>This enables design teams to manage and share the source of truth for design tokens using a convenient web interface.</p><h4>Pattern Lab Integration</h4><p>With the same approach described above, you can connect your cloud library to <a href="http://patternlab.io/">Pattern Lab</a>, a popular tool for building Atomic Design systems.</p><p>To get you up and running quickly, Brand.ai provides a <a href="https://github.com/brandai/starterkit-mustache-brandai/blob/master/README.md">Pattern Lab Starter Kit</a>. It also offers a command line tool so you can easily update Pattern Lab whenever your library changes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd12e29e15c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/sharing-an-atomic-design-library-in-sketch-and-beyond-with-brand-ai-cd12e29e15c9">Sharing an Atomic Design Library in Sketch (and beyond) with Brand.ai</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Version-Controlled Design Collaboration Workflow in Sketch]]></title>
            <link>https://medium.com/brand-ai/version-controlled-design-collaboration-workflow-in-sketch-afdce3b2fa29?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/afdce3b2fa29</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brand.ai]]></dc:creator>
            <pubDate>Thu, 16 Feb 2017 20:31:31 GMT</pubDate>
            <atom:updated>2017-02-20T09:55:33.474Z</atom:updated>
            <content:encoded><![CDATA[<p>You’ve been there before. You open up a folder with <em>final.sketch</em>, <em>final2017.sketch</em>, <em>FINAL-approved.sketch</em>, and you have no idea which is actually the final design.</p><p>Kyle has been working from<em> final2017.sketch</em> for weeks but Nancy insists that <em>FINAL-approved.sketch</em> has all of the latest UI elements in it.</p><p>You call a meeting and say “Hey, we need to fix this. From now on, all files need to be labeled with the date they were last modified, and we all need to be uploading our files to the cloud at the end of each day!” But two weeks go by and everyone resorts back to their old habits.</p><p>We’ve been there too. Using files and cloud storage as the backbone of our collaborative design workflow wasn’t working. The problem goes beyond poorly organized files, of course.</p><ul><li>Having multiple team members update a single file results in sync conflicts.</li><li>It’s difficult to maintain a single thread of discussion around a design as files change hands.</li><li>The rationale behind changes is lost across file versions.</li><li>Rolling back changes is difficult. Either a pre-change state is not captured at all, or retrieving an earlier version of the design requires a slow process of sifting through files and their content.</li></ul><p>So, we built Brand.ai Artboards to offer a better way to organize and share your designs and the conversations around them.</p><p>Simply <a href="https://brand.ai/sketch">download the Brand.ai Sketch plugin</a> to get started!</p><h3>Version Controlled Design Collaboration Workflow</h3><p>We internally referred to Brand.ai Artboards as GitHub for designers. It enables designers to collaborate on designs in Sketch, keep a version history for each artboard, comment on designs and gather feedback from team members throughout the design process.</p><h3>Here’s How it Works</h3><p>Download and install the <a href="https://brand.ai/sketch">Brand.ai Sketch plugin</a>.</p><p><strong>Uploading an Artboard</strong></p><p>Select one or more artboards and click “Upload Selected Artboard”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KQ-W7AtRkmac59Bx.png" /></figure><p>When you upload a new design to the Brand.ai cloud, it will appear in the Artboards section of the plugin, and become instantly available for your teammates to work with <em>right from Sketch</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1Ji3bttODyJajygL.png" /><figcaption>Drag &amp; drop an artboard to any page, or click “Add Page to Document” to add all artboards to your document.</figcaption></figure><p>To continue working on an artboard you’ve previously uploaded, you or any team member can simply drag &amp; drop the artboard into a document.</p><p>Alternatively, click “Add Page to Document” and a new page with all the artboards will be added to your Sketch document.</p><p>No more hunting for files!</p><p><strong>Creating a New Version of an Artboard</strong></p><p>When you’re ready to upload a new version of an artboard, simply upload the artboard again by clicking “Upload Selected Artboard” on the relevant page. Brand.ai will identify that a previous version is available, and will create a new version for it. You’ll see a dialog that lets you describe what changed from the previous version, and why.</p><p><strong>Viewing Version History</strong></p><p>Click the artboard in Brand.ai to see its version history.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HxTbI17QRyfmqAcO.png" /><figcaption>No final-final file extension needed. Versions are numbered automatically, for easy reference.</figcaption></figure><p>You can add any version to your document. To do so, select the version, and drag the drop the artboard image to the document . This allows you to roll back changes, or reuse elements from previous designs without having to re-create them.</p><p><strong>Sharing and Discussing Designs</strong></p><p>To share designs and gather feedback, click “Share and Discuss”. You’ll see an online view of your design, where team members can annotate your design and leave comments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6Ptkdhz3Dj5ARssB.png" /><figcaption>Keeping your conversations next to your design ensures feedback doesn’t fall through the cracks.</figcaption></figure><p>Comments appear in real-time, so you can use this view for easy reference while talking with a remote collaborator.</p><p>Brand.ai is built for teams. Any designer on your team can access your team’s artboards, and join the discussion. You can manage your team from the Team page in your online dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7ZJUhKsbPO8hJCdw.png" /><figcaption>Click “Add Team Member” in the plugin’s dropdown menu for a quick visit to your online Team management page.</figcaption></figure><h3>What’s Next</h3><p>We’ve built the Brand.ai web plaform to help teams manage and use a design system. We’re thinking of artboards as the expression of your design system. Artboards you upload to Brand.ai stay connected to your design system — they’re not rasterized images, but a collection of styles, components, and the hierarchical and spatial relationships between these elements.</p><p>In upcoming releases and articles we’ll demonstrate how this connectivity between your system and artboards helps your team maintain a consistent, cohesive design across complex projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afdce3b2fa29" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/version-controlled-design-collaboration-workflow-in-sketch-afdce3b2fa29">Version-Controlled Design Collaboration Workflow in Sketch</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Version Control for Design Systems]]></title>
            <link>https://medium.com/brand-ai/introducing-version-control-for-design-systems-d105796369bc?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/d105796369bc</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Brand.ai]]></dc:creator>
            <pubDate>Tue, 10 Jan 2017 22:38:31 GMT</pubDate>
            <atom:updated>2017-01-15T08:14:39.855Z</atom:updated>
            <content:encoded><![CDATA[<p>Version control fundamentally improves the way you build and manage your design system. Here’s why.</p><h3>Why version control?</h3><p>If you’re managing a design system and use a solution with no version control to store your assets, chances are you’re running into some or all of these issues:</p><ul><li>Having multiple team members contributing to the system is a pain — collaborators run into file conflicts.</li><li>You can’t easily roll back changes.</li><li>There’s no easy way to communicate rationale behind changes.</li><li>In turn, there’s no easy way to review history of changes and decisions.</li><li>If you’ve been working with Brand.ai, you know your updates are pushed to the entire team immediately. This is great, but what if you need to collaborate on changes in ‘draft mode’ without having work-in-progress pushed to the entire team? You can’t. — well, now you can!</li></ul><p>We’ve built the Brand.ai web plaform and Sketch plugin to help teams manage and use a design system. We’re happy to introduce version control so you can avoid all above issues. Here’s how it works.</p><h3>Releasing a version</h3><p>In the Sketch plugin menu, select ‘Release a Version…’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/0*cadtIAv4fTVDJPQg.png" /><figcaption>Release a version. You know you want to.</figcaption></figure><p>Fill out a version name and description and click ‘Create’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/0*b1ByLZjgVEljGeS9.png" /><figcaption>Enter version name, and describe what’s new in this version.</figcaption></figure><h4>What the rest of the team sees when you release a version</h4><p>When you release a new version, team members currently working with the design library will see an alert notifying them that the library has been updated to a new version. The updated assets and styles are available to use immediately. No manual opt-in or download is required.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/0*5tQaA52DRJFhpmG7.png" /><figcaption>Notifying users that the library has been updated.</figcaption></figure><h3>Switching between versions</h3><p>Team members can switch versions from the Sketch plugin menu:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/0*qYSlDH29oIOoi1rl.png" /><figcaption>How to switch between different versions of your design library.</figcaption></figure><h3>Version History</h3><p>To see the version history, choose ‘Version History…’ from the plugin menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/0*1tpLui7AhYR-Pv4D.png" /><figcaption>Version history FTW</figcaption></figure><p>You’ll see a list of versions, each with release notes and change summary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/0*Me_XuHhmQCkyyFuL.png" /><figcaption>Version History</figcaption></figure><h3>Change comparison</h3><p>To see what changed between two versions, in the Version History page, select a version and click <strong>Compare with previous version &gt;</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/1*H45j5UenR-jQTq3578et9A.png" /><figcaption>Compare those versions.</figcaption></figure><p>You’ll see a list of the assets that were added, removed, and changed.</p><p>To see a ‘before and after’ side-by-side comparison of a changed item, click ‘More Details’ on an item that changed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/0*X3w6rFpfWCiD5_l3.png" /></figure><p>If you’re having a hard time noticing the differences, you can click ‘Highlight Changes’ to see highlights of the differences between the two images.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RaeBURm12itQZlxl.png" /><figcaption>Automatic Visual Diffing</figcaption></figure><h3>Editing in Draft Mode</h3><p>Brand.ai members include Editors, and non-editors. As an editor, changes you make are immediately available to all other editors in a Shared Draft version (aka working copy). There’s one shared draft that all editors of a library are working with and editing together.</p><p>When an editor releases a new version, Brand.ai captures a snapshot of the Shared Draft, and makes it available to all team members as a new version.</p><h3>What’s next</h3><p>We’re looking forward to hearing how this works for you. If you haven’t already, <a href="https://brand.ai/sketch">download the Brand.ai plugin</a> and take it for a spin.</p><p>One extension we’re looking to add is personal drafts — editors would be able to work on a personal draft before adding their changes to the Shared Draft. Then, we can add a mechanism for change approval — before updates make it from the personal draft to the shared draft, they’d need to be reviewed and approved.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d105796369bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/introducing-version-control-for-design-systems-d105796369bc">Introducing Version Control for Design Systems</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Share a Design System in Sketch, Part 3: InVision Craft and Brand.ai]]></title>
            <link>https://medium.com/brand-ai/how-to-share-a-design-system-in-sketch-part-3-invision-craft-and-brand-ai-660bcc79ec67?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/660bcc79ec67</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[sketch]]></category>
            <dc:creator><![CDATA[Brand.ai]]></dc:creator>
            <pubDate>Mon, 19 Dec 2016 21:42:32 GMT</pubDate>
            <atom:updated>2017-01-13T00:53:17.778Z</atom:updated>
            <content:encoded><![CDATA[<p>In <a href="https://blog.brand.ai/how-to-share-a-design-system-in-sketch-1-3-245308f2d7f1#.haws2a3l0">parts 1</a> and <a href="https://blog.brand.ai/how-to-share-a-design-system-in-sketch-part-2-github-84a7bc3973cd#.yt6gzp8ps">2</a> we covered two approaches to sharing a design system — using Dropbox and using GitHub. In this third part we will talk about using two products that were specifically created to aid in creating and sharing design systems using Sketch.</p><p>Before we delve into the details though, let’s summarize what we’re looking for in a tool for sharing a design system.</p><p>At a high level, such a tool should help make our design system <strong>easy to use</strong>, and <strong>easy to maintain*.</strong> Below are the key requirements to facilitate each of these goals.</p><h3>Make the design system easy to use</h3><ul><li>Designers should be able to view their assets and styles side by side with the design they are working on. They should not have to switch pages, or worse, browse to a reference site. Context switching is a productivity killer.</li><li>Designers should always see the most <strong>up-to-date</strong> version of their design system. As the design system evolves, designers should see the changes reflect in their working environment <em>automatically</em>. As <a href="https://twitter.com/hallfire">Chris Hall</a>, UX Manager at eBay, <a href="https://www.crowdcast.io/e/unified-design-systems">says</a>, retrieving a new version of a design library manually is simply not part of a designer’s workflow.</li><li>Designers should be able to <strong>search </strong>their design library. As <a href="https://twitter.com/payamrajabi">Payam Rajabi</a>, ex-system designer at Shopify, mentioned to us: search enables designers to create a larger design system to meet the needs of product design, and not have to “dumb the system down” just so it’s easily scannable.</li><li>Designers should be able to automatically update existing designs with changes in the system.</li></ul><h3>Make the design system easy to maintain</h3><ul><li>Multiple designers (editors) can update the system.</li><li>Editors can update the design system directly from Sketch.</li><li>Editors don’t have to worry about overriding each other’s work when making updates.</li><li>Editors don’t have to worry about making a mistake when updating the system, since they can easily roll back a change.</li><li>Editors can easily roll out an update to all clients of the system, and guarantee everyone uses the latest version.</li><li>Editors can annotate changes they make to the design system with notes explaining why they made the change, or summarizing large sets of changes.</li><li>Editors should be able to share the library outside of Sketch. Viewing and editing directly from Sketch is a benefit to designers, but others such as marketers, developers, and QA people will find it easier to simply view a web page. Making the system available for non-designers helps drive organization-wide adoption of a consistent visual language.</li></ul><p>Let’s evaluate the approaches introduced in Part 1, and Part 2 of this series with the above requirements in mind.</p><p>Cloud storage solutions such as Dropbox are useful for a small team, or a small project. They do little to make the system easy to maintain and use for larger teams or projects.</p><p>The GitHub route addresses many of the requirements to making the system easy to maintain, especially if you also use Sketch plugins to add additional features. However, GitHub is not built specifically for design systems, and therefore does little to make the system easy to use. It also introduces complexity and a non-trivial learning curve.</p><p>And that brings us to Part 3. Two products — InVision Craft and Brand.ai (yes, that’s us!) satisfy many of the requirements to making the design system easy to maintain <em>and</em> easy to use. Let’s see how.</p><p>*Thanks <a href="https://twitter.com/alcor">Nicholas Jitkoff</a> for putting it in these terms.</p><h3>Purpose-built tools for sharing and working with a design system</h3><p>A central assumption of Part 1 and Part 2 was that a team uses a Sketch master file to represent a design system. In this post, we show how moving from sharing a design file with generic file management tools to sharing <em>design data</em> with purpose-built tools makes a design system easier to use and maintain.</p><p>InVision Craft and Brand.ai allow you to define a design system using Sketch with a dedicated plugin.</p><h3>InVision Craft — Overview</h3><p>To get started with Craft, you first <a href="https://www.invisionapp.com/craft">install the Sketch plugin</a>. Craft offers a set of powerful tools for visual designers; the one that helps you share a design system is called <em>Library</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/298/0*XV0I_2PJ1WspSWP_.png" /><figcaption>InVision Craft Library side bar is anchored to the right as you design, providing easy access to assets.</figcaption></figure><p>Library lets you store colors, text styles, and layers in a folder on your Mac. You can share this folder with your team by using Dropbox, Google Drive, or Box.</p><p>Craft takes advantage of Sketch’s symbol system. If you add a symbol layer to your library, you can use that symbol in your designs, including making overrides. If the symbol in the library is updated, you can update all instances of the symbol in your document and your overrides will be respected.</p><p>Text styles and colors saved in Craft work independently of Sketch’s text styles and document colors, so you’d need to use the Craft interface to access the global text styles in your design system, instead of the built-in Sketch interface. Once you use Craft to insert layers, you’d likely get comfortable using its interface and search functionality for applying text styles and colors too.</p><p>The <em>Document</em> tab in the Library panel is a style guide feature. It will generate a style guide for you — which is a new page in your Sketch document — reflecting the styles used in that document. The properties in the Document tab, as the name suggests, are tied to the current Sketch document. They are completely independent from the Shared library, with one exception: you can add styles in the Document tab to your Shared tab with a single click.</p><p>Learn more about <a href="https://www.invisionapp.com/craft#library">InVision Craft Library</a> on InVision’s web site. There is a short video that does a great job of summarizing the feature.</p><h3>Brand.ai — Overview</h3><p>Brand.ai works similarly to Craft: <a href="https://brand.ai/sketch">install a plugin</a>, add your design library via that plugin, and share it with your team. Brand.ai is different from Craft in that it provides its own cloud storage and sharing mechanisms. So instead of using Dropbox, you can create a team in Brand.ai and share design libraries among teammates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/0*2BFZVKYCrFAs7z1B.png" /><figcaption>Brand.ai window is overlayed above the page as you design. Toggle with Cmd+Shift+D.</figcaption></figure><p>You can use Brand.ai to set colors, add layers, and set text styles directly from the panel. Brand.ai also gives you the option to add your shared colors, text, and symbols to the native Sketch interface (just like you would without using any plugins), so you can use Brand.ai as a sync solution and continue using the Sketch interface while designing.</p><p>See our <a href="https://brand.ai/sketch">website</a> for more on the Brand.ai Sketch plugin. Or watch <a href="https://www.youtube.com/watch?v=6hsK2rtdZAE">a short video</a>.</p><h3>Keeping existing designs up to date with design system changes</h3><p>Brand.ai and Craft help you make sure your team is using the latest design elements.</p><p>Craft relies on using a cloud sync service, and whenever any changes are synced to your Mac, the contents of the Craft panel will change to reflect that. Brand.ai also always displays the latest design system, but uses its own sync service to instantly push updates to all connected Sketch clients.</p><p>Always having the latest design system available to draw from is a great starting point, but you can go further with these plugins. Specifically, you might want to update design elements that you have already added to your document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/0*ttbjjJmbHQhngzp8.png" /><figcaption>Craft Library indicates an update is available for the user icon</figcaption></figure><p>In Craft, any layer that you have added to the document is highlighted in the panel when a new version becomes available. You can click the refresh icon in the panel to update all instances of the layer in the current document.</p><p>Brand.ai’s approach is to use Sketch’s built-in tools for keeping designs current. For layers, this means using symbols. When a symbol in the design system gets updated, you can apply that update by syncing the design library to your document. Syncing will update the relevant symbol master in your document, and Sketch will take care of updating all the locations where that symbol is used (all the instances).</p><p>Brand.ai doesn’t provide its own mechanism for updating non-symbol layers throughout your document, so non-symbol layers are disconnected from your design system once you add them to the document. The reason is that non-symbol layers (or layer groups) don’t support <a href="https://www.sketchapp.com/learn/documentation/symbols/editing-symbols/">overrides</a>, and blindly replacing them with a newer version is prone to errors. Note that you can include symbols within disconnected groups (e.g. a navbar container layer with nested icon symbols in navbar items), and those symbols will get updated when newer versions become available.</p><p>Brand.ai supports sharing Sketch layer styles. Layer styles contain reusable styles like fills, borders, shadows, etc. You can save these layer styles to your Brand.ai design library and you can sync them into your design documents. This can be a powerful tool for maintaining consistency. Just as with symbols, Sketch takes care of keeping everything up to date after Brand.ai updates the layer style in the document. Brand.ai uses the same technique with text styles as well.</p><h3>Avoiding conflicts when multiple designers are editing</h3><p>One of the problems with using a Sketch master file and sharing it with your team is how easy it is to end up with two designers editing the file during the same time and running into conflicts. The simplest solution, splitting up the various elements of your design system into separate files, makes is difficult to use the system as you design, and keep things up to date. But with plugins like Craft and Brand.ai, you get the benefits of a single shareable design system and the ability to edit individual elements of the system.</p><p>Neither Craft nor Brand.ai offer a solution for dealing with simultaneous edits, but since you are working with a single color or a single component, the chances that conflicts will arise are greatly reduced.</p><h3>Organization, layout, and search</h3><p>Sketch’s artboards and pages work well for organizing a design system. You get the freedom to organize design elements in pages, artboards, and spatially on the canvas. The place of an element in the document is memorable, so after using the system for a while you may be able to find elements fairly quickly.</p><p>But this approach starts to break down with a large design system. You start having to switch pages, or zoom out to be able to see everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XxbInjOK3L7LFkf5.png" /><figcaption>Left: a small design system is easy to navigate in Sketch. Right: a larger design systems requires zooming in and out.</figcaption></figure><p>This is where having a tool that is designed to handle large numbers of design elements can make the difference between a usable, easily adopted system, and one that gets ignored.</p><p>Both Craft and Brand.ai support searching your design library by name and by the type of element so you don’t have to visually scan the system.</p><p>Both plugins allow you to not only find elements, but also directly <em>use</em> them in your design work. Dragging and dropping into your document from a floating panel is faster than copying and pasting between pages. Craft even adds a convenient button to the Sketch UI to make it easy to bring up the Library panel. Brand.ai has a keyboard shortcut to hide and show its window. This is a different way of working, but once you get used to it, you might find it hard to go back to using Sketch documents alone to organize your design elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/0*xPSHkAlVQVELJpK4.png" /><figcaption>Brand.ai window with filtered search results.</figcaption></figure><p>Of course, you can keep a version of the system that’s organized in a Sketch document while also using a plugin to manage the source of truth in the cloud. If anyone changes the design system via the plugin, you can update the document just as you would any other document.</p><h3>Sharing the design system outside of Sketch</h3><p>Storing a design system outside of Sketch opens the possibility of using your design system in other tools. Imagine sharing components between Illustrator and Sketch, or using your brand colors in PowerPoint. InVision has built a version of Craft for Photoshop, but it doesn’t yet support the Library features from the Craft Sketch plugin. This is a promising start, and when Library is enabled for Photoshop, designers may be able to share design assets between Photoshop and Sketch.</p><p>While connecting design tools will help designers works better together, the true potential of design systems lies in bridging the gap between designers and developers.</p><p>We have <a href="https://blog.brand.ai/how-to-connect-a-design-system-to-your-development-workflow-1-4-colors-6d8283edd571">written about</a> the benefits of connecting a code base to a design system that is built and maintained by designers. This is why Brand.ai provides an API to access your colors, type styles, and vector versions of your layers so they can be used by developers.</p><p>There is a class of tools that aid in the handoff between designers and developers — <a href="https://zeplin.io/">Zeplin</a>, <a href="https://support.invisionapp.com/hc/en-us/articles/207950906-Introduction-to-Inspect">InVision Inspect</a>, and <a href="http://utom.design/measure/">Sketch Measure</a> all help developers and designers to get the most out of designs created in Sketch by providing an interface for developers that exposes design data in formats that are useful to developers, such as CSS.</p><p>Zeplin even has a feature that puts colors and text styles in context by recognizing the name of the color from a list that you supply to Zeplin beforehand. But what if instead this information was taken from your design system? Imagine developers having access to all the relevant information about icons, UI components, etc. — their names, attributes, and sample code needed to use them. All this is possible with tools that are built on top of purpose-built design system storage.</p><p>Neither Craft nor Brand.ai support these kinds of advanced features yet, but the foundation is there to add them and much more.</p><h3>Conclusion</h3><p>InVision Craft and Brand.ai offer a new solution to building design systems using Sketch. Instead of sharing a Sketch master file, you use a plugin to help define, store, and access the design system. This approach makes design systems easier to use. You have all your assets right there <strong>side by side</strong> with your Sketch document as you work, and you can be confident you are <strong>always looking at the latest version</strong> as your design system evolves. You can <strong>search</strong> for design assets by name, which is especially helpful for large design systems. Finally, you can use the plugins to <strong>automatically update your designs</strong> with new changes to the design system.</p><p>As far as making your design system easy to maintain there are two main benefits of InVision Craft and Brand.ai. First, you can <strong>edit your design system directly from within Sketch. </strong>Second, because individual assets are stored separately,<strong> running into conflicts is a non-issue</strong>, assuming different designers work on different elements of the system at any given time.</p><p>As it stands, the downside of these products is their lack of support for change management features. Unlike GitHub there is no way to roll back to previous versions, or to annotate changes. There is no visual diff, where you can visually compare what has changed before and after an edit. And there is no change request and approval mechanism.</p><p>But the foundation for these kinds of features as well as other powerful ideas is there, and we’ll post about exciting developments in this blog.</p><p>[<strong>Update</strong>: we’re in the process of introducing version control, change management, and visual diffs. If you’d like an early preview, write to us at <a href="/service/mailto:%20hello@brand.ai?subject=Sign%20me%20up%20for%20an%20early%20preview">hello@brand.ai</a>.]</p><p>[<strong>Update 2: </strong>Version control is here! Read the <a href="https://blog.brand.ai/introducing-version-control-for-design-systems-d105796369bc#.d2q5hpggd">announcement post</a> to learn how version control fundamentally improves the way you build and manage your design system.</p><p>With this update the table below begs a checkmark for Brand.ai next to “Change Management”, but we’ll keep it as is to reflect on the past.]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b83ttynNqUBWCnqY.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=660bcc79ec67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/how-to-share-a-design-system-in-sketch-part-3-invision-craft-and-brand-ai-660bcc79ec67">How to Share a Design System in Sketch, Part 3: InVision Craft and Brand.ai</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Share a Design System in Sketch, Part 2: GitHub]]></title>
            <link>https://medium.com/brand-ai/how-to-share-a-design-system-in-sketch-part-2-github-84a7bc3973cd?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/84a7bc3973cd</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brand.ai]]></dc:creator>
            <pubDate>Thu, 01 Dec 2016 08:11:01 GMT</pubDate>
            <atom:updated>2016-12-19T22:42:03.856Z</atom:updated>
            <content:encoded><![CDATA[<p>In the <a href="https://blog.brand.ai/how-to-share-a-design-system-in-sketch-1-3-245308f2d7f1">first post</a> in this series, we talked about the pros and cons of using cloud storage systems like Dropbox to share a Sketch design system. In this post we’ll discuss a second approach for sharing a Sketch design system: GitHub.</p><h3>Why GitHub?</h3><p>Both GitHub and Dropbox provide a cloud storage solution for your Sketch master file, and enable each of your team members to work with a local copy of this file. But GitHub has some very useful advantages:</p><ol><li><strong>Well-documented history of changes</strong></li><li><strong>Support for visually comparing versions (visual diff)</strong></li><li><strong>Support for a change approval process</strong></li><li><strong>Advanced conflict resolution</strong></li></ol><p>Let’s explore each of these advantageous features of GitHub and see how they can support a team’s efforts to build and maintain a design system in Sketch.</p><h3>History of changes</h3><h4>Updating the master file on GitHub</h4><p>Every change you make to a file on GitHub has to be applied as part of a “commit.” Commits wrap up any number of modifications to a Sketch file together into a single conceptual change that makes sense in terms of the design. For example, you might fix several text alignment issues on multiple components, and then decide to <em>commit </em>all those changes together at once. First you make changes to your Sketch file as usual, then using GitHub you <em>commit</em> those changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*tXtfohbjK0BcUznvfr2VfA.png" /><figcaption>A GitHub commit log</figcaption></figure><h4>Documenting decisions</h4><p>GitHub automatically logs the time of every commit and who it was made by. It also requires you to write a description, and creates a searchable log with this information.</p><p>The beauty of descriptions written by designers is that they can contain useful context about <em>why</em> design decisions were made. For example, if a description says “Changed button text color to make it more readable” this tells you that the change was made for accessibility reasons, which isn’t something you would immediately know just from looking at what changed. This context can be useful for your team and future self as you look back through the log.</p><p>Note that for the early days of a project, having to provide a description for each change can feel like an extra hoop to jump through when you just want to get things done. You may want to start using GitHub after the system stabilizes.</p><h4>Working with older versions of the Sketch master file</h4><p>You can access any older version of the design system and open it in Sketch. This enables you to go back and try something different or recover from mistakes you made. You can even copy an object out of an old version and paste it into the most recent one.</p><h3>Visually comparing versions</h3><p>GitHub has <a href="https://help.github.com/articles/rendering-and-diffing-images/">a feature</a> that presents the difference between two images visually. This is a killer feature for designers, but unfortunately it doesn’t work out of the box with Sketch files. PNG, JPG, GIF, PSD, and SVG are supported.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/0*4QAV1h2jPHcFXEXM.gif" /><figcaption>Example of scrubbing between before and after images on GitHub</figcaption></figure><p>Worry not! There is a workaround. The solution is to export all your artboards to PNG images, and include the images in each GitHub commit along with the Sketch file. When you do this, GitHub will show you the changes visually.</p><p>The <a href="https://mathieudutour.github.io/git-sketch-plugin/">Git Sketch Plugin</a> automates this process and exports artboards as images. The plugin has other GitHub features as well, including allowing you to make commits directly from Sketch.</p><h3>Conflict resolution</h3><p>One drawback of sharing Sketch files via cloud storage services is dealing with simultaneous edits. While Dropbox and Google Drive do detect conflicts that arise when two users edit a file at the same time, GitHub provides a more formal and structured way to deal with this situation.</p><h4>Conflicts from simultaneous edits</h4><p>It’s easy for two people on a team to step on each other’s toes. If one designer opens a copy of the Sketch file, works on it for an hour, then commits it to GitHub, there’s a chance a second designer has committed her own changes to the file during that hour. The larger the team, the more likely this is to happen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DmssujqaP-kLD9A8.png" /><figcaption>GitHub Desktop prevents you from syncing your commits to the server when there are conflicts</figcaption></figure><p>An advantage of using GitHub over traditional cloud sync services is that GitHub prevents you from saving your commits back to the central repository when simultaneous edits have been made. If you are the second person to upload your changes, then you will have to — at a minimum — acknowledge that other changes have been made, and that by continuing you will override those changes.</p><p>The more appropriate way to handle it is to look at the history of changes and see who made the conflicting edits, and what they changed. You can then work with that person to re-create their changes in your copy of the file. Alternatively, you can accept their changes, and re-do your work on top of theirs.</p><h4>Limited conflict resolution automation for Sketch files</h4><p>Unfortunately, GitHub does not work optimally with Sketch files. It’s built to support text files, especially code. Each line of text is treated like a separate unit. So if two changes are made in the same file, as long as different lines were changed, GitHub can intelligently combine those changes automatically. This does not work for Sketch files.</p><p>GitHub sees Sketch files as one unit, instead of individual artboards or shapes. This is a consequence of the way Sketch files are formatted. The same limitations apply to image formats like PNG and JPEG (SVG files actually are text files).</p><p>The problem with Sketch files is compounded by the fact that saving an entire design system in a single file means that GitHub sees <em>everything</em> as one unit. Software developers typically build their systems out of many separate files, reducing the chances that any two developers will work on one file at the same time.</p><p>One way to address this is to split your Sketch file up into separate files, e.g. one artboard per file. This can reduce the frequency of simultaneous edits, and therefore conflicts. This same approach could be used to deal with similar issues on Dropbox or Google Drive, but designers typically don’t do this because it’s a strain on their workflow. It’s more convenient to keep a design system in a single files, and take advantage of multiple pages and artboards to keep things organized.</p><h3>Change approval workflow</h3><p>GitHub has a feature called <em>pull requests</em> that allow you to propose a set of changes to be made to your design library. You make the changes like you normally would in Sketch, but then you can use GitHub to create a pull request instead of simply saving your changes directly to the Sketch file stored in GitHub. The pull request wraps up your changes with a description, and GitHub then provides a web page where these changes can be reviewed.</p><p>Your team members have the opportunity to review the changes you have made, and either approve them, reject them, or ask you to make adjustments. If your changes are rejected, you can update the pull request with additional changes or corrections and request another review. If this is the kind of organizational process you want to follow, using GitHub helps support it.</p><h3>Conclusion</h3><h4><strong>Pros</strong></h4><p>GitHub is a mature collaboration tool with several built-in capabilities that are ideal for sharing a design system. Specifically, versioning, change history, and conflict resolution. You can use additional tools like Git Sketch Plugin to take advantage of GitHub’s visual diff features.</p><p>If your team has development resources you can use GitHub’s API to customize your workflow. For example, if you use Sketch templates, you could automate keeping your local templates in sync with the ones stored on GitHub.</p><h4><strong>Cons</strong></h4><p>GitHub was designed for software development teams. As such, it includes many features that your team will never need to use. Meanwhile, the most useful features have more technical details to worry about than with products like Dropbox.</p><p>Further, in this post we’ve assumed your team is storing their design system in a Sketch master file. Using GitHub to share and update this file does not address some key issues:</p><ul><li>There can be performance issues when working with a large Sketch file.</li><li>While GitHub prevents you from accidentally overwriting someone else’s work, it still requires you manually combine your changes with theirs.</li><li>Unlike Dropbox, GitHub relies on each user to decide when they want to update their local copy of the Sketch master file. It can be easy to forget to do this and end up working with out-of-date design elements.</li><li>GitHub helps you coordinate changes to your shared Sketch master file, but when it comes to working on designs in a separate file there is no mechanism to keep that document in sync with the master file.</li></ul><p>Stay tuned for Part 3 in this series [Update: Here is <a href="https://blog.brand.ai/how-to-share-a-design-system-in-sketch-part-3-invision-craft-and-brand-ai-660bcc79ec67#.y6jqgydhk">Part 3</a>.], where we’ll discuss using <a href="https://brand.ai/sketch">Brand.ai</a> and <a href="https://www.invisionapp.com/craft">Craft</a> to share your design system and further automate your workflow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84a7bc3973cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/how-to-share-a-design-system-in-sketch-part-2-github-84a7bc3973cd">How to Share a Design System in Sketch, Part 2: GitHub</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brandisty is joining Brand.ai]]></title>
            <link>https://medium.com/brand-ai/brandisty-is-joining-brand-ai-ff4f07d45a8d?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/ff4f07d45a8d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[branding]]></category>
            <dc:creator><![CDATA[Brand.ai]]></dc:creator>
            <pubDate>Wed, 30 Nov 2016 07:56:40 GMT</pubDate>
            <atom:updated>2016-11-30T07:34:04.916Z</atom:updated>
            <content:encoded><![CDATA[<p>We’re excited to announce that Brandisty is joining Brand.ai!</p><p>Over the last couple months we started having conversations with Michael and the Brandisty team. It was obvious from the start that we shared the same vision for how brands should be managed and distributed internally and externally.</p><p>Brandisty provides an impressive set of services for managing brand resources, from logo validation to an API for brand assets, and have helped support thousands of brands large and small.</p><p>Together we’ll offer a unified platform that seamlessly connects designers, developers, project managers, marketing and even the CEO through simple but powerful tools, allowing brand assets to be distributed directly to the products each already uses every day.</p><p>Ehud &amp; the Brand.ai Team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff4f07d45a8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/brandisty-is-joining-brand-ai-ff4f07d45a8d">Brandisty is joining Brand.ai</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Connect a Design System to Your Development Workflow — The Problem]]></title>
            <link>https://medium.com/brand-ai/how-to-connect-a-design-system-to-your-development-workflow-the-problem-f4b488a94e8a?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/f4b488a94e8a</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Amit Halberstam]]></dc:creator>
            <pubDate>Sun, 27 Nov 2016 08:27:04 GMT</pubDate>
            <atom:updated>2016-11-27T08:27:03.955Z</atom:updated>
            <content:encoded><![CDATA[<p>Robin started work as a UX team leader in a web startup. He was hired because the application user interface was a mess — it had hundreds of distinct colors, typography styles were all over the place, and the ‘trash bin’ icon had seven different versions. The UI code was bloated, slow and unmanageable.</p><p>It was time to start working on a re-design, only this time, Robin knew what he needed to do — build a <a href="http://styleguides.io/examples.html">design system</a> first. Along with the rest of the design team, Robin spent weeks specifying and documenting the different visual aspects of the system — arguing about colors, icons, and UI components, until everybody was finally happy. And the redesign was a success! Pages were rebuilt according to the design system principles, everything looked consistent, neat and clean.</p><p>A month passed, and the design system evolved: colors were updated, icons changed and UI components added. But in the real world, the application started deviating from the design library. Robin started seeing old colors that were not updated correctly and typography styles he did not approve. He kept sending emails to design and development team leaders asking them to fix things, but fixing inconsistencies was never a real priority for them.</p><p>Six months later, the old design system website was dead. As the actual product drifted further and further apart from the design system, people stopped using it. Most team members couldn’t even remember it was there.</p><blockquote>Building a new design system is not easy, but the real challenge is keeping the design system relevant as the product evolves.</blockquote><p>One of the root problems in maintaining a design system is the disconnect between the development workflow and the design system.</p><p>In this post series, we’ll take a close look at where things tend to break down and, in turn, how to prevent it from happening to you. Each post will cover a set of issues that are inherent to each asset type:</p><ul><li><a href="https://blog.brand.ai/how-to-connect-a-design-system-to-your-development-workflow-1-4-colors-6d8283edd571">Colors</a></li><li>UI components</li><li>Fonts &amp; Typography styles</li><li>Icons</li><li>Images</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4b488a94e8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/how-to-connect-a-design-system-to-your-development-workflow-the-problem-f4b488a94e8a">How to Connect a Design System to Your Development Workflow — The Problem</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Connect a Design System to Your Development Workflow (1/4)— Colors]]></title>
            <link>https://medium.com/brand-ai/how-to-connect-a-design-system-to-your-development-workflow-1-4-colors-6d8283edd571?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/6d8283edd571</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Amit Halberstam]]></dc:creator>
            <pubDate>Thu, 24 Nov 2016 14:28:04 GMT</pubDate>
            <atom:updated>2016-11-30T16:26:49.937Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is the first part of a post series about connecting design systems to development workflows. Read more about the problem </em><a href="https://blog.brand.ai/how-to-connect-a-design-system-to-your-development-workflow-the-problem-f4b488a94e8a"><strong><em>here</em></strong></a><em>.</em></p><p>Connecting design system colors to your development workflow is key to keeping them in sync with your application over time.</p><p>The first important decision you’ll need to make to successfully achieve this connection is between two methods of using colors in code: hard-coded CSS hex values, and CSS variables.</p><h4>Hard-coded CSS hex values</h4><p>Your team now has a design system, and colors are neatly documented in a website:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*rtMcyOSfa4xs-i84O4czlA.png" /><figcaption>Taken from <a href="https://rizzo.lonelyplanet.com/styleguide/design-elements/colours">Lonely Planet’s Rizzo style guide</a></figcaption></figure><p>As you can see in the example above — the website even makes copying hex values easy (just click to copy!). This plays well with the most natural way for developers to use colors in code — just use the hex values directly in CSS rules:</p><pre>.warning-text { <br> font-weight: bold; <br> color: #fa5e5b; <br>}</pre><p>It’s easy for a developer to sample a color from a mockup, or copy the hex value from a style guide, and paste it in code, without thinking about it. It takes seconds.</p><p>The colors are all in one place (the documentation website), the speed and simplicity benefit here are significant, which is why hard-coded values are still commonplace in many code bases. This is great, right?</p><p>Well… no. Despite the short-term productivity gain, copying hex values from the design system into your CSS code sets your team up for despair in the long run:</p><ol><li>It’s impossible to keep hard coded values in sync with the design system. A color change in the design system entails manually updating the code in many places. In practice, it’s impractical to find all the locations in the code that need to be updated, and some instances are likely to be missed, creating inconsistencies.</li><li>Hex values are not human readable (when looking at the code, most people can’t immediately tell which color #fa5e5b stands for). This often leads to mistakes and miscommunication.</li><li>It’s hard to get an overall picture of which colors are used in code, so it’s hard to catch errors or inconsistencies between the design system and code.</li></ol><h4>CSS variables</h4><p>The immediate alternative to using hex values in code is representing the design system colors in a CSS variable set, using a pre-processor such as Sass, Less, or the proposed CSS variable spec:</p><pre>:root {<br> -warning-color: #fa5e5b;<br>}<br> <br>.warning-text { <br> font-weight: bold; <br> color: var(—warning-color); <br>}</pre><p>Using color variables solves the problems mentioned above:</p><ol><li>The code is easier to update and maintain — when the design system changes, just change the variable values in code and the color changes across the app. Old colors can’t come back to haunt you.</li><li>It’s readable — “warning-color” is easier to understand and build business logic with than #fa5e5b.</li><li>If you place all these variables in a single file (which you should!), you can get an at-a-glance view of the state of UI colors in your app.</li></ol><h4>Keeping the variable list in sync with your design system</h4><p>Maintaining a list of color variables (development world) separate from the design system itself (the documentation website, designer world) is often a source of friction. Here’s why.</p><ol><li>Developers, which are responsible for code and hence for the color variable list, don’t know when a color was updated in the design system or don’t prioritize keeping the code up to date with every change. They’re busy working on complex business logic, and each color update requires productivity-squashing context switching.</li><li>Manually updating hex values and variable names from one source of truth to another is error-prone and slow.</li></ol><p>In some workflows, designers are responsible for updating the code color variable list, instead of developers. To avoid setting up a development environment in each designer’s workplace, and teaching designers how to create a branch in git (branches will usually be needed for testing purposes), a common solution is using GitHub’s code editing / pull request UI to do it. It’s simple enough for the entire team to use:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fc1sHf0cSSOG6Pu8i5vdjQ.gif" /></figure><p>If you define the variable file as the source of truth (by giving designers control of it), you can even build the design system documentation website so that the colors are drawn from the same CSS the app is built with. This way it’s easier to keep both in sync.</p><p>A second approach, possible with tools such as <a href="https://brand.ai/">Brand.ai</a>, is having the designers define the colors in a dedicated service, that exposes color data via a dedicated API. This way, colors are available to both the documentation website <em>and</em> the CSS variable file. No need to sync between the two manually!</p><p>For example, if you define an Atomic Design system using <a href="http://patternlab.io/">Pattern Lab</a>, you can automatically sync Brand.ai colors and document them (see Brand.ai’s <a href="https://github.com/brandai/starterkit-mustache-brandai">starter kit</a>).</p><h4>Mockup hand-off and colors</h4><p>When passing annotated mockups between designers and developers, it is important for the color annotations to refer to variables rather than hex values. In fact, using hex values in annotations can encourage developers to only use the hex values in code, which breaks apart from the system and makes the code difficult to maintain, as mentioned above.</p><p>Design hand-off tools such as <a href="https://zeplin.io/">Zeplin</a> allow you to define a color palette as part of a project and annotate artboards so that variable names are available to developers consuming the design.</p><h4>Dealing with multiple platforms and formats</h4><p>Up until now, we assumed that color variables come in just one flavor — either Sass, Less or CSS variables. In practice, many projects use multiple styling frameworks.</p><p>For example, a large project may include a web app using both SASS and LESS, as well as a client-side charting library that consumes JSON color data, a server-side rendering library using YAML key-value colors, a native iOS app that needs RGBA colors instead of hex colors, and an Android app that needs 8-bit hex colors in an XML format.</p><p>Manually keeping color variables in sync across multiple data formats is exponentially harder. Neither designers nor developers can handle such a task manually. Often, some data formats just get updated less frequently, and the color inconsistencies creep back into your app.<br>Once you need colors in more than one format, you’ll want to look into these solutions:</p><ol><li>Use <a href="https://github.com/salesforce-ux/theo">theo</a>, an open-source library by Salesforce. Theo allows you to define color palettes in JSON or YAML formats and then provides a set of gulp plugins to transform and format the colors into a wide range of outputs. You can use the same methodology described above — you can either have the designers or developers maintain the origin files, and place them either in source control or a shared folder, to be pulled by gulp as part of the build process.</li><li>Use <a href="https://brand.ai/">Brand.ai</a> — define colors using a web interface (or directly from Sketch), and get access to a data export API that allows you to consume the colors in a wide range of formats (Sass, Less, Stylus, YAML, XML, JSON, iOS and Android). Fetching the colors via API can be automated into your build process using Grunt, Gulp or a simple shell script. <a href="https://brand.ai/acme-demo-new/style/applications/data-export?ref=hp">See an example here</a>.</li></ol><p>Follow us for the next parts in this series, where we discuss connecting design system UI components, fonts &amp; typography styles, icons and images to your development workflow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d8283edd571" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/how-to-connect-a-design-system-to-your-development-workflow-1-4-colors-6d8283edd571">How to Connect a Design System to Your Development Workflow (1/4)— Colors</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Javascript Spell Checker for a Custom Dynamic Vocabulary]]></title>
            <link>https://medium.com/brand-ai/javascript-spell-checker-for-a-custom-dynamic-vocabulary-993acb8f67ff?source=rss----b925bcd35eed---4</link>
            <guid isPermaLink="false">https://medium.com/p/993acb8f67ff</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Kim Major]]></dc:creator>
            <pubDate>Mon, 14 Nov 2016 08:02:32 GMT</pubDate>
            <atom:updated>2016-10-26T08:08:03.485Z</atom:updated>
            <content:encoded><![CDATA[<p>Every company has a unique writing style in its products, marketing material and customer support. To standardize its style and help communicate with a consistent voice &amp; tone, companies often set up a writing guide.</p><p>A writing guide serves as a great reference, but requires context switching when writing, and is disconnected from spell checkers that help in real-time.</p><p>I will walk you through bridging this gap by creating an online vocabulary, using the new Language feature we just introduced on <a href="http://brand.ai/">Brand.ai</a>, and validating some user-input against it. I will first walk through the steps, but a link to a GitHub repo with a working sample is available at the bottom of this post.</p><p>The first step is to create a vocabulary that we can access. For this post I created a <a href="https://brand.ai/samples/primary-brand">sample design library</a>. A design library can contain language rules in addition to other assets such as logos, typography, images, components etc. The sample design library is public and can be viewed by anyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*TdkPKmYnUQ69LQ7G95t7uA.png" /></figure><p>On the design library page the Language link will scroll to the language section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*wF7-__nN4wJSL7UBAr3f-Q.png" /></figure><p>If you just created a design library and you don’t see a Language link, enter edit mode, by clicking the edit toggle in the header, and add a common words list or a words to avoid list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*fZr_Kak2mSS1XuxIB7rRMQ.png" /></figure><p>A vocabulary is a great companion in and of itself, but as I mentioned, it requires context switching between writing and validating against the vocabulary. At Brand.ai, we created an add-in that integrates a design library with Microsoft Word and it is available from the <a href="https://store.office.com/en-us/app.aspx?assetid=WA104380506&amp;sourcecorrid=a9f25613-b4af-470f-b3ef-018435613ebf&amp;searchapppos=0&amp;ui=en-US&amp;rs=en-US&amp;ad=US&amp;appredirect=false">Office store</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*k-PTrKj4VEQFELY_YOn8xg.jpeg" /></figure><p>However, we can’t anticipate all use-cases, so let’s go ahead with the validation of <em>any </em>user-input in a regular web app. This could for example be support tickets, comments or just about anything.</p><p>The following code snippet from the sample will validate any text you pass it against the design library above and render a list of issues found.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eb423d881cf49e6c4cb48c1565cd46e0/href">https://medium.com/media/eb423d881cf49e6c4cb48c1565cd46e0/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qwiVl918_ZxU2sVhK18biA.png" /></figure><p><a href="https://github.com/brandai/brandai-language">https://github.com/brandai/brandai-language</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=993acb8f67ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brand-ai/javascript-spell-checker-for-a-custom-dynamic-vocabulary-993acb8f67ff">Javascript Spell Checker for a Custom Dynamic Vocabulary</a> was originally published in <a href="https://medium.com/brand-ai">Brand.ai Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>