hypothesis / hypothesis/product-backlog
Expanded notifications
- Dominant language
- No language data
- Stars
- 122
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
## Expanded notifications
### Increase user engagement with product and material
### Add option to follow:
- new annotations from group
- new texts annotated by group
- replies from group members to other group members (besides user)
-
### From a user:
>I'm checking back in about notifications. I continue to think they would make it much easier to engage new users of Hypothesis in a group project. The existing notification feature, which tells me if someone replies to my annotation, is important so that I don't miss responses to my own work. But I'm looking for a higher level of notification that would alert anyone in a group to a new article being added, or maybe to any new annotation. (These would have to be optional, of course). I think that's the key to engaging people who, like my colleagues in the fake news project, are willing to create a Hyopthesis account but not sufficiently committed to keep a tab open or remember to check the page routinely.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing notification feature and deciding which group events are in scope: new annotations, newly annotated texts, replies between group members, or new articles. Define optional follow settings and acceptance criteria for each event before locating implementation and tests. Done means the agreed notification choices and delivery behavior are documented and validated.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100