Generalize recipient registration flow
samajammin opened this issue · 2 comments
Currently our entire recipient registration flow (https://eth2clrfund.netlify.app/#/join) assumes the funding round is using the optimistic recipient registry.
If the round is using a different registry (e.g. simple or kleros), we should hide the CTA links to the application flow:
- Landing page: https://github.com/ethereum/clrfund/blob/develop/vue-app/src/views/Landing.vue#L37
- Projects page: https://github.com/ethereum/clrfund/blob/develop/vue-app/src/views/ProjectList.vue#L42
- Anywhere else?
On the Join landing page, we should provide different instructions on how to get added to the round, or hide this page entirely.
We'll also need to refactor the subgraph - currently it's only configured to monitor the OptimisticRecipientRegistry contract:
Not sure we actually need to do this - @daodesigner mentioned only needing to account for using optimistic recipient registry & BrightID user registry. If so, I don't believe any changes are needed, so we could close this out.
Closing. Issue moved to clrfund#447