Skip to content

Settings and activity

8 results found

  1. 3,311 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    TJ Zafarana supported this idea  · 
  2. 1,809 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    TJ Zafarana supported this idea  · 
  3. 17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    TJ Zafarana supported this idea  · 
  4. 45 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    TJ Zafarana supported this idea  · 
  5. 259 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    TJ Zafarana supported this idea  · 
  6. 694 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    TJ Zafarana supported this idea  · 
  7. 8,057 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    TJ Zafarana supported this idea  · 
  8. 385 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Hi, all-

    “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.

    -Elaine

    An error occurred while saving the comment
    TJ Zafarana commented  · 

    Hi Elaine,

    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
    Export CSS?
    Export HTML?

    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.