Skip to content
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

Review handling of social media share links #4356

Open
StephDriver opened this issue Aug 9, 2024 · 1 comment · Fixed by #4368
Open

Review handling of social media share links #4356

StephDriver opened this issue Aug 9, 2024 · 1 comment · Fixed by #4368
Labels
UX UX related issues

Comments

@StephDriver
Copy link
Contributor

New Feature Request

We currently have three social media share links for articles:

  • Facebook
  • X
  • LinkedIn

There are other social media channels, and with the growth of AI for summarising articles, there may also be other desirable 'share' destinations. Some journal editors may have strong views on which platforms they want to support, and so this may not be a one size fits all situation.

Option 1:

provide a selection of social media share links (which?) from which a custom list can be defined as a setting at journal level.

Option 2:

Reconsider the current three share options and extend this to include other platforms (which ones?) e.g. Bluesky

Option 3

unify the share option so that articles are shared in a standard way compatible with any destination

Context

While working on

This lead to a larger discussion on whether which social media share optoins appear should be a customisable (i.e. a setting). and how this might link in with updating user profiles to allow for a choice of social media handles.

@StephDriver
Copy link
Contributor Author

StephDriver commented Aug 22, 2024

closed due to typo in PR issue link - that PR doesn't fix this issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX UX related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant