656680 - Update collage sharing tweet copy

Status: RESOLVED FIXED

(Websites :: webifyme.org, defect, P1)

Description

[William Reynolds [:williamr]]

The current tweet message copy needs to be updated with the new messaging and encourage more sharing.

Current message: What does your internet look like? Create your own Webify Me collage : @http://bit.ly/mdIMVp

New message: What does your Web look like? See my Webify Me collage and create your own: http://bit.ly/mdIMVp via @firefox

*Note the above bit.ly URL is just an example and should be unique for each user.

I believe the "via @firefox" string is added automatically when we use the related account parameter in query string to twitter.com. See bug 656678.

Note this blocks the string freeze.

Comment 1

[Austin King [:ozten]]

Updating copy to unblock string freeze. Feature not tested.

Note: This copy is duplicated across two templates
ff4/templates/shared/_share.html:      <a href="http://twitter.com/share?url=http%3A%2F%2Fmozilla.com" class="twitter-share-button" data-count="horizontal" data-text="{{ _('What does your internet look like? Create your own Webify Me collage') }}">{{ _('Tweet') }}</a>
ff4/templates/things/_collage_public_tools.html:		<a href="http://twitter.com/share?url=http%3A%2F%2Fmozilla.com" class="twitter-share-button" data-count="horizontal" data-text="{{ _('What does your internet look like? Create your own Webify Me collage') }}">{{ _('Tweet') }}</a>

I've gone ahead and updated only _collage_public_tools.html. This way we have both strings and some flexibility with the implementation, while unblocking string freeze. If we don't need the original string, please update it too.

Comment 2

[William Reynolds [:williamr]]

Commit for comment 1:
https://github.com/mozilla/webifyme/commit/033bba35e97c2bb0b2ac6d79a622c3cbb041f9c8

Comment 3

[Adam Miller]

Added the correct copy to the personal tweet button here: 
https://github.com/mozilla/webifyme/commit/918e61dea5f0de8c9748cf58834f5ec7db050ebb

Comment 4

[claudia // barbarian]

Marking as resolved / fixed as per Comment #3