(feat) generation of utility classes #146
Closed
Conversation
This file contains 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
|
Which is the difference between |
Hi! The design tokens are the design elements that will be applied to our project, like colors, font sizes, border-radius, etc. On the other hand, I created utility classes to implement those design tokens in this project: for example, we have colors, sure, but we have background colors, font colors, border colors, etc. So we can use utility classes to implement those in our design. Let me know if that answer was clear enough! :) |
|
Closing this PR because I'm uploading it again with design token documentation |
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.
Created design tokens with Sass and become them in utility classes to resolves #116 . Documentation pending