John Michael Kuhn Jr.
John Michael Kuhn Jr.
For Login/Logout, (#39 and this one), what does the flow look like when we need to consider that a user may belong to multiple DAO's?
We want the frontend to provide a rich user experience with features like... - Show a list of members. - Show a list of proposals. etc. The challenge here is...
Proposed solution 1: Store all of this info in a centralized database solution. When the frontend presents this info to the user (like showing a proposal) - it will reference...
We have a responsive design for this but not desktop. Should desktop mimic the layout albeit with a wider screen?
No design flow for frontend.
We have a responsive design for this but not desktop. Should desktop mimic the layout albeit with a wider screen?
I'll get started on the UI and involve the rest of you in the design process as I'm building it out.
Rough draft of UI with hardcoded data here https://github.com/syvita/daoos/pull/61
Miami DAO registry contract: https://gist.github.com/JMKJR/35b7802b4fcc2334cbc97ba4f57f2850 Will create a PR when I'm able to create unit tests.
Smart contract and frontend work. We don't have a frontend design flow for this yet.