Publish Character Style Names in Design Specs
When you are working with many different fonts it's handy to name them to keep check of what you are working with. However when uploading the design specs to hand over to the developer, it lists the font styles WITHOUT the custom names.
Please can you upload the style names too?
Maleeha Afzal commented
Hi. The font names only appear if i apply font style.
However if there are some overrides (e.g in the style heading1, I override color to grey) then font style name doesn't show in inspector. Can you work on this as its critical for development
This appears to be fixed, possibly. I was just troubleshooting with my designer and she had to relink the character styles to the text that she had. I reloaded the document and the custom names loaded. Hope this is working for you all as well because this has made me such a happy little dev :)
I still don't see this feature while doing the hand off to developers .
Can you please update this feature ASAP?
Please update on the status of this. I do not see this feature as completed!
Dean Christopher commented
I see this is tagged as Feature Complete. Can you advise on whether the ability to publish Character Style Names and have them accessible in Dev mode is possible?
Big problem for me to - Please fix this
Gerald Wildmoser commented
Absolutely needed functionality! It would be a great facilitation in communication with the production teams.
Does not seem logical that the custom names and colours do not get pulled through for the developer?
BIG VOTE TO CHANGE that please
Simon Fairweather commented
We ran into this issue today. Please add this.
How many times can we upvote this?
Richard Pearce commented
This would be useful for all platforms, but currently, I'm working with Material Design layouts for Android, and the mobile developers find it easier to work from the style names used by Material Design & their development platform.
I realise I could rename the type layers in my prototype to the name of the style, however this leads to a less-usable prototype for the designers. It also seems daft that we should have to do this, having gone to the effort of setting up and naming styles for this purpose.
Publishing those style names into the published spec that the developer uses would be the obvious solution to this.
When I rename my Charector Styles and pass to developers, they are not able to see the renamed styles when inspecting the prototype. I would expect that when they click on a charector its Renamed Style Name would show in addition to the Charector spec (font name, size, etc etc).
This would save Developers tones of time in project with complex Style guides.
Jon Coates commented
It would speed up handover time from UI to Frontend development to no end!
Nils Fagergren commented
This needs to be adressed as soon as possible, thanks!
Adam M Babkes commented
We take the time during design to develop a cohesive set of related character styles and name them for our developer to use. In the current setup, there is no way for him to see those style names which is very inconvenient. Ideally you would make it visible in the properties panel when the text is selected in Share for Development. This is a really important feature and will help in our design / development "handoff" making it so much more efficient.
I suggest displaying the names of the assets in a way that is more readable. Developers are interested in seeing the name of the color/character to quickly match to their code, so please display the names at side.
That constant mouseover to check names is not cool, but even worse:
CHARACTER STYLES DO NOT SHOW NAMES AT ALL (on spec).
Make this available please.
In conclusion: please rethink the assets displaying a little better. thanks!
Same problem! files with lots of font styles and we can not use it with the developers because this information doesn't appear when sharing with them.
Please, solve this soon