## Background
In {T333144} we moved all the existing DSG content to Codex and we created the component's guidelines (MVP) for all the existing Codex components. After this MVP task, we will need to solve some pending fixes and/or improve these guidelines.
### Open questions
We will need to evaluate/solve the following:
- Review each component's demo page and make sure the information is not duplicated in the Guidelines and Demos sections
- Add a new section for "Patterns" in Codex
- Add the "[[ https://docs.google.com/document/d/1ijapYGCW_0MP3PT5A6DyDooUtcq_ndp4gbK1-A3io7k/edit#heading=h.weq11p1fvvna | File input ]]" component's guidelines
- Evaluate if we want to remove the "States" section from the guidelines
- Color's documentation: decide if we want to use the option token's name (e.g. `Gray200`) or the decision one (e.g. `background-color-disabled-subtle`)
- References section: just the components moved from the DSG contain a "References" section. We need to review the [[ https://docs.google.com/document/d/1ijapYGCW_0MP3PT5A6DyDooUtcq_ndp4gbK1-A3io7k/edit#heading=h.uteb407jne6h | new Codex components ]] list and include references when needed
- Review the Figma library and make sure the info and use cases documented in Codex match with the ones in the library
- We could improve the component's guidelines by adding:
- Do and Don'ts to explain how to use the component
- Content recommendations for components
- Keyboard navigation info
- Evaluate if we want to rename the "Specifications" section to "Anatomy"
- Deal with MediaWiki (wiki) special interaction needs, like “Red Links” How technology agnostic do we make the descriptions?
- Add `title` element to component SVG images, while they already feature `alt` text.
### Acceptance criteria
[] Evaluate each one of the items in the list above and create the necessary tasks