You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: packages/components/CHANGELOG-FIGMA-COMPONENTS.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -70,10 +70,10 @@ In many cases, replacing v1.0 library components with the components in the Figm
70
70
- Added an `alignment` property which can be set at the root level to `left` or `center`.
71
71
- The footer now supports up to three actions at once. The actions are now organized in accordance with our [Button Organization](/patterns/button-organization) pattern.
72
72
- Updated several visual styles including:
73
-
- Removing the divider
74
-
- Reducing the title from `Display/400/Bold` to `Display/300/Bold`
75
-
- Changing the icon and the title color from `Foreground/Faint` to `Foreground/Strong`
76
-
- Changing the body text color from `Foreground/Faint` to `Foreground/Primary`
73
+
- Removing the divider
74
+
- Reducing the title from `Display/400/Bold` to `Display/300/Bold`
75
+
- Changing the icon and the title color from `Foreground/Faint` to `Foreground/Strong`
76
+
- Changing the body text color from `Foreground/Faint` to `Foreground/Primary`
77
77
78
78
_Adding support for three actions within the `ApplicationState` results in a breaking change to the previous actions. Before updating the library, we recommend annotating the text and icon name (with a comment or otherwise) in files that are in progress or still being referenced by engineering._
Copy file name to clipboardexpand all lines: packages/components/NEW-COMPONENT-CHECKLIST.md
+8-1
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,9 @@ The following should be available as resources for the Project Kickoff.
14
14
A project kickoff will be scheduled before the project start date. The kickoff will be used to align on project scope, timelines, and milestones and as a space to discuss any open questions. In attendance should be Design Systems Team leadership, lead Designer and Engineer on the project, and Design/Engineer buddies (if applicable).
15
15
16
16
## Design Checklist
17
+
17
18
The design checklist has 4 primary parts:
19
+
18
20
1. component design
19
21
2. testing
20
22
3. documentation
@@ -23,6 +25,7 @@ The design checklist has 4 primary parts:
23
25
The design process is largely cyclical, so some steps may be repeated until final approval.
24
26
25
27
### Component Design
28
+
26
29
-[ ][create a branch](https://help.figma.com/hc/en-us/articles/360063144053-Create-branches-and-merge-changes#Create_a_branch) in the [product components ui kit](https://www.figma.com/file/noyY6dUMDYjmySpHcMjhkN/HDS-Product---Components)
27
30
-[ ] add a new page for the component, as needed
28
31
-[ ] copy & paste the [new component template](https://www.figma.com/file/noyY6dUMDYjmySpHcMjhkN/HDS-Product---Components?type=design&node-id=46856-287&mode=design&t=V4zCk5Jv07PcHYzZ-4) to the new page
@@ -59,6 +62,7 @@ The design process is largely cyclical, so some steps may be repeated until fina
59
62
- let them know it's been approved and answer any remaining questions
60
63
61
64
### Component Testing
65
+
62
66
-[ ] prepare for testing
63
67
-[ ] lock the components
64
68
-[ ] change the badge in the banner to "Experimental"
@@ -72,24 +76,27 @@ The design process is largely cyclical, so some steps may be repeated until fina
72
76
-[ ] if iterations are needed, work through the process until approved (don't forget to branch!)
73
77
74
78
### Documentation
79
+
75
80
-[ ] while the component is being tested, write the documentation
76
81
- artifacts should include:
77
82
- design guidelines
78
83
- specifications
79
84
- relevant accessibility details
80
85
81
86
### Release in Figma
87
+
82
88
Once key stakeholders have tested the component and iterations are approved, prepare for a final release of the component.
83
89
84
90
-[ ] add a changelog entry to [CHANGELOG-FIGMA-COMPONENTS.md](https://github.com/hashicorp/design-system/blob/main/packages/components/CHANGELOG-FIGMA-COMPONENTS.md)
85
91
-[ ] if changes were made, publish the component
86
92
-[ ] once the code has been released, communicate the release in the slack channel [#team-design-systems](https://hashicorp.slack.com/archives/C7KTUHNUS)
87
93
88
-
89
94
## Engineering Checklist
95
+
90
96
The engineering checklist has six parts: creating the feature branch, component template, component backing class, component style, tests, and documentation.
91
97
92
98
### Dependency
99
+
93
100
- Since we are trying to align the component API naming with the same terms used in the Figma file, it is likely useful to have a fairly stable Figma design before we create a component; it should definitely be finalized before the component ships, however.
border-color: var(--token-color-border-strong); // notice: in the "neutral" color the "inline" has a slightly darker border color compared to the others to increase contrast (eg. could be used on a light gray background)
148
+
border-color: var(
149
+
--token-color-border-strong
150
+
); // notice: in the "neutral" color the "inline" has a slightly darker border color compared to the others to increase contrast (eg. could be used on a light gray background)
0 commit comments