/
2020-09-04 Meeting notes

2020-09-04 Meeting notes

Date

Sep 4, 2020

Goals

  • DECIDE: Who does this system support?

  • REVIEW: Taxonomy

  • REVIEW: Process for adding or updating components in the system

  • REVIEW: Component design spec template

Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

15m

Assumptions on: Who does this design system support?

Eugene


15m

Taxonomy of the design system.

Gabe

Change name of “Templates” to “Examples”

15m

A process of updating or creating new components in the design system

Eugene

What if someone would like to add a partially built component? How does that dovetail.

 

15m

Component design spec template

Gabe

Jeff to provide an a11y checklist for the spec.

No code formatting? It’s a e.g. Button

Action items

@Adam Butterworth (Deactivated) Create a Jira ticket template for proposals for new/updated components.
@Eugene Kang To improve visualization of updating/new component process.
@Gabriel Weinberg (Deactivated) Add formatting style for Code in component spec figma files where appropriate.
@Gabriel Weinberg (Deactivated) Transfer the Taxonomy documentation to Confluence

Decisions

  1. Assumptions on “Who does this system support?” accepted (pre-stakeholder interviews)
  2. Taxonomy proposal accepted
  3. Process for adding/updating components accepted pending formatting updates
  4. Component design spec template accepted pending additions of a11y checklist and code formatting

Related content

Examples of good design systems
Examples of good design systems
Read with this
2021-10-28 Meeting notes
2021-10-28 Meeting notes
More like this
Team Swarm on Design for Existing Paragon Components
Team Swarm on Design for Existing Paragon Components
Read with this
2023-11-06 Meeting notes
2023-11-06 Meeting notes
More like this
Paragon Working Group Meeting
Paragon Working Group Meeting
Read with this
2022-03-23 Meeting notes
2022-03-23 Meeting notes
More like this