This repository was archived by the owner on May 8, 2021. It is now read-only.
Jekyll: Upgrade to Tailwind CSS 1.2.0, fix purgecss, minor fixes #60
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.
Hey!
Thanks for all your work on Tailwind CSS and these setup examples. They're awesome :)
I was working with Jekyll for the past few days and came across a few problems. I fixed all of them and would like to contribute them back to this repository.
This also fixes #56 in which purgecss was not working. I noticed this due to the "generated"
site.css
being 1.1MB in size, which is the original size. After fixing purgecss, its size is now 8kb - sounds more reasonable.Major Changes
jekyll-feed
andjekyll-seo-tag
were missing, both in theGemfile
and in the_config.yml
. Their (liquid) tags were however used inlayouts/default.html
. So I assume the original intent was to include them and fixed it.Minor Changes
Gemfile
: Sync it with what jekyll generates for a new project (jekyll version3.8.6
).exclude
list in_config.yml
: Order alphabetically, remove unused entries (bin
andnetlify.toml
), addpackage.json
which was included in builds so far.