Skip to content

Conversation

@dancormier
Copy link
Contributor

@dancormier dancormier commented Oct 22, 2025

SPARK-49


Deploy preview

This PR updates Stacks to use the new SHINE color palettes.

TODO

  • All colors updated
    • Light
    • Dark
    • Light HC
    • Dark HC
  • Pink color set added
  • Metallic colors sets removed
  • Documentation updated as needed
  • (verify) Code highlight colors updated
  • (verify) Update or remove translucent color sets (these are mostly used for focus rings)

cc @leileitun3

@changeset-bot
Copy link

changeset-bot bot commented Oct 22, 2025

⚠️ No Changeset found

Latest commit: 8260d81

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@netlify
Copy link

netlify bot commented Oct 22, 2025

Deploy Preview for stacks ready!

Name Link
🔨 Latest commit 8260d81
🔍 Latest deploy log https://app.netlify.com/projects/stacks/deploys/68fa8e265c1da300080e5676
😎 Deploy Preview https://deploy-preview-2015--stacks.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Oct 22, 2025

Deploy Preview for stacks-svelte ready!

Name Link
🔨 Latest commit 8260d81
🔍 Latest deploy log https://app.netlify.com/projects/stacks-svelte/deploys/68fa8e262311030008fd88ae
😎 Deploy Preview https://deploy-preview-2015--stacks-svelte.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor Author

@dancormier dancormier left a comment

Choose a reason for hiding this comment

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

@CGuindon, @leileitun3 I've popped in a few questions here

//
// tl;dr: don't put inline after values in this file

// TODO SPARK update default values for white and black sets
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@CGuindon currently we have black and white colors with no stop (used like bg-black for example. What should those values be?

Here's what they are now for reference:

  • white
    • light: hsl(0, 0%, 100%)
    • dark: hsl(210, 3%, 15%)
    • light HC: hsl(0, 0%, 100%)
    • dark HC: hsl(0, 0%, 0%)
  • black
    • light: hsl(0, 0%, 0%)
    • dark: hsl(0, 0%, 100%)
    • light HC: hsl(0, 0%, 0%)
    • dark HC: hsl(0, 0%, 100%)

Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm assuming we can keep them all the same expect for the White > dark which looks custom.

I think that must be our background color when in dark mode? It's not a pure black background (like our pure white background in black). That value is hsl(0, 0%, 8%)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Note to reviewers: This file is where the vast majority of changes have happened.


// highlight
// TODO consult with design to potentially map static colors to new colors variables
// TODO SHINE request colors for use in code blocks (or verify these can be used for now)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@CGuindon These highlight sets are used for syntax-highlighted code (see Code blocks). Do we expect to change these colors now or should we keep them as-is for the moment?

Copy link
Collaborator

Choose a reason for hiding this comment

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

@dancormier These colors have their own custom hex/hsl code associations? I would keep the same

}

// translucent utility colors (HC set represents both light and dark HC modes)
// TODO SHINE remove once they're no longer used (probably once focus ring is updated -- currently used )
Copy link
Contributor Author

@dancormier dancormier Oct 23, 2025

Choose a reason for hiding this comment

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

@CGuindon we have these translucent colors which are used as focus rings (and around the stepped variant of the progress bar). Can you remind me of the plan for focus rings?

If we can make them non-translucent across the board (as they currently are on buttons), I think we can get rid of these sets.

Copy link
Collaborator

Choose a reason for hiding this comment

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

@dancormier Yes our plan would be to transition everything from translucent to use actual color stops. So for that stepped progress bar, we'd use a solid blue-100 on the outer ring instead of something with opacity (if I understood that correctly). Focus-rings should use a solid color (like buttons). Anything with a translucent style (like that stepped progress bar will get removed once it gets redesigned). We removed it from the activity indicator so I see this no longer being part of our visual language moving forward.

Are you able to get a list of all the translucent places? Rule of thumb re-mapping would be to use the 100 stop variant instead for now until we redesign that component altogether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants