![]() ![]() ![]() InVision Craft and Brand.ai allow you to define a design system using Sketch with a dedicated plugin. In this post, we show how moving from sharing a design file with generic file management tools to sharing design data with purpose-built tools makes a design system easier to use and maintain. Purpose-built tools for sharing and working with a design systemĪ central assumption of Part 1 and Part 2 was that a team uses a Sketch master file to represent a design system. *Thanks Nicholas Jitkoff for putting it in these terms. Two products - InVision Craft and Brand.ai (yes, that’s us!) satisfy many of the requirements to making the design system easy to maintain and easy to use. It also introduces complexity and a non-trivial learning curve.Īnd that brings us to Part 3. However, GitHub is not built specifically for design systems, and therefore does little to make the system easy to use. 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. They do little to make the system easy to maintain and use for larger teams or projects. Let’s evaluate the approaches introduced in Part 1, and Part 2 of this series with the above requirements in mind.Ĭloud storage solutions such as Dropbox are useful for a small team, or a small project. Making the system available for non-designers helps drive organization-wide adoption of a consistent visual language. 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. ![]() Editors should be able to share the library outside of Sketch.Editors can annotate changes they make to the design system with notes explaining why they made the change, or summarizing large sets of changes.Editors can easily roll out an update to all clients of the system, and guarantee everyone uses the latest version.Editors don’t have to worry about making a mistake when updating the system, since they can easily roll back a change.Editors don’t have to worry about overriding each other’s work when making updates.Editors can update the design system directly from Sketch.Multiple designers (editors) can update the system.Designers should be able to automatically update existing designs with changes in the system.As Payam Rajabi, 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. Designers should be able to search their design library.As Chris Hall, UX Manager at eBay, says, retrieving a new version of a design library manually is simply not part of a designer’s workflow. As the design system evolves, designers should see the changes reflect in their working environment automatically. Designers should always see the most up-to-date version of their design system.Context switching is a productivity killer. They should not have to switch pages, or worse, browse to a reference site. Designers should be able to view their assets and styles side by side with the design they are working on.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.īefore we delve into the details though, let’s summarize what we’re looking for in a tool for sharing a design system.Īt a high level, such a tool should help make our design system easy to use, and easy to maintain*. Below are the key requirements to facilitate each of these goals. In parts 1 and 2 we covered two approaches to sharing a design system - using Dropbox and using GitHub. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |