-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistent Social Share tool #321
Comments
DPA discussion [Laurel] Request from HS R&L as well (deals and bundles page): opportunity to explore together Next steps
|
It's been tough to find objective research on how much social share tools are used. This post from 2018 states:
I've contacted Farhan of Daily Hive and he's looking into his site's social share analytics. I'll update this if he gets back with numbers. |
Problem Statement
Recommendation
On desktop, the social share tool appears vertically on the left hand side of the article and scrolls with the user. On mobile, the bar appears horizontally, pinned to the bottom.
This bar allows the user to share content easily on their social networks (facebook, whatsapp, FB messenger, wechat, twitter), as well as simply copying the URL itself. It opens a new window with the respective social network's draft panel open, the content prepopulated with the article headline and link.
Daily Hive uses the addthis.com service for this functionality, in case that's worth studying for further reference.
The TELUS Digital blog uses a block that comes close to this functionality (see https://www.telus.com/en/digital/blog/automated-accessibility-testing-TELUS for an example, right hand side), but there are several issues with it. It's not vertically oriented, doesn't scroll with article, lacks some popular social channels, and looks not like a social share tool but instead like the article author's social bio links.
NOTE: Brand Experience pages are looking for a prominent social share tool because our primary KPIs are awareness and engagement, hence the importance of having people share our content. We're a bit different than the other pages on T.com, where all that is probably secondary to ecomm conversion.
Design intent
(This space is intentionally left blank. The motivation and design intent go here.)
Designs
Acceptance criteria
This section is intentionally left blank. See story writing process.
User stories
(This section is intentionally left blank. User stories and acceptance criteria go here.)
Example:
Scenario: Displaying the component
Given text is provided
Then the text is displayed as a child
And the text size matches core-text
medium
Out of scope
(This section is intentionally left blank. Features or items that were deliberately left out of scope during design intent or may be mistaken as within scope are noted here. Link to related issues if possible.)
Meta
The text was updated successfully, but these errors were encountered: