Hi.

I was literally just on a session with A.J. Atwood on the 24 Hours of UX conference wherein a guy shared his screen that had BOTH downloadable assets AND colors in the artboard AND the character styles, so something is not right.

Hey Jodi,

We treat layers marked for export as image assets and donot list the colors and character styles contained in them in design specs. I'd like to understand this usecase better in order to support your request. Can you please elaborate on why you want the colors and charcter styles from your image assets ito be listed in the spec links?

To get you unlocked rightaway, I suggest you try this workaround. Right click over the desired element to see a mini-list of all layers present at that point. Then select your desired layer to see its properties.

That said, we have in our plans to provide all the colors and character styles in the assets panel as variables through design specs. This will land in design specs pretty soon .

Let me know if the above suggestions help to get you unblocked.

I've just spent TWO HOURS with one of your support reps because I could no longer see the color palette info for my artboards when I selected them in Design Specs view online. At the end of the TWO HOURS (during which I had to share my computer with him so he could try to see what the issue might be), he told me this is the expected behavior because the colors had been added to the Assets panel and I'd marked my assets for export (as you do, so the developers (devs) can download the assets they need).

In other words, only one of two options is available: either you can have the colors (i.e. all the colors used on an artboard) and character styles visible in the Design Specs OR you can have downloadable assets available for your devs. BOTH CANNOT EXIST! I find this ridiculous! Clicking on an item gives you its color and/or character style information, true, but that’s not good enough. We need the palette and styles all in one place and to have downloadable assets.

Either make it so both can exist in what you've built or do as another person suggested (https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/19588753-assets-artboard-should-get-created-automatically) and automatically create a separate artboard which will be home to all assets in the project (not just assets on a page-by-page basis because that gets confusing, as another person mentioned: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/35206633-export-assets-from-design-specs-we-need-a-better).

My devs need both. It seems absurd to have to create a separate file for the devs where all of the info they need should be in the project itself! I have to create a separate project (which means a separate link) just so they can have access to what should already be part of the same project.

(Side note: Having a separate artboard might sort the problem of having SVGs with the same class names as mentioned here: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/17817826-export-svg-with-inline-styles)

Thank for responding. For example when developer need assets in Design Spec they must click on each page on artboards and download. But when we have a lot of artboards with same assets and we don't need to include for all page because link will take more time to load and update. It's not easy to find out which page has assets include. I think if I open Design spec link and I can see all assets that include in project.