Skip to content

Commit 2af5366

Browse files
authored
Updating an existing component template (#916)
Create a new issue template for updating an existing component
1 parent 775b821 commit 2af5366

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
name: Update existing component
3+
about: Outline the update requirements for an existing component.
4+
labels: Design System, update component request, sev-1
5+
---
6+
7+
# Component name:
8+
9+
> Name/Description of the component being updated
10+
11+
12+
## Design specification updates
13+
14+
<!--
15+
Snapshots and link to mock-ups for this component update. Should cover themes and states with guidelines for spacing, typography, and structure. Breakpoint details for desktop, tablet, and mobile or general guidance for responsive changes.
16+
-->
17+
18+
19+
## Accessibility updates
20+
21+
<!--
22+
Guidance for keyboard navigation and screen-reader engagement. [Best practice documentation](https://usability.yale.edu/web-accessibility/articles) from Yale University.
23+
-->
24+
25+
26+
## Interaction updates
27+
28+
<!-- General guidance for how a user should interact with this component. -->
29+
30+
31+
## Analytics updates
32+
33+
<!-- How will this component be tracked? Are any custom events needed to hook into the state of the component? -->

0 commit comments

Comments
 (0)