---
# System prepended metadata

title: Component Spec Meeting notes
tags: [meeting-notes]

---

---
robots: nofollow, noindex
tags: meeting-notes
---

# Component Spec Meeting notes

Issues:
- Specs were too big 

1. Go take a look at design spec (in figma)
2. Open UI spec page updated
3. Audit/Review phase

First Phase of proposal
- Fabric - Stardust comparison
- Open UI Page
- Industry research (What does this mean? Need specifics)
    - Should this be: "look at these N libraries"
- Component name boundaries and props

Next phase:
- Api/example for each specimen in figma file

Third step:
- What is the upgrade path from 
    - Fabric -> New
    - Stardust -> New

Spec:
- We have these components
- With these props
- that do these things
- Add on tokens

Work:
- Team does component updates
- David/Levi: Builder updates
- Theme system updates


Definately
- Go through design specs
- List of component names
- and Props

Core deliverable we need:
- First: we need the Open UI spec for the component
- Second: Proposed API that can generate the example (component names and props)
    - JSX for each design specimen in figma file

