Organize assets panel objects (symbols/components/colors/character styles) into folders
Would love to organize symbols into folder for easy accessibility. I spend too much time looking through symbols into one library.
This is something we are planning to do! Stay tuned for more details.
Florian Purchill commented
This ruins the whole experience users have with Assets. The Assets panel is a total mess all the time...............
PLEASE do this. It would make life so much easier! It's nearly impossible to create an efficient design system without something this like because otherwise you just have a list of assets that is a mile long and you can never find what you need :)
Christian Tewes commented
Come on Adobe Devs, this is a low hanging fruit but will help all xd users, that do more than just onepagers with your tool. You speak about design system but dont have folders for better structure and organisation. Seriously?
Christian Tewes commented
We use XD for big projects and clients. Especially when using well organised design systems, the Element List gets higher and higher.
I just want to create Folders (and subfolders) like shown in the screenshot.
This feature and maybe the addition of unlimited or - better - multiple Canvases would fit perfectly into our workflow. Otherwise XD lacks in overview and style-organisation. Sketch does a very much better job in this case, but please don´t make me switch back.
This is a great ideas, please add this to the to do list immediately!
Really longing for these features, and it would be great if you let the community know what you are working on, so that we can follow the progress and plan our own work according to that. It is very hard to make a fully working DSM on an enterprise level working blindfolded not knowing which features will be available when.
- Custom folder/category structure for components/styles that can be fetched by e.g. Diez, Haiku or similar dev-tools. It is impossible to structure your components in a meaningful way for collaboration.
- Option to search for components only, not including colors.
- Option to share specific tokens/styles and not only an entire library with teammembers.
- Do not automatically place "linked components" within the components area of the file you are copying to, if you copy assets from one file to another. The assets ought to be visually seperated and afterwards you can choose to make a local component. It gets really messy .
- Shareable artboard templates in components / Pages from a master document
- Multiple component libraries with sublibraries pr. file. e.g. "Web", "iOS" and "Android" where all three mentioned also have "dark" and "light" sublibrary e.g. in a master document. managing 3 different files is cumbersome and errorprone. Consistency, speed and collaboration is key.
- Shared components across said UI-kits. - A lot of UI components are the same across platforms.
- Possibility to be granted update rights for shared links if you are not the owner of a document.
- Optimized color management, extract colors from file, find and replace. Posibility to choose to "overwrite" a color. That automatic merge is annoying.
- "Hightlighting" of assets, components etc. is barely visible when you have a huge artboard or document. Something simple as navigation through where they are used would be helpful.
I believe that many of us working in UX/UI and closely with DEV in an enterprise setup, are lacking the above on a daily basis.
This should be NATIVE features and not handled by a sea of plugins that require login or payment to 10+ 3rd party services. Please consider keeping your eco-system more lean.
I know you don't reply on requests on facebook. but you should consider engaging in conversation there instead of just sending everyone in here on Uservoice. An open dialogue would be much appreciated.
Just like the one suggestion above. This would be great. It can get chaotic otherwise. Also please add keyboard shortcut to collapse all open layers/group/folders like you do in photoshop.
Jeff Chester commented
It's absolutely insane to me that this feature was first requested two and a half years ago and still has not been implemented. It makes larger design systems impossible to work with. If XD ever wants to be taken seriously as a competitor to Sketch or Figma it desperately needs to step up its game when it comes to design system management. One gigantic asset list with all components and no way to group them is such a terrible user experience, I don't know how this made it past user testing.
Does anyone from Adobe actually read these requests? This one has 740 votes at the moment and 159 comments from people who desperately need this functionality. What are you spending time developing instead of this?
Samuel Humeau commented
It could be great if we've been able to create subfolders in the assets panel to sort them
I would love to see a more customizable asset panel as well! Sort of like what's done with Adobe Spectrum!
From what I see this sounds like you’re looking for a way to better nest components and have some kind of nested structure to find and maintain them? Sketch does this by using backslash to create a deeper structure and put items into sub-categories. Not sure if this is possible with XD right now but would be super helpful.
Kelleigh Sedate commented
This is the ONLY reason our team does not use Adobe XD.
Matt Brogan commented
No presets. Just a better way to showcase the structuring for design system components within Xd. I know sketch you can add components to a list like tables, image gallery and many more. At the moment my design system is getting a little out of hand all the Icons & Symbols are mixed with other components. For me I want to start a 'booking flow' components as these are very different to a landing page components however the way these are all currently handled is getting very messy.
A way to create folders for components
Being able to organise assets into 'buttons' 'icons' 'nav' etc would be really handy. At the moment I have a huge list that is a bit painful to search through even when I have given things a naming convention
Matt Brogan commented
A clients Design system is reaching a phase 2 and we need a library for components.
Icons / Cards / Tables / Gallery ect
I just want to be able to see what assets are used where or what assets are not being used so it can be deleted. more like how styles work in Indesign.
Matt Pearce commented
When I'm working on large projects i have a lot of components, it would be good to create folders to put my assets/components in to organise things better.
I find it really hard to search for a layer or a component via the Assets and Layers panel. There's a search to make it easier to find what i'm looking for, but what if i don't remember the name? If there's a way to logically group all components or layers, supposedly grouping them by artboards similar to Figma's frames and nested frames, that will be a really great and enjoyable designing experience!
So for example i created an artboard for a Dashboard screen in an Android app and name it likewise. This "Dashboard" artboard will appear as a group in the Layers panel. And inside this parent group there will be other child groups nested together such as header bar, body, bottom bar. They will all appear in a hierarchial folder-tree like in the Layers panel.
And inside each child group there will be components and items shown. Neat, huh? This will make it a lot easier for me to find what i'm looking for. And later i can share just the particular artboard or even save it as a new file and send it to my colleague.
Parent group (artboard), similar to Figma frame
Child group, similar to Figma nested frame
Share artboard (choose one or more artboard to share, easily)
Save artboard (choose one or more artboard to save as a new file)
sometimes it gives characterformats, where you can say its a group in example: Text, Text attention, Text links etc.
Now when you want to change the fonts you must go in every single character format and change the font. it would be cool you have a undergroup in the characterformats
Adobe, come on - that request should be an easy one for you and large projects are really missing this feature!
Sketch is handling component structure and folders so much better than XD.