Skip to content

Commit

Permalink
Update product-groups.md (#23457)
Browse files Browse the repository at this point in the history
  • Loading branch information
randy-fleet authored Nov 1, 2024
1 parent 65d703b commit b4a5a1f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions handbook/company/product-groups.md
Original file line number Diff line number Diff line change
Expand Up @@ -589,9 +589,9 @@ In the Slack reminder thread, the on-call developer includes their retrospective

We have certain design conventions that we include in Fleet. We will document more of these over time.

**Figma component library**
**Design system**

Use the 🧩 ["Design System (current)"](https://www.figma.com/file/8oXlYXpgCV1Sn4ek7OworP/%F0%9F%A7%A9-Design-System-(current)?type=design&mode=design&t=BytcobQwypszkxf5-1) Figma library as a source of truth for components. Components in the product ([Storybook](https://fleetdm.com/storybook/)) should match the style of components defined in the Figma library. If the frontend component is inconsistent with one in the Figma library, treat that as a [bug](https://fleetdm.com/handbook/engineering#finding-bugs).
The 🧩 ["Design System"](https://www.figma.com/file/8oXlYXpgCV1Sn4ek7OworP/%F0%9F%A7%A9-Design-System-(current)?type=design&mode=design&t=BytcobQwypszkxf5-1) component library in Figma is the source of truth for components. Components in the product (documented in [Storybook](https://fleetdm.com/storybook/)) should match the style of components defined in the Figma library. If the frontend component is inconsistent with one in the Figma library, treat that as a [bug](https://fleetdm.com/handbook/engineering#finding-bugs). As new components are being created, or existing components are being updated, ensure ensure updates are applied to both the Figma Library and Storybook and guidelines are documented in Figma.

**Table empty states**

Expand Down

0 comments on commit b4a5a1f

Please sign in to comment.