## 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.
**General question concerning all components:**
High impact:
- Review the Figma library and make sure the info and use cases documented in Codex match with the ones in the library
- 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, see also T345904
- Deal with MediaWiki (wiki) special interaction needs, like “Red Links” How technology agnostic do we make the descriptions?
Medium impact:
- 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`)
- Evaluate if we want to remove the "Interaction states" section from the guidelines
- Evaluate if we want to rename the "Specifications" section to "Anatomy"
Low impact:
- 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
-- Also decide where to put the References, if we continue with it. Right now it's hanging in the air underneath Guidelines, where the more natural expectation would be to have it end of page.
-- If References, then add direct link references, not links to the heading. For satisfying UX and a11y needs: See https://gerrit.wikimedia.org/r/c/design/codex/+/959603/14/packages/codex-docs/component-demos/button/button.md for example. We put in a enumerated list of Reference ids, otherwise the link is no semantic connection. We can leave this for post MVP.
- 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
- Add `title` element to component SVG images, while they already feature `alt` text.
- In the [[ https://www.figma.com/file/3izw9LhVfK4XCL6immUada/Codex-as-Wikimedia-DS | Codex as DS Figma template ]] we're using two different background shades (lighter and darker) for the image asset backgrounds. We need to evaluate how to implement that simply…
**Component specific questions:**
High impact:
- Button: revisit the documentation in the "Types" section.
- Card interactive states: This should only describe a fully linked card, which is not the default for Cards.
- Dialog: Think about a different image for specifications-max-width-height. That's 2.8 MB.
Medium impact:
- [[ https://docs.google.com/document/d/1ijapYGCW_0MP3PT5A6DyDooUtcq_ndp4gbK1-A3io7k/edit#heading=h.weq11p1fvvna | File input ]]: Add to component's guidelines
- Checkbox, ChipInput, Field, Radio, Select, ToggleSwitch, TextInput, TextArea: Add the list of interaction states in 2 columns, preferably CSS column layout
### Acceptance criteria
[] Evaluate each one of the items in the list above and create the necessary tasks