Skip to content
A plugin to use PostCSS plugins like Autoprefixer or Tailwind CSS with Jekyll.
Ruby Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib Bump version to v0.2.2 Jun 6, 2019

Jekyll PostCSS

Build Status Gem Version

A plugin to use PostCSS plugins like Autoprefixer or Tailwind CSS with Jekyll.

The goal of this project is to be able to use modern CSS tooling with Jekyll, without the hassle of dealing with other build tools. It should be as easy as bundle exec jekyll serve.


Add this line to your application's Gemfile:

gem 'jekyll-postcss'

And then add this line to your application's _config.yml:

# _config.yml

  - jekyll-postcss


Make sure you have postcss-cli installed and has its binary located at ./node_modules/.bin/postcss.

Add your PostCSS plugins to a postcss.config.js file in the root of your repository.

// postcss.config.js

module.exports {
  plugins: [
    require("autoprefixer") // example of plugin you might use

All files with the .css extension will now be processed by PostCSS.


jekyll-postcss will cache your styles to avoid rebuilding when nothing has changed.


After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to


Bug reports and pull requests are welcome on GitHub at This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.


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

Code of Conduct

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

You can’t perform that action at this time.