Currently we have a ?feed=true route in our web app.
This is inconsistent with our new URL formats such as /my-doc/:discussions
Proposal
Introduce a new /:feed URL format
So the site feed for this site is https://seedteamtalks.hyper.media/:feed
And this also opens up the possibility to open the feed for a specific page. If I want to see whats new with all projects, I open /projects/:feed
Concerns
This is similar but different from the /:activity format because the activity focuses on a single document, while the feed shows you all the things that happen in the whole site or section.
Maybe we should consider :activity/all or something instead.
Also note that the activity page has filters such as versions or citations. This could be handled with a query param but it is probably better to handle as part of the "panel param" because that is sometimes a ?panel= query param, and sometimes is located after the colon in the main path, when the feature is expected to appear in the main panel
Conclusion
While writing this document I realized, I have no idea what to do.
We have talked about moving away from the word "feed"
But in any case, I believe its very important to have "recursive activity" of some kind, so a reader can see all of the recent activity within a site or a section of a site. And definitely, the ?feed=true is an inconsistency in our URL design.
I'm not sure the solution, but I believe we should solve this soon!