/
2020-09-11 Meeting notes
2020-09-11 Meeting notes
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
5 | Assemble! |
| Always takes time |
| Review action items from last time | Adam | |
10 | Competitive Research/Inspiration | E/G/A |
|
20 | Design System Principles | Adam | |
10 | Next Weeks Objectives |
|
|
Notes
Let’s design ALL the states as we being designing components. Think about states and how they interplay. Engineers shouldn’t need to infer loading, hover, focus, “unsaved” or other state from a design.
Jeff: Generally designers take a very subtle approach to hover states. Does this need to be the case?
Action items
@Adam Butterworth (Deactivated) Share Design System Principles on slack for more input for next week
@Jeff Witt (Deactivated) To share some examples of strong hover/focus states in successful designs.
Decisions
, multiple selections available,
Related content
Design System Weekly Reviews
Design System Weekly Reviews
Read with this
[ARCHIVE] Taxonomy
[ARCHIVE] Taxonomy
Read with this
Design System Principles
Design System Principles
Read with this
Paragon Working Group Meeting
Paragon Working Group Meeting
Read with this
2020-09-04 Meeting notes
2020-09-04 Meeting notes
Read with this
Team Swarm on Design for Existing Paragon Components
Team Swarm on Design for Existing Paragon Components
Read with this