-
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
Read about changes required to make UI responsive #333
Comments
This unfortunately wasn't practical as it essentially documented how material design approaches responsive layout grid as opposed to how a developer can use existing properties, components, and classes to implement a responsive UI. |
@rmanaem can you say why it wasn't practical, so we don't try it again next time just to learn the same thing twice |
I also think it'd be good to expand the issue description to list some questions / things you have/will review here and what behaviour we want solutions for. The list in #122 should be a good source of things to get answers for |
Yea, let's use the list in the parent issue as the source and not duplicate it here. |
🚀 Issue was released in |
The goal is to find tools/ways/best practices to modify the existing UI so that elements are reasonably spaced and do not overlap when screen size changes.
A good starting point for research would be to take a look at the material design docs on responsive layout: https://m2.material.io/design/layout/responsive-layout-grid.html#columns-gutters-and-margins
summarize strategies for responsivenessThe text was updated successfully, but these errors were encountered: