Skip to content
Discussion options

You must be logged in to vote

To achieve that, you'd need separate source CSS files per page. You'd then disable automatic source detection and handpick the files that Tailwind should scan per CSS file (per page).

However, I would say this would get unweildy. Rather, The paradigm of Tailwind CSS is to have one global CSS file as you do now. Initially the CSS file size goes up quickly for a project, but after a certain size, the CSS file size mellows out. This is because as a project grows, there is more class reuse. Further, having one CSS file means that only 1 CSS file needs to be downloaded once for the site. The cache could then be used for other page visits. I see you've use compression so the transfer size is on…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by outbound
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
2 participants