-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
WIP: chore: adds initial tailwind config #50
base: main
Are you sure you want to change the base?
Conversation
@@ -1,78 +1,120 @@ | |||
<!doctype html> |
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.
Uff. Sorry about the diff. Prettier got me. Will fix.
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.
This looks like a great start to me, in getting the workflow set up. Thanks for figuring out Chomp here.
chompfile.toml
Outdated
name = 'generate:api:css' | ||
run = 'tailwindcss -i ./public_html/styles/input.css -o ./public_html/style.main.css' | ||
invalidation = 'always' |
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.
To integrate, public_html/style.main.css
should be added into the dependencies of the top-level tasks.
The dep
is then public_html/styles/input.css
. Then invalidation doesn't need to be set and will happen automatically.
Also can we move public_html/styles/input.css
outside of public_html if it doesn't need to be served itself?
WIP: Adds initial tailwind config (which works)
The reason for tailwind is if we stick to "no custom css" with tailwind, we can quickly change themes, maintain, and update the site.