8 results found
Reopening the feature request, based on feedback.
“Convert to code” is fairly ambiguous, and I’m looking for more specifics as to what you’re hoping to get out of this. We already have a number of stories that go to specific technologies: HTML/CSS, XCode, Android Studio, etc. I’d like to close this one out in the interest of having more specific export paths.
An error occurred while saving the commentTJ Zafarana commented
We're starting to use this at my company and have had some feedback on the Publish Specs option from our dev team. It appears to be causing more work for them. I believe all the information is there that is necessary for them, but laid out in a way that doesn't make for a fast + seamless build.
They think it would be useful to:
Cut out icons, and use css syntax (aka no tracking icon, use text instead)
Make attributes copy and paste-able
A few changes would go a long way. I think the current build of publish specs focuses a bit too much on the design workflow rather than the code workflow.