-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create How it Works content page #52
Comments
We want to use the according view the Morty came up with. |
How it looks using the accordion default viewon mouse over:after expanding one itemafter moving the mouse outsideIMHO the accordion is not that intuitive, I vote for leaving as it looks after fixing the header styles @lukestokes, please advice |
@str looks great to me! |
Which one? The accordion or the first one? |
Oh, sorry. I was thinking we were doing both (fix the H1 styles in general and using the accordion). I'm fine with not using the accordion approach. Looks okay to me and it's not too much content to require an accordion. |
- adding a default root font size - adding missing translation - simplify and clean the HowItworks page - adding missing autogenerated file
Any ideas on this page?
How technical do we want to get? We could show a diagram of the accounts involved, explain the dacdirectory account, explain how eosDAC will host the front end and APIs and such, etc... I don't want to make it too technical, but I do want it to explain enough to set proper expectations as to what they are actually paying for.
The text was updated successfully, but these errors were encountered: