-
Notifications
You must be signed in to change notification settings - Fork 720
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
Update styles to reflect changes in new Material Design guidelines #189
Labels
Milestone
Comments
Hi! |
I remake this material design to new M design- here is an example: http://ondrovywebovky.tk |
sesemaya
added a commit
that referenced
this issue
Jun 25, 2018
sesemaya
added a commit
that referenced
this issue
Jun 25, 2018
Material design 2 Daemonite material UI is available here : https://djibe.github.io/material/ |
sesemaya
added a commit
that referenced
this issue
Jan 10, 2020
sesemaya
added a commit
that referenced
this issue
Jan 10, 2020
sesemaya
added a commit
that referenced
this issue
Jan 10, 2020
My fork uses latest Design guidelines: https://djibe.github.io/material/docs/4.5/getting-started/introduction/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Google just unveiled the next stage for Material Design and updated its stylistic guidelines. Some of the changes may require changes to
daemonite-material
in order to stay up to date. These changes will be listed here as a ship list for a future release (probably v4.2).New Material guidelines vs previous guidelines.
General changes
2px
to4px
Individual component changes
.navbar
).btn
).card
).chip
).table
).modal
).list-group
and.expansion-panel
).dropdown-menu
and.menu
).navdrawer
).progress
).custom-control
).custom-range
).snackbar
).nav-tabs
).form-control
).tooltip
)App bars (bottom and top)
Banners
.jumbotron
)Buttons
Buttons: floating action button
Chips
.chip-danger
,.chip-success
,.chip-warning
, etc.)Dialogs
Navigation drawers
Progress indicators
Text fields
This list is not complete yet.
The text was updated successfully, but these errors were encountered: