Context

Multiple gateways set up covered here will not rule out content-vertical focus, as a way to build up a congruent value proposition by external operators.

• https://github.com/Joystream/marketing/issues/289

Gleev, operated by JSG as the prime example of this case is planned to focus on Web3/ Crypto vertical only.

For the benefit of end users of Gleev the idea is to inform them on all entry points to the app, about the specific focus of the app, be it content, business model, cause or any other point of differentiation.

This issue attempts to capture all relevant places

YPP adaptation is covered in a separate issue:

• https://github.com/Joystream/marketing/issues/292

☝️ Importantly the designs (and implementation) must be done in such a way that will make it easy for external operators to configure this content to their purposes without rebuilding the pages in a custom ways.

Scope

1. Introduce a global variable allowing gateway operators to describe the app's content focus so that it can be later referenced in the UI. Ideally, the content focus description is contained within 25 characters (at most), and a few examples of usage are provided for a gateway operator, e.g.:

• "Your {{contentFocus}} creator journey starts here"
  Example: Your web3 & crypto creator journey starts here
• "Welcome to {{appName}}, a video platform focused on {{contentFocus}} content."
  Example: Welcome to Gleev, a video platform focused on web3 & crypto content.
  >> this will be hardcoded on Gleev side.

2. Introduce an App KV component based on the designs, docs, and changelog, which can be found here

   Note
   @drillprop Please let me know on Discord once you get to this, as we need to discuss the matter of keeping illustration assets in the Figma file. Thanks!

3. Introduce a Welcome dialog component based on the designs, docs, and changelog, which can be found here,
4. Update the Sign in dialog component based on the designs, docs, and changelog, which can be found here,
5. Update the Studio welcome screen based on the designs, docs, and changelog, which can be found here,

┆Issue is synchronized with this Asana task by Unito