Being able to share the assets when we are several UX/UI working on different files for the same project became essential. It is the best way to ensure style guidelines are respected and coherence of the product is guaranteed.
As of today, the most common solution is to store all the components in a big file that needs to be downloaded by the team. Any time someone updates or changes a component he/she needs to warn the rest of the team and re-send the new file for everyone to download… not very convenient right ?
In order to solve this issue (and to pursue my quest of discovering the best methods to work in atomic design), I decided to start looking into shared libraries… and ended up fully deep diving into it!
Adobe shared libraries: Introduction
Adobe libraries enable several people who work on one project to use the same assets. These assets act as symbols or dynamic objects and once drag & dropped in a document, they remain linked to the library. Any update of the asset in the library will automatically update all the occurrences of it.
You can show the library by clicking in the tab “window / libraries”. The library supports colors, texts’ styles, paragraphs’ styles and assets (images, icons, components…).
The shared library becomes the single point of reference for your team, always up to date and shared between all the designers.
More about Adobe CC libraries