I have also prepared a brief feature list that talks about the different parts of the platform’s mvp:
Context
To expand on the last reply I posted, I want to create an mvp that allows:
- People to create accounts on chocolate
- Projects to create their admin account on chocolate.
- Projects to create their profile.
- The Community to leave reviews on those projects.
Feature List
A checklist of features I think would be needed in each part of the mvp.
1 and 2, account creation
UI form for user profile creation
UI form for admin account creation
Ui account management
Onchain separation of user accounts
Onchain extrinsics for user profile creation
Onchain extrinsics for admin account creation
3, profile creation
UI form to collect information on project profile
Complete UI displaying information on project profile
Extrinsic for project profile creation
Onchain CES system for screening project profiles
The CES stands for content evaluation system and is pretty much a filter for NSFW content or CopyCat profiles/reviews.
Content team for handling flags by CES on-chain
Persistent Ui notifications
Content team dashboard for reviewing CES flags.
4. Community leaving reviews on chocolate
UI form to submit review
Concerns
A lot of these are pretty straight forward such as the ui forms, and some have already received a lot of very helpful feedback such as the CES, but I’m still unclear on how some of these would work or best practices on implementing them. These are:
Ui account management
I am unsure how to approach the concept of “logging in” and “logging out” with web3 accounts
Content team
I want the CES to be as fast as possible, but I understand that having people look at things is much better than doing it programmatically (without machine learning). ideally, the team would answer yes/no to the flags after reading through. What’s the best way of achieving this onchain without complex voting??
Persistent Ui Notifications
The polkadotjs apps capture events from the chain based on extrinsics sent out, but they disappear across refresh. I’m planning to do something similar but I would need them to persist across refreshes for long-running tasks like the CES, how could that be accomplished?