Welcome page stub

[cubap]

In support of the Login workflow, an Interface page must exist to send users to who have logged in without a resolvable state to refer them to.

Behaviors

This page is the generic and should be left as simple as possible, but has certain complexities.

When to not appear

If the state parameter from the login callback defines a location, this page is skipped. For third parties, this is an easy way to return to their own app after login. For continuing work or network disconnections, this helps the flow. For sharing, linking, and bookmarking, this allows for restricted links to be readable and not require sharing exciting tokens etc.

It may be useful to allow the user to configure [TODO: Issue for config option] a replacement for the Welcome page based on their user preference.

Users with no projects

Any user without any projects should expect to have more of a "welcome experience". This can be stubbed out for the scope of this issue, but it should be obvious that it has been detected no projects exist. The resulting page should offer some learning options (videos, guides, about pages), places to find projects to start (internal tools and external sites), or links into the start a project interfaces that are most generic or topical.

Users with projects

Similar to the existing 2.8 interface, a user may expect to see their recent activity, last modified folio especially, list of all projects (perhaps with their role indicated clearly), and any relevant notices (maintenance, announcements, changes in groups).

Users will also need to have access to the "start a project" links and help documentation, but this can be deprioritized.

Consider some variance based on last login time or last activity time. A user who has been making changes to the same project for the last month may want that "continue this project" link more obvious. If a user has bounced around a dozen projects in the week, the last modified may not be so important. If a user hasn't logged in or modified anything for over 6 months, maybe going back to something more like the welcome page would be helpful. A user with many non-leader memberships in groups may respond to a "start your own" prompt.

Notes

1. The scope of this issue does not expect all the modules and copy to be perfect and set. Indicate what will be there and just focus on how best to detect the correct state or redirect to a new location.
2. In any case where the redirection occurs, we should consider how to track the redirect and prevent loops from poorly configured Interfaces that keep requesting a login or send the user to broken pages.
3. Language used here is about what the user will see, but more than half the work here is scripting logic. It maybe that the best way to detect a user has no projects is that they have no group membership. Be creative and clever.