Your first plugin
Plugins allow you to extend Jekyll’s behavior to fit your needs. There are six types of plugins in Jekyll.
GeneratorsPermalink
Generators create content on your site. For example:
- jekyll-feed creates an Atom feed of blog posts.
- jekyll-archives creates archive pages for blog categories and tags.
- jekyll-sitemap creates a sitemap.
ConvertersPermalink
Converters change a markup language into another format. For example:
- jekyll-textile-converter converts textile to HTML.
- jekyll-coffeescript converts Coffeescript to JavaScript.
- jekyll-opal converts Ruby to JavaScript.
CommandsPermalink
Commands extend the jekyll
executable with
subcommands. For example:
- jekyll-compose adds subcommands for creating a post, page or draft.
TagsPermalink
Tags create custom Liquid tags. For example:
- jekyll-youtube embeds a YouTube video.
- jekyll-asset-path-plugin outputs a relative URL for assets.
- jekyll-swfobject embeds a SWF object.
FiltersPermalink
Filters create custom Liquid filters. For example:
- jekyll-time-ago - The distance between two dates in words.
- jekyll-toc - Generates a table of content.
- jekyll-email-protect - Obfuscates emails to protect them from spam bots.
HooksPermalink
Hooks give fine-grained control to extend the build process.
FlagsPermalink
There are two flags to be aware of when writing a plugin:
Flag | Description |
---|---|
|
A boolean flag that informs Jekyll whether this plugin may be safely
executed in an environment where arbitrary code execution is not
allowed. This is used by GitHub Pages to determine which core plugins
may be used, and which are unsafe to run. If your plugin does not
allow for arbitrary code execution, set this to |
|
This flag determines what order the plugin is loaded in. Valid values
are: |
To use one of the example plugins above as an illustration, here is how you’d specify these two flags:
module Jekyll
class UpcaseConverter < Converter
safe true
priority :low
...
end
end
Best PracticesPermalink
The guides help you with the specifics of creating plugins. We also have some recommended best practices to help structure your plugin.
We recommend using a gem for your plugin. This will help you manage dependencies, keep separation from your site source code and allow you to share functionality across multiple projects. For tips on creating a gem take a look a the Ruby gems guide or look through the source code of an existing plugin such as jekyll-feed.