new conf design — colors #2
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
saihaj
approved these changes
Apr 28, 2025
hasparus
force-pushed
the
new-conf-design--colors
branch
from
c9f0a87 to
a263043
Compare
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced May 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added new colors to the Tailwind config.
https://www.figma.com/design/aPUvZDSxJfYDJtPd7GF2sB/GraphQL.org?node-id=54-1444&m=dev
Similarly as in the design system in Figma, and to avoid conflicts with it, the neutral palette is scheme-swapped (Theme UI-style, not Tailwind-style). I probably wouldn't do it for an app or super high fidelity landing page, but it might be a fair decision for something smaller, like a conference website.