Update Tailwind configs to align UI with the design system #272
+360
−247
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
✅ Deploy Preview for criipto-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
nmoskaleva
commented
Jan 16, 2026
Collaborator
Author
|
@Trinurt Side navigation should probably be white on mobile as well? |
The docs were using colors and typography different from those defined by our design system. This change enforces a consistent design language and includes: - Replacing obsolete colors with brand (new) ones - Updating `<code>` styles - Changing side navigation background to white and using the same "divider"(border) styles as on the Dashboard
nmoskaleva
force-pushed
the
update-colors
branch
from
e2da8bb to
2fec87a
Compare
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.
The docs were using colors and typography different from those defined by our design system. This change enforces a consistent design language and includes:
<code>stylesQA: Please click around and verify that color choices (backgrounds, fonts) are appropriate.
Updating form field elements (input fields, select, checkboxes etc.) and buttons will follow in a different PR, so if you see older-looking input fields – this is expected.