-
Notifications
You must be signed in to change notification settings - Fork 71
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
Pink Elephant Diagnostics #521
Comments
@BSFishy round 2: // Core
$ouiColorPrimary: #CFB3FF;
$ouiColorSecondary: #FFD481;
$ouiColorAccent: #9DCD65;
// Status
$ouiColorSuccess: $ouiColorSecondary;
$ouiColorWarning: #FFCBC3;
$ouiColorDanger: #F57600;
// Grays
$ouiColorEmptyShade: #FDDFEC;
$ouiColorLightestShade: #FBD2E2;
$ouiColorLightShade: #F8B8D0;
$ouiColorMediumShade: #F194B8;
$ouiColorDarkShade: #E6308A;
$ouiColorDarkestShade: #CD2576;
$ouiColorFullShade: #B51963;
// Backgrounds
$ouiPageBackgroundColor: $ouiColorLightestShade; I am unclear on if this should be |
@KrooshalUX I know the original scope of this is for theming, which is primarily about colors. But do we wand to also take a similar approach to identify other gaps, such as font stacks? |
@joshuarrrr yes - I am working on identifying some additional changes we can make to the other style driven elements. One of our biggest questions however, is if theming is overriding the overrides, as much more is "pink" than we expected. There is a meeting next week to come up with additional investigation and next steps. Stay tuned! |
Should we open another issue for fonting @BSFishy @joshuarrrr @seanneumann |
Is your feature request related to a problem? Please describe.
I'd like to build an OUI diagnostics theme called Pink Elephant. Let's change all the OUI styles to be pink to highlight where in OpenSearch Dashboards and plugins that aren't using oui. Basically, anything that is not pink is not using OUI.
It should be deployable to staging domain: pink.playground.opensearch.org
Related Playground Issue: opensearch-project/dashboards-anywhere#158
The text was updated successfully, but these errors were encountered: