== Background goal
Since we included just the MVP version of the Components Guidelines in Codex, there are some misalignments between these Guidelines in Codex and the components specs in Figma since the following sections from the Figma specs are missing:
- **Use cases** (Do - Don't) explaining the best practices for the component
- **Minimum and maximum examples:** explaining how the component behaves with short and long content
- **Keyboard navigation:** explaining all the shortcuts to navigate the component with the keyboard
The Codex site should be the source of truth of our Design System, so we need all these info there.
=== User stories
- As a Codex user (designer, developer, or other) I need to know all the information about a component when navigating the component's page.
=== Documentation
| [[ https://docs.google.com/document/d/1ijapYGCW_0MP3PT5A6DyDooUtcq_ndp4gbK1-A3io7k/edit#heading=h.44j4hicgxpd3 | Doc with the components guidelines ]] |
=== Open questions
-
=== Acceptance criteria (or Done)
**Design**
[] Update the [[ https://docs.google.com/document/d/1ijapYGCW_0MP3PT5A6DyDooUtcq_ndp4gbK1-A3io7k/edit#heading=h.44j4hicgxpd3 | doc ]] including the missing sections in all the components in that list
[] Review the new documentation with the DST before including it in Codex
**Code**
[] Include these new sections in the components pages in Codex