-
Notifications
You must be signed in to change notification settings - Fork 54
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
[OUDS] Add "Colors" tokens, utilities and documentation #2802
base: ouds/main
Are you sure you want to change the base?
Conversation
2872936
to
7f97176
Compare
✅ Deploy Preview for boosted ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
8d41cf0
to
11e7727
Compare
@@ -6,7 +6,7 @@ | |||
display: flex; // OUDS mod | |||
flex-direction: column; // OUDS mod | |||
margin: 0 ($bd-gutter-x * -.5) 1rem; | |||
border: solid var(--bs-border-color-subtle); // OUDS mod: instead of `var(--bs-border-color)` | |||
border: solid var(--bs-color-border-emphasized); // OUDS mod: instead of `var(--bs-border-color)` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would have replaced border-color-subtle
by border-color-default
I think, it's much in the subtle spirit than emphasized.
{{< callout danger >}} | ||
Some of the colors below do not belong to the Orange Unified Design System specifications. | ||
<!-- TODO LM: Decide how to link to the new DSM --> | ||
Please refer to our [color palette section](#palette)<!-- and to the [Color guidelines](https://unified-design-system.orange.com/472794e18/p/217ac6-colour/b/4705d3) on the Orange Unified Design System website-->. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should link to this page : https://unified-design-system.orange.com/472794e18/p/92b911-colour/b/886430 ? Not sure since it seems to contain colors we don't have through tokens :/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we will see when it'll be uncommented, but for now the page is kinda of desynchronized with the actual colors, I've set another for now: https://unified-design-system.orange.com/472794e18/p/217ac6-color
|
||
<h3>Example</h3> | ||
|
||
Here's how you should not use these in your Sass: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find it dangerous to show what we should not do. Developer may only see the code and don't read this sentence.
Maybe we should have comments directly in the following code, together with the good way to do it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tried something in the last commit
|
||
### Sass maps | ||
|
||
<!-- TODO LM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you want to do with this commented content ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still not quite sure how to handle it properly, maybe we should wait for the Bootstrap compatibility to uncomment it.
@@ -317,6 +298,7 @@ $cyans: ( | |||
) !default; | |||
// fusv-enable | |||
|
|||
// TODO LM: take care of the rest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does that mean ? Should it be done in this PR ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe at some point when we will tackle the bootstrap compatibility, so it might happen on a PR based on this one.
Note: Please transform
- [ ]
into- (NA)
in the description when things are not applicableRelated issues
NA
Description
Remaining tasks and questions
Questions:
Tasks:
Done list
The following was done in the PR:
_color-palette.scss
._config.scss
to prepare the arrival oftokens/_semantic-colors-custom-props.scss
generated by Tokenator.--#{$prefix}focus-visible-inner-color
and--#{$prefix}focus-visible-outer-color
by--#{$prefix}color-border-focus-inset
and--#{$prefix}color-border-focus
.--#{$prefix}border-color-subtle
by--#{$prefix}color-border-emphasized
and--#{$prefix}disabled-color
by--#{$prefix}color-content-disabled
(might be changed in the future) and--#{$prefix}tertiary-active-bg
by--#{$prefix}color-action-primary-pressed
.tokens/_semantic-colors-custom-props.scss
ones.tokens/_semantic-colors-custom-props.scss
.$enable-bootstrap-compatibility
.colors.yml
,grays.yml
,palette.yml
.To be done after the PR is merged
color-palette.md
should be updated once the Color theme page is developed.color-palette.md
should be updated once the Utilities colors (text) page is developed.color-palette.md
should be updated once the Utilities background (bg) page is developed.color-palette.md
should be updated once the Helpers text + background (text-bg) page is developed.color-palette.md
should be updated once the mapping to Bootstrap variable have been done.color-palette.md
should be updated once the method to generate utilities is merged.Motivation & Context
Types of change
Live previews