New library sharing - combining linked with local

Question

Hi,A new way of sharing libraries...is quite nice. Seems easier to manage. But...Previously we had an opportunity to see local as well linked components in the same panel.Right now they are divided - linked/activated library and local. Local contains locally made components and linked, but only already used ones. It's quite annoying when I have to jump through different libraries, especially when you have complex design system with Core elements, Team elements and local elements. The second problem is with enabling libraries...globally? Why? Why?If will have single big product...it will work fine.But if I will have like 10+ products, with the separate design systems - it is a disaster. Right now I have to work with the local library, jump into list full of different libraries, search for a proper one...sick. If it will stay this way, I will have to push everything into Figma...because it's totally unusable at this point. Fix it or bring old components managing system back...was way better.

Atul_Saini · Answer

Hi Amadeusz,

Thank you for reaching out. I really appreciate your feedback about CC libraries integration into the Design system. I'll share it to the product team. However, I'd like to share my personal opinion about this new system.

It's true that we had local and linked components on the same panel. So, what has changed now? With the new system, in addition to all the local and linked components (Document Assets), you can access other libraries from the same panel.

More options may lead to confusion. However, if you had to add assets from 4 different documents, you'd have a huge list of components, fonts, and character styles. Earlier there was no way to organize them in the assets panel. Now with CC Libraries integration, you can create groups within the libraries, and also view by type. This allows you to cherry-pick the object which you need, unlike flooding all the assets from the linked document which you might not need at the moment.

While managing Libraries you can disable or even unpublish the libraries to avoid confusion while working on a specific project. Eg. All the libraries besides XYZ project Libraries are turned off.

This is definitely a new experience and will require some curation effort from your end. Eg, You might want to create groups based on your need for individual libraries/projects. Like for Primary fonts, secondary fonts, graphics sets, and probably groups based on different pages. Once you put yourself through the onboarding process, you might get fond of it.

This is my opinion about CC libraries integration with Design Systems. I'd request you to invest some time curating your libraries and write back about the experience.

Post away!

Atul_Saini

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded