-
Notifications
You must be signed in to change notification settings - Fork 11
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
Rethink purge settings and dist #7
Comments
Response from @Scotchester:
I think it could be nice to offer this as an extra CSS distribution, like Or at least offer advice on how a consumer of Explorer 1 can get access to those. I think the options for this would be:
Does that sound right? |
@Scotchester Yes, I agree with that approach! |
Another approach that users can take that would eliminate this problem:
|
Other versions of compiled CSS we should consider providing:
|
Right now, the compiled CSS is purged according to usage in
www-frontend
. (note: I think we'd change this to purge against our HTML stories once those are ready.)This means that other tailwind classes are removed from
explorer-1.min.css
. Should we also provide a version that doesn't purge them? The file would be much larger, but then users could have access to other Tailwind classes that we aren't using and purge them on their own.I noticed this when testing
BaseCarouselCards
inindex.html
. I usedp-28
for each slide. When testing this same HTML with the purged CSS,p-28
was purged, so some formatting was lost.The text was updated successfully, but these errors were encountered: