You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 2, 2021. It is now read-only.
We will need to update the onboarding flow to reflect changes from the Fundraising template to the Gardens template.
However, rather than just using Aragon Onboarding flow we should consider instead creating a streamlined onboarding outside the client that relies on defaults for nearly everything. This simple version can be closer to the final target for setting up a garden when build out a simplified interface that is separate from the client.
In the simplified onboarding we would only really care about the following:
Name
Agreement Text (but not the parameters)
Everything else we will have as defaults for all gardens. The specific details of all the parameters still need to be specced out.
After creation, the community will be in the "pre-sale" stage, and the interface will need to allow members to pledge support to the community and show progress towards a support goal, and if it fails allow supporters to withdraw. If it succeeds we will want to switch over to #3
The text was updated successfully, but these errors were encountered:
lkngtn
changed the title
Update Onboarding
Simplified Onboarding
Apr 11, 2020
We will need to update the onboarding flow to reflect changes from the Fundraising template to the Gardens template.
However, rather than just using Aragon Onboarding flow we should consider instead creating a streamlined onboarding outside the client that relies on defaults for nearly everything. This simple version can be closer to the final target for setting up a garden when build out a simplified interface that is separate from the client.
In the simplified onboarding we would only really care about the following:
Everything else we will have as defaults for all gardens. The specific details of all the parameters still need to be specced out.
After creation, the community will be in the "pre-sale" stage, and the interface will need to allow members to pledge support to the community and show progress towards a support goal, and if it fails allow supporters to withdraw. If it succeeds we will want to switch over to #3
The text was updated successfully, but these errors were encountered: