Closed dovalid closed 3 years ago
I started working on this issue today:
CommunityCard
component.Account
components are under each other on smaller screens, this way they have enough room, and the layout is nicely arranged this way[community]
page, I tweaked the buttons on the "Platforms" card, they're under each other on small screensresize
event handler to the AccessIndicator
Level
component,I feel like the right (or bottom right) side of the Level
component doesn't look great on small screens, the "You have access" label looks a little bit odd there, but hopefully I'll have a better idea for its placement!
I changed the design of the Level
component on mobile, it looks better this way (at least in my opinion). Let me know what's your opinion on the overall UI design of the site on smaller screens!
I made the following changes after our meeting today:
ActionCard
component. Now it accepts a boolean prop called withAccordion
, and if you pass it, the card will only show its title initially, and you can open it, so you can reveal its content too. All this logic is handled in the ActionCard
component, so I haven't changed the markup in the Platforms
/Staked
components!Level
component. I played with the spacings inside it, and now the "You have access"/"Wallet not connected" texts aren't visible on mobile (so we can display the images on the left side instead!), but you can see a checkmar or an x icon next to the level's name, with a tooltip on focus stateI'll work on the modal appearance later today, and keep you updated on that too!
Update:
Tooltip
component, but we can talk about it laterforwardRef
issue was caused by the Platforms
component, and not by the tooltips and icons in the Level
component, but I fixed that too now!I decided to play a bit with the spacings on the community page instead of just putting the "Platforms" and "Staked" sections under the levels, because I feel like those are pretty important and they shouldn't be at the bottom of the page. This way, the users can see the first 2 levels even on smaller mobiles, and they can still find the join TG/DC buttons pretty easily.
There're no designs for mobile view. Feel free to experiment and implement the UI for mobile and every possible screen size as you think it fits best. I think this issue can sum the progress of everything we have currently becoming responsive, you should just open different PRs for different parts of the app, that's where the relevant communication will go.