We want to bring back Feeds.
Problem
People need to understand what is new within a certain context, or across their whole node.
Solution
(re)introduce a news feed page that shows all activity across the app. Add this to the main navigation sidebar next to library. It should be called "All Activity" to remain consistent with the "Activity" panel of each document. For now this page will just include the feed. Eventually it should support some kind of filtering/tabs like we have in Library.
The activity panel should show all activity of that document plus all children documents.
Missing Features (Aug 15th)
Web Feed. ( @Eric Vicenti )
Go to Full Discussion Link
Making every element clickable ( @Eric Vicenti )
High Fidelity Design ( @horacio )
Mentions Feed API is ready @Julio
Feed Types
We have the following four Feed Types:
Node Feed: See all activity that is visible on this node. It has its own menu item above the Library item.
Account Feed: See all the activity that this person has done on this node, across all sites. The account feed is location on the Contact page.
Site Feed: See all of the activity that have happened in the context of one site. The all activity panel from the home.
Document Feed: See all activity in the context of one document.
Feed Items
Issue: Duplicate Feed Items
We should make an effort to reduce duplicate feed items. For example if you're looking at doc A and it has children docs A1 and A2. When A2 introduces a citation on A1, there are multiple feed items generated. (A2 was edited, and A1 has a new citation). Maybe in cases like this we want to intelligently reduce the number of feed items that are shown from A. But only if we have an intelligent way to combine or summarize them.
API Support
We will probably need some additional API support to make this possible. We need the ability to filter down to a specific site+path so we can generate the activity panel for each document. Also we may need to introduce additional feed event types, for example an event when somebody makes a comment, so that we can see those comments in the event feed when we are filtering down to either the target document or the author account. (This gets even more tricky when the signer does not match the author)
Hopefully @Julio will have bandwidth to take on this project.