Kits are to Lingo as documents are to Google Docs. They're the "containers" for your design language, and they're also what you share with your team members in order to grant access to your design language. 

You can create an unlimited number of Kits in your Space, and Kits can either be private (only Space members can access) or public (anyone can access, no Lingo account required). 

Creating a Kit

To create a Kit you'll need to be in the Mac app. If you don't have any Kits in your Space you'll be prompted to create one. If you already have a Kit and you want to create another one you can do so by selecting "All Kits" in the Left Rail > Create Kit. 

Hierarchy within a Kit

Inside a Kit there are two levels of hierarchy: Sections and Headings. Sections are displayed in the Kit Navigator and are self contained meaning you can not scroll to another Section of a Kit but rather have to select it in the Navigator.  

Headings are contained inside a Section and also display in the Navigator but they are not self contained, meaning you can scroll between multiple Headings inside a Section. We'll talk about best practices for using Sections and Headings in another article

Kit best practices

How you use Kits will have an affect on how easy it is to find and share assets in your Lingo. Because of this we created a couple simple guidelines that will set you up for success. 

A single design language should be contained inside a single Kit not spread across multiple Kits. 

Let's say you're using Lingo to manage your company's Brand components. We recommend you contain those components inside a single Kit instead of organizing them across multiple Kits because it will make distribution and member management easier. For example if you want a new team member to have access to your Brand Kit you simply have to invite them to one Kit instead of multiple. Also as we roll out more advanced functionality like Kit Versioning, it will be important to have your design language contained inside a single Kit. 

Different design languages should be contained in different Kits. 

Now let's say in addition to your Brand Kit you also want to use Lingo to manage your Sketch UI components for your iOS app. Since these are different design languages we recommend you manage them in separate Kits. This is because often times different design languages need to be shared with different people. Since sharing in Lingo happens at the Kit level your design languages will need to be in separate Kits if you want to share them with different sets of people. 

Of course there are exceptions to these rules, but we've found teams that stick to these rules find their Lingo easier to use and manage.  

Up next: Learn what types of assets can be added to a Kit

Did this answer your question?