In order to prevent users from being overwhelmed by a fire hose of notifications from the hubs they’re subscribed to and from all the other apps connected to Fedora Hubs, we decided to design a filtering system.
If a user sees a type of notification that they don’t find valuable, they can use a dropdown located in the upper right of the notification card to decide how they want to filter out these sorts of posts.
As you can see, there are three different options for how users can block future posts. First, they can decide not to see any notifications that are exactly like the active card – here, the example is design team meeting reminders. The user can also choose to hide all updates from the design-team hub, if that is the kind of content they find unhelpful, or hide all meeting reminders. We hope that with these three options will allow users to gain full control over their notification streams.
Also in this dropdown are the options to ‘save link’ or ‘pin link’. The idea here is that users will be able to bookmark specific notifications they find important. Saving the link will be a private area of the main notification stream, while pinning the link will put it in their library, which is a kind of public reference area. Libraries were initially conceptualized as being a place where team or project hubs can put links to content important for new contributors, but we realized that individual users may also want to collect these references to show to their peers or to new users they may be mentoring.
To complement the ability to filter ones stream, we needed to design the filtered stream itself. Each tab here reveals a different stream of notifications: ‘my stream’ has the contextual filters from above applied. ‘My actions’ is notifications that require action – generally things like approving subscribers, new hub members, answering private messages on IRC, and looking at tickets that have been assigned to you. The ‘saved notifications’ was mentioned above, and it’s where the notifs people explicitly wanted to save will populate. The ‘all’ tab is the firehose of all notifications.
If people want to look at their filters and remove any, they can do that by clicking ‘view filters’, which will open a modal.
I wasn’t sure whether these interactions would be clear to potential users, so I threw together a quick sketch and tested it on one of my fellow Red Hat interns.
Her feedback informed me that while the filtering dropdown was in the usual place, the wording of ‘hide this notification’ implied that it would only hide that specific card, not all cards with that exact overlap of traits. She also informed me that filter management seemed like something that would happen by going to the main settings panel in the upper right corner of the whole page. This issue may come from the fact that the ‘view filters’ link isn’t as visually prominent on my sketch as it is on the more polished design, but her feedback did encourage me to try to make the link as noticeable as possible. Fedora Hubs is still moving forward!