-
Notifications
You must be signed in to change notification settings - Fork 43
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
Design: Reduce community head stat box size #447
Comments
I disagree, I think the the header is a better place to show the info than the sidebar, which is inaccessible on narrow screens. Some vertical compacting on desktop too would help though. |
This info has to be accessible somewhere but I don't know where I'd put it on mobile |
My suggestion would be to make in an expandable that is collapsed by default. When collapsed it only shows the banner image, community logo and name. |
Adding community description below the name takes up valuable space for no reason and Markdown parsing from links to lists being rendered breaks the visual flow. Full banner size, with description takes up more than half the page on 1080p desktop. It literally leaves enough space to see a single post. Reduced banner size, with no description still takes up 1/3 of the page on 1080p desktop. At least you can see 3 posts now.
@Xyphyn since iOS finally added proper gesture support on PWA, you make the sidebar accessible that way. It's also already what most mobile user are used to. |
The gestures conflict with Android though. I'll work on the header later today, im really stressed with hwk. |
Your cropped screenshot just gave me an idea for a more compact design hold up |
Is your feature request related to a problem? Please describe.
So, 360px width is just a tiny bit too little to make the stats fit in a 2x2 grid. In 368px they do.
Describe the solution you'd like
Reduce margin or size or something to make 2 stat blocks fit horizontally on a 360px wide screen.
Describe alternatives you've considered
-
Additional context
The text was updated successfully, but these errors were encountered: