New feature

New feature

Creating a new component, or something that adds a new capability to the Design System.

When to use this

Use this when you're building something that doesn't exist yet — most often a new component. If the new capability spans several existing components, use New feature across components instead. If it changes the system's structure, it's a Major initiative.

At a glance

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

This is the fullest single-component path: all phases, all three checkpoints.

Flow

1. Propose

• Check existing issues.
• Open a Feature request / contribution proposal: what, why, for whom, by when, plus drafted requirements.

Checkpoint — Core team triage. Scope and type are confirmed; labels and a milestone are assigned.

2. Design

• Start from a new file based on the Components library; pull in Typography, SVG Icons, Identity as needed.
• Design the component; align with Design Tokens; annotate for developers.

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

3. Code

• Create a branch (feat type in commitlint.config.js); use the Stencil scaffolding for a new web component.
• Draft and document the component API.
• Implement (HTML/CSS/JS/TS); add a Storybook view (visual + a11y).
• Add unit and functional tests; verify supported 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

• Write the documentation from template: intro, examples, and design / accessibility / content guidelines, plus static images.

6. Release

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

---

Step descriptions: Steps reference. Questions: Stack Overflow.