@mention a person to add them as an attendee and they will be notified.
Goals
List goals for this meeting (e.g., Set design priorities for FY19):
Discussion topics
Time
Item
Presenter
Notes
Card.Header
Long
Is it hard to support responsive if you can pass any node into the component?
There are use cases for supporting buttons in addition to iconbuttons in the header
overflow menu is a little restrictive in its behavior
If we let nodes pass into the header, we shouldn't restrict the overflow menu
Manny: Maybe the Collapsible Button Group type behavior in DataTable (e.g., overflow menu) is its own components that could be used by the consumer.
10-15 min
Bulk Enrollment V2
Amy
Gut check needed for use of Paragon components
can use the table action to pass in a disabled state
Action items
Add action items to close the loop on open questions or discussion topics:
Design spec for the card header should guide designers on best practice for how to bring a component into the header row Gabriel Weinberg Note: Whatever is passed into the row will stay top aligned.
Look into adding a separate Collapsible Button Group type of component that could be used within DataTable, Card.Header, etc. (from Figma library and implementation)
Decisions
Type /decision to record the decisions you make in this meeting:
418f7236-a1d2-4dfd-a197-7f57a3a2a147DECIDEDe1a7b4a4-10d1-46cb-a180-53c4db421ab6Card header should be able to accept any component, not just an icon button or standard button. 1ee88d70-3663-4259-9a61-a369815b62e3DECIDEDData Table table action can be used to pass a disabled button state into the row
Card header should be able to accept any component, not just an icon button or standard button.
Data Table table action can be used to pass a disabled button state into the row