[Local-Preview] In-product nudge towards next installation steps (i.e. PoV reference Architecture)

[lucasvaltl]

Is your feature request related to a problem? Please describe

When a user successfully installed and seems to be using / happy with their installation, we should nudge them towards the logical next step in the user journey: to install Gitpod on K8s, likely via our PoV Reference architecture (#10622).

Describe the behaviour you'd like

• When a user has successfully installed and started 1 workspace, there should be a toast that asks them to go to the next installation method.
• The amount of workspaces needed until we nudge should be configurable
• The nudge should point to the community license form, however with attribution (we should be able to track that a user came from a preview installation) - e.g. using an UTM link
• The same nudge should also be in the documentation.
• This only happens in the local preview

Describe alternatives you've considered

• Only do this in the documentation - which might be overlooked.

Additional context

• Internal planning document
• Internal release plan

Implementation Ideas:

• Can show a goodbye message ("thanks for trying Gitpod, go to this link for next steps") on terminate signal in the CLI (with condition "has opened a workspace")
• AND show this within the dashboard - see internal discussion
  • We can hide this behind a feature flag such that it only gets shown in local preview mode - see this function
  • From @gtsiolis: I’d suggest to use a non-closable, info variant of the alert component variant placed at as a global page alert (see examples[1][2]).
    • The content of the alert could inform users they are running a preview that is not intended production usage, and provide a call-to-action (CTA) to install with a community license, contact sales for buying an enterprise license, or later on start a free trial of the enterprise license.

[Pothulapati]

Merged #11434 which adds a warning alert in the dashboard! I've tried to do the terminate CLI option, but it's heavily dependent on which terminates first i.e script or the container itself, and couldn't get far.

Because the website nudge provides a direct path to action (as its through the browser), and always there, I'm thinking this is enough. WDYT?

(A release will be done this week, along with documentation being updated)

[lucasvaltl]

Let's stick to the in UI nudge for now :) Is it shown immediately or after some time? (going to close this for now)

[Pothulapati]

Is it shown immediately or after some time?

Immediately, and is on the top of the Window always!