DRAFT - Stream page review

[srenault-meeds]

Rationale

The stream page agreggate all the activities shared in spaces the user is member of AND it displays portlet to the right column to show the user there is other informations to check (user activity, gamification, suggestions, getting started, perks and wallet portlet, who's online)

Feedbacks are the following:

• Most of the times, stream page is reworked to display informations list and to remove default gadgets
• getting started portlet is not custom and needs to be updated (outdated use case)
• suggestion propose to users to add contact which is not clear to the user. That brings more confusion than efficiency.

1. Functional requirements

First, we suggest to remove from the stream page the following items:

• current getting started portlet
• suggestions portlet

We suggest the following rework of the stream page to focus the user to its activities from his communities and to important activities:

• A "Pinned activities" list will display the "Hot news" / "Important activities" pinned from spaces he is member of. That way, user gets to know what is important and can easily access to these activities without searching it. In the meantime, hosts and redactors can that way make sure key infos are published and visible.
• A "Trends for you" list will display the most read activities grouped by tags (the most viewed/commented activities related to this tag) in the period (the current month - rolling period). From there, users can click to the hashtag and this will filter the stream to this tag only
• A "Don't miss it" portlet should be displayed finally to inform about current challenges that can be done by the current user. That way, we make the stream page a way to enhance and to communicate about challenges in the organization. Of course, if challenges is deactivated for the user, this portlet is not displayed

In addition to this, we suggest to create a new portlet to replace the getting started one:

• Portlet called "Discovery"
• Portlet list any challenges related to the Discovery program
• Default challenges will be created to help users onboard and discovery the platform
• Once a challenge is done and accepted, then this is removed from the list
• Once the user has done these challenges and they are accepted, the user can close the portlet to remove it
• Once a challenge is added to the discovery program or when a challenge is updated while the user has done all its challenges before, the portlet is not displayed again

2. Non Functional Requirements

• Expected volume & Performance requirements

• Security requirements (Authentication, Authorizations, Audit track / traceability, data retention…)

• Extensibility requirements (Identified extension points, plugables implementations...)

• Configurability requirements

• Requirements related to existing users data

• Requirements related to existing features (ex: Add a button to existing modules...)

• Feature Flag needed ? (shall we allow activation of the feaure on demand ?)

• Other NFR (ex: Use of VueX, Vue, Vuetify)

3. Impacts

• Documentation to update?
• Flag to be set to false the time we deliver all the new portlets

4. Software Architecture

• Security

• Access (GUI, API…)

  • Rest API design (Entry points, domain objects)
  • Portlet Vue & Vuetify, simple portlet, extension WAR ...

• Services & processing

  • Ex: Scheduled Jobs

• Data and persistence

  • Macro data model
  • Persistence layer (RDBMS, elasticsearch...)
  • Use of caches

• Support for clustering

• Support for multitenancy

• Integrations

• Migration strategy

5. Annexes

• Reasoning that explain the technical choices
• Impacts (ex: impact on public REST/Java API)
• References (links...)

[srenault-meeds]

Closed as it will be done in different MIP