Skip to content

Commit

Permalink
feat(colors)!: update all colors (#1508)
Browse files Browse the repository at this point in the history
* feat(color): Add new color palette (#1415)

* Prepare docs for new colors

* Create color-legacy.less

* Update colors docs page

* Render all new and legacy colors + classes in docs page

* Add tabs to color docs

* Add new color sets

* Maintain new and legacy colors pages separately

* Fix new atomic color class docs

* Add atomic color class generation

* Add new black, white colors

* Add new gold, silver, bronze

* Move new color variable, class generation to new file

* Generate theme color classes

* Add docs to new less color functions

* Fix docs page class rendering

* Move new color files, refactor less functions; add theming

* Remove cruft

* Simplify docs page

* theming…

* Refactor and make some theming progress

* Tweaks!

* Simplify color mixins

* Turn color sets into objects with key/value pairs

* Clean up theme generation

* Simplify color sets

* Add custom theme variables

* Cleanup

* Revert entry.colors.js

* Documentation, cleanup

* add setup to test less mixins

* fix unnecessary extra semicolon in atomic classes rule

* run tests and linters for PRs and pushes into stacks-next

* beautify css snapshots for better readability

* add snapshot of the legacy color/theme generated css

* Get rid of unneeded redirect

* Add page for new theming variables

* Move atomic class generation to atomic/color-new.less

* change .theme-variables to .theme-variables()

* Add utility color variables

* Cleanup!

* Theming!

* font color need to be set per mode

* Update tests

* ⌘ + s

* Update figma link

* Update theming docs slightly

* Update legacy color page to minimize changes to output

* Update new theming docs page

It's not *good*, but it is informative and hopefully useful while we build

* Revert "Update new theming docs page"

This reverts commit a7a19e7.

* Generate custom theme variables for use in light/dark mode by default

* Update theming (new) docs page

* Add child theming docs

* add snapshots for old and new atomic color files

* Implement suggested tweaks

* Show output of theme sliders

* Add new fc variables, update bc variable values

* Cleanup comments

* Tweak theme color stops

* Add status, lightness alias fc/bg classes; tweak theming

* Tweak theming, remove r/g/b from new

* rename theme function

* cleanup

* Add base theme color classes, values

* snapshots, documentation fix

* Move aliased utility class generation

* add snapshot for create-aliased-utility-colors mixin

* Remove new theme rgb references

* Add .fc-new-* alias classes to docs

* Remove border color alias cruft from docs

* Remap new highlight color variables where possible

* Revert "Remove border color alias cruft from docs"

This reverts commit e0aeaca.

* Add new border colors

* Update snapshots

* Add a Borders (new) docs page

* Remove duplicate component-specific theme variables

---------

Co-authored-by: Giamir Buoncristiani <[email protected]>

* chore(deps): fix small conflict resolution mistake

* Implement legacy naming for old color palette (#1440)

* Add legacy suffix to all black colors

* Add legacy suffix to orange, red, blue, green, powder, yellow

* Tons of other misc color changes

* Update css snapshots

* add legacy to theme primary, secondary

* Use legacy colors across docs

* use legacy for single-digit border class stops

* add legacy to utility aliases

* Remove transparent and inherit from legacy color docs

* Label legacy borders as legacy in docs

* Add "(legacy)" to docs page names

* Label remaining legacy colors

* add legacy to fc-light, fc-medium, fc-dark

* add legacy to focus-ring variables

* Add legacy to bc alias vars

* add TODOs for highlight color vars

* Add theme variable todo

* update --focus-ring with legacy suffix

* Update css snapshots

* Update test colors

* Update card visual test colors

* fix typo

* Minor fixes

* Rename docs pages; consolidate border docs

* Tweak theming docs

* move color Less files into versioned directories

* move all legacy files into v1 folders and v2 into root

* Label v1 generated theming variables as legacy

* fix incorrect file paths for less tests

* remove "new" suffix from all v2 colors

* update snapshots

* Update less tests to import from absolute paths

lib/exports/color.less.test.ts was importing "color.less", which would import "lib/atomic.color.less" for some reason. I changed the paths to be explicit and work no matter what directory we chuck this files into.

* Cleanup todos

* Remove dupe variables from legacy (accounted for in new)

* Standardize around v1/v2 for legacy/new colors

* Cleanup stacks-documentation.less a little

* Put those theme colors back!

* Put those focus variables back!

* Refactor utility class generation

* remove new suffix from test setup to avoid confusion

* Fix ADR typo

Resolves #1440 (comment)

* Add more Less tests for create-color-classes

Resolves #1440 (comment)

* Update border color link

Resolves #1440 (comment)

* Add test for create-aliased-utility-classes

Resolves #1440 (comment)

* Ensure high-contrast uses base theme colors

Addresses #1440 (comment)

* theming tweak

---------

Co-authored-by: Giamir Buoncristiani <[email protected]>

* Apply v2 colors to components (#1449)

* Replace component legacy color variables, utility classes

* Replace component monochromatic variables

* Replace gold, sliver, bronze variables

* Replace shade utility variables

* Update a few missed theme variables, --blue

* Missed a couple more theme variables

* Update focus ring variables

* Update generated sidebar widget colors

* Replace less base black/white variables with static CSS vars

* Remove completed todos

* Fix focus ring variable name generation

* Tweak focus-ring default value

* Fix focus ring var generation

* Theming updates

* Update base theme variable color names

* Move legacy border color classes to v1 directory

* Move legacy typography color classes to v1 directory

* Replace misc lingering legacy color references

* Replace legacy Less vars with v2 variables, references

* Replace legacy var references in ADR

* Minor alterations to white values

* Cleanup

* Update Less test snapshot

* Update baseline test images

* Remove errant whitespace

* Remove a11y test skippedTestids

* Replace legacy color reference in docs with new colors (#1450)

* 2.0.0-rc.0

* 2.0.0-rc.1

* Apply v2 colors to components proposed color alterations (#1451)

* Replace component legacy color variables, utility classes

* Replace component monochromatic variables

* Replace gold, sliver, bronze variables

* Replace shade utility variables

* Update a few missed theme variables, --blue

* Missed a couple more theme variables

* Update focus ring variables

* Update generated sidebar widget colors

* Replace less base black/white variables with static CSS vars

* Remove completed todos

* Fix focus ring variable name generation

* Tweak focus-ring default value

* Fix focus ring var generation

* Theming updates

* Update base theme variable color names

* Move legacy border color classes to v1 directory

* Move legacy typography color classes to v1 directory

* Replace misc lingering legacy color references

* Replace legacy Less vars with v2 variables, references

* Replace legacy var references in ADR

* Minor alterations to white values

* Cleanup

* Update Less test snapshot

* Update baseline test images

* Remove errant whitespace

* Improve validation state contrast, differentiation

See all validation states sections in elements under "form" heading in sidebar nav ("Checkbox & Radio", "Inputs", etc)

* Improve label state badge contrast

* activity-indicator: improve warning, dark mode contrast

* badges: improve state badge contrast

* badges: improve user badge contrast, differentiation

I'm not 100% sure about this one. Tough to differentiate them now that the color stops have been reduced

* badges: tweak number count badge bg colors

* badges: remove unneeded hc mode exception

* notice: improve contrast, fix button interaction colors

We can remove sooooo many high-contrast and dark mode overrides 😄 🎉

* post-summary: improve hotness colors

* notice: tweak code background color

* sidebar widgets: tweak background colors

* notice: improve high contrast mode contrast

* activity indicator: improve high contrast

* Darken input success text color

* Remove a11y test skippedTestids

* formatting

* Revert success color change

* update baseline images

* Deprecate primary btn, update filled secondary, other minor btn styling tweaks

* Remove primary variant from btn visual test

* Remove skipped link-preview tests

* Dcormier/components colors v2 proposal vis image revert (#1466)

* Revert "update baseline images"

This reverts commit c2e23a5.

* Kinda revert 19f67c0

* Update activity-indicator.less

* invert activity indicator font color in dark mode

* Update color-sets.less (#1467)

See #1451 (comment)

* Apply v2 color accessibility fixes (round 2) (#1477)

* Add s-block-link__danger to docs, make small tweaks

* activity-indicator: use black text for warning state

Resolves test failure for s-activity-indicator-light-warning-new

* Update activity indicator docs

* link-preview: fix footer/header hc contrast issues

* link-preview: followup contrast fix

* toggle-switch: fix hc contrast on multiple "off"

* Revert 'toggle-switch: fix hc contrast on multiple "off"'

* Update light HC 400 stops

See https://docs.google.com/spreadsheets/d/1ghhgOY3SOpKwGIFFoUrNTM6t3xNp9jOreAb9P_vcuQ0/edit?disco=AAAA32ZEHLA

* Tweak notice btn colors

Resolve failure of s-banner-light-warning-important

* link-preview/code-block: update blue values to pass

resolves s-link-preview-dark-code failure

* toggle-switch: fix dark mode contrast issues

resolves s-toggle-switch-dark-multiple, s-toggle-switch-dark-multiple-off failures

* description: skip accessibility test for disabled variant

side-steps s-description-light-is-disabled, s-description-dark-is-disabled failures

* card: fix accessibility test failures on muted variant

Resolves s-card-dark-muted, s-card-highcontrast-light-muted

* highlight variables: tweak values

* Tweak orange-500, orange-600 light hc values

This resolves all badge-related accessibility test failures

* Remove skipping of various accessibility test ids

* docs: add migration guide (#1481)

* docs: add migration guide

* Remove some extra returns

* Update MIGRATION_GUIDE.md

Co-authored-by: Giamir Buoncristiani <[email protected]>

* Apply suggestions from code review

Co-authored-by: Giamir Buoncristiani <[email protected]>

* Make theming alterations

* Add "Upgrading dependencies" section

* Minor tweaks to migration guide

* The definite article

☝️ good professional wrestler name. When others refer to you as "Definite Article", you could angrily correct them: "It's **The** Definite Article"

* Update MIGRATION_GUIDE.md

---------

Co-authored-by: Giamir Buoncristiani <[email protected]>

* Update light mode orange-400; orange-500 values for APCA (#1485)

* Update MIGRATION_GUIDE.md

* Update MIGRATION_GUIDE.md

* Update MIGRATION_GUIDE.md

* Add missed silver HC color alteration

* Add stacks dep version to MIGRATION_GUIDE

* Remove inline comments from color-sets.less

* Update MIGRATION_GUIDE.md

* 2.0.0-rc.2

* Update MIGRATION_GUIDE.md

* Apply v2 color fixes (round 3) (#1488)

* Set black to #000 in light mode; #fff in dark mode; cleanup

* Darken input, textarea border color

* Lighten s-label, s-description

* Set badge border colors from 400 to 300 stops

* lighten default important notice bg

* Bold page title header

* darken pagination item border color

* Lighten post summary accepted answer color

* Lighten stepped progress bar

* Darken accordion expandable control

* Lighten highlighted user card background color

* Lighten prose kbd border

* Update tag colors

* 2.0.0-rc.3

* Update light mode red-100

* Fix code block bg color in light mode

* 2.0.0-rc.4

* Update less output snapshots

* Fix custom theming; forced dark/light modes

* Update test images

* Formatting

* 2.0.0-rc.5

* Remove component-specific theme variable definitions

Instead, we provide fallback values where they're referenced to prevent cascade collisions/overrulings from consumers

* Update baseline Less test output

* 2.0.0-rc.6

* Tweak color cascade

* 2.0.0-rc.7

* Fix --theme-secondary-400 typo

* 2.0.0-rc.8

* Update MIGRATION_GUIDE.md

* Some unwanted notice docs changes slipped through

* Ensure aliased styles respond to forced color modes

* Update fc-success to use 400 instead of 500

From the sheet:
> The (--fc-success) class looks a bit too dark. It should be set to use green-400 (instead of 500)
> PubPlat - example on Badges list page if you've gotten a badge
> Not sure if this is theme or not actually? Note that accepted answers use green-400 so we should match that.

* Update link font colors per state

* update select border color

* Update color.less.test.ts.snap

* Update baseline test images

* 2.0.0-rc.9

* Update other link interaction state colors

* Update recently merged tests

* Update baseline images

* 2.0.0-rc.10

* Change post summary watched bg to yellow-100

* Update admin badge border color; tweak hc syntax

* Only apply topbar vars to child s-navigation when not within s-popover

* Cleanup

* Update badge baseline visual test images

* Update --theme-topbar-item-color to black-400

Resolves:

> The top nav bar icons are too dark. Change to black-400

* Update a11y tests

* Update baseline images

* 2.0.0-rc.11

* Doc updates to colors and theming (#1500)

* Re-org nav, creating design section

* Add color fundamentals back and half of content

* Add crushed assets

* Move theming items around

* Heading level fix

* Add depecration warnings

* Box in more content, add alt text

* Layer swatches

* Fix dark mode

* Accessibility info

* Theming page updates

* Minor spacing

* Fix heading level

* Update color roles

* Replace most images in color fundamentals docs page

* Replace all color fundamental example images

* Use standard tip

* Swap primary and secondary theme color usages

---------

Co-authored-by: Dan Cormier <[email protected]>

* Match topbar light class to light mode

* Update MIGRATION_GUIDE.md

* Update dark mode toggle switch, radio, checkmark

* Update dark mode saturated colors

* Update color.less.test.ts.snap

* tweak theme generation; rm lightness clamping

* 2.0.0-rc.12

* Change bold text weight from 600 to 700

* Update theming algo

* 2.0.0-rc.13

* Simplify custom theme variable generation

* 2.0.0-rc.14

* Fix tag high contrast theme colors

* 2.0.0-rc.15

* Update purple 100, 200 values

* update less snapshots

* Documentation and migration guide updates

---------

Co-authored-by: Giamir Buoncristiani <[email protected]>
Co-authored-by: Giamir Buoncristiani <[email protected]>
Co-authored-by: paintedbicycle <[email protected]>
  • Loading branch information
4 people authored Oct 6, 2023
1 parent aaf26f2 commit 0ce7557
Show file tree
Hide file tree
Showing 6,162 changed files with 36,632 additions and 17,454 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
7 changes: 5 additions & 2 deletions .github/workflows/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@ name: CI

on:
push:
branches: [develop]
branches: [develop, stacks-next]
pull_request:
branches: [develop]
branches: [develop, stacks-next]

jobs:
build-and-test:
Expand All @@ -30,6 +30,9 @@ jobs:
- name: ▶️ Linting
run: npm run lint

- name: ▶️ Less Tests
run: npm run test:less

- name: ▶️ Unit Tests
run: npm run test:unit -- --config web-test-runner.config.ci.mjs

Expand Down
198 changes: 198 additions & 0 deletions MIGRATION_GUIDE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,198 @@
# Migrating from Stacks v1 to v2

With the release of Stacks v2, we've made some breaking changes to the library. The purpose of this guide is to help you prepare your code be compatible with the changes in Stacks v2.

## Table of contents

- [Upgrading dependencies](#upgrading-dependencies)
- [Using Stacks v2 colors](#using-stacks-v2-colors)
- [Color stop mappings](#color-stop-mappings)
- [Orange, blue, green, red, yellow, theme-primary, theme-secondary](#orange-blue-green-red-yellow-theme-primary-theme-secondary)
- [Black](#black)
- [Gold, sliver, bronze](#gold-sliver-bronze)
- [Regular expression patterns](#regular-expression-patterns)
- [Deprecation of powder color set](#deprecation-of-powder-color-set)
- [Referencing theme colors without stop suffix](#referencing-theme-colors-without-the-stop-suffix)
- [Deprecation of Less color variables](#deprecation-of-less-color-variables)
- [Replacing Less color variables](#replacing-less-color-variables)
- [Referencing Less color variables](#referencing-less-color-variables)
- [Using legacy colors](#using-legacy-colors)
- [Using the `-legacy` suffix](#using-the--legacy-suffix)
- [Examples of legacy color references](#examples-of-legacy-color-references)
- [Helpful regular expressions](#helpful-regular-expressions)
- [Add `-legacy` suffix to colors](#add--legacy-suffix-to-colors)
- [Add `-legacy` to aliased values](#add--legacy-to-aliased-values)
- [Custom theme generation](#custom-theme-generation)
- [Replacing `.generate-calculated-themed-variables()`](#replacing-generate-calculated-themed-variables)
- [Deprecation of `.s-btn__primary`](#deprecation-of-s-btn__primary)

## Upgrading dependencies

While updating to Stacks v2, you must also update other Stacks dependencies you may have included in your project. Below is a table of Stacks dependencies and the corresponding minimum versions compatible with Stacks v2.

Dependency | Minimum version
:-:|:-:
[stacks](https://github.com/StackExchange/Stacks) | [2.0.0](https://www.npmjs.com/package/@stackoverflow/stacks/v/2.0.0)
[stacks-editor](https://github.com/StackExchange/Stacks-Editor) | [0.9.0](https://www.npmjs.com/package/@stackoverflow/stacks-editor/v/0.9.0)
[stacks-icons](https://github.com/StackExchange/Stacks-Icons) | [6.0.0](https://www.npmjs.com/package/@stackoverflow/stacks-icons/v/6.0.0)

## Using Stacks v2 colors

In Stacks v2, all components and atomic classes have been updated to use new color sets optimized for accessibility. In the process, the previous colors have been deprecated and the number of color stops has been reduced. This section will help you migrate to use the new colors.

### Color stop mappings

Stacks v2 reduces and unifies the number of color stops for each set of colors. Below, you'll find a series of tables that map the old color stops to the new color stops. Update your color references by mapping them to the new stop values.

> **Note**
> The `powder` color set has been deprecated and is not included in the updated colors. See the [deprecation of powder color set](#deprecation-of-powder-color-set) section for more information.
#### Orange, blue, green, red, yellow, theme-primary, theme-secondary

Stacks v1 | Stacks v2
:-:|:-:
025*† | 100
050, 075* | 200
100, 150*, 200 | 300
300, 350*, 400, 500 | 400
600, 700 | 500
800, 900 | 600

- *only applies to theme colors
- †only applies to green and red

#### Black

Stacks v1 | Stacks v2
:-:|:-:
N/A | 050
025 | 100
050 | 150
075 | 200
100 | 225
150 | 250
200 | 300
300, 350 | 350
400, 500 | 400
600, 700 | 500
750, 800, 900 | 600

#### Gold, sliver, bronze

Stacks v1 | Stacks v2
:-:|:-:
[color]-lighter | 100
N/A | 200
[color] | 300
[color]-darker | 400

#### Regular expression patterns

Below is just one example of a regular expression that can help you find and replace color references. Swap the color names and stop suffixes to update different remappings.

###### Find
```regexp
(theme-primary|theme-secondary|orange|blue|green|red|yellow)-(100|150|200)
```

###### Replace
```regexp
$1-300
```

### Deprecation of `powder` color set

Stacks v2 no longer includes the `powder` color set. We recommend you replace all references to `powder` with `blue`. If you need to continuing referencing `powder`, you can use the `-legacy` suffix until the library permanently removes legacy colors. See the [using legacy colors](#using-legacy-colors) section for more information.

### Referencing theme colors without the stop suffix

We've removed the `-color` suffix from the default theme variable custom properties. Previously, you could reference the 400 stop of theme colors with `theme-(primary|secondary)-color`. Now, you should reference the 400 stop of theme colors with `theme-(primary|secondary)`. Below is a table showing the old and new custom property names, though this pattern also applies to color, background, and border utility classes.

Variable | Stacks v1 | Stacks v2
:-:|:-:|:-:
**Primary** | `--theme-primary-color` | `--theme-primary`
**Secondary** | `--theme-secondary-color` | `--theme-secondary`

## Deprecation of Less color variables

Stacks v2 deprecates the usage of Less variables outside of Stacks. Although there's no way to make these variables truly private, we now discourage referencing them directly unless otherwise stated in our official documentation and advise that changes to psuedo-private variables may break your code if you reference them.

### Replacing Less color variables

Stacks v2 includes new CSS custom properties to replace a handful of commonly referenced Less variables. Update your Less variable references to the new CSS custom properties where possible.

Stacks v1 | Stacks v2
:-:|:-:
`@black` | `var(--_black-static)`
`@white` | `var(--_white-static)`

### Referencing Less color variables

In rare circumstances, you may need to reference a color value directly in order to operate on it and generate a new color or extract some value. In these cases, you *can* reference colors within a given color set. We advise against this and don't guarantee that these variables will remain stable. Nevertheless, here's how you would reference a Less color variable in Stacks v2.

Stacks v1 | Stacks v2
:-:|:-:
`@black-350` | `.set-black()[350]`

## Using legacy colors

Legacy colors are deprecated and will be removed January 2024. We **strongly** recommend you migrate to the new colors as soon as possible. With that said, you may have a need to reference legacy colors in the short term. This section gives an overview of how to reference legacy colors.

### Using the `-legacy` suffix

Stacks v2 replaces v1 colors, but you can still reference the v1 colors by adding the `-legacy` label to your color references. The `-legacy` suffix will generally come *after* the color name and *before* a color stop suffix (if it exists). This applies to atomic color classes (such as `.bc-*`, `.bg-*`, and `.fc-*`), CSS custom properties, and Less variables. See the [legacy color documentation](https://stackoverflow.design/product/v1/base/colors/) for more information.

### Examples of legacy color references

Stacks v1 | Stacks v2
:-:|:-:
`.bc-red-800` | `.bc-red-legacy-800`
`--theme-secondary-400` | `--theme-secondary-legacy-400`
`--theme-base-primary-color-h` | `--theme-base-primary-color-legacy-h`
`.fc-light` | `.fc-light-legacy`
`.fc-white__forced` | `.fc-white-legacy__forced`
`@black` | `@black-legacy`

### Helpful regular expressions

Below you'll find a set of regular expressions to help you find and replace existing color references with corresponding legacy reference.

> **Note**
> Even with these regular expressions, you'll may still need to find and replace some color references manually. For example, this regex will not alter references to `black` that don't contain a numeric stop suffix.
#### Add `-legacy` suffix to colors

##### Find
```regexp
(theme-primary|theme-secondary|black|orange|blue|green|red|yellow|powder|fog)-(025|050|075|100|150|200|300|350|400|500|600|700|750|800|900)
```

##### Replace
```regexp
// Replace
$1-legacy-$2
```

#### Add `-legacy` to aliased values

##### Find
```regexp
(bc|fc|bg)-(lightest|lighter|light|medium|darker|dark)
```

##### Replace
```regexp
$1-$2-legacy
```

## Custom theme generation

Stacks v2 has deprecated the Less function `.generate-calculated-themed-variables()` in favor of the newly added `.create-custom-theme-hsl-variables()` function. This new function works differently behind the scenes, but it accepts the same arguments and generates the same CSS custom properties as its deprecated equivelent. See the [theming documentation](https://stackoverflow.design/product/guidelines/theming/).

### Replacing `.generate-calculated-themed-variables()`

To update to the new custom theme variable generation function, simply search for `.generate-calculated-themed-variables` in your codebase and replace it with `.create-custom-theme-hsl-variables`.

## Deprecation of `.s-btn__primary`

Stacks v2 deprecates the `.s-btn__primary` variant. To retain a similar style, we recommend replacing all instances of `.s-btn__primary` with `.s-btn__filled`. See the [button documentation](https://stackoverflow.design/product/components/buttons/) for more information.
20 changes: 20 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ Stacks documentation can be found at https://stackoverflow.design/
## Table of contents

- [Using Stacks](#using-stacks)
- [Migrating from v1 to v2](#migrating-from-v1-to-v2)
- [Building Stacks](#building-stacks)
- [Format Stacks](#format-stacks)
- [Linting Stacks](#linting-stacks)
Expand All @@ -33,6 +34,10 @@ Stacks documentation can be found at https://stackoverflow.design/
## Using Stacks
Using Stacks is outlined in our [usage guidelines](https://stackoverflow.design/product/guidelines/using-stacks).

## Migrating from v1 to v2

To migrate from Stacks v1 to v2, see our [migration guide](/MIGRATION_GUIDE.md).

## Building Stacks
To contribute to Stacks documentation or its CSS library, you’ll need to build Stacks locally. View our [building guidelines](https://stackoverflow.design/product/guidelines/building).

Expand Down Expand Up @@ -109,6 +114,21 @@ npm run test:visual:update

Failing tests (including diffs) can be found under `screenshots/[browser]/failed/` folders.

### Less Tests

This is an experimental suite to test the generation of CSS from Less files.
Less tests end with this suffix `*.less.test.ts`.

Execute the less tests suite by running:
```sh
npm run test:less
```

Update the css snapshots via:
```sh
npm run test:less:update
```

## Releasing a new version of Stacks
Stacks uses [Semantic Versioning](https://semver.org/), is distributed via [npm](https://www.npmjs.com/package/@stackoverflow/stacks), and publishes [release notes on Github](https://github.com/StackExchange/Stacks/releases). Follow the steps below to release a new version of Stacks.

Expand Down
4 changes: 2 additions & 2 deletions adrs/0001-pseudo-private-custom-properties.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ Defining a structure for component styles using pseudo-private custom properties
--_cn-bg: var(--yellow-100);

&.s-component-name__filled {
--_cn-bg-filled: var(--yellow-800);
--_cn-bg-filled: var(--yellow-600);
}
}

Expand All @@ -100,7 +100,7 @@ Defining a structure for component styles using pseudo-private custom properties

// INTERACTION
&:hover {
--_cn-bg: var(--_black-050);
--_cn-bg: var(--black-150);
}

// STYLES MODIFIED BY COMPONENT-SPECIFIC CUSTOM PROPERTIES
Expand Down
Loading

0 comments on commit 0ce7557

Please sign in to comment.