feat: AI.md Documentation (tokens & components)#2620
feat: AI.md Documentation (tokens & components)#2620joelharkes wants to merge 14 commits intomainfrom
Conversation
|
|
|
|
||
| Use for paragraph text, labels, descriptions, and general UI copy. | ||
|
|
||
| | Class | When to use | |
There was a problem hiding this comment.
Is it validated that this aligns with how the designers use it?
|
|
||
| Each heading has a **`-strong`** (bold) variant for extra emphasis. Example: `tw-heading-large-strong` | ||
|
|
||
| ### Font Family (rarely needed directly) |
|
|
||
| ### Primary Colors | ||
|
|
||
| For main actions, CTAs, links, and brand elements. |
There was a problem hiding this comment.
is it validated this aligns with design?
packages/tokens/AI.md
Outdated
|
|
||
| | Class | When to use | | ||
| |---|---| | ||
| | `tw-bg-overlay` | Modal/dialog backdrop scrim | |
There was a problem hiding this comment.
is it validated this aligns with designers usage guides?
| **Only** for data visualization (charts, graphs, plots). Do not use for UI elements. | ||
|
|
||
| | Class | Purpose | | ||
| |---|---| |
There was a problem hiding this comment.
is it validated this aligns with the analytics team?
| @@ -0,0 +1,320 @@ | |||
| # Fondue Design Tokens — Tailwind Class Reference for AI | |||
There was a problem hiding this comment.
Too many things are made up. These docs need to be audited carefully to not hallucinate and align with the guidelines by the designers.
Most likely this should be linked the the docs that are currently being created
https://fondue.frontify.com/document/51#/-/colors
There was a problem hiding this comment.
valid point. the website linked though is very limited. i could make a claude command to extract info from here but i think there is not enough info there yet. ill check with the designers, joanna and bubo how we can best solve this :)
| @@ -0,0 +1,455 @@ | |||
| # Fondue Components — React Component Reference for AI | |||
There was a problem hiding this comment.
These docs are duplicates of the information available within the mcp server.
The docs should be added as component desicriptions to also be available through the mcp, manifest and storybook UI
There was a problem hiding this comment.
yes its duplicate, the idea is to have a simpler alternative to avoid having to run an mcp server and make it work a bit more out of the box. I totally agree this should align with the designers documentation, i will look into this and improve the docs.
| @@ -0,0 +1,455 @@ | |||
| # Fondue Components — React Component Reference for AI | |||
|
|
|||
| This document describes the React components exported by `@frontify/fondue-components`. All components are TypeScript-first, support ref forwarding, and are theme-aware via Fondue design tokens. Most interactive components are built on [Radix UI](https://www.radix-ui.com/) primitives for accessibility (keyboard navigation, ARIA attributes, focus management). | |||
There was a problem hiding this comment.
Referencing Radix will most likely be misleading for a LLM as it is not relevant for the usage but might lead to it using a radix prop which is not exposed
There was a problem hiding this comment.
valid point, ill do some experimenting and see. I found it was helpful as it does help sometimes suggest that we should start adding a radix prop to make a functionality work. so let me try out some more stuff here.
Why?
We can reference to these files/urls in web-app (as they are publicly available).
This hopefully improves our generate code quality.
Considerations
Scope
I left other stuff out of scope:
Next steps