## Open questions
The following open questions should be answered by this spike.
### 1. Which components will we plan to implement as css-only components?
Thus far, we have discussed limiting this to a small set of components for which a css-only implementation will still be useful even after we have SSR available within MediaWiki. We've identified these components from mediawiki.ui:
- anchor `a`
- `form`
- `label`
- `button`
- `input[type="text"]`
- `input[type="search"]`
- `input[type="radio"]`
- `input[type="checkbox"]`
- `select` (limited)
- icon (debatable)
...as well as potentially including loading indicators like Skeleton and ProgressIndicator (spinner and bouncing dots).
#### To do
- [] Discuss with the Web team which components will be needed for the ArticleTools work so we can determine a priority set of components
- [] Finalize the list of initial components to implement
### 2. How will we implement css-only components?
We have identified 2 options:
- Output Codex CSS, at least for the specified components, as a separate package so styles can apply to any markup with the appropriate classes
- Release Less mixins, similar to the Link component, which can be applied to any markup as the implementer sees fit
We will build a prototype of the second option using a group of components with a range of complexity (probably button, radio, and select). If needed, we will also build a prototype of the first option.
#### To do
- [] Build a prototype of the Less mixin components solution for a small set of components
- [] Review it as a team and determine if we want to also prototype out the other option
## Acceptance criteria
- [] [[ https://docs.google.com/document/d/1y6DMlrqIy0bQzAc7kdkgROs0VIlSQL3PoF0LbheVnjg/edit#heading=h.vlvz8k1kr1aj | Spike output doc ]] is complete and shared with DST
- [] DST has provided feedback and aligned on scope, timeline, owner(s)
- [] {T321351} description has been updated
- [] Known subtasks have been added to T321351