Skip to content

Color foundations enhancements - Website docs #2335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 17 commits into from
Aug 20, 2024

Conversation

majedelass
Copy link
Contributor

@majedelass majedelass commented Aug 13, 2024

πŸ“Œ Summary

If merged, this PR will update the foundations color docs to a more comprehensive guide to using our color system.

πŸ› οΈ Detailed description

We expanded on how our colors are created, how we use them semantically, and how to be accessible with our color choices.

πŸ”— External links

Jira ticket: HDS-1360
Figma file: Link to images


πŸ’¬ Please consider using conventional comments when reviewing this PR.

Copy link

vercel bot commented Aug 13, 2024

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Updated (UTC)
hds-showcase βœ… Ready (Inspect) Visit Preview Aug 19, 2024 7:05pm
hds-website βœ… Ready (Inspect) Visit Preview Aug 19, 2024 7:05pm

@hashibot-hds hashibot-hds added the docs-website Content updates to the documentation website label Aug 13, 2024
@majedelass majedelass requested review from a team August 13, 2024 15:05
Co-authored-by: Andrew Gendel <124841193+andgen404@users.noreply.github.com>
Copy link
Contributor

@jorytindall jorytindall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a couple of very small comments, but looking good. Much improved over what was currently here! πŸŽ‰

Copy link
Contributor

@heatherlarsen heatherlarsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took a more thorough look. There are several inconsistencies with how we've communicated about colors/tokens in the past, so I'd like to see the terminology corrected (added suggestions and references throughout that are blocking).

I also added a few brevity and grammar suggestions to help with readability. And I'm not sure where the spaces in the style naming conventions came from, but in other documentation, we use Body/200/Link, so it'd be good to make that consistent.

Updating as per folk's suggestions.

Co-authored-by: Heather Larsen <hlarsen@hashicorp.com>
Co-authored-by: Jory Tindall <jory.tindall@hashicorp.com>
…removed border / primary from disabled colors section.
Co-authored-by: Kristin Bradley <kristin.bradley@hashicorp.com>
Copy link
Contributor

@KristinLBradley KristinLBradley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good! Just added a few minor wording and punctuation suggestions.

majedelass and others added 2 commits August 19, 2024 14:25
Co-authored-by: Kristin Bradley <kristin.bradley@hashicorp.com>

We intend to be conformant with WCAG 2.2 Level AA requirements. In terms of color contrast, this means a luminosity ratio of 4.5:1 for normal sized text, and 3:1 for large text (commonly 22px). Further details are outlined on [WCAG’s understanding of Contrast (Minimum)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html). By default, semantic color tokens provide accessible color combinations out of the box with their associated naming conventions, while using palette colors requires manual validation, especially if you plan to mix and match. As an example, if a color has a semantic status name in it, then other associated status colors will be accessible.

It is important to note that we [do not recommend the usage of disabled elements](/patterns/disabled-patterns), especially isolating disabled colors out of context, as they are not accessible.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love that you snuck this in 😈 great placement and reminder for people


### Using palette colors

The Core Palette is available if semantic colors do not meet your needs. These styles are usage-agnostic, which can introduce challenges in consistently scaling designs but also allow more freedom and flexibility in color pairing.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is πŸ‘©β€πŸ³ πŸ’‹ (chef's kiss) β€” concise and clear without telling consumers not to use palette colours

Co-authored-by: LilithJames-HDS <lilith.james@hashicorp.com>
Copy link
Contributor

@heatherlarsen heatherlarsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the edits! πŸ‘πŸ»

@majedelass majedelass merged commit fe8f874 into main Aug 20, 2024
12 checks passed
@majedelass majedelass deleted the webdoc-color-enhancements branch August 20, 2024 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-website Content updates to the documentation website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants