-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: removed data from config and add in data #75
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for dainty-scone-61e301 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks Good To Me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ... must have been a tedious task
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we merge this PR later? Also I have some suggestions:
- rename
tailwind-colors
tocolors
- after that, rather than using
{{ site.data.colors.bg-colors.___ }}
, we can assign a variable eg.{% assign bg-colors = site.data.colors.bg-colors %}
then just use{{ bg-colors.orange }}
. This variable will be assigned inheader.html
which ensures consistency across layouts.
@aayush105 |
This PR resolves #74
All the tailwind color are moved to the
data/tailwind-colors.yml
file and also updated all the html files respectively with the value fromsite.bg-colors -
>site.data.tailwind-colors.bg-colors
.