jekyll-docs 3.2.1 → 3.3.0

data/site/news/index.html

@@ -4,7 +4,7 @@
 <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.2.1">
+  <meta name="generator" content="Jekyll v3.3.0">
   <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="stylesheet" href="//fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
@@ -28,7 +28,7 @@
     "@type": "WebPage",
     "headline": "News",
     "description": "Transform your plain text into static websites and blogs",
-    "logo": "https://jekyllrb.comimg/logo-2x.png",
+    "logo": "https://jekyllrb.com/img/logo-2x.png",
     "url": "https://jekyllrb.com/news/"
   }
 </script>
@@ -110,6 +110,10 @@
     <option value="/news/">Home</option>
     <optgroup label="v1.x">
       
+      <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>
@@ -221,6 +225,159 @@
 
       <div class="unit four-fifths">
         
+  <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" src="https://avatars3.githubusercontent.com/parkr?v=3&amp;s=24" alt="parkr" srcset="https://avatars3.githubusercontent.com/parkr?v=3&amp;s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&amp;s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&amp;s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&amp;s=96 4x" width="24" height="24" data-proofer-ignore="true">
+      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="themes-can-now-ship-static--dynamic-assets-in-an-assets-directory">1. Themes can now ship static &amp; 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="relativeurl-and-absoluteurl-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> =&gt; /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> =&gt; /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 URL’s 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> =&gt; http://jekyllrb.com/myproject/docs/assets</code></pre></figure>
+
+<h3 id="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" src="https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&amp;s=24" alt="mertkahyaoglu" srcset="https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&amp;s=24 1x, https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&amp;s=48 2x, https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&amp;s=72 3x, https://avatars0.githubusercontent.com/mertkahyaoglu?v=3&amp;s=96 4x" width="24" height="24" data-proofer-ignore="true">
+      mertkahyaoglu
+    </a>
+  </div>
+  <div class="post-content">
+    <p><a href="http://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/">
@@ -303,7 +460,7 @@ now dogfoods this feature, using the <a href="https://github.com/jekyll/minima">
   <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 URL’s for any
-post, page, or document based on its path relative to the site source</li>
+post or document based on its path relative to the site source</li>
   <li>… and lots more!</li>
 </ul>
 
@@ -2625,6 +2782,10 @@ examples and for compiling this list):</p>
     <h4>Recent Releases</h4>
     <ul>
       
+      <li class="">
+        <a href="/news/2016/10/06/jekyll-3-3-is-here/">Version 3.3.0</a>
+      </li>
+      
       <li class="">
         <a href="/news/2016/08/02/jekyll-3-2-1-released/">Version 3.2.1</a>
       </li>
@@ -2641,10 +2802,6 @@ examples and for compiling this list):</p>
         <a href="/news/2016/05/18/jekyll-3-1-5-released/">Version 3.1.5</a>
       </li>
       
-      <li class="">
-        <a href="/news/2016/05/18/jekyll-3-1-4-released/">Version 3.1.4</a>
-      </li>
-      
       <li>
         <a href="/docs/history/">History »</a>
       </li>
@@ -2655,6 +2812,14 @@ examples and for compiling this list):</p>
         
         
         
+        <li class="">
+          <a href="/news/2016/08/24/jekyll-admin-initial-release/">Jekyll Admin Initial Release</a>
+        </li>
+        
+        
+        
+        
+        
         
         
         <li class="">

data/site/news/releases/index.html

@@ -4,7 +4,7 @@
 <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.2.1">
+  <meta name="generator" content="Jekyll v3.3.0">
   <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="stylesheet" href="//fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
@@ -28,7 +28,7 @@
     "@type": "WebPage",
     "headline": "Releases",
     "description": "Transform your plain text into static websites and blogs",
-    "logo": "https://jekyllrb.comimg/logo-2x.png",
+    "logo": "https://jekyllrb.com/img/logo-2x.png",
     "url": "https://jekyllrb.com/news/releases/"
   }
 </script>
@@ -110,6 +110,10 @@
     <option value="/news/">Home</option>
     <optgroup label="v1.x">
       
+      <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>
@@ -221,6 +225,122 @@
 
       <div class="unit four-fifths">
         
+  <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" src="https://avatars3.githubusercontent.com/parkr?v=3&amp;s=24" alt="parkr" srcset="https://avatars3.githubusercontent.com/parkr?v=3&amp;s=24 1x, https://avatars3.githubusercontent.com/parkr?v=3&amp;s=48 2x, https://avatars3.githubusercontent.com/parkr?v=3&amp;s=72 3x, https://avatars3.githubusercontent.com/parkr?v=3&amp;s=96 4x" width="24" height="24" data-proofer-ignore="true">
+      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="themes-can-now-ship-static--dynamic-assets-in-an-assets-directory">1. Themes can now ship static &amp; 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="relativeurl-and-absoluteurl-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> =&gt; /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> =&gt; /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 URL’s 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> =&gt; http://jekyllrb.com/myproject/docs/assets</code></pre></figure>
+
+<h3 id="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/02/jekyll-3-2-1-released/">
@@ -303,7 +423,7 @@ now dogfoods this feature, using the <a href="https://github.com/jekyll/minima">
   <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 URL’s for any
-post, page, or document based on its path relative to the site source</li>
+post or document based on its path relative to the site source</li>
   <li>… and lots more!</li>
 </ul>
 
@@ -2397,6 +2517,10 @@ examples and for compiling this list):</p>
     <h4>Recent Releases</h4>
     <ul>
       
+      <li class="">
+        <a href="/news/2016/10/06/jekyll-3-3-is-here/">Version 3.3.0</a>
+      </li>
+      
       <li class="">
         <a href="/news/2016/08/02/jekyll-3-2-1-released/">Version 3.2.1</a>
       </li>
@@ -2413,10 +2537,6 @@ examples and for compiling this list):</p>
         <a href="/news/2016/05/18/jekyll-3-1-5-released/">Version 3.1.5</a>
       </li>
       
-      <li class="">
-        <a href="/news/2016/05/18/jekyll-3-1-4-released/">Version 3.1.4</a>
-      </li>
-      
       <li>
         <a href="/docs/history/">History »</a>
       </li>
@@ -2427,6 +2547,14 @@ examples and for compiling this list):</p>
         
         
         
+        <li class="">
+          <a href="/news/2016/08/24/jekyll-admin-initial-release/">Jekyll Admin Initial Release</a>
+        </li>
+        
+        
+        
+        
+        
         
         
         <li class="">

data/site/sitemap.xml

@@ -1,6 +1,14 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd" xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
 <url>
+<loc>https://jekyllrb.com/news/2016/10/06/jekyll-3-3-is-here/</loc>
+<lastmod>2016-10-06T11:10:38-07:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/news/2016/08/24/jekyll-admin-initial-release/</loc>
+<lastmod>2016-08-24T23:50:00-07:00</lastmod>
+</url>
+<url>
 <loc>https://jekyllrb.com/news/2016/08/02/jekyll-3-2-1-released/</loc>
 <lastmod>2016-08-02T13:20:11-07:00</lastmod>
 </url>

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jekyll-docs
 version: !ruby/object:Gem::Version
-  version: 3.2.1
+  version: 3.3.0
 platform: ruby
 authors:
 - Parker Moore
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-08-03 00:00:00.000000000 Z
+date: 2016-10-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: jekyll
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 3.2.1
+        version: 3.3.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 3.2.1
+        version: 3.3.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -62,7 +62,6 @@ files:
 - lib/jekyll-docs.rb
 - site/404.html
 - site/CNAME
-- site/README.md
 - site/community/index.html
 - site/conduct/index.html
 - site/css/screen.css
@@ -177,6 +176,8 @@ files:
 - site/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/index.html
 - site/news/2016/07/26/jekyll-3-2-0-released/index.html
 - site/news/2016/08/02/jekyll-3-2-1-released/index.html
+- site/news/2016/08/24/jekyll-admin-initial-release/index.html
+- site/news/2016/10/06/jekyll-3-3-is-here/index.html
 - site/news/index.html
 - site/news/releases/index.html
 - site/sitemap.xml