jekyll-tailwindcss

jekyll-tailwindcss

Jekyll plugin to use tailwindcss without node

jekyll logo

Want a Jekyll website built?

Hire a Jekyll developer
Download

Jekyll::Tailwindcss

Bring the fun of building with TailwindCSS into your Jekyll project (without any JavaScript)

TL;DR This gem borrows heavily from tailwindcss-rails to provide platform-specific tailwind executables and provide a smooth developer experience in Jekyll projects

"Because building a great jekyll site shouldn't require a node_modules folder"

Installation

Install the gem in your jekyll project's Gemfile by executing the following:

bundle add jekyll-tailwindcss --group jekyll_plugins

Or by adding the gem manually

# Gemfile
# ...
group :jekyll_plugins do
 # ...
 gem "jekyll-tailwindcss"
end

[!NOTE] By adding this gem to the jekyll_plugins group, you don't need to explicitly configure it in _config.yml.

Choosing a specific version of tailwindcss

This gem uses the latest TailwindCSS by default. However since CLI versions are managed by the tailwindcss-ruby gem, it supports older versions as well.

You can use an older Tailwind version by specifying it in your Gemfile:

# Gemfile
# ...
group :jekyll_plugins do
 # ...
 gem "jekyll-tailwindcss"
end
# gem versions track against tailwind releases
gem "tailwindcss-ruby", "~> 3.4"
Tailwind Version 3 Setup

Tailwind V3 required a tailwind configuration file (tailwind.config.js), which needs to be specified in _config.yml:

tailwindcss:
  config: "./tailwind.config.js"

Tailwind will generate CSS for the classes found in content directories. For most jekyll sites, this would work well.

// ./tailwind.config.js
/** @type {import('tailwindcss').Config} */
module.exports = {
  content: [
    "./_drafts/**/*.md",
    "./_includes/**/*.html",
    "./_layouts/**/*.html",
    "./_pages/*.{html,md}",
    "./_posts/*.md",
    "./*.{html,md}",
  ],
  // ...
};

Learn more at https://v3.tailwindcss.com/docs/configuration

Example CSS

Any CSS file with frontmatter and @tailwind directives will be converted.

/* assets/css/styles.css */
---
# This yaml frontmatter is required for jekyll to process the file
---

@tailwind base;
@tailwind components;
@tailwind utilities;

.btn {
  @apply font-bold py-2 px-4 rounded !important;
}

will be converted to

/* _site/assets/css/styles.css */

/*
 * Tailwind generated CSS 
 * ...
 */

PostCSS Support

This gem includes basic PostCSS support. If a postcss.config.js file is included in your _config.yml, the Tailwind CLI will be invoked with the --postcss flag.

tailwindcss:
  config: "./tailwind.config.js" # this is the default location
  postcss: "./postcss.config.js" # OPTIONAL, only if you have a postcss config file

[!NOTE] PostCSS configuration is considered an advanced use case and is outside the scope of this gem. Users should verify their PostCSS setup outside this gem by running: bundle exec tailwindcss --postcss postcss.config.js

Usage

bundle exec jekyll serve # or build

Any *.css file processed by jekyll [^1] that contains the @import "tailwindcss"; directive will be converted through the Tailwind CLI.

[^1]: Jekyll will process any file that begins with yaml frontmatter

Example

Any CSS file with frontmatter and @import "tailwindcss"; will be converted.

Your CSS file

/* assets/css/styles.css */
---
# This yaml frontmatter is required for jekyll to process the file
---

@import "tailwindcss";

.btn {
  @apply rounded border border-gray-300;
}

will be converted to

/* _site/assets/css/styles.css */

/*
 * Tailwind generated CSS 
 * ...
  .btn {
    border-radius: 0.25rem;
    border-style: var(--tw-border-style);
    border-width: 1px;
    border-color: var(--color-gray-300);
  }
 * ...
 */

Minification

The --minify flag is automatically added when the JEKYLL_ENV environment variable is present and set to anything other than development. Jekyll Docs

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests.

To install this gem on your local machine, run bundle exec rake install.

Testing this gem

Running the test suite

The unit tests are run with bundle exec rspec

Testing in a Jekyll project

If you want to test modifications to this gem, you can point your Jekyll project's Gemfile at the local version of the gem as you normally would:

# Gemfile
# ...
group :jekyll_plugins do
 # ...
  gem "jekyll-tailwindcss", path: "/path/to/jekyll-tailwindcss"
end

Cutting a release

  • bump the version
    • update lib/jekyll-tailwindcss/version.rb
    • update CHANGELOG.md
    • bundle install to pick up the new version
    • commit and create a git tag ( example git tag -a v0.3.1 -m "Release 0.3.1" )
  • push
    • bundle exec rake build
    • `gem push pkg/jekyll-tailwind-[NEW_VERSION].gem
    • git push --follow-tags
  • announce

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/vormwald/jekyll-tailwindcss. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Jekyll::Tailwindcss project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the code of conduct.

minimalacademicresumeportfoliodocumentationwikitailwindbootstrapdarkecommercegithub-pagesblog
jekyll logo

Want a Jekyll website built?

Hire a Jekyll developer