New feature across components

New feature across components

A change that introduces a new capability affecting several components at once, with architectural impact — for example, a new shared attribute added to many components.

When to use this

Use this when a single conceptual change has to land in multiple components. If the change is contained to one component, use New feature or Large enhancement. If it restructures the system itself (tokens, global styling), it's a Major initiative.

At a glance

Design	Code	Doc	Checkpoints	Typical release
✓	✓ (multi-package)	✓	triage → design → review & merge	minor / major

Because the work spans packages, it's usually organised as a parent (tracking) issue plus independently shippable sub-issues — this is also what makes it approachable for outside contributors (good first issue / help wanted).

Flow

1. Propose

• Check existing issues and the project board.
• Open a parent (tracking) issue describing the shared capability, then break it into per-component sub-issues.

Checkpoint — Core team triage. The core team confirms the architectural approach, the split into sub-issues, labels and milestone.

2. Design

• Design the shared pattern once, then show how it applies across the affected components — start from Components and Design Tokens.
• Align with design tokens; annotate.

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

3. Code

• Create a branch per shippable unit (feat / change in commitlint.config.js; change for breaking API changes).
• Implement the shared attribute/behaviour consistently across the components; document the API.
• Add Storybook views (visual + a11y) and tests per component; verify browsers/devices.
• Update dependent packages; write the changelog.

4. Submit

• Open one Pull Request per shippable sub-issue to dev (avoid one giant PR), each linked to its sub-issue.

Checkpoint — Core team review & merge, per PR.

5. Doc

• Document the new capability once at the pattern level, and update each affected component's page.

6. Release

• Handled by the core team — minor, or major if the shared change breaks existing APIs.

---

Step descriptions: Steps reference. Questions: Stack Overflow.