<!DOCTYPE HTML>
<html lang="en-US">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta name="generator" content="Jekyll v3.8.3">
<link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites">
<link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
<link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css">
<link rel="stylesheet" href="/css/screen.css">
<link rel="icon" type="image/x-icon" href="/favicon.ico">
<!-- Begin Jekyll SEO tag v2.4.0 -->
<title>News | Jekyll • Simple, blog-aware, static sites</title>
<meta name="generator" content="Jekyll v3.8.3">
<meta property="og:title" content="News">
<meta name="author" content="all">
<meta property="og:locale" content="en_US">
<meta name="description" content="Transform your plain text into static websites and blogs">
<meta property="og:description" content="Transform your plain text into static websites and blogs">
<link rel="canonical" href="https://jekyllrb.com/news/">
<meta property="og:url" content="https://jekyllrb.com/news/">
<meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites">
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@jekyllrb">
<meta name="twitter:creator" content="@all">
<meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY">
<script type="application/ld+json">
{"description":"Transform your plain text into static websites and blogs","author":{"@type":"Person","name":"all"},"@type":"WebPage","url":"https://jekyllrb.com/news/","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"},"name":"all"},"headline":"News","@context":"http://schema.org"}</script>
<!-- End Jekyll SEO tag -->
<!--[if lt IE 9]>
<script src="/js/html5shiv.min.js"></script>
<script src="/js/respond.min.js"></script>
<![endif]-->
</head>
<body class="wrap">
<header>
<div class="flexbox">
<div class="center-on-mobiles">
<h1>
<a href="/" class="logo">
<span class="sr-only">Jekyll</span>
<img src="/img/logo-2x.png" width="140" height="65" alt="Jekyll Logo">
</a>
</h1>
</div>
<nav class="main-nav hide-on-mobiles">
<ul>
<li class="">
<a href="/">Home</a>
</li>
<li class="">
<a href="/docs/home/">Docs</a>
</li>
<li class="current">
<a href="/news/">News</a>
</li>
<li class="">
<a href="/help/">Help</a>
</li>
</ul>
</nav>
<div class="search hide-on-mobiles">
<input type="text" id="docsearch-input" placeholder="Search the docs…">
</div>
<div class="meta hide-on-mobiles">
<ul>
<li>
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.3">v3.8.3</a>
</li>
<li>
<a href="https://github.com/jekyll/jekyll">GitHub</a>
</li>
</ul>
</div>
</div>
<nav class="mobile-nav show-on-mobiles">
<ul>
<li class="">
<a href="/">Home</a>
</li>
<li class="">
<a href="/docs/home/">Docs</a>
</li>
<li class="current">
<a href="/news/">News</a>
</li>
<li class="">
<a href="/help/">Help</a>
</li>
<li>
<a href="https://github.com/jekyll/jekyll">GitHub</a>
</li>
</ul>
</nav>
</header>
<section class="news">
<div class="grid">
<div class="docs-nav-mobile unit whole show-on-mobiles">
<select onchange="if (this.value) window.location.href=this.value">
<option value="">Navigate the blog…</option>
<option value="/news/">Home</option>
<optgroup label="v1.x">
<option value="/news/2018/06/05/jekyll-3-8-3-released/">Jekyll 3.8.3 Released</option>
<option value="/news/2018/05/19/jekyll-3-8-2-released/">Jekyll 3.8.2 Released</option>
<option value="/news/2018/05/01/jekyll-3-8-1-released/">Jekyll 3.8.1 Released</option>
<option value="/news/2018/02/24/jekyll-3-7-3-released/">Jekyll 3.7.3 Released</option>
<option value="/news/2018/02/19/meet-jekyll-s-new-lead-developer/">Meet Jekyll's New Lead Developer</option>
<option value="/news/2018/01/25/jekyll-3-7-2-released/">Jekyll 3.7.2 Released</option>
<option value="/news/2018/01/02/jekyll-3-7-0-released/">Jekyll 3.7.0 Released</option>
<option value="/news/2017/10/21/jekyll-3-6-2-released/">Jekyll 3.6.2 Released</option>
<option value="/news/2017/10/19/diversity-open-source/">Diversity in Open Source, and Jekyll's role in it</option>
<option value="/news/2017/09/21/jekyll-3-6-0-released/">Jekyll turns 3.6!</option>
<option value="/news/2017/08/12/jekyll-3-5-2-released/">Jekyll 3.5.2 Released</option>
<option value="/news/2017/07/17/jekyll-3-5-1-released/">Jekyll 3.5.1 Released</option>
<option value="/news/2017/06/15/jekyll-3-5-0-released/">Jekyll turns 3.5, oh my!</option>
<option value="/news/2017/03/21/jekyll-3-4-3-released/">Jekyll 3.4.3 Released</option>
<option value="/news/2017/03/09/jekyll-3-4-2-released/">Jekyll 3.4.2 Released</option>
<option value="/news/2017/03/02/jekyll-3-4-1-released/">Jekyll 3.4.1, or "Unintended Consequences"</option>
<option value="/news/2017/01/18/jekyll-3-4-0-released/">Jekyll turns 3.4.0</option>
<option value="/news/2016/11/14/jekyll-3-3-1-released/">Jekyll 3.3.1 Released</option>
<option value="/news/2016/10/06/jekyll-3-3-is-here/">Jekyll 3.3 is here with better theme support, new URL filters, and tons more</option>
<option value="/news/2016/08/24/jekyll-admin-initial-release/">Jekyll Admin Initial Release</option>
<option value="/news/2016/08/02/jekyll-3-2-1-released/">Jekyll 3.2.1 Released with Fix for Windows</option>
<option value="/news/2016/07/26/jekyll-3-2-0-released/">Jekyll turns 3.2</option>
<option value="/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/">Jekyll's Google Summer of Code Project: The CMS You Always Wanted</option>
<option value="/news/2016/05/19/jekyll-3-1-6-released/">Jekyll 3.1.6 Released</option>
<option value="/news/2016/05/18/jekyll-3-1-5-released/">Jekyll 3.1.5 Released</option>
<option value="/news/2016/05/18/jekyll-3-1-4-released/">Jekyll 3.1.4 "Stability Sam" Released</option>
<option value="/news/2016/04/26/jekyll-3-0-5-released/">Jekyll 3.0.5 Released</option>
<option value="/news/2016/04/19/jekyll-3-1-3-released/">Jekyll 3.1.3 Released</option>
<option value="/news/2016/04/19/jekyll-3-0-4-released/">Jekyll 3.0.4 Released</option>
<option value="/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/">Making it easier to contribute to Jekyll</option>
<option value="/news/2016/02/19/jekyll-3-1-2-released/">Jekyll 3.1.2 Released!</option>
<option value="/news/2016/02/08/jekyll-3-0-3-released/">Jekyll 3.0.3 Released</option>
<option value="/news/2016/01/28/jekyll-3-1-1-released/">Jekyll 3.1.1 Released</option>
<option value="/news/2016/01/24/jekyll-3-1-0-released/">Jekyll 3.1.0 Released</option>
<option value="/news/2016/01/20/jekyll-3-0-2-released/">Jekyll 3.0.2 Released</option>
<option value="/news/2015/11/17/jekyll-3-0-1-released/">Jekyll 3.0.1 Released</option>
<option value="/news/2015/10/26/jekyll-3-0-released/">Jekyll 3.0 Released</option>
<option value="/news/2015/02/26/introducing-jekyll-talk/">Join the Discussion at Jekyll Talk</option>
<option value="/news/2015/01/24/jekyll-3-0-0-beta1-released/">Jekyll 3.0.0.beta1 Released</option>
<option value="/news/2015/01/20/jekyll-meet-and-greet/">Jekyll Meet & Greet at GitHub HQ</option>
<option value="/news/2014/12/22/jekyll-2-5-3-released/">Jekyll Release for the Holidays! v2.5.3 Out</option>
<option value="/news/2014/12/17/alfredxing-welcome-to-jekyll-core/">Alfred Xing has joined the Jekyll core team</option>
<option value="/news/2014/11/12/jekyll-2-5-2-released/">Jekyll 2.5.2 Released</option>
<option value="/news/2014/11/09/jekyll-2-5-1-released/">Jekyll 2.5.1 Released</option>
<option value="/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/">Jekyll's Mid-Life Crisis (Or, Jekyll turns 2.5.0)</option>
<option value="/news/2014/09/09/jekyll-2-4-0-released/">A Wild Jekyll 2.4.0 Appeared!</option>
<option value="/news/2014/08/10/jekyll-2-3-0-released/">Jekyll 2.3.0 Released</option>
<option value="/news/2014/07/29/jekyll-2-2-0-released/">Jekyll 2.2.0 Released</option>
<option value="/news/2014/07/01/jekyll-2-1-1-released/">Jekyll 2.1.1 Released</option>
<option value="/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/">Jekyll Turns 21! Err... I mean 2.1.0.</option>
<option value="/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/">Pick Up your $1 Jekyll Sticker</option>
<option value="/news/2014/05/08/jekyll-2-0-3-released/">Jekyll 2.0.3 Released</option>
<option value="/news/2014/05/06/jekyll-turns-2-0-0/">Jekyll turns 2.0.0</option>
<option value="/news/2014/03/27/jekyll-1-5-1-released/">Jekyll 1.5.1 Released</option>
<option value="/news/2014/03/24/jekyll-1-5-0-released/">Jekyll 1.5.0 Released</option>
<option value="/news/2014/01/13/jekyll-1-4-3-released/">Jekyll 1.4.3 Released</option>
<option value="/news/2013/12/16/jekyll-1-4-2-released/">Jekyll 1.4.2 Released</option>
<option value="/news/2013/12/09/jekyll-1-4-1-released/">Jekyll 1.4.1 Released</option>
<option value="/news/2013/12/07/jekyll-1-4-0-released/">Jekyll 1.4.0 Released</option>
<option value="/news/2013/11/26/jekyll-1-3-1-released/">Jekyll 1.3.1 Released</option>
<option value="/news/2013/11/04/jekyll-1-3-0-released/">Jekyll 1.3.0 Released</option>
<option value="/news/2013/10/28/jekyll-1-3-0-rc1-released/">Jekyll 1.3.0.rc1 Released</option>
<option value="/news/2013/09/14/jekyll-1-2-1-released/">Jekyll 1.2.1 Released</option>
<option value="/news/2013/09/06/jekyll-1-2-0-released/">Jekyll 1.2.0 Released</option>
<option value="/news/2013/07/25/jekyll-1-1-2-released/">Jekyll 1.1.2 Released</option>
<option value="/news/2013/07/25/jekyll-1-0-4-released/">Jekyll 1.0.4 Released</option>
<option value="/news/2013/07/24/jekyll-1-1-1-released/">Jekyll 1.1.1 Released</option>
<option value="/news/2013/07/14/jekyll-1-1-0-released/">Jekyll 1.1.0 Released</option>
<option value="/news/2013/06/07/jekyll-1-0-3-released/">Jekyll 1.0.3 Released</option>
<option value="/news/2013/05/12/jekyll-1-0-2-released/">Jekyll 1.0.2 Released</option>
<option value="/news/2013/05/08/jekyll-1-0-1-released/">Jekyll 1.0.1 Released</option>
<option value="/news/2013/05/05/jekyll-1-0-0-released/">Jekyll 1.0.0 Released</option>
</optgroup>
</select>
</div>
<div class="unit four-fifths">
<article>
<h2>
<a href="/news/2018/06/05/jekyll-3-8-3-released/">
Jekyll 3.8.3 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
05 Jun 2018
</span>
<a href="https://github.com/pathawks" class="post-author">
<img class="avatar avatar-small" alt="pathawks" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/pathawks?v=3&s=24" srcset="https://avatars3.githubusercontent.com/pathawks?v=3&s=24 1x, https://avatars3.githubusercontent.com/pathawks?v=3&s=48 2x, https://avatars3.githubusercontent.com/pathawks?v=3&s=72 3x, https://avatars3.githubusercontent.com/pathawks?v=3&s=96 4x">
pathawks
</a>
</div>
<div class="post-content">
<p>This release fixes a regression in 3.8 where collections with <code class="highlighter-rouge">published: false</code>
do not show when using the <code class="highlighter-rouge">--unpublished</code> flag.</p>
<p>Thanks to <a href="https://github.com/philipbelesky" class="user-mention">@philipbelesky</a> for reporting and fixing this issue; collections with
<code class="highlighter-rouge">published: false</code> now behave the same way as Posts.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2018/05/19/jekyll-3-8-2-released/">
Jekyll 3.8.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
19 May 2018
</span>
<a href="https://github.com/pathawks" class="post-author">
<img class="avatar avatar-small" alt="pathawks" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/pathawks?v=3&s=24" srcset="https://avatars3.githubusercontent.com/pathawks?v=3&s=24 1x, https://avatars3.githubusercontent.com/pathawks?v=3&s=48 2x, https://avatars3.githubusercontent.com/pathawks?v=3&s=72 3x, https://avatars3.githubusercontent.com/pathawks?v=3&s=96 4x">
pathawks
</a>
</div>
<div class="post-content">
<p>Hello Jekyllers!!</p>
<p>Today we are releasing <code class="highlighter-rouge">v3.8.2</code>, which fixes the way Jekyll generates excerpts
for posts when the first paragraph of the post contains Liquid tags that take
advantage of <a href="https://shopify.github.io/liquid/basics/whitespace/">Liquid’s whitespace control feature</a>.</p>
<p>Big thanks to <a href="https://github.com/kylebarbour" class="user-mention">@kylebarbour</a>, who first reported this issue and also very quickly
submitted a fix. Also thanks to <a href="https://github.com/nickskalkin" class="user-mention">@nickskalkin</a> for making sure that we are using
the latest version of Rubocop to lint our code.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2018/05/01/jekyll-3-8-1-released/">
Jekyll 3.8.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
01 May 2018
</span>
<a href="https://github.com/pathawks" class="post-author">
<img class="avatar avatar-small" alt="pathawks" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/pathawks?v=3&s=24" srcset="https://avatars3.githubusercontent.com/pathawks?v=3&s=24 1x, https://avatars3.githubusercontent.com/pathawks?v=3&s=48 2x, https://avatars3.githubusercontent.com/pathawks?v=3&s=72 3x, https://avatars3.githubusercontent.com/pathawks?v=3&s=96 4x">
pathawks
</a>
</div>
<div class="post-content">
<p>Happy May Day <img class="emoji" title=":tada:" alt=":tada:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f389.png" height="20" width="20"></p>
<p>The Jekyll team is happy to announce the release of <code class="highlighter-rouge">v3.8.1</code>, which fixes
a couple of bugs that were introduced two weeks ago in <code class="highlighter-rouge">v3.8.0</code>. If you have
experienced trouble regarding post excerpts or non-published posts, this release
should be the remedy. Thanks to <a href="https://github.com/Chaosed0" class="user-mention">@Chaosed0</a> and <a href="https://github.com/domLocalHeroes" class="user-mention">@domLocalHeroes</a> for originally
reporting these issues, and to <a href="https://github.com/ashmaroli" class="user-mention">@ashmaroli</a> for fixing them so quickly.</p>
<p>As a reminder, we have started work on Jekyll 4.0. If there are any
features that you would love to see added to Jekyll, or any pain points you
would like to see removed, please do add your ideas to the <a href="https://github.com/jekyll/jekyll/issues/6948">Jekyll 4.0 idea
list</a>.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2018/02/24/jekyll-3-7-3-released/">
Jekyll 3.7.3 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
24 Feb 2018
</span>
<a href="https://github.com/ashmaroli" class="post-author">
<img class="avatar avatar-small" alt="ashmaroli" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/ashmaroli?v=3&s=24" srcset="https://avatars0.githubusercontent.com/ashmaroli?v=3&s=24 1x, https://avatars0.githubusercontent.com/ashmaroli?v=3&s=48 2x, https://avatars0.githubusercontent.com/ashmaroli?v=3&s=72 3x, https://avatars0.githubusercontent.com/ashmaroli?v=3&s=96 4x">
ashmaroli
</a>
</div>
<div class="post-content">
<p>Hello Jekyllers!! <img class="emoji" title=":wave:" alt=":wave:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f44b.png" height="20" width="20"></p>
<p>We’re pleased to announce the release of <code class="highlighter-rouge">v3.7.3</code> which fixes a bug one might encounter while using <code class="highlighter-rouge">Jekyll - 3.7.x</code> along with a
Jekyll plugin that in turn uses the <code class="highlighter-rouge">I18n</code> library.</p>
<p>When <a href="/news/2018/01/02/jekyll-3-7-0-released/">v3.7.0</a> enhanced our <code class="highlighter-rouge">slugify</code> filter with a <code class="highlighter-rouge">latin</code> option, we also
hardcoded a default fallback locale for the <code class="highlighter-rouge">I18n</code> library to avoid an exception raised in the event the library fails to find
any locale. This led to issues with third-party i18n plugins for Jekyll, especially since the default locale got assigned before
the plugin was loaded, irrespective of whether the <code class="highlighter-rouge">slugify</code> filter was used.</p>
<p>Jekyll will henceforth set the default locale if and only if necessary.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2018/02/19/meet-jekyll-s-new-lead-developer/">
Meet Jekyll's New Lead Developer
</a>
</h2>
<span class="post-category">
<span class="label">
team
</span>
</span>
<div class="post-meta">
<span class="post-date">
19 Feb 2018
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Jekyll has a new Lead Developer: <a href="https://liv.cat/">Olivia</a>!</p>
<p>After over 5 years of leading Jekyll, many releases from 0.12.1 to 3.6.0, and
countless conversations in GitHub Issues, Pull Requests, Jekyll Talk, and
more, I am passing on the torch as Lead Developer of Jekyll.</p>
<p>Olivia has been working with the Jekyll community for some time now. You
may have seen her around in issues and pull requests on the various Jekyll
repositories. She started as a contributor, then joined the Core team as our
community lead. Olivia joined the Jekyll Core Team with experience in the
Node.js community, both online and as a volunteer organizer with JSConf EU.</p>
<p>In my conversations with Olivia, it is clear that Jekyll’s vision of
simplicity for the user (<a href="/philosophy#1-no-magic">no magic!</a>) and letting
users’ <a href="/philosophy#3-content-is-king">content be king</a> will remain a top
priority. In just the last few weeks as the transition has been occurring,
we have seen some incredible work on performance that will make future
versions of Jekyll work better at scale. She will be prioritizing work on
innovative improvements to make Jekyll that much better for all of us.
Olivia balances an eye for quality with the need for shipping well.</p>
<p>When Tom Preston-Werner met me at GitHub HQ 2.0 in January 2013 to pass on
the torch, I could never have dreamed of all the amazing experiences this
community would share with me over the next 5 years. From visiting <a href="https://github.com/qrush" class="user-mention">@qrush</a>
in Buffalo, NY for a hack night on Jekyll to attending a Jekyll planning
session hosted by <a href="https://github.com/benbalter" class="user-mention">@benbalter</a> at GitHub to Google Summer of Code which gave
us jekyll-admin, I am eternally grateful to all of you for the opportunity
to lead this excellent community. I’m confident Olivia will continue to
lead Jekyll to even greater heights.</p>
<p>As always, Happy Jekylling!</p>
<p>Parker</p>
<p><em>Curious about who else runs this show? <a href="/team/">Check out our excellent team.</a></em></p>
</div>
</article>
<article>
<h2>
<a href="/news/2018/01/25/jekyll-3-7-2-released/">
Jekyll 3.7.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
25 Jan 2018
</span>
<a href="https://github.com/ashmaroli" class="post-author">
<img class="avatar avatar-small" alt="ashmaroli" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/ashmaroli?v=3&s=24" srcset="https://avatars0.githubusercontent.com/ashmaroli?v=3&s=24 1x, https://avatars0.githubusercontent.com/ashmaroli?v=3&s=48 2x, https://avatars0.githubusercontent.com/ashmaroli?v=3&s=72 3x, https://avatars0.githubusercontent.com/ashmaroli?v=3&s=96 4x">
ashmaroli
</a>
</div>
<div class="post-content">
<p>Close on the heels of shipping 3.7.0, we were informed of a couple of
regressions due to the changes made in that release. In due time, Team Jekyll
set out to address those issues as early as possible.</p>
<p>Days later here we’re, announcing 3.7.2 (sorry for skipping 3.7.1,
RubyGems didn’t want to play nice) that fixes numerous issues! <img class="emoji" title=":tada:" alt=":tada:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f389.png" height="20" width="20">
The highlights being:</p>
<ul>
<li>
<p>A major regression in 3.7.0 was that when a Front Matter Default was
configured with a <code class="highlighter-rouge">scope["path"]</code> set to a directory, Jekyll would scan
that directory for any subfolders and files, for each document in that
<code class="highlighter-rouge">path</code>.
Though this is intended, it increases build times in proportion to the size
of the directory.</p>
<p>We addressed this by having Jekyll scan the directory path only if the user
explicitly configures the <code class="highlighter-rouge">scope["path"]</code> using wildcards.</p>
<p>Read our <a href="/docs/configuration/#glob-patterns-in-front-matter-defaults">documentation</a>
for more details.</p>
<p>A huge shout-out to <a href="https://github.com/mmistakes" class="user-mention">@mmistakes</a> for bringing this to our notice and
additionally providing us with a test repository to aid in resolving the issue.</p>
</li>
<li>
<p>Another regression reported was related to our “Custom collections
directory” feature introduced in 3.7.0.</p>
<p>Users setting <code class="highlighter-rouge">collection_dir</code> to a certain directory would have <em>altered</em>
paths to their posts still at the root of their site’s source. This
roughly translated to 404 errors on URLs to their posts.</p>
<p>Props to <a href="https://github.com/localheinz" class="user-mention">@localheinz</a> for bringing this regression to our notice.</p>
<p>We decided to resolve this by having Jekyll ignore posts and drafts at the
root of the site’s source directory if the user customizes the
<code class="highlighter-rouge">collection_dir</code> setting.</p>
<p>Ergo, if you set a custom location for your collections, please ensure you
move all of your collections into that directory. <strong>This includes posts and
drafts as well</strong>. Your links generated by
<code class="highlighter-rouge">{% post_url %}</code> or <code class="highlighter-rouge">{% link %}</code>
will adapt automatically.</p>
</li>
<li>
<p>We also found out that <code class="highlighter-rouge">gem "wdm"</code> boosts performance while directories are
being watched on Windows. So we recommend having it included in your Gemfile
for a better development experience on Windows. (Newly generated Gemfiles
will hereafter have that gem listed automatically <img class="emoji" title=":wink:" alt=":wink:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f609.png" height="20" width="20">)</p>
</li>
</ul>
<p>In addition to the above, numerous other minor fixes and documentation updates
have been made that should improve your Jekyll experience. All of which, would
not have been possible without our wonderful contributors:</p>
<p>Alexandr, Andreas Möller, Ashwin Maroli, Chayoung You, Florian Thomas,
Frank Taillandier, Hendrik Schneider, Kacper Duras, Olivia, Parker Moore and
Paul Robert Lloyd.</p>
<p>As always, you can see our full changelog on <a href="/docs/history/">the History page</a>.</p>
<p>Happy Jekylling! <img class="emoji" title=":sparkles:" alt=":sparkles:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/2728.png" height="20" width="20"></p>
</div>
</article>
<article>
<h2>
<a href="/news/2018/01/02/jekyll-3-7-0-released/">
Jekyll 3.7.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
02 Jan 2018
</span>
<a href="https://github.com/DirtyF" class="post-author">
<img class="avatar avatar-small" alt="DirtyF" width="24" height="24" data-proofer-ignore="true" src="https://avatars1.githubusercontent.com/DirtyF?v=3&s=24" srcset="https://avatars1.githubusercontent.com/DirtyF?v=3&s=24 1x, https://avatars1.githubusercontent.com/DirtyF?v=3&s=48 2x, https://avatars1.githubusercontent.com/DirtyF?v=3&s=72 3x, https://avatars1.githubusercontent.com/DirtyF?v=3&s=96 4x">
DirtyF
</a>
</div>
<div class="post-content">
<p>We’re happy to release a new minor for the new year.
Here are a few of the latest additions from our contributors:</p>
<ul>
<li>LiveReload is available as an option during development: with <code class="highlighter-rouge">jekyll serve --livereload</code> no more manual page refresh. A big thanks to <a href="https://github.com/awood" class="user-mention">@awood</a> for this feature and to <a href="https://github.com/andreyvit" class="user-mention">@andreyvit</a>, LiveReload author.</li>
<li>New <code class="highlighter-rouge">collections_dir</code> configuration option allows you to store all your <a href="/docs/collections">collections</a> in a single folder. Your source root folder should now look cleaner <img class="emoji" title=":sparkles:" alt=":sparkles:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/2728.png" height="20" width="20"> .</li>
<li>If you’re using a <a href="/docs/themes/">gem-based theme</a> in coordination with the <code class="highlighter-rouge">--incremental</code> option, you should notice some significant speed during the regeneration process, we did see build time went down <strong>from 12s to 2s</strong> with <a href="https://github.com/mmistakes" class="user-mention">@mmistakes</a> <a href="https://github.com/mmistakes/minimal-mistakes">minimal-mistakes theme</a> during our tests.</li>
<li>Jekyll will now check to determine whether host machine has internet connection.</li>
<li>A new <code class="highlighter-rouge">latin</code> option is available to better <a href="/docs/templates/#options-for-the-slugify-filter">handle URLs slugs</a>.</li>
<li>And of course many bug fixes and updates to our documentation — which you can now search thanks to our friends <a href="https://github.com/Algolia" class="user-mention">@Algolia</a>.</li>
<li>
<a href="/docs/history/#v3-7-0">Full history is here</a>.</li>
</ul>
<p>This release wouldn’t have been possible without all the following people:</p>
<p>Aaron Borden, Alex Tsui, Alex Wood, Alexey Pelykh, Andrew Dassonville, Angelika Tyborska, Ankit Singhaniya, Ashwin Maroli, bellvat, Brandon Dusseau, Chris Finazzo, Doug Beney, Dr. Wolfram Schroers, Edward Shen, Florian Thomas, Frank Taillandier, Gert-jan Theunissen, Goulven Champenois, János Rusiczki, Jed Fox, Johannes Müller, Jon Anning, Jonathan Hooper, Jordon Bedwell, Junko Suzuki, Kacper Duras, Kenton Hansen, Kewin Dousse, Matt Rogers, Maximiliano Kotvinsky, mrHoliday, Olivia, Parker Moore, Pat Hawks, Sebastian Kulig, Vishesh Ruparelia, Xiaoiver and Yashu Mittal.</p>
<p>A big thanks to everyone!</p>
<p>Oh, one last thing…</p>
<h3 id="pray-upgrade-your-ruby">
<img class="emoji" title=":pray:" alt=":pray:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f64f.png" height="20" width="20"> upgrade your Ruby</h3>
<p>Prepare for the next major update, as next major version Jekyll 4.0 will drop support for Ruby 2.1 and 2.2.</p>
<blockquote>
<p>Ruby 2.2 is now under the state of the security maintenance phase, until the end of the March of 2018. After the date, maintenance of Ruby 2.2 will be ended. We recommend you start planning migration to newer versions of Ruby, such as 2.4 or 2.3. — <a href="https://www.ruby-lang.org/en/news/2017/12/14/ruby-2-2-9-released/">Ruby Core Team</a></p>
</blockquote>
<p>We strongly encourage you to upgrade to at least Ruby 2.4.x <a href="https://pages.github.com/versions/">like our friends at GitHub Pages</a> or even go with <a href="https://www.ruby-lang.org/en/news/2017/12/25/ruby-2-5-0-released/">Ruby 2.5</a>.</p>
<p>Happy new year to all from the Jekyll team!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/10/21/jekyll-3-6-2-released/">
Jekyll 3.6.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
21 Oct 2017
</span>
<a href="https://github.com/dirtyf" class="post-author">
<img class="avatar avatar-small" alt="dirtyf" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/dirtyf?v=3&s=24" srcset="https://avatars3.githubusercontent.com/dirtyf?v=3&s=24 1x, https://avatars3.githubusercontent.com/dirtyf?v=3&s=48 2x, https://avatars3.githubusercontent.com/dirtyf?v=3&s=72 3x, https://avatars3.githubusercontent.com/dirtyf?v=3&s=96 4x">
dirtyf
</a>
</div>
<div class="post-content">
<p>3.6.2 is out, it’s a tiny patch release and we invite you to run <code class="highlighter-rouge">bundle update</code>
if you want to avoid possible build problems with:</p>
<ul>
<li>some UTF-8 and UTF-16 encoded files,</li>
<li>fully numeric layout names (we convert those to string for you now).</li>
</ul>
<p>Other changes include updates to our documentation, like this <a href="../tutorials/video-walkthroughs/">complete
video series by Giraffe Academy</a> aimed at
complete beginners. A big thanks to Mike for this.</p>
<p>And if you’re wondering what happened to version 3.6.1, it was just our new
release maintainer getting familiar with the release process. 😄</p>
<p>We try to release patch releases as quickly as possible and we’re already
working on the next minor version 3.7.0 that will allow you to store all your
collections in a single directory. Stay tuned.</p>
<p>Theme developers are invited to test the brand new
<a href="https://github.com/benbalter/jekyll-remote-theme"><code class="highlighter-rouge">jekyll-remote-theme</code></a> plugin
and give their feedback to <a href="https://github.com/benbalter" class="user-mention">@benbalter</a>. This plugin allows you to use any
GitHub hosted theme as a remote theme!</p>
<p>Once again, many thanks to our contributors who helped make this release possible:
ashmaroli, bellvat, Frank Taillandier, i-give-up, Jan Piotrowski, Maximiliano
Kotvinsky, Oliver Steele and Pat Hawks. For some it was their <a href="/news/2017/10/19/diversity-open-source/">first
contribution to open-source</a> 👏</p>
<p>As it’s been nine years this week that Tom Preston-Werner started this project,
I also wanna seize this opportunity to thank <a href="https://github.com/jekyll/jekyll/graphs/contributors">all of the 732 contributors</a> who
helped make it possible for Jekyll to power millions of websites around the world
today.</p>
<p>Happy Birthday Jekyll! 🎂</p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/10/19/diversity-open-source/">
Diversity in Open Source, and Jekyll's role in it
</a>
</h2>
<span class="post-category">
<span class="label">
community
</span>
</span>
<div class="post-meta">
<span class="post-date">
19 Oct 2017
</span>
<a href="https://github.com/oe" class="post-author">
<img class="avatar avatar-small" alt="oe" width="24" height="24" data-proofer-ignore="true" src="https://avatars2.githubusercontent.com/oe?v=3&s=24" srcset="https://avatars2.githubusercontent.com/oe?v=3&s=24 1x, https://avatars2.githubusercontent.com/oe?v=3&s=48 2x, https://avatars2.githubusercontent.com/oe?v=3&s=72 3x, https://avatars2.githubusercontent.com/oe?v=3&s=96 4x">
oe
</a>
</div>
<div class="post-content">
<p>Open Source has a problem with diversity. GitHub recently conducted a <a href="http://opensourcesurvey.org/2017">survey</a> which revealed that 95% of the respondents were identifying as male. This is even worse than in the tech industry overall, where the percentage is only about 76%. Every other week, there seems to be another case of a maintainer engaging in targeted harassment against minorities. People somehow deem it completely okay to let these things slide, though.</p>
<p>Fortunately, there’s a couple of things we can do to make it easier and more comfortable for people that have never contributed to any open source project before, to contribute to our projects.</p>
<h2 id="add-a-code-of-conduct-and-enforce-it">Add a Code of Conduct, and enforce it</h2>
<p>This might seem like one of the easiest steps to do, but it actually requires a lot of dedication to pull through with. Basically, a Code of Conduct is a document detailing what is and what isn’t acceptable behavior in your project. A good Code of Conduct also details enforcement procedures, that means how the person violating the Code of Conduct gets dealt with. This is the point at which I’ve seen a looooot of projects fail. It’s easy enough to copy-paste a Code of Conduct into your project, but it’s more important to be clear on how to enforce it. Inconsistent —or worse, nonexistent— enforcement is just going to scare off newcomers even more!</p>
<p>The most widely adopted Code of Conduct is the <a href="https://www.contributor-covenant.org/">Contributor Covenant</a>. It’s a very good catch-all document, but it is a bit light in the enforcement section, so I’d recommend to flesh it out by yourself, be it by means of adding contact information or expanding the enforcement rules.</p>
<p>No matter which Code of Conduct you pick, the most important thing is to actually <em>read it for yourself</em>. The worst thing in open source is a maintainer that doesn’t know when they’ve violated their own Code of Conduct.</p>
<h2 id="document-your-contributing-workflow">Document your contributing workflow</h2>
<p>The problem that puts people off the most is incomplete or missing documentation, as revealed through GitHub’s <a href="http://opensourcesurvey.org/2017">open source survey</a>. A very popular myth in programming is that good code explains itself, which might be true, but only for the person writing it. It’s important, especially once you put your project out there for the world to see, to document not only your code, but also the process by which you maintain it. Otherwise, it’s going to be extremely hard for newcomers to even figure out where to begin contributing to your project.</p>
<p>Jekyll has <a href="/docs/contributing">an entire section of its docs</a> dedicated to information on how to contribute for this very reason. Every documentation page has a link to directly edit and improve it on GitHub. It’s also important to realize that not all contributions are code. It can be documentation, it can be reviewing pull requests, but it can also just be weighing into issues, and all of this should be recognized in the same way. At Jekyll, out of 397 total merged pull requests in the last year, <strong>204</strong> were documentation pull requests!</p>
<h2 id="create-newcomer-friendly-issues">Create newcomer-friendly issues</h2>
<p>For most people new to open source, the biggest hurdle is creating their first pull request. That’s why initiatives such as <a href="https://twitter.com/yourfirstpr">YourFirstPR</a> and <a href="http://www.firsttimersonly.com/">First Timers Only</a> were started. Recently, <a href="https://github.com/hoodiehq/first-timers-bot">a GitHub bot that automatically creates first-timer friendly issues</a> was launched, which makes it very easy for maintainers to convert otherwise small or trivial changes into viable pull requests that can be taken on by newcomers! So we decided to give it a shot, and we’ve created a couple of very easy <code class="highlighter-rouge">first timers only</code> issues:</p>
<ul>
<li><a href="https://github.com/jekyll/jekyll/issues/6437">Issue #6437</a></li>
<li><a href="https://github.com/jekyll/jekyll/issues/6438">Issue #6438</a></li>
<li><a href="https://github.com/jekyll/jekyll/issues/6439">Issue #6439</a></li>
</ul>
<p>(There’s also an up-to-date listing of all of our <code class="highlighter-rouge">first timers only</code> issues <a href="https://github.com/jekyll/jekyll/issues?q=is%3Aissue+is%3Aopen+label%3Afirst-time-only">here</a>)</p>
<p>These issues are designed to be taken on only by someone who has had little to no exposure to contributing to open source before, and additionally, project maintainers offer support in case a question arises.</p>
<p>Jekyll is a very big and popular open source project, and we hope that with these special issues, we can help people who haven’t contributed to open source before to catch a footing in these unsteady waters.</p>
<h2 id="be-nice">Be nice</h2>
<p>I know this is a cliche and a overused phrase, but really, it works if you pull through with it. Come to terms with the fact that some people aren’t as fast or reliable as you might want to think. Don’t get angry when a contributor takes a day longer than you might like them to. Treat new contributors to your project with respect, but also with hospitality. Think twice before you send that comment with slurs in it.</p>
<p>I’ve been contributing to open source for about 4 years now, and I’ve had my fair share of horrible, horrible experiences. But Jekyll has historically been a project that has always valued the people contributing to it over the code itself, and I hope we can keep it that way. I also hope that other project maintainers read this and take inspiration from this post. Every project should be more diverse.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/09/21/jekyll-3-6-0-released/">
Jekyll turns 3.6!
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
21 Sep 2017
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Another much-anticipated release of Jekyll. This release comes with it Rouge 2 support, but note you can continue to use Rouge 1 if you’d prefer. We also now require Ruby 2.1.0 as 2.0.x is no longer supported by the Ruby team.</p>
<p>Otherwise, it’s a massive bug-fix release! A few bugs were found and squashed with our <code class="highlighter-rouge">Drop</code> implementation. We’re using the Schwartzian transform to speed up our custom sorting (thanks, Perl community!). We now protect against images that are named like posts and we generally worked on guarding our code to enforce requirements, instead of assuming the input was as expected.</p>
<p>Please let us know if you find any bugs! You can see <a href="/docs/history/#v3-6-0">the full history here</a>.</p>
<p>Many thanks to our contributors who helped make this release possible: Aleksander Kuś, André Jaenisch, Antonio Argote, ashmaroli, Ben Balter, Bogdan, Bradley Meck, David Zhang, Florian Thomas, Frank Taillandier, Jordon Bedwell, Joshua Byrd, Kyle Zhao, lymaconsulting, Maciej Bembenista, Matt Sturgeon, Natanael Arndt, Ohad Schneider, Pat Hawks, Pedro Lamas, and Sid Verma.</p>
<p>As always, Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/08/12/jekyll-3-5-2-released/">
Jekyll 3.5.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
12 Aug 2017
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>3.5.2 is out with 6 great bug fixes, most notably one which should dramatically speed up generation of your site! In testing #6266, jekyllrb.com generation when from 18 seconds down to 8! Here is the full line-up of fixes:</p>
<ul>
<li>Backport #6266 for v3.5.x: Memoize the return value of <code class="highlighter-rouge">Document#url</code> (#6301)</li>
<li>Backport #6247 for v3.5.x: kramdown: symbolize keys in-place (#6303)</li>
<li>Backport #6281 for v3.5.x: Fix <code class="highlighter-rouge">Drop#key?</code> so it can handle a nil argument (#6288)</li>
<li>Backport #6280 for v3.5.x: Guard against type error in <code class="highlighter-rouge">absolute_url</code> (#6287)</li>
<li>Backport #6273 for v3.5.x: delegate <code class="highlighter-rouge">StaticFile#to_json</code> to <code class="highlighter-rouge">StaticFile#to_liquid</code> (#6302)</li>
<li>Backport #6226 for v3.5.x: <code class="highlighter-rouge">Reader#read_directories</code>: guard against an entry not being a directory (#6304</li>
</ul>
<p>A <a href="/docs/history/#v3-5-2">full history</a> is available for your perusal. As always, please file bugs if you encounter them! Opening a pull request with a failing test for your expected behaviour is the easiest way for us to address the issue since we have a reproducible example to test again. Short of that, please fill out our issue template to the best of your ability and we’ll try to get to it quickly!</p>
<p>Many thanks to our contributors without whom this release could not be
possible: Ben Balter & Kyle Zhao.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/07/17/jekyll-3-5-1-released/">
Jekyll 3.5.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
17 Jul 2017
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>We’ve released a few bugfixes in the form of v3.5.1 today:</p>
<ul>
<li>Some plugins stopped functioning properly due to a NoMethodError for <code class="highlighter-rouge">registers</code> on NilClass. That’s been fixed.</li>
<li>A bug in <code class="highlighter-rouge">relative_url</code> when <code class="highlighter-rouge">baseurl</code> is <code class="highlighter-rouge">nil</code> caused URL’s to come out wrong. Squashed.</li>
<li>Static files’ liquid representations should now have all the keys you were expecting when serialized into JSON.</li>
</ul>
<p>We apologize for the breakages! We’re working diligently to improve how we test our plugins with Jekyll core to prevent breakages in the future.</p>
<p>More details in <a href="/docs/history/#v3-5-1">the history</a>. Many thanks to all the contributors to Jekyll v3.5.1: Adam Voss, ashmaroli, Ben Balter, Coby Chapple, Doug Beney, Fadhil, Florian Thomas, Frank Taillandier, James, jaybe, Joshua Byrd, Kevin Plattret, & Robert Jäschke.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/06/15/jekyll-3-5-0-released/">
Jekyll turns 3.5, oh my!
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
15 Jun 2017
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Good news! Nearly 400 commits later, Jekyll 3.5.0 has been released into
the wild. Some new shiny things you might want to test out:</p>
<ul>
<li>Jekyll now uses Liquid 4, the latest! It comes with whitespace control, new filters <code class="highlighter-rouge">concat</code> and <code class="highlighter-rouge">compact</code>, loop performance improvements and <a href="https://github.com/Shopify/liquid/blob/master/History.md#400--2016-12-14--branch-4-0-stable">many fixes</a>
</li>
<li>Themes can specify runtime dependencies (in their gemspecs) and we’ll require those. This makes it easier for theme writers to use plugins.</li>
<li>Speaking of themes, we’ll properly handle the discrepancy between a convertible file in the local site and a static file in the theme. Overriding a file locally now doesn’t matter if it’s convertible or static.</li>
<li>Pages, posts, and other documents can now access layout variables via <code class="highlighter-rouge">{{ layout }}</code>.</li>
<li>The <code class="highlighter-rouge">gems</code> key in the <code class="highlighter-rouge">_config.yml</code> is now <code class="highlighter-rouge">plugins</code>. This is backwards-compatible, as Jekyll will gracefully upgrade <code class="highlighter-rouge">gems</code> to <code class="highlighter-rouge">plugins</code> if you use the former.</li>
<li>Filters like <code class="highlighter-rouge">sort</code> now allow you to sort based on a subvalue, e.g. <code class="highlighter-rouge">{% assign sorted = site.posts | sort: "image.alt_text" %}</code>.</li>
<li>You can now create tab-separated data files.</li>
<li>Using <code class="highlighter-rouge">layout: none</code> will now produce a file with no layout. Equivalent to <code class="highlighter-rouge">layout: null</code>, with the exception that <code class="highlighter-rouge">none</code> is a truthy value and won’t be overwritten by front matter defaults.</li>
<li>No more pesky errors if your URL contains a colon (sorry about those!)</li>
<li>We now automatically exclude the <code class="highlighter-rouge">Gemfile</code> from the site manifest when compiling your site. No more <code class="highlighter-rouge">_site/Gemfile</code>!</li>
<li>We fixed a bug where abbreviated post dates were ignored, e.g. <code class="highlighter-rouge">_posts/2016-4-4-april-fourth.md</code>.</li>
</ul>
<p>And <a href="/docs/history/">so much more!</a></p>
<p>There was a huge amount of effort put into this release by our maintainers,
especially <a href="https://github.com/pathawks" class="user-mention">@pathawks</a>, <a href="https://github.com/DirtyF" class="user-mention">@DirtyF</a>, and <a href="https://github.com/pup" class="user-mention">@pup</a>. Huge thanks to them for ushering
this release along and keeping the contributions flowing! Jekyll wouldn’t
work without the tireless dedication of our team captains & maintainers.
Thank you, all!</p>
<p>A huge thanks as well to our contributors to this release: Adam Hollett, Aleksander Kuś, Alfred Myers, Anatoliy Yastreb, Antonio Argote, Ashton Hellwig, Ashwin Maroli, Ben Balter, BlueberryFoxtrot, Brent Yi, Chris Finazzo, Christoph Päper, Christopher League, Chun Fei Lung, Colin, David Zhang, Eric Leong, Finn Ellis, Florian Thomas, Frank Taillandier, Hendrik Schneider, Henry Kobin, Ivan Storck, Jakub Klímek, Jan Pobořil, Jeff Puckett, Jonathan Hooper, Kaligule, Kevin Funk, Krzysztof Szafranek, Liu Cheng, Lukasz Brodowski, Marc Bruins, Marcelo Canina, Martin Desrumaux, Mer, Nate, Oreonax, Parker Moore, Pat Hawks, Pedro Lamas, Phil Nash, Ricardo N Feliciano, Ricky Han, Roger Sheen, Ryan Lue, Ryan Streur, Shane Neuville, Sven Meyer, Tom Johnson, William Entriken, Yury V. Zaytsev, Zarino Zappia, dyang, jekylltools, sean delaney, zenHeart</p>
<p>Please file any bugs with detailed replication instructions if you find any
bugs. Better yet, submit a patch if you find the bug in the code and know
how to fix it! <img class="emoji" title=":heart:" alt=":heart:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/2764.png" height="20" width="20"></p>
<p>Happy Jekylling! <img class="emoji" title=":tada:" alt=":tada:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f389.png" height="20" width="20"></p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/03/21/jekyll-3-4-3-released/">
Jekyll 3.4.3 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
21 Mar 2017
</span>
<a href="https://github.com/pathawks" class="post-author">
<img class="avatar avatar-small" alt="pathawks" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/pathawks?v=3&s=24" srcset="https://avatars3.githubusercontent.com/pathawks?v=3&s=24 1x, https://avatars3.githubusercontent.com/pathawks?v=3&s=48 2x, https://avatars3.githubusercontent.com/pathawks?v=3&s=72 3x, https://avatars3.githubusercontent.com/pathawks?v=3&s=96 4x">
pathawks
</a>
</div>
<div class="post-content">
<p>Another one-PR patch update as we continue our quest to destroy all bugs. A
fairly technical debriefing follows, but the TLDR is that we have updated the
<code class="highlighter-rouge">uri_escape</code> filter to more closely follow the pre-v3.4.0 behavior.</p>
<p>In <a href="/news/2017/01/18/jekyll-3-4-0-released/">v3.4.0</a>, we
moved away from using the deprecated
<a href="https://ruby-doc.org/stdlib-2.3.0/libdoc/uri/rdoc/URI/Escape.html#method-i-encode"><code class="highlighter-rouge">URI.escape</code></a>
in favor of
<a href="http://www.rubydoc.info/gems/addressable/Addressable/URI#encode-class_method"><code class="highlighter-rouge">Addressable::URI.encode</code></a>.
This is what powers our <a href="https://jekyllrb.com/docs/templates/"><code class="highlighter-rouge">uri_escape</code>
filter</a>.</p>
<p>While this transition was mostly a smooth one, the two methods are not
identical. While <code class="highlighter-rouge">URI.escape</code> was happy to escape any string,
<code class="highlighter-rouge">Addressable::URI.encode</code> first turns the string into an <code class="highlighter-rouge">Addressable::URI</code>
object, and will then escape each component of that object. In most cases, this
difference was insignificant, but there were a few cases where this caused some
unintended regressions when encoding colons.</p>
<p>While <strong>Addressable</strong> can understand that something like <code class="highlighter-rouge">"/example :page"</code> is a
relative URI, without the slash it cannot figure out how to turn
<code class="highlighter-rouge">"example :page"</code> into an <code class="highlighter-rouge">Addressable::URI</code> object. <code class="highlighter-rouge">URI.escape</code> had no such
objection. This lead to the following Liquid code working fine in Jekyll 3.3.x
but breaking in 3.4.0:</p>
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{{</span><span class="w"> </span><span class="s2">"example :page"</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">uri_escape</span><span class="w"> </span><span class="p">}}</span>
</code></pre></div></div>
<p>This was not an intended consequence of switching to <strong>Addressable</strong>.</p>
<p>Fortunately, the solution was not complicated. <strong>Addressable</strong> has a method
<a href="http://www.rubydoc.info/gems/addressable/Addressable/URI#normalize_component-class_method"><code class="highlighter-rouge">Addressable::URI.normalize_component</code></a>
which will simply escape the characters in a string, much like <code class="highlighter-rouge">URI.escape</code>.</p>
<p>Thanks to <a href="https://github.com/cameronmcefee" class="user-mention">@cameronmcefee</a> and <a href="https://github.com/FriesFlorian" class="user-mention">@FriesFlorian</a> for reporting
<a href="https://github.com/jekyll/jekyll/issues/5954">this issue</a>.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/03/09/jekyll-3-4-2-released/">
Jekyll 3.4.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
09 Mar 2017
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Another one-PR patch update, though without the same <a href="/news/2017/03/02/jekyll-3-4-1-released/">lessons as for the
previous release</a>.</p>
<p>This release includes a beneficial change for a number of plugins:
<strong>static files now respect front matter defaults</strong>.</p>
<p>You might be asking yourself: “why would static files, files that are
static files explicitly because they <em>don’t</em> have YAML front matter, want
to respect YAML front matter?” That’s a great question. Let me illustrate
with an example.</p>
<p>Let’s look at <code class="highlighter-rouge">jekyll-sitemap</code>. This plugin generates a list of documents,
pages, and static files, and some metadata for them in an XML file for a
Google/Yahoo/Bing/DuckDuckGo crawler to consume. If you don’t want a given
file in this list, you set <code class="highlighter-rouge">sitemap: false</code> in the YAML front matter. But
what about static files, which don’t have YAML front matter? Before this
release, they could not be excluded because they had no properties in YAML
other than <a href="https://github.com/jekyll/jekyll/blob/v3.4.1/lib/jekyll/static_file.rb#L98-L106">the ones we explicitly assigned</a>.
So if you had a PDF you didn’t want to be in your sitemap, you couldn’t use
<code class="highlighter-rouge">jekyll-sitemap</code>.</p>
<p>With this release, you can now set <a href="/docs/configuration/#front-matter-defaults">front matter
defaults</a> for static files:</p>
<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span>
<span class="pi">-</span>
<span class="na">scope</span><span class="pi">:</span>
<span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">pdfs/"</span>
<span class="na">values</span><span class="pi">:</span>
<span class="na">sitemap</span><span class="pi">:</span> <span class="no">false</span>
</code></pre></div></div>
<p>Now, for every file in the Liquid <code class="highlighter-rouge">site.static_files</code> loop which is in the
folder <code class="highlighter-rouge">pdfs/</code>, you’ll see <code class="highlighter-rouge">sitemap</code> equal to <code class="highlighter-rouge">false</code>.</p>
<p>Many thanks to <a href="https://github.com/benbalter" class="user-mention">@benbalter</a> for coming up with the solution and ensuring
sitemaps everywhere are filled with just the right content.</p>
<p>As always, if you notice any bugs, please search the issues and file one if
you can’t find another related to your issue.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/03/02/jekyll-3-4-1-released/">
Jekyll 3.4.1, or "Unintended Consequences"
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
02 Mar 2017
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Conformity is a confounding thing.</p>
<p>We write tests to ensure that a piece of functionality that works today
will work tomorrow, as further modifications are made to the codebase. This
is a principle of modern software development: every change must have a
test to guard against regressions to the functionality implemented by that
change.</p>
<p>And yet, occasionally, our very best efforts to test functionality will be
thwarted. This is because of how our code produces unintended
functionality, which naturally goes untested.</p>
<p>In our documentation, we tell users to name their posts with the following
format:</p>
<div class="language-text highlighter-rouge"><div class="highlight"><pre class="highlight"><code>YYYY-MM-DD-title.extension
</code></pre></div></div>
<p>That format specifies exactly four numbers for the year, e.g. 2017, two
letters for the month, e.g. 03, and two letters for the day, e.g. 02. To
match this, we had the following regular expression:</p>
<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="sr">%r!^(?:.+/)*(</span><span class="se">\d</span><span class="sr">+-</span><span class="se">\d</span><span class="sr">+-</span><span class="se">\d</span><span class="sr">+)-(.*)(</span><span class="se">\.</span><span class="sr">[^.]+)$!</span>
</code></pre></div></div>
<p>You might already see the punchline. While our documentation specifies the
exact number of numbers that is required for each section of the date, our
regular expression does not enforce this precision. What happens if a user
doesn’t conform to our documentation?</p>
<p>We recently <a href="https://github.com/jekyll/jekyll/issues/5603">received a bug report</a>
that detailed how the following file was considered a post:</p>
<div class="language-text highlighter-rouge"><div class="highlight"><pre class="highlight"><code>84093135-42842323-42000001-b890-136270f7e5f1.md
</code></pre></div></div>
<p>Of course! It matches the above regular expression, but doesn’t satisfy
other requirements about those numbers being a valid date (unless you’re
living in a world that has 43 million months, and 42 million (and one)
days). So, we <a href="https://github.com/jekyll/jekyll/pull/5609">modified the regular expression to match our
documentation</a>:</p>
<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="sr">%r!^(?:.+/)*(</span><span class="se">\d</span><span class="sr">{4}-</span><span class="se">\d</span><span class="sr">{2}-</span><span class="se">\d</span><span class="sr">{2})-(.*)(</span><span class="se">\.</span><span class="sr">[^.]+)$!</span>
</code></pre></div></div>
<p>Our tests all passed and we were properly excluding this crazy date with 43
million months and days. This change shipped in Jekyll v3.4.0 and all was
well.</p>
<p>Well, not so much.</p>
<p>A very common way to specify the month of February is <code class="highlighter-rouge">2</code>. This is true for
all single-digit months and days of the month. Notice anything about our
first regular expression versus our second? The second regular expression
imposes a <strong>minimum</strong>, as well as maximum, number of digits. This change
made Jekyll ignore dates with single-digit days and months.</p>
<p>The first eight years of Jekyll’s existence had allowed single-digit days
and months due to an imprecise regular expression. For some people, their
entire blog was missing, and there were no errors that told them why.</p>
<p>After receiving a few bug reports, it became clear what had happened.
Unintended functionality of the last eight years had been broken. Thus,
v3.4.0 was broken for a non-negligible number of sites. With a test site
in-hand from <a href="https://github.com/andrewbanchich" class="user-mention">@andrewbanchich</a>, I tracked it down to this regular expression
and <a href="https://github.com/jekyll/jekyll/pull/5920">reintroduced</a> a proper
minimum number of digits for each segment:</p>
<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="sr">%r!^(?:.+/)*(</span><span class="se">\d</span><span class="sr">{2,4}-</span><span class="se">\d</span><span class="sr">{1,2}-</span><span class="se">\d</span><span class="sr">{1,2})-(.*)(</span><span class="se">\.</span><span class="sr">[^.]+)$!</span>
</code></pre></div></div>
<p>And, I wrote a test.</p>
<p>This change was quickly backported to v3.4.0 and here we are: releasing
v3.4.1. It will fix the problem for all users who were using single-digit
months and days.</p>
<p>With this, I encourage all of you to look at your code for <em>unintended</em>
functionality and make a judgement call: if it’s allowed, <em>should it be</em>?
If it should be allowed, make it <em>intended</em> functionality and test it! I
know I’ll be looking at my code with much greater scrutiny going forward,
looking for unintended consequences.</p>
<p>Many thanks to our Jekyll affinity team captains who helped out, including
<a href="https://github.com/pathawks" class="user-mention">@pathawks</a>, <a href="https://github.com/pnn" class="user-mention">@pnn</a>, and <a href="https://github.com/DirtyF" class="user-mention">@DirtyF</a>. Thanks, too, to <a href="https://github.com/ashmaroli" class="user-mention">@ashmaroli</a> for reviewing my
change with an eye for consistency and precision. This was certainly a team
effort.</p>
<p>We hope Jekyll v3.4.1 brings your variable-digit dates back to their
previous glory. We certainly won’t let that unintended functionality be
unintended any longer.</p>
<p>As always, Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2017/01/18/jekyll-3-4-0-released/">
Jekyll turns 3.4.0
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
18 Jan 2017
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hey there! We have a quick update of Jekyll for you to enjoy this January.
Packed full of bug fixes as usual, thanks to the tireless efforts of our
exceptional Jekyll community. Three changes to call out:</p>
<ol>
<li>If you’re a big fan of <a href="/docs/templates/#filters"><code class="highlighter-rouge">where_by_exp</code></a>, you’ll be an
even bigger fan of <a href="/docs/templates/#filters"><code class="highlighter-rouge">group_by_exp</code></a>.</li>
<li>Using a custom timezone in Jekyll on Windows? Yeah, sorry that hasn’t ever worked
properly. We made it possible to accurately <a href="https://jekyllrb.com/docs/windows/#timezone-management">set the timezone using IANA
timezone codes</a>.</li>
<li>Documentation has been improved, notably on themes, includes and permalinks.</li>
</ol>
<p>And <a href="/docs/history/#v3-4-0">lots and lots more!</a></p>
<p>This update was made possible by the dedicated efforts of our excellent
contributors: Ajay Karwal, Alexey Rogachev, Ashwin Maroli,
BlueberryFoxtrot, Chase, Chayoung You, Dean Attali, Dmitrii Evdokimov, Don
Denton, Eldritch Cheese, Fabrice Laporte, Florian Thomas, Frank
Taillandier, Hugo, Ivan Dmitrievsky, Joel Meyer-Hamme, Josh Habdas, Kenton
Hansen, Kevin Wojniak, Kurt Anderson, Longwelwind, Max Chadwick, Nicolas
Hoizey, Nursen, Parker Moore, Pat Hawks, Purplecarrot, Ricardo N Feliciano,
Rob Crocombe, Roger Ogden, Skylar Challand, Thiago Arrais, Tim Banks, Tom
Johnson, Tunghsiao Liu, XhmikosR, Zlatan Vasović, alexmalik, brainscript,
kimbaudi, muratayusuke, penny, and yoostk.</p>
<p>As always, if you encounter bugs, please do <a href="https://github.com/jekyll/jekyll/issues">search the issues</a>
and <a href="https://github.com/jekyll/jekyll/issues/new">file an issue</a> if you aren’t able to
find a resolution. We also have <a href="https://talk.jekyllrb.com">our Jekyll Talk
forum</a> for those of you with general questions
about how to accomplish certain tasks with Jekyll.</p>
<p>We have some exciting updates in store for v3.5, and we’re hard at work on
those already.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/11/14/jekyll-3-3-1-released/">
Jekyll 3.3.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
14 Nov 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hello! We have a bugfix release of Jekyll hot off the presses for you. Key
fixes to call out:</p>
<ol>
<li>Only warn about auto-regeneration issues on Windows instead of disabling</li>
<li>Exclude very specific <code class="highlighter-rouge">vendor/</code> subdirectories instead of all of <code class="highlighter-rouge">vendor/</code>
</li>
<li>Allow permalink templates to have plaintext underscores</li>
</ol>
<p>..and lots more! Check out the <a href="/docs/history/#v3-3-1">full history for more</a>.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/10/06/jekyll-3-3-is-here/">
Jekyll 3.3 is here with better theme support, new URL filters, and tons more
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
06 Oct 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>There are tons of great new quality-of-life features you can use in 3.3.
Three key things you might want to try:</p>
<h3 id="1-themes-can-now-ship-static--dynamic-assets-in-an-assets-directory">1. Themes can now ship static & dynamic assets in an <code class="highlighter-rouge">/assets</code> directory</h3>
<p>In Jekyll 3.2, we shipped the ability to use a theme that was packaged as a
<a href="http://guides.rubygems.org/">gem</a>. 3.2 included support for includes,
layouts, and sass partials. In 3.3, we’re adding assets to that list.</p>
<p>In an effort to make theme management a bit easier, any files you put into
<code class="highlighter-rouge">/assets</code> in your theme will be read in as though they were part of the
user’s site. This means you can ship SCSS and CoffeeScript, images and
webfonts, and so on – anything you’d consider a part of the
<em>presentation</em>. Same rules apply here as in a Jekyll site: if it has YAML
front matter, it will be converted and rendered. No YAML front matter, and
it will simply be copied over like a static asset.</p>
<p>Note that if a user has a file of the same path, the theme content will not
be included in the site, i.e. a user’s <code class="highlighter-rouge">/assets/main.scss</code> will be read and
processed if present instead of a theme’s <code class="highlighter-rouge">/assets/main.scss</code>.</p>
<p>See our <a href="/docs/themes/#assets">documentation on the subject</a>
for more info.</p>
<h3 id="2-relative_url-and-absolute_url-filters">2. <code class="highlighter-rouge">relative_url</code> and <code class="highlighter-rouge">absolute_url</code> filters</h3>
<p>Want a clean way to prepend the <code class="highlighter-rouge">baseurl</code> or <code class="highlighter-rouge">url</code> in your config? These
new filters have you covered. When working locally, if you set your
<code class="highlighter-rouge">baseurl</code> to match your deployment environment, say <code class="highlighter-rouge">baseurl: "/myproject"</code>,
then <code class="highlighter-rouge">relative_url</code> will ensure that this baseurl is prepended to anything
you pass it:</p>
<figure class="highlight"><pre><code class="language-liquid" data-lang="liquid"><span class="p">{{</span><span class="w"> </span><span class="s2">"/docs/assets/"</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">relative_url</span><span class="w"> </span><span class="p">}}</span> => /myproject/docs/assets</code></pre></figure>
<p>By default, <code class="highlighter-rouge">baseurl</code> is set to <code class="highlighter-rouge">""</code> and therefore yields (never set to
<code class="highlighter-rouge">"/"</code>):</p>
<figure class="highlight"><pre><code class="language-liquid" data-lang="liquid"><span class="p">{{</span><span class="w"> </span><span class="s2">"/docs/assets/"</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">relative_url</span><span class="w"> </span><span class="p">}}</span> => /docs/assets</code></pre></figure>
<p>A result of <code class="highlighter-rouge">relative_url</code> will safely always produce a URL which is
relative to the domain root. A similar principle applies to <code class="highlighter-rouge">absolute_url</code>.
It prepends your <code class="highlighter-rouge">baseurl</code> and <code class="highlighter-rouge">url</code> values, making absolute URLs all the
easier to make:</p>
<figure class="highlight"><pre><code class="language-liquid" data-lang="liquid"><span class="p">{{</span><span class="w"> </span><span class="s2">"/docs/assets/"</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">absolute_url</span><span class="w"> </span><span class="p">}}</span> => https://jekyllrb.com/myproject/docs/assets</code></pre></figure>
<h3 id="3-siteurl-is-set-by-the-development-server">3. <code class="highlighter-rouge">site.url</code> is set by the development server</h3>
<p>When you run <code class="highlighter-rouge">jekyll serve</code> locally, it starts a web server, usually at
<code class="highlighter-rouge">http://localhost:4000</code>, that you use to preview your site during
development. If you are using the new <code class="highlighter-rouge">absolute_url</code> filter, or using
<code class="highlighter-rouge">site.url</code> anywhere, you have probably had to create a development config
which resets the <code class="highlighter-rouge">url</code> value to point to <code class="highlighter-rouge">http://localhost:4000</code>.</p>
<p>No longer! When you run <code class="highlighter-rouge">jekyll serve</code>, Jekyll will build your site with
the value of the <code class="highlighter-rouge">host</code>, <code class="highlighter-rouge">port</code>, and SSL-related options. This defaults to
<code class="highlighter-rouge">url: http://localhost:4000</code>. When you are developing locally, <code class="highlighter-rouge">site.url</code>
will yield <code class="highlighter-rouge">http://localhost:4000</code>.</p>
<p>This happens by default when running Jekyll locally. It will not be set if
you set <code class="highlighter-rouge">JEKYLL_ENV=production</code> and run <code class="highlighter-rouge">jekyll serve</code>. If <code class="highlighter-rouge">JEKYLL_ENV</code> is
any value except <code class="highlighter-rouge">development</code> (its default value), Jekyll will not
overwrite the value of <code class="highlighter-rouge">url</code> in your config. And again, this only applies
to serving, not to building.</p>
<h2 id="a-lot-more">A <em>lot</em> more!</h2>
<p>There are dozens of bug fixes and minor improvements to make your Jekyll
experience better than ever. With every Jekyll release, we strive to bring
greater stability and reliability to your everyday development workflow.</p>
<p>As always, thanks to our many contributors who contributed countless hours
of their free time to making this release happen:</p>
<p>Anatoliy Yastreb, Anthony Gaudino, Antonio, Ashwin Maroli, Ben Balter,
Charles Horn, Chris Finazzo, Daniel Chapman, David Zhang, Eduardo
Bouças, Edward Thomson, Eloy Espinaco, Florian Thomas, Frank Taillandier,
Gerardo, Heng Kwokfu, Heng, K. (Stephen), Jeff Kolesky, Jonathan Thornton,
Jordon Bedwell, Jussi Kinnula, Júnior Messias, Kyle O’Brien, Manmeet Gill,
Mark H. Wilkinson, Marko Locher, Mertcan GÖKGÖZ, Michal Švácha, Mike
Kasberg, Nadjib Amar, Nicolas Hoizey, Nicolas Porcel, Parker Moore, Pat
Hawks, Patrick Marsceill, Stephen Checkoway, Stuart Kent, XhmikosR, Zlatan
Vasović, mertkahyaoglu, shingo-nakanishi, and vohedge.</p>
<p><a href="/docs/history/#v3-3-0">Full release notes</a> are available
for your perusal. If you notice any issues, please don’t hesitate to file a
bug report.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/08/24/jekyll-admin-initial-release/">
Jekyll Admin Initial Release
</a>
</h2>
<span class="post-category">
<span class="label">
community
</span>
</span>
<div class="post-meta">
<span class="post-date">
24 Aug 2016
</span>
<a href="https://github.com/mertkahyaoglu" class="post-author">
<img class="avatar avatar-small" alt="mertkahyaoglu" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&s=24" srcset="https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&s=24 1x, https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&s=48 2x, https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&s=72 3x, https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&s=96 4x">
mertkahyaoglu
</a>
</div>
<div class="post-content">
<p><a href="https://jekyllrb.com/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/">Jekyll’s Google Summer of Code Project</a> has concluded. After three months of hard (but fun) work with my mentors <a href="https://github.com/benbalter" class="user-mention">@benbalter</a>, <a href="https://github.com/jldec" class="user-mention">@jldec</a>, and <a href="https://github.com/parkr" class="user-mention">@parkr</a>, I’m proud to announce <a href="https://github.com/jekyll/jekyll-admin">Jekyll Admin</a>’s <a href="https://github.com/jekyll/jekyll-admin/releases/tag/v0.1.0">initial release</a>. Jekyll admin is a Jekyll plugin that provides users with a traditional CMS-style graphical interface to author content and administer Jekyll sites. You can start to use it right away by following <a href="https://github.com/jekyll/jekyll-admin#installation">these instructions</a>.</p>
<p>As a Google Summer of Code student, I feel very lucky to be part of a project that the community has been wanting for such a long time. The three-month Google Summer of Code period was a great journey. It was a lot of fun developing the project and seeing how it could help the community, and going forward, we are really excited to see where the project goes with the help of the amazing Jekyll community.</p>
<p>I would like to thank my mentors who embraced me as their teammate and guided me throughout the process. They have put a lot of work and time to mentor me and helped me with everything. It was a great pleasure to work with them. I also would like to thank the wonderful Jekyll community for making Jekyll what it is today. It was amazing to see the community contribute to the project and give their feedback
prior to its release. I’m sure that they will support Jekyll Admin as much as they can and move Jekyll even further.</p>
<p>Please let us know what you think about <a href="https://github.com/jekyll/jekyll-admin">Jekyll Admin</a> and feel free to <a href="https://github.com/jekyll/jekyll-admin/blob/master/.github/CONTRIBUTING.md">contribute</a>. Your feedback and contributions are greatly appreciated.</p>
<p>Happy (graphical) Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/08/02/jekyll-3-2-1-released/">
Jekyll 3.2.1 Released with Fix for Windows
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
02 Aug 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Well, 3.2.0 has been a success, but with one fatal flaw: it doesn’t work on
Windows! Sorry, Windows users. Hot on the trail of 3.2.0, this release
should squash that <img class="emoji" title=":bug:" alt=":bug:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f41b.png" height="20" width="20">. Sorry about that!</p>
<p>This release also fixes an issue when using <a href="/docs/themes/">gem-based themes</a>
where the theme was rejected if it existed behind a symlink. This is a
common setup for the various ruby version managers, and for Ruby installed
via Homebrew. Props to <a href="https://github.com/benbalter" class="user-mention">@benbalter</a> for fixing that up.</p>
<p>Thanks to the contributors for this release: Adam Petrie, Ben Balter,
Daniel Chapman, DirtyF, Gary Ewan Park, Jordon Bedwell, and Parker Moore.</p>
<p>As always, you can see our full changelog on <a href="/docs/history/">the History page</a>.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/07/26/jekyll-3-2-0-released/">
Jekyll turns 3.2
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
26 Jul 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Happy Day! Jekyll v3.2.0 is out, and packed full of goodies.</p>
<p>Our flagship feature for this release has been <strong>themes</strong>. <em>Themes?!</em>, you
say? Yes, proper, versionable, releasable, first-class themes. We’re pretty
stoked about it and we hope you like building and using them. For now, it
only supports layouts, includes, and sass, but we have plans to include
static assets like images and CSS/JS in a future release. <a href="/docs/themes/">Read more about
it in the docs.</a> Our site template generated by <code class="highlighter-rouge">jekyll new</code>
now dogfoods this feature, using the <a href="https://github.com/jekyll/minima">minima</a> theme.</p>
<p>Some other notable changes:</p>
<ul>
<li>Symlinks are allowed as long as they target a file in the site source</li>
<li>Explicit support for Ruby 2.0.x was dropped</li>
<li>Added an <code class="highlighter-rouge">:after_init</code> Hook</li>
<li>Added a <code class="highlighter-rouge">where_exp</code> filter to provide more powerful filtering</li>
<li>Added a <code class="highlighter-rouge">link</code> liquid tag which can be used to generate URLs for any
post or document based on its path relative to the site source</li>
<li>… and lots more!</li>
</ul>
<p>As always, there is <a href="/docs/history/#v3-2-0">a full list of changes</a> for
your perusal.</p>
<p>Every release is made possible by the countless hours of hard work that our
fellow community members put into sending patches, filing thoughtful
patches, and so on. These release took the work of over 80 people:</p>
<ul>
<li>Aaron Sky</li>
<li>Adam Hollett</li>
<li>ajhit406</li>
<li>Aki</li>
<li>Alex Hanselka</li>
<li>Alex Hoyau</li>
<li>Alex Ivkin</li>
<li>Alex Kitchens</li>
<li>Alex Plescan</li>
<li>Alex Wood</li>
<li>Anatoliy Yastreb</li>
<li>Andrew Artajos</li>
<li>Andrew Munsell</li>
<li>AndrewCz</li>
<li>Ankush Menat</li>
<li>Anthony Smith</li>
<li>Ben Balter</li>
<li>Brian Jones</li>
<li>Brint O’Hearn</li>
<li>Chayoung You</li>
<li>Chris Wells</li>
<li>chrisfinazzo</li>
<li>Clark Winkelmann</li>
<li>Dan Allen</li>
<li>David Von Lehman</li>
<li>David Zhang</li>
<li>Derek Gottlieb</li>
<li>Enes Gönültaş</li>
<li>EricH</li>
<li>Erick Sasse</li>
<li>Eugênio Cabral</li>
<li>Florian Thomas</li>
<li>Frank Taillandier</li>
<li>Henry Goodman</li>
<li>Henry Wright</li>
<li>Hugo Duksis</li>
<li>Hugo Giraudel</li>
<li>Jack Reed</li>
<li>Jamie Bilinski</li>
<li>Jeff Kolesky</li>
<li>Jens Willmer</li>
<li>Jordon Bedwell</li>
<li>Josh Waller</li>
<li>Joshua Barnett</li>
<li>Keegan Mullaney</li>
<li>Kevin Miller</li>
<li>Krzysztof Jurewicz</li>
<li>Loren Rogers</li>
<li>Marcos Brito</li>
<li>Marcus Stollsteimer</li>
<li>Matt Rogers</li>
<li>Michaël Guitton</li>
<li>Mike Linksvayer</li>
<li>Mike Neumegen</li>
<li>Nathan Hazout</li>
<li>Nick</li>
<li>No</li>
<li>nscyclone</li>
<li>Parker Moore</li>
<li>Pat Hawks</li>
<li>Pierre Fenoll</li>
<li>Praveen Kumar</li>
<li>Rares Vernica</li>
<li>Saleem Rashid</li>
<li>Sam Dutton</li>
<li>Shengbin Meng</li>
<li>Shinn Kondo</li>
<li>Shinnosuke Kondo</li>
<li>skim</li>
<li>Sondre Nilsen</li>
<li>Spencer A. Bywater</li>
<li>Stephen Checkoway</li>
<li>Suriyaa Kudo</li>
<li>surrim</li>
<li>TheLucasMoore</li>
<li>Thomas Wood</li>
<li>Tim Wisniewski</li>
<li>Tom Fejfar</li>
<li>Tony Garnock-Jones</li>
<li>Vincent Wochnik</li>
<li>XhmikosR</li>
<li>Yanis Vieilly</li>
<li>Yordis Prieto</li>
<li>Zack Spencer</li>
</ul>
<p>We are so grateful to all of you for helping to put together a terrific
release. Thank you!</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/">
Jekyll's Google Summer of Code Project: The CMS You Always Wanted
</a>
</h2>
<span class="post-category">
<span class="label">
community
</span>
</span>
<div class="post-meta">
<span class="post-date">
03 Jun 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>This year, Jekyll applied to be a part of <a href="https://summerofcode.withgoogle.com/how-it-works/">Google Summer of Code</a>. Students were able to propose any project related to Jekyll. With a gracious sponsorship from GitHub and the participation of myself, <a href="https://github.com/benbalter" class="user-mention">@benbalter</a> and <a href="https://github.com/jldec" class="user-mention">@jldec</a>, Jekyll was able to accept two students for the 2016 season, <a href="https://github.com/mertkahyaoglu" class="user-mention">@mertkahyaoglu</a> and <a href="https://github.com/rush-skills" class="user-mention">@rush-skills</a>.</p>
<p>These students are working on a project that fills a huge need for the community: <em>a graphical solution for managing your site’s content.</em> Current plans include a fully-integrated admin which spins up when you run jekyll serve and provides a friendly web interface for creating and editing your content. The server and web interface will speak a common HTTP interface so either piece could be switched out for, e.g. a server which writes directly to a repository on GitHub.</p>
<p>The strength of text files as the storage medium for content has been part of Jekyll’s success. <a href="/">Our homepage</a> lauds the absence of a traditional SQL database when using Jekyll – your content should be what demands your time, not pesky database downtime. Unfortunately, understanding of the structure of a Jekyll site takes some work, enough that for some users, it’s prohibitive to using Jekyll to accomplish their publishing goals.</p>
<p>Mert and Ankur both applied to take on this challenge and agreed to split the project, one taking on the web interface and the other taking on the backend. We’re very excited to see a fully-functional CMS for Jekyll at the end of the summer produced by these excellent community members, and we hope you’ll join us in cheering them on and sharing our gratitude for all their hard work.</p>
<p>Thanks, as always, for being part of such a wonderful community that made this all possible. I’m honored to work with each of you to create something folks all around the globe find a joy to use. I look forward to our continued work to move Jekyll forward.</p>
<p>As always, Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/05/19/jekyll-3-1-6-released/">
Jekyll 3.1.6 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
19 May 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Upon releasing 3.1.5 and kicking the tires, we noticed a glaring bug: our
beloved <code class="highlighter-rouge">jsonify</code> filter doesn’t work! With that, our work was cut out for
us and we decided a 3.1.6 was necessary. This release restores sanity to
our object-to-JSON generation in Liquid and we hope you enjoy.</p>
<p>For the gory details, see <a href="https://github.com/jekyll/jekyll/pull/4914">the pull
request</a> or <a href="/docs/history/#v3-1-6">the
changelog</a>.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/05/18/jekyll-3-1-5-released/">
Jekyll 3.1.5 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
18 May 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>There’s always at least one bug, right? :)</p>
<p>Hot on the trails of <a href="/news/2016/05/18/jekyll-3-1-4-released/">v3.1.4</a>, we
bring you v3.1.5! It fixes one bug around requiring the <code class="highlighter-rouge">ExcerptDrop</code>,
which only affects Linux. For the gory details, see <a href="https://github.com/jekyll/jekyll/pull/4912">the pull
request for the fix</a>.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/05/18/jekyll-3-1-4-released/">
Jekyll 3.1.4 "Stability Sam" Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
18 May 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hey Jekyllites!</p>
<p>Today, we released v3.1.4 in an effort to bring more stability to the v3.1.x series. This bugfix release consists of:</p>
<ul>
<li>A fix for <code class="highlighter-rouge">layout</code> in Liquid where values would carry over from one document to the next</li>
<li>A fix for <code class="highlighter-rouge">layout</code> in Liquid where a parent layout (e.g. <code class="highlighter-rouge">default</code> or <code class="highlighter-rouge">base</code>) would overwrite the metadata of the child layout (e.g. <code class="highlighter-rouge">post</code> or <code class="highlighter-rouge">special</code>).</li>
<li>A fix where <code class="highlighter-rouge">page.excerpt</code> referencing its excerpt would cause an infinite loop of recursive horror.</li>
<li>We added <code class="highlighter-rouge">Configuration.from</code> and the great permalink fix from <a href="/news/2016/04/19/jekyll-3-0-4-released/">v3.0.4</a> to the v3.1.x series</li>
<li>
<code class="highlighter-rouge">site.collections</code> in Liquid is now sorted alphabetically by label, so <code class="highlighter-rouge">docs</code> shows up before <code class="highlighter-rouge">posts</code> reliably.</li>
</ul>
<p>The fixes for <code class="highlighter-rouge">layout</code> may not be seamless for everyone, but we believe they will be the “right thing to do” going forward.</p>
<p>We are alwawys striving to make Jekyll more straight-forward to use. Please do open an issue if you believe an aspect of Jekyll’s user experience isn’t up to par.</p>
<p>For a full history of our changes, <a href="/docs/history/#v3-1-4">see the changelog</a>.</p>
<p>As always, Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/04/26/jekyll-3-0-5-released/">
Jekyll 3.0.5 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
26 Apr 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>This version fixes a bug affecting only v3.0.4 where autoregeneration was
<em>always</em> disabled when running Jekyll locally. This feature is a huge
reason why Jekyll (or any static site generator, for that matter) is a joy
to use. Sorry for the regression!</p>
<p>If you’re using GitHub Pages, <a href="https://github.com/github/pages-gem/pull/285">you can follow the progress of the upgrade
on the github/pages-gem repo</a>.</p>
<p>As always, our <a href="/docs/history/#v3-0-5">history doc</a> has links to the pull
requests and issues associated with the release for your perusal.</p>
<p>We’re looking forward to the upcoming release of v3.2 which <a href="https://github.com/jekyll/jekyll/blob/master/History.markdown#head">has some
excellent goodies</a>
we think you’ll love.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/04/19/jekyll-3-1-3-released/">
Jekyll 3.1.3 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
19 Apr 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>v3.1.3 is a patch release which fixes the follow two issues:</p>
<ul>
<li>Front matter defaults may not have worked for collection documents and posts due to a problem where they were looked up by their URL rather than their path relative to the site source</li>
<li>Running <code class="highlighter-rouge">jekyll serve</code> with SSL enabled was broken due to a bad configuration.</li>
</ul>
<p>Both of these issues have been resolved. For more information, check out <a href="/docs/history/#v3-1-3">the full history</a>.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/04/19/jekyll-3-0-4-released/">
Jekyll 3.0.4 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
19 Apr 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>v3.0.4 is a patch release which fixes the follow two issues:</p>
<ul>
<li>Front matter defaults may not have worked for collection documents and posts due to a problem where they were looked up by their URL rather than their path relative to the site source</li>
<li>Configuration for the posts permalink might be borked when a user specified a value for <code class="highlighter-rouge">collections.posts.permalink</code> directly. This forced the use of <code class="highlighter-rouge">permalink</code> at the top level, which also affected pages. To configure a permalink <em>just for posts</em>, you can do so with:</li>
</ul>
<figure class="highlight"><pre><code class="language-yaml" data-lang="yaml"><span class="na">collections</span><span class="pi">:</span>
<span class="na">posts</span><span class="pi">:</span>
<span class="na">output</span><span class="pi">:</span> <span class="no">true</span>
<span class="na">permalink</span><span class="pi">:</span> <span class="s">/blog/:year/:title/</span></code></pre></figure>
<p>Both of these issues have been resolved. For more information, check out <a href="/docs/history/#v3-0-4">the full history</a>.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/">
Making it easier to contribute to Jekyll
</a>
</h2>
<span class="post-category">
<span class="label">
community
</span>
</span>
<div class="post-meta">
<span class="post-date">
10 Mar 2016
</span>
<a href="https://github.com/benbalter" class="post-author">
<img class="avatar avatar-small" alt="benbalter" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/benbalter?v=3&s=24" srcset="https://avatars0.githubusercontent.com/benbalter?v=3&s=24 1x, https://avatars0.githubusercontent.com/benbalter?v=3&s=48 2x, https://avatars0.githubusercontent.com/benbalter?v=3&s=72 3x, https://avatars0.githubusercontent.com/benbalter?v=3&s=96 4x">
benbalter
</a>
</div>
<div class="post-content">
<p>Jekyll is an open source project, built one contribution at a time by community members just like you. These community contributions can come in many forms beyond just writing code, from reporting an issue or suggesting a new feature to improving documentation or providing feedback on proposed changes.</p>
<p>If you’ve been looking to get involved with the Jekyll community, but didn’t know, we’ve recently made it easier to contribute to Jekyll in two ways:</p>
<p>First, we’ve completely rewritten <a href="https://jekyllrb.com/docs/contributing/">the project’s contributing guidelines</a>, outlining <a href="https://jekyllrb.com/docs/contributing/#ways-to-contribute">the various ways you can contribute</a>, and including better instructions for <a href="https://jekyllrb.com/docs/contributing/#submitting-a-pull-request-via-githubcom">submitting proposed changes via GitHub.com</a> or for <a href="https://jekyllrb.com/docs/contributing/#code-contributions">submitting your first code improvement</a>. And if you have any feedback, we’d love to hear it! Simply click the “improve this page” button in the top right corner of the contributing documentation.</p>
<p>Second, this week, we created six community interest groups, we’re calling <a href="https://teams.jekyllrb.com">Jekyll affinity teams</a>. If you’re interested in a particular aspect of the project (or just want to learn more), you can join any one of these teams (or two, or three), to participate in discussions about potential bugs and proposed improvements. And the best part is there’s no commitment. If you just want to listen, or if at any point you want to leave (or switch teams), that’s totally fine. We won’t say a thing. To learn more about the various affinity teams, or to join one (please do!), just head on over to <a href="https://teams.jekyllrb.com/">teams.jekyllrb.com</a>.</p>
<p>We hope these changes will make it easier for you to make your first (or second, or third) contribution to Jekyll today. Thanks for helping to make Jekyll awesome!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/02/19/jekyll-3-1-2-released/">
Jekyll 3.1.2 Released!
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
19 Feb 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Happy Friday from sunny California! Today, we’re excited to announce the release of Jekyll v3.1.2, which comes with some crucial bug fixes:</p>
<ul>
<li>If a syntax error is encountered by Liquid, it will now print the line number.</li>
<li>A nasty war between symbols and strings in our configuration hash caused kramdown syntax highlighting to break. That has been resolved; you stand victorious!</li>
<li>A tilde at the beginning of a filename will no longer crash Jekyll.</li>
<li>The <code class="highlighter-rouge">titleize</code> filter mistakenly dropped words that were already capitalized. Fixed!</li>
<li>Permalinks which end in a slash will now always output as a folder with an <code class="highlighter-rouge">index.html</code> inside.</li>
</ul>
<p>Nitty-gritty details, like always, are available in the <a href="/docs/history/">history</a>.</p>
<p>Thanks to those who contributed to this release: Alfred Xing, atomicules, bojanland, Brenton Horne, Carlos Garcés, Cash Costello, Chris, chrisfinazzo, Daniel Schildt, Dean Attali, Florian Thomas, Jordon Bedwell, Juuso Mikkonen, Katya Demidova, lonnen, Manabu Sakai, Michael Lee, Michael Lyons, Mitesh Shah, Nicolas Hoizey, Parker Moore, Pat Hawks, Prayag Verma, Robert Martin, Suriyaa Kudo, and toshi.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/02/08/jekyll-3-0-3-released/">
Jekyll 3.0.3 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
08 Feb 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p><a href="https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0">GitHub Pages upgraded to Jekyll 3.0.2</a> last week. With a testbed of
over a million sites, this really put Jekyll 3 through the wringer. This
release addresses a handful of bugs that were surfaced as a result. The
fixes:</p>
<ul>
<li>Fix problem where outputting to a folder would have two extensions</li>
<li>Handle tildes (<code class="highlighter-rouge">~</code>) in filenames properly</li>
<li>Fix issue when comparing documents without dates</li>
<li>Include line numbers in liquid error output</li>
</ul>
<p>Read more on the <a href="/docs/history/#v3-0-3">changelog</a> with links to the
related patches.</p>
<p>Please keep <a href="https://github.com/jekyll/jekyll/issues">submitting bugs</a> as you find them! Please do take a look
<a href="/help/">in our various help resources</a> before filing a bug and use <a href="https://talk.jekyllrb.com/">our
forum</a> for asking questions and getting help on a specific problem
you’re having.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/01/28/jekyll-3-1-1-released/">
Jekyll 3.1.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
28 Jan 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>This release squashes a few bugs <img class="emoji" title=":bug:" alt=":bug:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f41b.png" height="20" width="20"> <img class="emoji" title=":bug:" alt=":bug:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f41b.png" height="20" width="20"> <img class="emoji" title=":bug:" alt=":bug:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f41b.png" height="20" width="20"> noticed by a few
wonderful Jekyll users:</p>
<ul>
<li>If your <code class="highlighter-rouge">permalink</code> ended with a <code class="highlighter-rouge">/</code>, your URL didn’t have any extension,
even if you wanted one</li>
<li>We now strip the BOM by default per Ruby’s <code class="highlighter-rouge">IO.open</code>.</li>
<li>
<code class="highlighter-rouge">page.dir</code> will not always end in a slash.</li>
</ul>
<p>We also updated our <a href="/docs/conduct/">Code of Conduct</a> to the latest version of
the Contributor Covenant. The update includes language to ensure that the
reporter of the incident remains confidential to non-maintainers and that
all complaints will result in an appropriate response. I care deeply about
Jekyll’s community and will do everything in my power to ensure it is a
welcoming community. Feel free to reach out to me directly if you feel
there is a way we can improve the community for everyone! If you’re
interested in more details, <a href="https://github.com/ContributorCovenant/contributor_covenant/blob/v1_4/diffs/1_3_vs_1_4.patch">there is a diff for
that</a>.</p>
<p>See links to the PR’s on <a href="/docs/history/#v3-1-1">the history page</a>.</p>
<p>Thanks to Jordon Bedwell, chrisfinazzo, Kroum Tzanev, David Celis, and
Alfred Xing for their commits on this latest release! <img class="emoji" title=":sparkles:" alt=":sparkles:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/2728.png" height="20" width="20"></p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/01/24/jekyll-3-1-0-released/">
Jekyll 3.1.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
24 Jan 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Happy weekend! To make your weekend all the better, we have just released
v3.1.0 of Jekyll.</p>
<p>There are <em>lots</em> of great performance improvements, including a huge one
which is to use Liquid drops instead of hashes. Much of the slowness in
Jekyll is due to Jekyll making lots of objects it doesn’t need to make.
By making these objects only as they’re needed, we can speed up Jekyll
considerably!</p>
<p>Some other highlights:</p>
<ul>
<li>Fix: <code class="highlighter-rouge">permalink</code>s with non-HTML extensions will not be honored</li>
<li>Fix: <code class="highlighter-rouge">jekyll clean</code> now accepts build flags like <code class="highlighter-rouge">--source</code>.</li>
<li>Enhancement: <code class="highlighter-rouge">include</code> tags can now accept multiple liquid variables</li>
<li>Feature: adds new <code class="highlighter-rouge">sample</code> liquid tag which gets random element from an array</li>
<li>Fix: Jekyll will read in files with YAML front matter that has extraneous
spaces after the first line</li>
<li>Enhancement: extract the <code class="highlighter-rouge">title</code> attribute from the filename for
collection items without a date</li>
<li>Fix: gracefully handle empty configuration files</li>
</ul>
<p>… and <a href="/docs/history/#v3-1-0">a whole bunch more</a>!</p>
<p>Please <a href="https://github.com/jekyll/jekyll/issues/new?title=Jekyll+3.1.0+Issue:">file a bug</a>
if you encounter any issues! As always, <a href="https://talk.jekyllrb.com">Jekyll Talk</a>
is the best place to get help if you’re encountering a problem.</p>
<p>Special thanks to all our amazing contributors who helped make v3.1.0 a
possibility:</p>
<p>Alex J Best, Alexander Köplinger, Alfred Xing, Alistair Calder, Atul
Bhosale, Ben Orenstein, Chi Trung Nguyen, Conor O’Callaghan, Craig P.
Motlin, Dan K, David Burela, David Litvak Bruno, Decider UI, Ducksan Cho,
Florian Thomas, James Wen, Jordon Bedwell, Joseph Wynn, Kakoma, Liam
Bowers, Mike Neumegen, Nick Quaranto, Nielsen Ramon, Olivér Falvai, Pat
Hawks, Paul Robert Lloyd, Pedro Euko, Peter Suschlik, Sam Volin, Samuel
Wright, Sasha Friedenberg, Tim Cuthbertson, Vincent Wochnik, William
Entriken, Zshawn Syed, chrisfinazzo, ducksan cho, leethomas,
midnightSuyama, musoke, and rebornix</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2016/01/20/jekyll-3-0-2-released/">
Jekyll 3.0.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
20 Jan 2016
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>A crucial bug was found in v3.0.1 which caused invalid post dates to go
unnoticed in the build chain until the error that popped up was unhelpful.
v3.0.2 <a href="https://github.com/jekyll/jekyll/issues/4375">throws errors as you’d expect</a>
when there is a post like <code class="highlighter-rouge">_posts/2016-22-01-future.md</code> or a post has an
invalid date like <code class="highlighter-rouge">date: "tuesday"</code> in their front matter.</p>
<p>This should make the experience of working with Jekyll just a little
better.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2015/11/17/jekyll-3-0-1-released/">
Jekyll 3.0.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
17 Nov 2015
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hey, folks! Bunch of bug fixes here. Notables:</p>
<ul>
<li>Only superdirectories of <code class="highlighter-rouge">_posts</code> will be categories.</li>
<li>
<code class="highlighter-rouge">:title</code> in permalink templates are now properly cased as before</li>
<li>
<code class="highlighter-rouge">.jekyll-metadata</code> being erroneously written when not using incremental build.</li>
<li>Failure in liquid will now always fail the <code class="highlighter-rouge">jekyll</code> process.</li>
<li>All hooks should now be properly registered & documented</li>
</ul>
<p>And a bunch more changes which you can see over in the
<a href="/docs/history">changelog</a>.</p>
<p>Thanks to the 17 developers who contributed code and documentation to this
patch release: Alfred Xing, Christian Trosell, Jordan Thornquest, Jordon
Bedwell, Larry Fox, Lawrence Murray, Lewis Cowles, Matt Rogers, Nicole
White, Parker Moore, Paul Robert Lloyd, Sarah Kuehnle, Vincent Wochnik,
Will Norris, XhmikosR, chrisfinazzo, and rebornix.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2015/10/26/jekyll-3-0-released/">
Jekyll 3.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
26 Oct 2015
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>The much-anticipated Jekyll 3.0 has been released! Key changes:</p>
<ul>
<li>Incremental regeneration (experimental, enable with <code class="highlighter-rouge">--incremental</code>)</li>
<li>Liquid profiler (add <code class="highlighter-rouge">--profile</code> to a build or serve)</li>
<li>Hook plugin API (no more monkey-patching!)</li>
<li>Dependencies reduced from 14 to 8, none contain C extensions. We’re hoping to reduce this even more in the future.</li>
<li>Changed version support: no support for Ruby 1.9.3, added basic JRuby support. Better Windows support.</li>
<li>Extension-less URLs</li>
<li>
<code class="highlighter-rouge">site.collections</code> is an array of collections, thus:
<ul>
<li>
<code class="highlighter-rouge">collection[0]</code> becomes <code class="highlighter-rouge">collection.label</code>
</li>
<li>
<code class="highlighter-rouge">collection[1]</code> becomes <code class="highlighter-rouge">collection</code>
</li>
</ul>
</li>
<li>Default highlighter is now Rouge instead of Pygments</li>
<li>Lots of performance improvements</li>
<li>… and lots more!</li>
</ul>
<p>We also added a <a href="/docs/conduct/">Code of Conduct</a> to encourage a happier, nicer community where contributions and discussion is protected from negative behaviour.</p>
<p>A huge shout-out to the amazing Jekyll Core Team members Jordon Bedwell, Alfred Xing, and Matt Rogers for all their hard work in making Jekyll 3 the best release yet.</p>
<p>We also added <a href="https://talk.jekyllrb.com">Jekyll Talk</a>, managed solely by Jordon, which offers a modern forum experience for Jekyllers across the globe to talk and learn about Jekyll!</p>
<p>As always, check out the <a href="/docs/history/#v3-0-0">full history</a> for more details.</p>
<p>Our contributors are the core of what makes Jekyll great! Many thanks to the 132 contributors who made this release possible (in alphabetical order): AJ Acevedo, Adam Richeimer, Alan Scherger, Alfred Xing, Anatol Broder, Andrew Dunning, Anna Debenham, Anton, Arne Gockeln, Arthur Hammer, Arthur Neves, BRAVO, Ben Balter, Bernardo Dias, BigBlueHat, Brandon Mathis, Bruce Smith, Cai⚡️, Carlos Matallín, ChaYoung You, Christian Vuerings, Cory Simmons, David Herman, David Silva Smith, David Smith, David Wales, David Williamson, DigitalSparky, Dimitri König, Dominik, Eduardo Boucas, Eduardo Bouças, Eduardo Bouças, Erlend Sogge Heggen, Eugene Pirogov, Ezmyrelda Andrade, Fabian Rodriguez, Fabian Tamp, Fabio Niephaus, Falko Richter, Florian Weingarten, Fonso, Garen Torikian, Guillaume LARIVIERE, Günter Kits, I´m a robot, Jason Ly, Jedd Ahyoung, Jensen Kuras, Jesse Pinho, Jesse W, Jim Meyer, Joel Glovier, Johan Bové, Joop Aué, Jordan Thornquest, Jordon Bedwell, Joseph Anderson, Julien Bourdeau, Justin Weiss, Kamil Dziemianowicz, Kevin Locke, Kevin Ushey, Leonard, Lukas, Mads Ohm Larsen, Malo Skrylevo, Marcus Stollsteimer, Mark Phelps, Mark Tareshawty, Martijn den Hoedt, Martin Jorn Rogalla, Martin Rogalla, Matt Rogers, Matt Sheehan, Matthias Nuessler, Max, Max Beizer, Max White, Merlos, Michael Giuffrida, Michael Tu, Mike Bland, Mike Callan, MonsieurV, Nate Berkopec, Neil Faccly, Nic West, Nicholas Burlett, Nicolas Hoizey, Parker Moore, Pascal Borreli, Pat Hawks, Paul Rayner, Pedro Euko, Peter Robins, Philipp Rudloff, Philippe Loctaux, Rafael Picanço, Renaud Martinet, Robert Papp, Ryan Burnette, Ryan Tomayko, Seb, Seth Warburton, Shannon, Stephen Crosby, Stuart Kent, Suriyaa Kudo, Sylvester Keil, Tanguy Krotoff, Toddy69, Tom Johnson, Tony Eichelberger, Tunghsiao Liu, Veres Lajos, Vitaly Repin, Will Norris, William Entriken, XhmikosR, chrisfinazzo, eksperimental, hartmel, jaybe@jekyll, kaatt, nightsense, nitoyon, robschia, schneems, sonnym, takuti, and tasken.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2015/02/26/introducing-jekyll-talk/">
Join the Discussion at Jekyll Talk
</a>
</h2>
<span class="post-category">
<span class="label">
community
</span>
</span>
<div class="post-meta">
<span class="post-date">
26 Feb 2015
</span>
<a href="https://github.com/alfredxing" class="post-author">
<img class="avatar avatar-small" alt="alfredxing" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/alfredxing?v=3&s=24" srcset="https://avatars0.githubusercontent.com/alfredxing?v=3&s=24 1x, https://avatars0.githubusercontent.com/alfredxing?v=3&s=48 2x, https://avatars0.githubusercontent.com/alfredxing?v=3&s=72 3x, https://avatars0.githubusercontent.com/alfredxing?v=3&s=96 4x">
alfredxing
</a>
</div>
<div class="post-content">
<p>We’re super excited to announce the launch of <a href="https://talk.jekyllrb.com">Jekyll Talk</a>, a Discourse forum for anything related to Jekyll!</p>
<p>The forum was set up by <a href="https://github.com/envygeeks">@envygeeks</a> to build a community more accessible to Jekyll users and more suitable for general discussion.</p>
<p>There’s already been a lot of interesting topics, including a <a href="https://talk.jekyllrb.com/t/showcase-sites-made-using-jekyll/18">site showcase</a> and <a href="https://talk.jekyllrb.com/t/poll-installation-priorities-for-3-0/106/9">a poll for Jekyll 3.0 priorities</a>.</p>
<p>Come join the fun!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2015/01/24/jekyll-3-0-0-beta1-released/">
Jekyll 3.0.0.beta1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
24 Jan 2015
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hey!</p>
<p>Exciting news! First beta for Jekyll 3 is out. Check out the <a href="https://github.com/jekyll/jekyll/blob/v3.0.0.beta1/History.markdown#head">sizable
changelog</a>
to get a feel for what changes are afoot. Key features:</p>
<ol>
<li>
<strong>Speed.</strong> Jekyll now features incremental regeneration and greatly
improved problematic code that caused slow-downs.</li>
<li>Gobs of bugfixes and customization.</li>
<li>Uniformity and sanity to Jekyll extensions of Liquid.</li>
</ol>
<p>To install just run:</p>
<figure class="highlight"><pre><code class="language-shell" data-lang="shell"><span class="nv">$ </span>gem <span class="nb">install </span>jekyll <span class="nt">--pre</span></code></pre></figure>
<p>Future versions will include <a href="https://github.com/jekyll/jekyll/issues/3324">some awesome new
features</a> that we haven’t
built yet. If you see one you want to tackle, submit a PR & you’ll be
featured in the Jekyll 3.0 release post as a contributor to that epic
release.</p>
<p>Please file bugs as you encounter them, being sure to include your version
of Ruby, the Jekyll version, and (if possible) a link to your site so we
can reproduce.</p>
<p>If you think there’s room for improvement in the UX, also do let us know.
We’re always looking to make Jekyll easier to use!</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2015/01/20/jekyll-meet-and-greet/">
Jekyll Meet & Greet at GitHub HQ
</a>
</h2>
<span class="post-category">
<span class="label">
meetup
</span>
</span>
<div class="post-meta">
<span class="post-date">
20 Jan 2015
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hey! Our friends at GitHub have agreed to host a Jekyll meet & greet on
<strong>February 5, 2015 at 7pm</strong>. The event will be hosted at
<a href="https://goo.gl/maps/Bmy7i">GitHub’s Headquarters</a>
here in San Francisco, CA. Pizza & beer will be available for those interested,
and there will be much time to sit and chat about all things Jekyll. This would
be an especially good time to get help with bugs you’ve encountered or to talk
over a potential feature with the core team in attendance.</p>
<p>A special thanks to <a href="https://github.com/gjtorikian">@gjtorikian</a> for making this
all possible! You rock.</p>
<p>We look forward to meeting all you fine folks. Cheers!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/12/22/jekyll-2-5-3-released/">
Jekyll Release for the Holidays! v2.5.3 Out
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
22 Dec 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Happy Holidays, everyone.</p>
<p>Jekyll v2.5.3 is a quick patch release, containing some minor fixes. See the
<a href="/docs/history/">full history</a> for more info. If you notice any problems,
please <a href="https://github.com/jekyll/jekyll">let us know</a>.</p>
<p>This release also marks the start of Jekyll 3 development. I wrote about it
over on my personal blog: <a href="https://byparker.com/blog/2014/jekyll-3-the-road-ahead/">Jekyll 3 — The Road Ahead</a>.
Feel free to chime in over on GitHub.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/12/17/alfredxing-welcome-to-jekyll-core/">
Alfred Xing has joined the Jekyll core team
</a>
</h2>
<span class="post-category">
<span class="label">
team
</span>
</span>
<div class="post-meta">
<span class="post-date">
17 Dec 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>We’re excited to announce that <a href="https://github.com/alfredxing">@alfredxing</a> has joined the @jekyll/core
team!</p>
<p>He hails from Vancouver, BC, Canada, where he is studying Economics and
Computer Science at the <a href="http://www.ubc.ca">University of British Columbia</a>. Alfred popped up in
the issues a few months ago with terrific insights, focus, and humility.
Performance buffs may be pleased to hear incremental regeneration will be
released in a future version of Jekyll – a significant piece of the
feature written by Alfred.</p>
<p>Please join me in welcoming Alfred to the Jekyll core team. We’re excited
he’s agreed to lend his talents to this project. The future is an exciting
place!</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/11/12/jekyll-2-5-2-released/">
Jekyll 2.5.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
12 Nov 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>A very minor release, 2.5.2 fixes a bug with path sanitation that 2.5.1
introduced. It also improves the <code class="highlighter-rouge">post_url</code> tag such that it checks the
posts’ name (e.g. <code class="highlighter-rouge">2014-03-03-my-cool-post</code>) instead of a compiled time and
name. This fixes issues where posts are created and the day changes based
on timezone discrepancies.</p>
<p><a href="/docs/history/">Full history here.</a></p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/11/09/jekyll-2-5-1-released/">
Jekyll 2.5.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
09 Nov 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hot on the heels of v2.5.0, this release brings relief to our Windows
users. It includes a fix for a 2.5.0 path sanitation change that has been
confirmed to work on Windows.</p>
<p>To our Windows users: while we don’t officially support Windows, we don’t
wish to impede your normal use of Jekyll at all. Our lack of full support
for Windows is due to our lack of a Windows machine for development testing
(no one on the core team has a Windows machine upon which to test new
release candidates), not due to any malice or willful oversight. If you
come to us with an issue, we are more than happy to work through it with
you to come to a solution that works for all platforms. Along those lines,
we have created a <a href="https://github.com/jekyll/jekyll/issues/3069"><strong>Windows Test Force</strong></a> (WTF) which is a group of Jekyll
users dedicated to making sure all future releases work on Windows <em>before</em>
they’re released so we don’t have this issue again. A special thanks goes
out to the initial WTF team members, XhmikosR, Julian Thilo, Pedro Rogério,
and Alfred Xing.</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/">
Jekyll's Mid-Life Crisis (Or, Jekyll turns 2.5.0)
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
05 Nov 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>A new day, a new release! Jekyll just turned 2.5.0 and has gained a lot of
wisdom along the way. This 2.5.0 release also comes just a few weeks after
Jekyll turned 6 years old! In fashion, we’re celebrating this huge
milestone with a pretty big release. What’s changed in 2.5.0? Here are some
highlights:</p>
<ul>
<li>Require plugins in the <code class="highlighter-rouge">:jekyll_plugins</code> Gemfile group (turned off with an environment variable)</li>
<li>YAML Front Matter permalinks can now contain placeholders like <code class="highlighter-rouge">:name</code>. Check out all the placeholders on the <a href="/docs/permalinks/">Permalinks docs page</a>.</li>
<li>The <code class="highlighter-rouge">jsonify</code> filter now deep-converts arrays to liquid.</li>
<li>Shorted <code class="highlighter-rouge">build</code> and <code class="highlighter-rouge">serve</code> commands with <code class="highlighter-rouge">b</code> and <code class="highlighter-rouge">s</code> aliases, respectively</li>
<li>WEBrick will now list your directory if it can’t find an index file.</li>
<li>Any enumerable can be used with the <code class="highlighter-rouge">where</code> filter.</li>
<li>Performance optimizations thanks to <a href="https://github.com/tmm1" class="user-mention">@tmm1</a>’s <a href="https://github.com/tmm1/stackprof">stackprof</a>
</li>
<li>Fix for Rouge’s Redcarpet interface</li>
<li>Security auditors will love this: path sanitation has now been centralized.</li>
<li>Specify a log level with <code class="highlighter-rouge">JEKYLL_LOG_LEVEL</code>: debug, info, warn, or error.</li>
</ul>
<p>…and a whole bunch of other fixes and enhancements you can read more
about in <a href="/docs/history/">the changelog!</a></p>
<p>As always, if you run into issues, please <a href="https://github.com/jekyll/jekyll/issues">check the issues</a>
and <a href="https://github.com/jekyll/jekyll/issues/new">create an issue if one doesn’t exist for the bug you encountered</a>.
If you just need some help, the extraordinary <a href="">jekyll help team is here for
you!</a></p>
<p><em>When was the <a href="https://github.com/jekyll/jekyll/commit/d189e05d236769c1e5594af9db4d6eacb86fc16e">first commit to Jekyll</a>?
All the way back on October 19, 2008. It features interesting historical
tidbits, such as the old name for Jekyll was “autoblog”, and was first
released via Rubyforge. What a difference 6 years has made!</em></p>
<p>Thanks to the following contributors for making this release possible:</p>
<p>Parker Moore, XhmikosR, Alfred Xing, Ruslan Korolev, Pat Hawks,
chrisfinazzo, Mike Kruk, Tanguy Krotoff, Matt Hickford, Philipp Rudloff,
Rob Murray, Sean Collins, Seth Warburton, Tom Thorogood, Vasily Vasinov,
Veres Lajos, feivel, mitaa, nitoyon, snrbrnjna, tmthrgd, Bret Comnes,
Charles Baynham, Christian Mayer, Dan Croak, Frederic Hemberger, Glauco
Custódio, Igor Kapkov, and Kevin Ndung’u!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/09/09/jekyll-2-4-0-released/">
A Wild Jekyll 2.4.0 Appeared!
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
09 Sep 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Well, lookie here! A new release of Jekyll! v2.4.0 contains lots of goodies, including some brilliant new additions:</p>
<ul>
<li>A new <code class="highlighter-rouge">relative_include</code> Liquid tag (<a href="https://github.com/jekyll/jekyll/issues/2870">#2870</a>)</li>
<li>Render Liquid in CoffeeScript files (<a href="https://github.com/jekyll/jekyll/issues/2830">#2830</a>)</li>
<li>Add 4 new array Liquid filters: <code class="highlighter-rouge">push</code>, <code class="highlighter-rouge">pop</code>, <code class="highlighter-rouge">shift</code>, and <code class="highlighter-rouge">unshift</code> (<a href="https://github.com/jekyll/jekyll/pull/2895">#2895</a>)</li>
<li>Auto-enable watch on ‘serve’ (<a href="https://github.com/jekyll/jekyll/issues/2858">#2858</a>). No more <code class="highlighter-rouge">-w</code>!</li>
<li>Add <code class="highlighter-rouge">:title</code> and <code class="highlighter-rouge">:name</code> to collection URL template fillers (<a href="https://github.com/jekyll/jekyll/issues/2864">#2864</a> & <a href="https://github.com/jekyll/jekyll/issues/2799">#2799</a>)</li>
<li>Add support for CSV files in the <code class="highlighter-rouge">_data</code> directory (<a href="https://github.com/jekyll/jekyll/issues/2761">#2761</a>)</li>
<li>Add <code class="highlighter-rouge">inspect</code> liquid filter (<a href="https://github.com/jekyll/jekyll/issues/2867">#2867</a>)</li>
<li>Add a <code class="highlighter-rouge">slugify</code> Liquid filter (<a href="https://github.com/jekyll/jekyll/issues/2880">#2880</a>)</li>
</ul>
<p>Some other wunderbar bug fixes in there as well. Check out the <a href="/docs/history/">full changelog</a> for the whole scoop.</p>
<p>As always, many thanks to our amazing contributors who made this release possible: Chris Frederick, Garen Torikian, James Smith, Ruslan Korolev, Joel Glovier, Michael Kühnel, Minn Soe, Pat Hawks, Peter deHaan, Shu Uesugi, TJ, Zhuochun, Alfred Xing, nitoyon, Anatol Broder, Faruk AYDIN, Frederic Hemberger, and Gordon Gao. Thank you!!</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/08/10/jekyll-2-3-0-released/">
Jekyll 2.3.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
10 Aug 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>This latest release of Jekyll includes a slew of enhancements and bug
fixes. Some of the highlights:</p>
<ul>
<li>Strange bug around spacing/indentation should be resolved. <a href="https://github.com/jekyll/jekyll/issues/2676">It was a
curious bug indeed.</a>
</li>
<li>Pages, Posts, and Drafts can now be converted by multiple converters.</li>
<li>Static files can now be safely included in collections. They’ll be placed
in a <code class="highlighter-rouge">collection.files</code> array. <code class="highlighter-rouge">collection.docs</code> still holds exclusively
content with YAML front matter.</li>
<li>Sass files can once again be rendered by Liquid. However, neither Sass
nor CoffeeScript can ever have a layout. Bonus: <code class="highlighter-rouge">scssify</code> and <code class="highlighter-rouge">sassify</code>
Liquid filters.</li>
<li>Partial variables allowed now in the path argument of <code class="highlighter-rouge">include</code> calls</li>
<li>We added a <code class="highlighter-rouge">jekyll help</code> command. Pass it a subcommand to see more info
about that subcommand. Or don’t, to see the help for <code class="highlighter-rouge">jekyll</code> itself.</li>
<li>Lots of fixes to the site template we use for <code class="highlighter-rouge">jekyll new</code>, including
converting the CSS into SCSS.</li>
<li>The <code class="highlighter-rouge">jsonify</code> filter will now call <code class="highlighter-rouge">#to_liquid</code> for you</li>
<li>Lots, lots more!</li>
</ul>
<p>One change deserves special note. In <a href="https://github.com/jekyll/jekyll/issues/2633">#2633</a>, subfolders <em>inside</em> a
<code class="highlighter-rouge">_posts</code> folder were processed and added as categories to the posts. It
turns out, this behaviour was unwanted by a large number of individuals, as
it is a handy way to organize posts. Ultimately, we decided to revert this
change in <a href="https://github.com/jekyll/jekyll/issues/2705">#2705</a>, because it was a change in behaviour that was already
well-established (at least since Jekyll v0.7.0), and was convenient.</p>
<p>For more excellent CHANGELOG reading material, check out the <a href="/docs/history/">History
page</a>! Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/07/29/jekyll-2-2-0-released/">
Jekyll 2.2.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
29 Jul 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Jekyll 2.2.0 contains a few key updates:</p>
<ol>
<li>A warning will now fire if you specify a layout in any of your pages or
posts that doesn’t exist.</li>
<li>Certain Pygments options are now whitelisted in safe mode</li>
<li>Categories in a post’s path are now respected (i.e. folders in <code class="highlighter-rouge">_posts</code>
will now work properly).</li>
</ol>
<p>As always, a full list of the updates are on the
<a href="/docs/history/#v2-2-0">history page</a>. Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/07/01/jekyll-2-1-1-released/">
Jekyll 2.1.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
01 Jul 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>This is a minor release for Jekyll 2.1.0. It fixes a couple bugs and
introduces fixes for a couple security-related issues.</p>
<p>It covers two security vulnerabilities:</p>
<ol>
<li>One in the reading of data</li>
<li>One in the <code class="highlighter-rouge">layouts</code> setting</li>
</ol>
<p>They were identified in Jekyll 1.5.1 and has been confirmed as patched
in this version and the version used by GitHub Pages. If you are in the
business of building Jekyll sites, please ensure you upgrade to 2.1.1 as
soon as possible.</p>
<p>For more, check out <a href="https://github.com/jekyll/jekyll/pull/2563"><code class="highlighter-rouge">jekyll/jekyll#2563</code></a>.</p>
<p>Additionally, the dependency on Maruku has been loosened and a bug was
fixed with document URLs.</p>
<p>As always, check out the <a href="/docs/history/">full changelog</a> for more info!</p>
<p>Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/">
Jekyll Turns 21! Err... I mean 2.1.0.
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
28 Jun 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Jekyll’s finally <a href="https://en.wikipedia.org/wiki/Legal_drinking_age">legal to drink in the States</a>.
And he’s done a lot of learning in the process! Here are some of the new
things to look forward to:</p>
<ul>
<li>Uses the latest Liquid version (2.6.1) (#2495)</li>
<li>Set front matter defaults for collections (#2419)</li>
<li>Set a collection-specific URL template (#2418)</li>
<li>
<code class="highlighter-rouge">pygments.rb</code> 0.6.0! (#2504)</li>
<li>
<code class="highlighter-rouge">.json</code> files in <code class="highlighter-rouge">_data</code> (#2369)</li>
<li>Allow subdirectories in <code class="highlighter-rouge">_data</code> (#2395)</li>
<li>Add support for <code class="highlighter-rouge">hl_lines</code> in <code class="highlighter-rouge">highlight</code> tag (#2532)</li>
<li>Post categories now merge with directory, front matter, and defaults (#2373)</li>
<li>New <code class="highlighter-rouge">--skip_initial_build</code> flag for <code class="highlighter-rouge">jekyll serve</code> (#2477)</li>
<li>A bajilion bug fixes and site updates!</li>
</ul>
<p>Let’s go party!</p>
<p><em>Check out the <a href="/docs/history/#v2-1-0">full changelog</a> for more.</em></p>
<p>Many thanks to these 37 contributors for the 2.1.0 release:</p>
<p>Alberto Grespan, Alessandro Lorenzi, Alex Medearis, Alfred Xing, Anatol Broder, Ben, Ben Balter, Bud Parr, Chezou, Denilson Figueiredo de Sá, Denilson Sá, Ivan Tse, Jens Nazarenus, Jesse Shawl, Jordon Bedwell, Josh Davis, János Rusiczki, Marc Ransome, Mathieu Bruyen, Matt Rogers, Parker Moore, Pat Hawks, Paul Henry, Peter Rhoades, Philipp Rudloff, Quinn Shanahan, Renaud Martinet, Rob Murray, Rodrigo Dumont, Simon Sarris, Terry, Terry Schmidt, Tomer Cohen, XhmikosR, Yihang Ho, jaybe@jekyll, and mikecole.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/">
Pick Up your $1 Jekyll Sticker
</a>
</h2>
<span class="post-category">
<span class="label">
partners
</span>
</span>
<div class="post-meta">
<span class="post-date">
04 Jun 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p><img src="/img/jekyll-sticker.png" alt="Jekyll Sticker"></p>
<p>You may have heard that <a href="https://github.com/cobyism">@cobyism</a>’s excellent
Jekyll logo has been made into a sticker. You may have sat idly by, wishing
that you could have a sticker honoring your beloved Jekyll.</p>
<p>The StickerMule team says, <em>“Pine no longer!”</em> StickerMule has <strong><a href="https://www.stickermule.com/marketplace/825-jekyll-stickers">discounted the
price of Jekyll stickers down to $1 and are offering free (domestic)
shipping</a>!</strong>
Go grab one now on the StickerMule marketplace – <a href="https://twitter.com/parkr/status/430826309707902976/photo/1">they’ll look
swell on your favourite hardware.</a></p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/05/08/jekyll-2-0-3-released/">
Jekyll 2.0.3 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
08 May 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hey again! Just wanted to let you know we’ve released another version of Jekyll, jam-packed with bug fixes.</p>
<p>A huge “thank you” is in order for all the folks who have submitted bug reports over the last 2 days — your input is what allows this project to continue. It’s always a pain to deal with a MAJOR version bump release, but it’s been pretty smooth so far and you have all been nice about the flaws you’ve found in the tool. Keep filing those reports so we can continue to make Jekyll even better!</p>
<p>Thank you to the contributors that contributed code to 2.0.1, 2.0.2, and/or 2.0.3:</p>
<p>Parker Moore, Yi Zeng, Gabe Ortiz, Aaron Broder, Alberto Grespan, gpxl, David Briggs, Kevin Ingersoll, and Troy Swanson.</p>
<p>As always, check out the <a href="/docs/history/">changelog</a> for more info. Happy Jekylling!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/05/06/jekyll-turns-2-0-0/">
Jekyll turns 2.0.0
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
06 May 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>A year ago to the day, <a href="/news/2013/05/05/jekyll-1-0-0-released/">we released Jekyll 1.0.0</a>. One year later, we present to you the next major version: Jekyll 2.0.0.</p>
<p>Jam-packed with some <a href="/docs/history/">highly-requested features and bugfixes galore</a>, this is the best Jekyll yet. Some notable changes:</p>
<ol>
<li>
<a href="/docs/collections/">Collections</a> - Collections allow you to define an unlimited number of custom document types (beyond just posts and pages) for different types of content you may want to author in Jekyll such as API documentation or a cookbook!</li>
<li>
<a href="https://github.com/jekyll/jekyll/pull/2050#issuecomment-35938016">Brand new site template</a> (thanks <a href="https://github.com/jglovier">@jglovier</a>!) - Getting started with Jekyll just got a lot easier and a lot more beautiful. Just run <code class="highlighter-rouge">jekyll new <path></code> and you’re good to go.</li>
<li>
<a href="/docs/assets/">Native Sass & CoffeeScript support</a> - We love CSS and JavaScript as much as the next guy, but there will always be a special place in our hearts for Sass and CoffeeScript. We now offer native support for these file types — no more messing around with Rake or Grunt!</li>
<li>
<a href="/docs/configuration/#front-matter-defaults">YAML Front Matter defaults</a> - If you’ve set <code class="highlighter-rouge">layout: post</code> more than once in your life, you’ll love this new feature: set front matter defaults for a given directory or type.</li>
<li>
<a href="/docs/configuration/#custom-markdown-processors">Custom markdown processors</a> - Always wanted to use your favourite home-grown Markdown converter, but couldn’t with Jekyll? Now you can. Simply specify <code class="highlighter-rouge">markdown: MyConverterClass</code> and you’re on your way.</li>
<li>
<a href="/docs/templates/#filters">Addition of <code class="highlighter-rouge">where</code> and <code class="highlighter-rouge">group_by</code> Liquid filters</a> - Simplifying your Liquid templates one filter at a time. The <code class="highlighter-rouge">where</code> filter selects from an array all items within which have a given value for a property. The <code class="highlighter-rouge">group_by</code> filter groups all items in an array which have the same value for a given property.</li>
<li>
<a href="https://github.com/jekyll/jekyll/pull/1988">Switch from Maruku to Kramdown as default markdown converter</a> - Maruku is dead. We’ve replaced it with the converter which has the closest feature parity: Kramdown!</li>
</ol>
<p>Check out our <a href="/docs/history/">changelog</a> for a complete list of all (200+) changes.</p>
<p>Many thanks to these 183 contributors for making Jekyll 2.0.0 happen:</p>
<p>Parker Moore, Matt Rogers, maul.esel, Anatol Broder, Zach Gersh, Joel Glovier, Ben Balter, XhmikosR, Coby Chapple, John Piasetzki, Aidan Feldman, Robin Dupret, Pascal Borreli, Troy Swanson, Erik Michaels-Ober, albertogg, Lucas Jenss, Matt Rogers & Persa Zula, Eric Mill, Shigeya Suzuki, Jens Nazarenus, ddavison, Pat Hawks, Rob Wierzbowski, MURAOKA Taro, Casey Lang, Fabian Rodriguez, Greg Karékinian, Zlatan Vasović, Christopher Nicotera, Dmitry Chestnykh, Ryan Morrissey, Jordon, John Hughes, akira yamada, Matt Swanson, Jashank Jeremy, Matthew Iversen, Meeka, liufengyun, Anand Narayan, nitoyon, Geoff Shannon, Benjamin J. Balter, Juan Ignacio Donoso, David Briggs, Benjamin Esham, Slava Pavlutin, Assaf Gelber, Josh Brown, Nick Fagerlund, Davide Ficano, pilosus, Anthony Smith, André Arko, Mikael Konutgan, Matthew Scharley, Dan Tao, scribu, Mort Yao, m, Stephen McDonald, Marcus Stollsteimer, Thomas Torsney-Weir, Jordon Bedwell, Tom Preston-Werner, Lincoln Mullen, Philip Poots, Ivan Tse, Christopher Giroir, Valery Tolstov, Wlodek Bzyl, Xavier Noria, Yi Zeng, Persa Zula, Phil Leggetter, Pirogov Evgenij, Rafael Revi, Rob McGuire-Dale, Rob Muhlestein, Robin Mehner, Roland Warmerdam, Rusty Geldmacher, Sam Rayner, Santeri Paavolainen, Sebastian Morr, Stephan Groß, Steven Spasbo, Tobias Brunner, Tuomas Kareinen, Tyler Margison, Uwe Dauernheim, Yihang Ho, Zach Leatherman, Zequez, andrew morton, andrewhavens, imathis, jannypie, jaybe@jekyll, kk_Ataka, markets, redwallhp, schneems, szymzet, thomasdao, tomsugden, wǒis神仙, 张君君, Noah Slater, Abhi Yerra, Adam Heckler, Ahmed Hazem, Aigars Dzerviniks, Aleksey V. Zapparov, Andreas Möller, Andy Lindeman, Arlen Cuss, Aziz Shamim, Ben Baker-Smith, Ben Hanzl, Ben Hildred, Brian Kim, Brice, Carol Nichols, Chezou, Chris Jones, Christian Grobmeier, Christoph Hochstrasser, Christoph Schiessl, Clint Shryock, Colin Dean, Corey Ward, Damian Lettie, Daniel Schauenberg, David Ensinger, David Paschich, David Sawyer, David Silva Smith, Donald Perry, Doug Johnston, Edward Ball, Eric Dobson, Erik Dungan, Florent Guilleux, Francis, Frederic ROS, GSI2013, Garen Torikian, George Anderson, Giuseppe Capizzi, Ishibashi Hideto, Jarrod Birch, Jeff Kolesky, Jens Bissinger, Jens Krause, John Firebaugh, John Papandriopoulos, Josh Branchaud, Katy DeCorah, Lachlan Holden, Mark Prins, Markus Roth, Martin Charles, Matt Iversen, Matt Sheehan, Matt Swensen, Matthias Vogelgesang, Michael Parker, Miha Rekar, Nathan Youngman, Nick Quaranto, Nick Quinlan, Nick Schonning, Nicolas Alpi, Nicolás Reynolds, Nikkau, 4ensicLog, Octavian Damiean, Olov Lassus, PatrickC8t, Paul Annesley, and Paul Oppenheim.</p>
<p>Happy developing!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/03/27/jekyll-1-5-1-released/">
Jekyll 1.5.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
27 Mar 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>The hawk-eyed <a href="https://github.com/gregose">@gregose</a> spotted a bug in our
<code class="highlighter-rouge">Jekyll.sanitized_path</code> code:</p>
<figure class="highlight"><pre><code class="language-ruby" data-lang="ruby"><span class="o">></span> <span class="n">sanitized_path</span><span class="p">(</span><span class="s2">"/tmp/foobar/jail"</span><span class="p">,</span> <span class="s2">"..c:/..c:/..c:/etc/passwd"</span><span class="p">)</span>
<span class="o">=></span> <span class="s2">"/tmp/foobar/jail/../../../etc/passwd"</span></code></pre></figure>
<p>Well, we can’t have that! In 1.5.1, you’ll instead see:</p>
<figure class="highlight"><pre><code class="language-ruby" data-lang="ruby"><span class="o">></span> <span class="n">sanitized_path</span><span class="p">(</span><span class="s2">"/tmp/foobar/jail"</span><span class="p">,</span> <span class="s2">"..c:/..c:/..c:/etc/passwd"</span><span class="p">)</span>
<span class="o">=></span> <span class="s2">"/tmp/foobar/jail/..c:/..c:/..c:/etc/passwd"</span></code></pre></figure>
<p>Luckily not affecting 1.4.x, this fix will make 1.5.0 that much safer for
the masses. Thanks, Greg!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/03/24/jekyll-1-5-0-released/">
Jekyll 1.5.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
24 Mar 2014
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>As work continues on Jekyll 2.0.0, we felt it was important to address two key
issues of Jekyll 1.4.3, namely the <code class="highlighter-rouge">safe_yaml</code> dependency below 1.0 and the
inability to use Jekyll 1.4.3 on Windows due to a <a href="https://github.com/jekyll/jekyll/issues/1948">fun issue with path sanitizing</a>.</p>
<p>For a full changelog, check out our <a href="/docs/history/#v1-5-0">history</a> page.</p>
<p>Now, back to work on 2.0.0!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2014/01/13/jekyll-1-4-3-released/">
Jekyll 1.4.3 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
13 Jan 2014
</span>
<a href="https://github.com/benbalter" class="post-author">
<img class="avatar avatar-small" alt="benbalter" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/benbalter?v=3&s=24" srcset="https://avatars0.githubusercontent.com/benbalter?v=3&s=24 1x, https://avatars0.githubusercontent.com/benbalter?v=3&s=48 2x, https://avatars0.githubusercontent.com/benbalter?v=3&s=72 3x, https://avatars0.githubusercontent.com/benbalter?v=3&s=96 4x">
benbalter
</a>
</div>
<div class="post-content">
<p>Jekyll 1.4.3 contains two <strong>critical</strong> security fixes. If you run Jekyll locally
and do not run Jekyll in “safe” mode (e.g. you do not build Jekyll sites on behalf
of others), you are not affected and are not required to update at this time.
(<a href="https://github.com/jekyll/jekyll/pull/1944">See pull request.</a>)</p>
<p>Versions of Jekyll prior to 1.4.3 and greater than 1.2.0 may allow malicious
users to expose the content of files outside the source directory in the
generated output via improper symlink sanitization, potentially resulting in an
inadvertent information disclosure.</p>
<p>Versions of Jekyll prior to 1.4.3 may also allow malicious users to write
arbitrary <code class="highlighter-rouge">.html</code> files outside of the destination folder via relative path
traversal, potentially overwriting otherwise-trusted content with arbitrary HTML
or Javascript depending on your server’s configuration.</p>
<p><em>Maintainer’s note: Many thanks to <a href="https://github.com/gregose" class="user-mention">@gregose</a> and <a href="https://github.com/charliesome" class="user-mention">@charliesome</a> for discovering
these vulnerabilities, and to <a href="https://github.com/BenBalter" class="user-mention">@BenBalter</a> and <a href="https://github.com/alindeman" class="user-mention">@alindeman</a> for writing the patch.</em></p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/12/16/jekyll-1-4-2-released/">
Jekyll 1.4.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
16 Dec 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>This release fixes <a href="https://github.com/jekyll/jekyll/pull/1830">a regression</a> where Maruku fenced code blocks were turned
off, instead of the previous default to on. We’ve added a new default
configuration to our <code class="highlighter-rouge">maruku</code> config key: <code class="highlighter-rouge">fenced_code_blocks</code> and set it to
default to <code class="highlighter-rouge">true</code>.</p>
<p>If you do not wish to use Maruku fenced code blocks, you may turn this option
off in your site’s configuration file.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/12/09/jekyll-1-4-1-released/">
Jekyll 1.4.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
09 Dec 2013
</span>
<a href="https://github.com/mattr-" class="post-author">
<img class="avatar avatar-small" alt="mattr-" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/mattr-?v=3&s=24" srcset="https://avatars0.githubusercontent.com/mattr-?v=3&s=24 1x, https://avatars0.githubusercontent.com/mattr-?v=3&s=48 2x, https://avatars0.githubusercontent.com/mattr-?v=3&s=72 3x, https://avatars0.githubusercontent.com/mattr-?v=3&s=96 4x">
mattr-
</a>
</div>
<div class="post-content">
<p>Another quick turnover, anyone? A <a href="https://github.com/jekyll/jekyll/issues/1794">critical
bug</a> in the reading of
posts snuck itself into the 1.4.0 release.</p>
<p>To address this issue, we’re releasing v1.4.1 of Jekyll so that you can
keep on writing without any problems.</p>
<p>As always, you can find the full list of fixes in this release in the
<a href="/docs/history/">change log</a>!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/12/07/jekyll-1-4-0-released/">
Jekyll 1.4.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
07 Dec 2013
</span>
<a href="https://github.com/mattr-" class="post-author">
<img class="avatar avatar-small" alt="mattr-" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/mattr-?v=3&s=24" srcset="https://avatars0.githubusercontent.com/mattr-?v=3&s=24 1x, https://avatars0.githubusercontent.com/mattr-?v=3&s=48 2x, https://avatars0.githubusercontent.com/mattr-?v=3&s=72 3x, https://avatars0.githubusercontent.com/mattr-?v=3&s=96 4x">
mattr-
</a>
</div>
<div class="post-content">
<p>About a month after the release of Jekyll v1.3.0, we are releasing
Jekyll v1.4.0. This release will be the last non-patch release to support Ruby
1.8.7 and our next release will be Jekyll 2.0.0.</p>
<p>Here are a few things we think you’ll want to know about this release:</p>
<ul>
<li>
<p>TOML is now a supported markup language for config files.</p>
</li>
<li>
<p>Maruku has been updated to 0.7.0 which provides some new features and
a ton of bugfixes over the previous 0.6.x releases.</p>
</li>
<li>
<p>Non-<code class="highlighter-rouge">gem</code> Plugins are now sorted alphabetically by filename before they’re
processed, which can provide a rudimentary way to establish a load order for
plugins.</p>
</li>
</ul>
<p>For a full run-down, visit our <a href="/docs/history/">change log</a>!</p>
<p>As always, Jekyll wouldn’t be possible without the contributions from
others in the Jekyll community. We’d like to thank the following people
for contributing to this release: Anatol Broder, David Sawyer, Greg
Karékinian, Jordon Bedwell, Matthew Iversen, Persa Zula, and Yi Zeng.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/11/26/jekyll-1-3-1-released/">
Jekyll 1.3.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
26 Nov 2013
</span>
<a href="https://github.com/mattr-" class="post-author">
<img class="avatar avatar-small" alt="mattr-" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/mattr-?v=3&s=24" srcset="https://avatars0.githubusercontent.com/mattr-?v=3&s=24 1x, https://avatars0.githubusercontent.com/mattr-?v=3&s=48 2x, https://avatars0.githubusercontent.com/mattr-?v=3&s=72 3x, https://avatars0.githubusercontent.com/mattr-?v=3&s=96 4x">
mattr-
</a>
</div>
<div class="post-content">
<p>Just in time for the US holiday Thanksgiving, we’re releasing version
1.3.1 of Jekyll to address some of the issues seen since the
release of 1.3.0.</p>
<p>In addition to a couple of other smaller bug fixes, the biggest thing
we’ve fixed is an issue with the <code class="highlighter-rouge">--watch</code> option with Ruby 1.8.7. For a
full run-down, visit our <a href="/docs/history/">change log</a>!</p>
<p>Thanks to all the people who have contributed to this release! They are
(in alphabetical order): Abhi Yerra, Anatol Broder, Andreas Möller, Greg
Karékinian, Sam Rayner, Santeri Paavolainen, Shigeya Suzuki, Yihang Ho,
albertogg, andrewhavens, maul.esel, and thomasdao</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/11/04/jekyll-1-3-0-released/">
Jekyll 1.3.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
04 Nov 2013
</span>
<a href="https://github.com/mattr-" class="post-author">
<img class="avatar avatar-small" alt="mattr-" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/mattr-?v=3&s=24" srcset="https://avatars0.githubusercontent.com/mattr-?v=3&s=24 1x, https://avatars0.githubusercontent.com/mattr-?v=3&s=48 2x, https://avatars0.githubusercontent.com/mattr-?v=3&s=72 3x, https://avatars0.githubusercontent.com/mattr-?v=3&s=96 4x">
mattr-
</a>
</div>
<div class="post-content">
<p>It’s been about six weeks since v1.2.0 and the Jekyll team is happy to
announce the arrival of v1.3.0. This is a <strong>huge</strong> release full of all
sorts of new features, bug fixes, and other things that you’re sure to
love.</p>
<p>Here are a few things we think you’ll want to know about this release:</p>
<ul>
<li>
<p>You can add <a href="/docs/datafiles/">arbitrary data</a> to the site by adding YAML files under a
site’s <code class="highlighter-rouge">_data</code> directory. This will allow you to avoid
repetition in your templates and to set site specific options without
changing <code class="highlighter-rouge">_config.yml</code>.</p>
</li>
<li>
<p>You can now run <code class="highlighter-rouge">jekyll serve --detach</code> to boot up a WEBrick server in the
background. <strong>Note:</strong> you’ll need to run <code class="highlighter-rouge">kill [server_pid]</code> to shut
the server down. When ran, you’ll get a process id that you can use in
place of <code class="highlighter-rouge">[server_pid]</code></p>
</li>
<li>
<p>You can now <strong>disable automatically-generated excerpts</strong> if you set
<code class="highlighter-rouge">excerpt_separator</code> to <code class="highlighter-rouge">""</code>.</p>
</li>
<li>
<p>If you’re moving pages and posts, you can now check for <strong>URL
conflicts</strong> by running <code class="highlighter-rouge">jekyll doctor</code>.</p>
</li>
<li>
<p>If you’re a fan of the drafts feature, you’ll be happy to know we’ve
added <code class="highlighter-rouge">-D</code>, a shortened version of <code class="highlighter-rouge">--drafts</code>.</p>
</li>
<li>
<p>Permalinks with special characters should now generate without errors.</p>
</li>
<li>
<p>Expose the current Jekyll version as the <code class="highlighter-rouge">jekyll.version</code> Liquid
variable.</p>
</li>
</ul>
<p>For a full run-down, visit our <a href="/docs/history/">change log</a>!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/10/28/jekyll-1-3-0-rc1-released/">
Jekyll 1.3.0.rc1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
28 Oct 2013
</span>
<a href="https://github.com/mattr-" class="post-author">
<img class="avatar avatar-small" alt="mattr-" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/mattr-?v=3&s=24" srcset="https://avatars0.githubusercontent.com/mattr-?v=3&s=24 1x, https://avatars0.githubusercontent.com/mattr-?v=3&s=48 2x, https://avatars0.githubusercontent.com/mattr-?v=3&s=72 3x, https://avatars0.githubusercontent.com/mattr-?v=3&s=96 4x">
mattr-
</a>
</div>
<div class="post-content">
<p>Jekyll 1.3.0 is going to be a big release! In order to make sure we
didn’t screw anything up too badly, we’re making a release candidate
available for any early adopters who want to give the latest and
greatest code a spin without having to clone a repository from git.</p>
<p>Please take this prerelease for a spin and <a href="https://github.com/jekyll/jekyll/issues/new">let us
know</a> if you run into any
issues!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/09/14/jekyll-1-2-1-released/">
Jekyll 1.2.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
14 Sep 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Quick turnover, anyone? A <a href="https://github.com/jekyll/jekyll/pull/1525">recent incompatibility with Liquid
v2.5.2</a> produced a nasty bug in
which <code class="highlighter-rouge">include</code> tags were not rendered properly within <code class="highlighter-rouge">if</code> blocks.</p>
<p>This release also includes a better handling of detached servers (prints pid and
the command for killing the process). <strong>Note</strong>: the <code class="highlighter-rouge">--detach</code> flag and
<code class="highlighter-rouge">--watch</code> flags are presently incompatible in 1.2.x. Fix for that coming soon!</p>
<p>For a full list of the fixes in this release, check out <a href="/docs/history/">the change
log</a>!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/09/06/jekyll-1-2-0-released/">
Jekyll 1.2.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
06 Sep 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>After nearly a month and a half of hard work, the Jekyll team is happy to
announce the release of v1.2.0. It’s chock full of bug fixes and some
enhancements that we think you’ll love.</p>
<p>Here are a few things we think you’ll want to know about this release:</p>
<ul>
<li>Run <code class="highlighter-rouge">jekyll serve --detach</code> to boot up a WEBrick server in the background. <strong>Note:</strong> you’ll need to run <code class="highlighter-rouge">kill [server_pid]</code> to shut the server down.</li>
<li>You can now <strong>disable automatically-generated excerpts</strong> if you set <code class="highlighter-rouge">excerpt_separator</code> to <code class="highlighter-rouge">""</code>.</li>
<li>If you’re moving around pages and post, you can now check for <strong>URL conflicts</strong> by running <code class="highlighter-rouge">jekyll doctor</code>.</li>
<li>If you’re a fan of the drafts feature, you’ll be happy to know we’ve added <code class="highlighter-rouge">-D</code>, a shortened version of <code class="highlighter-rouge">--drafts</code>.</li>
<li>Permalinks with special characters should now generate without errors.</li>
<li>Expose the current Jekyll version as the <code class="highlighter-rouge">jekyll.version</code> Liquid variable.</li>
</ul>
<p>For a full run-down, visit our <a href="/docs/history/">change log</a>!</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/07/25/jekyll-1-1-2-released/">
Jekyll 1.1.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
25 Jul 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Version 1.1.2 fixes a minor, but nonetheless important security vulnerability affecting several third-party Jekyll plugins. If your Jekyll site does not use plugins, you may, but are not required to upgrade at this time.</p>
<p>Community and custom plugins extending the <code class="highlighter-rouge">Liquid::Drop</code> class may inadvertently disclose some system information such as directory structure or software configuration to users with access to the Liquid templating system.</p>
<p>We recommend you upgrade to Jekyll v1.1.2 immediately if you use <code class="highlighter-rouge">Liquid::Drop</code> plugins on your Jekyll site.</p>
<p>Many thanks for <a href="https://github.com/benbalter">Ben Balter</a> for alerting us to the problem
and <a href="https://github.com/jekyll/jekyll/issues/1349">submitting a patch</a> so quickly.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/07/25/jekyll-1-0-4-released/">
Jekyll 1.0.4 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
25 Jul 2013
</span>
<a href="https://github.com/mattr-" class="post-author">
<img class="avatar avatar-small" alt="mattr-" width="24" height="24" data-proofer-ignore="true" src="https://avatars0.githubusercontent.com/mattr-?v=3&s=24" srcset="https://avatars0.githubusercontent.com/mattr-?v=3&s=24 1x, https://avatars0.githubusercontent.com/mattr-?v=3&s=48 2x, https://avatars0.githubusercontent.com/mattr-?v=3&s=72 3x, https://avatars0.githubusercontent.com/mattr-?v=3&s=96 4x">
mattr-
</a>
</div>
<div class="post-content">
<p>Version 1.0.4 fixes a minor, but nonetheless important security vulnerability affecting several third-party Jekyll plugins. If your Jekyll site does not use plugins, you may, but are not required to upgrade at this time.</p>
<p>Community and custom plugins extending the <code class="highlighter-rouge">Liquid::Drop</code> class may inadvertently disclose some system information such as directory structure or software configuration to users with access to the Liquid templating system.</p>
<p>We recommend you upgrade to Jekyll v1.0.4 immediately if you use <code class="highlighter-rouge">Liquid::Drop</code> plugins on your Jekyll site.</p>
<p>Many thanks for <a href="https://github.com/benbalter">Ben Balter</a> for alerting us to the problem
and <a href="https://github.com/jekyll/jekyll/issues/1349">submitting a patch</a> so quickly.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/07/24/jekyll-1-1-1-released/">
Jekyll 1.1.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
24 Jul 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Coming just 10 days after the release of v1.1.0, v1.1.1 is out with a patch for
the nasty excerpt inception bug (<a href="https://github.com/jekyll/jekyll/issues/1339">#1339</a>) and
non-zero exit codes for invalid commands (<a href="https://github.com/jekyll/jekyll/issues/1338">#1338</a>).</p>
<p>To all those affected by the <a href="https://github.com/jekyll/jekyll/issues/1321">strange excerpt bug in v1.1.0</a>, I’m sorry. I think we have it all patched up and it should be
deployed to <a href="https://pages.github.com/">GitHub Pages</a> in the next couple weeks.
Thank you for your patience!</p>
<p>If you’re checking out v1.1.x for the first time, definitely check out <a href="https://github.com/jekyll/jekyll/releases/tag/v1.1.0">what
shipped with v1.1.0!</a></p>
<p>See the <a href="https://github.com/jekyll/jekyll/releases/tag/v1.1.1">GitHub Release</a> page for
more a more detailed changelog for this release.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/07/14/jekyll-1-1-0-released/">
Jekyll 1.1.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
14 Jul 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>After a month of hard work, the Jekyll core team is excited to announce the release of
Jekyll v1.1.0! This latest release of Jekyll brings some really exciting new additions:</p>
<ul>
<li>Add <code class="highlighter-rouge">docs</code> subcommand to read Jekyll’s docs when offline. (<a href="https://github.com/jekyll/jekyll/issues/1046">#1046</a>)</li>
<li>Support passing parameters to templates in <code class="highlighter-rouge">include</code> tag (<a href="https://github.com/jekyll/jekyll/issues/1204">#1204</a>)</li>
<li>Add support for Liquid tags to post excerpts (<a href="https://github.com/jekyll/jekyll/issues/1302">#1302</a>)</li>
<li>Fix pagination for subdirectories (<a href="https://github.com/jekyll/jekyll/issues/1198">#1198</a>)</li>
<li>Provide better error reporting when generating sites (<a href="https://github.com/jekyll/jekyll/issues/1253">#1253</a>)</li>
<li>Latest posts first in non-LSI <code class="highlighter-rouge">related_posts</code> (<a href="https://github.com/jekyll/jekyll/issues/1271">#1271</a>)</li>
</ul>
<p>See the <a href="https://github.com/jekyll/jekyll/releases/tag/v1.1.0">GitHub Release</a> page for more a more detailed changelog for this release.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/06/07/jekyll-1-0-3-released/">
Jekyll 1.0.3 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
07 Jun 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>v1.0.3 contains some key enhancements and bug fixes:</p>
<ul>
<li>Fail with non-zero exit code when MaRuKu errors (<a href="https://github.com/jekyll/jekyll/issues/1190">#1190</a>) or Liquid errors (<a href="https://github.com/jekyll/jekyll/issues/1121">#1121</a>)</li>
<li>Add support for private gists to <code class="highlighter-rouge">gist</code> tag (<a href="https://github.com/jekyll/jekyll/issues/1189">#1189</a>)</li>
<li>Add <code class="highlighter-rouge">--force</code> option to <code class="highlighter-rouge">jekyll new</code> (<a href="https://github.com/jekyll/jekyll/issues/1115">#1115</a>)</li>
<li>Fix compatibility with <code class="highlighter-rouge">exclude</code> and <code class="highlighter-rouge">include</code> with pre-1.0 Jekyll (<a href="https://github.com/jekyll/jekyll/issues/1114">#1114</a>)</li>
<li>Fix pagination issue regarding <code class="highlighter-rouge">File.basename</code> and <code class="highlighter-rouge">page:num</code> (<a href="https://github.com/jekyll/jekyll/issues/1063">#1063</a>)</li>
</ul>
<p>See the <a href="/docs/history/#v1-0-3">History</a> page for more information on this release.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/05/12/jekyll-1-0-2-released/">
Jekyll 1.0.2 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
12 May 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>v1.0.2 has some key bugfixes that optionally restore some behaviour from pre-1.0
releases, and fix some other annoying bugs:</p>
<ul>
<li>Backwards-compatibilize relative permalinks (<a href="https://github.com/jekyll/jekyll/issues/1081">#1081</a>)</li>
<li>Add <code class="highlighter-rouge">jekyll doctor</code> command to check site for any known compatibility problems (<a href="https://github.com/jekyll/jekyll/issues/1081">#1081</a>)</li>
<li>Deprecate old config <code class="highlighter-rouge">server_port</code>, match to <code class="highlighter-rouge">port</code> if <code class="highlighter-rouge">port</code> isn’t set (<a href="https://github.com/jekyll/jekyll/issues/1084">#1084</a>)</li>
<li>Update pygments.rb and kramdon versions to 0.5.0 and 1.0.2, respectively (<a href="https://github.com/jekyll/jekyll/issues/1061">#1061</a>, <a href="https://github.com/jekyll/jekyll/issues/1067">#1067</a>)</li>
<li>Fix issue when post categories are numbers (<a href="https://github.com/jekyll/jekyll/issues/1078">#1078</a>)</li>
<li>Add a <code class="highlighter-rouge">data-lang="<lang>"</code> attribute to Redcarpet code blocks (<a href="https://github.com/jekyll/jekyll/issues/1066">#1066</a>)</li>
<li>Catching that Redcarpet gem isn’t installed (<a href="https://github.com/jekyll/jekyll/issues/1059">#1059</a>)</li>
</ul>
<p>See the <a href="/docs/history/#v1-0-2">History</a> page for more information on this release.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/05/08/jekyll-1-0-1-released/">
Jekyll 1.0.1 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
08 May 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hot on the trails of v1.0, v1.0.1 is out! Here are the highlights:</p>
<ul>
<li>Add newer <code class="highlighter-rouge">language-</code> class name prefix to code blocks (<a href="https://github.com/jekyll/jekyll/issues/1037">#1037</a>)</li>
<li>Commander error message now preferred over process abort with incorrect args (<a href="https://github.com/jekyll/jekyll/issues/1040">#1040</a>)</li>
<li>Do not force use of toc_token when using generate_toc in RDiscount (<a href="https://github.com/jekyll/jekyll/issues/1048">#1048</a>)</li>
<li>Make Redcarpet respect the pygments configuration option (<a href="https://github.com/jekyll/jekyll/issues/1053">#1053</a>)</li>
<li>Fix the index build with LSI (<a href="https://github.com/jekyll/jekyll/issues/1045">#1045</a>)</li>
<li>Don’t print deprecation warning when no arguments are specified. (<a href="https://github.com/jekyll/jekyll/issues/1041">#1041</a>)</li>
<li>Add missing <code class="highlighter-rouge"></div></code> to site template used by <code class="highlighter-rouge">new</code> subcommand, fixed typos in code (<a href="https://github.com/jekyll/jekyll/issues/1032">#1032</a>)</li>
</ul>
<p>See the <a href="/docs/history/#v1-0-1">History</a> page for more information on this release.</p>
</div>
</article>
<article>
<h2>
<a href="/news/2013/05/05/jekyll-1-0-0-released/">
Jekyll 1.0.0 Released
</a>
</h2>
<span class="post-category">
<span class="label">
release
</span>
</span>
<div class="post-meta">
<span class="post-date">
05 May 2013
</span>
<a href="https://github.com/parkr" class="post-author">
<img class="avatar avatar-small" alt="parkr" width="24" height="24" data-proofer-ignore="true" src="https://avatars3.githubusercontent.com/parkr?v=3&s=24" srcset="https://avatars3.githubusercontent.com/parkr?v=3&s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&s=96 4x">
parkr
</a>
</div>
<div class="post-content">
<p>Hey! After many months of hard work by Jekyll’s contributors, we’re excited
to announce the first major release of the project in a long while. v1.0.0 is
finally here! While the list of improvements and bug fixes is <a href="/docs/history/#v1-0-0">quite lengthy</a>,
here are the highlights (thanks to <a href="https://twitter.com/BenBalter">@benbalter</a> for the
examples and for compiling this list):</p>
<ul>
<li>Support for the Gist tag for easily embedding Gists (<a href="https://gist.github.com/benbalter/5555251">example</a>)</li>
<li>Automatically generated post excerpts (<a href="https://gist.github.com/benbalter/5555369">example</a>)</li>
<li>Save and preview drafts before publishing (<a href="https://gist.github.com/benbalter/5555992">example</a>)</li>
</ul>
<p>Take a look at the <a href="/docs/upgrading/">Upgrading</a> page in the docs for more detailed information.</p>
</div>
</article>
</div>
<div class="unit one-fifth hide-on-mobiles">
<aside>
<ul>
<li class="current">
<a href="/news/">All News</a>
</li>
<li class="">
<a href="/news/releases/">Jekyll Releases</a>
</li>
</ul>
<h4>Recent Releases</h4>
<ul>
<li class="">
<a href="/news/2018/06/05/jekyll-3-8-3-released/">Version 3.8.3</a>
</li>
<li class="">
<a href="/news/2018/05/19/jekyll-3-8-2-released/">Version 3.8.2</a>
</li>
<li class="">
<a href="/news/2018/05/01/jekyll-3-8-1-released/">Version 3.8.1</a>
</li>
<li class="">
<a href="/news/2018/02/24/jekyll-3-7-3-released/">Version 3.7.3</a>
</li>
<li class="">
<a href="/news/2018/01/25/jekyll-3-7-2-released/">Version 3.7.2</a>
</li>
<li>
<a href="/docs/history/">History »</a>
</li>
</ul>
<h4>Other News</h4>
<ul>
<li class="">
<a href="/news/2018/02/19/meet-jekyll-s-new-lead-developer/">Meet Jekyll's New Lead Developer</a>
</li>
<li class="">
<a href="/news/2017/10/19/diversity-open-source/">Diversity in Open Source, and Jekyll's role in it</a>
</li>
<li class="">
<a href="/news/2016/08/24/jekyll-admin-initial-release/">Jekyll Admin Initial Release</a>
</li>
<li class="">
<a href="/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/">Jekyll's Google Summer of Code Project: The CMS You Always Wanted</a>
</li>
<li class="">
<a href="/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/">Making it easier to contribute to Jekyll</a>
</li>
<li class="">
<a href="/news/2015/02/26/introducing-jekyll-talk/">Join the Discussion at Jekyll Talk</a>
</li>
<li class="">
<a href="/news/2015/01/20/jekyll-meet-and-greet/">Jekyll Meet & Greet at GitHub HQ</a>
</li>
<li class="">
<a href="/news/2014/12/17/alfredxing-welcome-to-jekyll-core/">Alfred Xing has joined the Jekyll core team</a>
</li>
<li class="">
<a href="/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/">Pick Up your $1 Jekyll Sticker</a>
</li>
</ul>
</aside>
</div>
<div class="clear"></div>
</div>
</section>
<footer>
<div class="grid">
<div class="unit one-third center-on-mobiles">
<p>The contents of this website are <br>© 2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
</div>
<div class="unit two-thirds align-right center-on-mobiles">
<p>
Proudly hosted by
<a href="https://github.com">
<img src="/img/footer-logo.png" width="100" height="30" alt="GitHub • Social coding">
</a>
</p>
</div>
</div>
</footer>
<script>
var anchorForId = function (id) {
var anchor = document.createElement("a");
anchor.className = "header-link";
anchor.href = "#" + id;
anchor.innerHTML = "<span class=\"sr-only\">Permalink</span><i class=\"fa fa-link\"></i>";
anchor.title = "Permalink";
return anchor;
};
var linkifyAnchors = function (level, containingElement) {
var headers = containingElement.getElementsByTagName("h" + level);
for (var h = 0; h < headers.length; h++) {
var header = headers[h];
if (typeof header.id !== "undefined" && header.id !== "") {
header.appendChild(anchorForId(header.id));
}
}
};
document.onreadystatechange = function () {
if (this.readyState === "complete") {
var contentBlock = document.getElementsByClassName("docs")[0] || document.getElementsByClassName("news")[0];
if (!contentBlock) {
return;
}
for (var level = 1; level <= 6; level++) {
linkifyAnchors(level, contentBlock);
}
}
};
</script>
<!-- Google Analytics (https://www.google.com/analytics) -->
<script>
!function(j,e,k,y,l,L){j.GoogleAnalyticsObject=y,j[y]||(j[y]=function(){
(j[y].q=j[y].q||[]).push(arguments)}),j[y].l=+new Date,l=e.createElement(k),
L=e.getElementsByTagName(k)[0],l.src='https://www.google-analytics.com/analytics.js',
L.parentNode.insertBefore(l,L)}(window,document,'script','ga');
ga('create', 'UA-50755011-1', 'jekyllrb.com');
ga('send', 'pageview');
</script>
<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.js"></script>
<script type="text/javascript"> docsearch({
apiKey: '50fe39c839958dfad797000f33e2ec17',
indexName: 'jekyllrb',
inputSelector: '#docsearch-input',
enhancedSearchInput: true,
debug: false // Set debug to true if you want to inspect the dropdown
});
</script>
</body>
</html>