Settings and activity

100% Agree - Linking assets via Adobe's cloud does not work for Enterprise clients due to internal security measures.

Need the ability to link documents locally, a library file or from a internal server.

Adobe XD, listen to your users on this. You forcing the "cloud" on all users is a losing strategy. Many enterprise users can't afford to send all files and versioning to you and your "secure" systems. We use GIT and need full control over versioning and document ownership.

FIX THIS!!!!!!!!!!!!!!!!!!!!!!!!

+1

Disappointing that this still isn't addressed as part of May 19, 2020 release

The current design and implementation of XD components is absolutely infuriating and horribly inefficient. Way too many bugs right now and almost certainly any file with complexity will lead to orphaned assets, multiple references to the same asset and source document .xd file for assets that are hard if not impossible to remove or relink.

If there was ever a time, situation and urgency to listen to your users, now is that time. Please fix your component management or lose users to other platforms that allow management of components in more efficient ways that doesn't waste our time and effort. It's a nightmare right now and the effort and time required to clean up your inefficient component implementation is more work than it's worth.

XD Team,
This must be fixed ASAP!!!!!

This feature is long overdue and getting to be incredibly frustrating managing orphaned instances within and across documents. Adobe if you actually listen, this is a must have feature!!!!

To say this is ".. as designed.." means it's now time for a redesign...

I believe Adobe XD has designed themselves into a corner with the way their components "work" or lack thereof. Managing components within and across documents has gotten to be a full-time chore right now and if they don't improve it will be losing users to Figma.

Still waiting for a better solution to this problem. Please provide better tools for managing components and unused objects etc..

+1

I absolutely agree with this statement from thomasbricker:

"Yes, there should definitely be a way to "clear" all unused Assets and Symbols from a document.
Its too confusing to wade through all of the Assets and Symbols that build up."

Hovering is not an efficient way of solving the issue of many unused or orphaned components and elements etc..

+100

+1

I absolutely agree with this. However, there is a partially working solution right now that already exists for Font Awesome icons. Currently when a text box is active and has Font Awesome as the font to be used you can type in the shorthand name of the icon and it will auto populate the icon for you. Subsequently as a result of this it shows the shorthand name in the bottom right "Content" area instead of an empty font slot. (See image attached). Also, this short-hand text doesn't help specify the actual type / style of the icon e.g. (light, regular, solid) so additional information is required to "help developers drive better consistency for end product if using an existing design system" etc..

The above described is somewhat helpful, however what would be most helpful is if:

1. It also added the ability to comment uniquely on each asset (Dev notes) as you've described for developers to see (Additional information) when selecting an element in spec mode

AND

2. Also show the actual class name text for developers to see and reference with their css files in the code-base e.g. ("fas fa-filter")