Slice entirely relies on the use of Team libraries as modules. This means that to use them correctly, you first need to publish all Slice Figma files as libraries into your Team space.
- Go to Team Projects ➝ New Project;
- Name your project (ex. "New Project");
And drag all library files into the new project window;
Then, open all the files and Publish each one separately;
- Done. Now open any file, verify that your Team library looks like this:
The Core file contains all the styles that are synced with other libraries. This makes global changes to the system super fast. To customize colors:
- Open the Core file. Navigate to Color Styles page;
- Select a Color you wish to change. Use the Edit icon to choose a new color;
- Publish the changes to your team library.
Slice relies on the use of Styles and not components to store the font. This approach lets you reuse styles within other libraries and component instances with a single, unified set of text styles.
- Open the Core file. Navigate to Text Styles page;
- Select font style you wish to change. Use the Edit icon to customize it;
- Make changes to the rest of the styles;
- Publish the changes to your Team Library.
Slice provides a wide range of building blocks, allowing you to combine and use them at your discretion.
Nevertheless, managing such an extensive collection can be tedious. That’s why we have developed Galleries, whose primary purpose is to serve as a mirror for your components.
These files are designed for the fastest possible drag and drop. To use them properly, open a new file tab, and paste the needed components.Gallery files only contain Component Instances from corresponding libraries. This means that to distribute all updates into the Gallery, you must publish changes to your team libraries first.
Naming and Extending
Slice provides you with a reliable and straightforward naming convention that you can easily extend and use with your team through the following principles:
- Always use components category names in each instance. This will improve the Assets menu structure and simplify navigation to the desired component;
- When adding new variations of components, make sure to include them in the Contents group. Doing this will allow you to enable new component override quickly;
- When coming up with names for new components — always use the description of its contents. This approach wins by eliminating confusion and making it easier for users of your files to understand the functional meaning of new components.