From bug 875062 comment 43: I think that our next step should be outlining 3 A/B tests we can run for placement and 3 A/B tests we can run for button design: For location I suggest: 1) Top of the page under the title 2) Inside the right column TOC, at the bottom, if there is one on the page 3) End of the article (where they are now) For button design I suggest: 1) Current design 2) Logo only, with no heading 3) A derivative of the fellowship design First step on this is designs; second step is the test; third step is deploying the most successful combination.
Created attachment 8585763 [details] 3 styles in 3 positions Here's a screen shot of 3 different styles displaying in the 3 different positions. For the tests, of course, only one style at a time will be visible in one position at a time.
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/ce32e846198d81207898e89fdcfdee8d2658ded9 Bug 1145630: Social Sharing A/B tests Styling for 3 different types of buttons going in 3 different places. Classes: .share .share.share-group .share.share-thin All hidden by default at the moment and need the class .show added to them to display. https://github.com/mozilla/kuma/commit/73d9312edcf3fd5592def9000f0510082ec42220 Merge pull request #3142 from stephaniehobson/bug-1145630-sharing-ab-tests Bug 1145630: Social Sharing A/B tests
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/85f836a4e242185ca9d17ce9627407d874326025 Bug 1145630: Manually activate social experiment https://github.com/mozilla/kuma/commit/8ac8a6539ccb8247ed2a0046736c07a5579a91c9 Merge pull request #3187 from openjck/bug-1145630-manual-social-experiment-activation Bug 1145630: Manually activate social experiment
Making this depend on the bug for storing the shortened urls in the db.
In bug 1182210 we decided not to store the short urls from bitly, because bitly charges extra to preserve the utm_* parameters. So, for this bug we need to change the share urls from short urls to regular long urls, which is bug 1194257 now blocking this bug.