"Save to Github Gist": wording confusing

[Fryie]

Maybe it's just me, but seeing the "save to github gist" option, it's not clear at all to me that using this i will end up with a shareable twiddle URL. Maybe "save this twiddle" would be more useful?

[KTKate]

But it should also impart the knowledge of where it will be accessed. I search my gists all the time to find old twiddles I made. Maybe just some kind of explanation of this in a help page?

[vikram7]

"Save to Github Gist" seems pretty clear. Perhaps "Save this Ember Twiddle to Github as a Gist" would be the clearest, but it seems a bit long.

[Fryie]

Well there's at least one person who didn't find it clear (me) ;) "Save this Ember Twiddle to Github as a Gist" means the exact same thing as the current version, so it wouldn't improve anything.

People who use Twiddle want to share that Twiddle so it can be run. They don't want a static file listing that people understand a Github Gist to be. That Twiddles are saved as gists is a mere implementation detail, that's not the reason to click this button.

I propose "Share this twiddle (creates a Github Gist)".

[brianally]

Better, but I think the clearest would be:

Save (creates a gist)
Share this Twiddle
Embed ...

I think most people are comfortable with what they can expect from "share" and "embed" buttons. Telling them that clicking "share" will create a mystery "gist" thing could be confusing.

Also, be unequivocal about the purpose of the "save" button--it saves the twiddle, full stop. Where it saves to is less important but the answer is there as an aside.

[sheriffderek]

I felt pretty uneasy at first about spending too much time on a twiddle for fear it would be saved as a gist, and then again as another, and then another. In general, I kept waiting to save because I wanted to be sure I was at a good spot to take an impression. I didn't' really feel comfortable with where the code would go, and getting back to it. Things felt mysterious. These thoughts are a little whacky, I know... but I still had them, which proves that while it may be the wording, or or may be something else - the confidence you want in a "save" button, is not there.

I also think that the save option is too far away. What about it I click "unsaved" in the header and it saves? I may be clumsy, but I lost my work the first few times with the expectation that it would autosave or something like I'm used to in things like codepen.