openlibhums / openlibhums/janeway
Review handling of social media share links
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
New Feature Request
We currently have three social media share links for articles:
- X
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
- https://github.com/BirkbeckCTP/janeway/issues/4353
there was a discussion about updating Twitter to X, and then whether we should also have Bluesky or other social media share buttons.
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing Facebook, X, and LinkedIn share links and the discussion in issue #4353 first. Define which destinations and journal-level configuration are in scope; done means the selected sharing behavior is agreed and implemented with coverage for the supported options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100