atlas
atlas copied to clipboard
Gleev adaptation for YPP
@dmtrjsg commented on Tue Sep 27 2022
Context
Context of multiple gateways and rebranding of Atlas to Gleev will impact YPP project. This an issue raised addressing the overall change to the YPP project.
YPP incentive programme will only be carried out for Gleev App (which focusses on the more narrow set of categories, listed here> , operated by JSG and we need to adapt the relevant parts of the YPP participants onboarding flow with regards to this.
There is also an impact on the category selection, which needs to be done as part of YPP onboarding flow.
⚠️ ℹ️ `YT sync scraps the YT category, and lets creator select a single category. What they select is default display category for the video category. We need to inform users that this will be propagated to all videos, but can be changed manually.'
As specified in these issues:
- https://github.com/Joystream/atlas/issues/3183
- https://github.com/Joystream/youtube-synch/issues/42
Scope
- [ ] Add relevant copy to the Marketing website wrt Gleev YPP programme that would focus on Crypto/ Web3 Creators.
- [ ] Add the criteria for YPP partnership onboarding flow to the assessment criteria-> relevant content selection based on categories. List of categories is provided in the additional info section below
- [ ] YPP dashboard needs to be updated for posting YT content to Joystream channel only adhering to the content strategy of Gleev (Web3).
- [ ] For YPP onboarding flow the Category selection/ confirmation screen after auth needs to include the selection of category manually, based on the list in the additional info below.
- [ ] Mention that Gleev will only focus on Web3 creators on the page which contains multiple apps (covered in scope of
- #289)
- [ ] Mention YPP programme on the Gleev app (label and tooltip, or smth else)
Additional Info ℹ️
Categories: (Web3/ Crypto/ Blockchain) Investing Podcasts Conferences Reviews Tutorials News Memes Interviews Analysis Predictions Trading
@dmtrjsg As discussed before, since https://github.com/Joystream/marketing/issues/297 is ready to tackle, I'm putting this task on hold. Below I include a changelog outlining what I have managed to accomplish so far. Please note that these changes are ready to be implemented. The below changelog, along with designs and docs, can also be found in this Figma file.
- Updated all illustrations (across both the landing page and the app) to feature Gleev logo, name and sample content,
- Replaced all instances of the “Atlas” name in copy with “Gleev”,
- Updated the Authorized channel dialog to replace Atlas logo with Gleev (link),
- Updated the YT channel card component to replace Altas logo with Gleev (link).
Edits to the original scope:

@dmtrjsg This task is ready to be reviewed and/or implemented based on the designs, documentation, and changelog that can be found in this Figma file. 🚀
Scope
[...]
- [ ] YPP dashboard needs to be updated for posting YT content to Joystream channel only adhering to the content strategy of Gleev (Web3).
I haven't addressed the above item from the scope as the Figma designs had never accurately reflected the detailed program mechanics anyway. Since we haven't received any documentation for the exact requirements and the list of steps required for a given task to be considered complete, the copy in Figma is just @KubaMikolajczyk's best guess he had at the time of designing this.
This touches upon this unresolved discussion from Figma.
Please, let me know if anything has changed since then. If the program mechanics are documented somewhere, I'm happy to update Figma designs to reflect that.
@toiletgranny thank you for handling this. The programme details and the specific steps I will make sure to populate 👌
Final copy will be updated in a separate task, along with parameters. Captured here (and blocked by operating model sim validation):
- https://github.com/Joystream/atlas/issues/3570
@WRadoslaw fyi