Background
Description
Input for entering a number.
User stories
Add at least one user story.
History
Number inputs are part of the DSG and OOUI.
Known use cases
- GrowthExperiments mentee filters form contains a NumberInput built in the GrowthExperiments extension (based on the CdxTextInput component)
- Codex docs site uses a number input on the Menu demo page
Existing implementations
These artifacts are listed for historical context. The Figma spec, linked below, is the source of truth for the new component.
Wikimedia community:
- Design style guide: Number inputs
- OOUI: NumberInput component in OOUI
- Vue:
- GrowthExperiments CNumberInput
External libraries:
Codex implementation
Component task owners
- Designer: @bmartinezcalvo
- Developer: add the main developer's name
Open questions
- List any current open questions here
Design spec
Once a component spec sheet has been created in Figma, remove the note stating that the spec is missing and link to the spec below.
| Component spec sheet |
Anatomy
Designer should list the structure and properties of the component.
Style
Designer should list the visual features of the component.
Interaction
Designer should list interaction specifications.
Documentation
Designer should describe how the component should be documented, including configurable and standalone demos.
Acceptance criteria
Minimum viable product
This task covers the minimum viable product (MVP) version of this component. MVP includes basic layout, default states, and most important functionality.
MVP scope
- List all parts of the MVP scope for this component
Design
- Design the Figma spec sheet and add a link to it in this task
- Update the component in the Figma library. This step will be done by a DST member.
Code
- Implement the component in Codex
Future work
- If applicable, list future work that should be done for this component after the MVP is implemented as part of this task. You should open new, standalone tasks for all future work.