Large enhancement

Large enhancement

A change that goes beyond extending an existing capability — it requires deeper integration or a refactor of a specific component.

When to use this

Use this when the change reshapes how a single component works internally. If it only adds a contained option, it's a Small enhancement; if it creates something entirely new, it's a New feature.

At a glance

Design	Code	Doc	Checkpoints	Typical release
✓	✓	✓	triage → design → review & merge	minor

All three checkpoints apply.

Flow

1. Propose

• Check existing issues.
• Open a Feature request with a clear set of requirements (Must / Should / Could / Won't).

Checkpoint — Core team triage.

2. Design

• Start from the Components Figma file (and Design Tokens if tokens change).
• Design the reworked behaviour; align with design tokens; annotate.

Checkpoint — Core team design validation (before any code).

3. Code

• Create a branch (feat / change type in commitlint.config.js — use change for breaking API changes).
• Draft and document the (possibly reshaped) component API.
• Implement; add a Storybook view (visual + a11y).
• Add unit and functional tests; verify browsers/devices.
• Update dependent packages; write the changelog.

4. Submit

• Open a Pull Request to dev, linking the issue.

Checkpoint — Core team review & merge.

5. Doc

• Update the component documentation: intro, examples, and design / accessibility / content guidelines as needed.

6. Release

• Handled by the core team — typically a minor release.

---

Step descriptions: Steps reference. Questions: Stack Overflow.