jekyll 1.0.0.rc1 → 1.0.0

data/site/_posts/2012-07-01-pages.md

@@ -35,8 +35,8 @@ There are two main ways of creating pages:
 - Create a folder in the site's root for each page, and place an index.html file
   in each page folder.
 
-Both methods work fine (and can be used in conjunction with each other), with the
-only real difference being the resulting URLs.
+Both methods work fine (and can be used in conjunction with each other),
+with the only real difference being the resulting URLs.
 
 ### Named HTML files
 

data/site/_posts/2012-07-01-pagination.md

@@ -36,6 +36,7 @@ page in the generated site.
 The pagination plugin exposes the `paginator` liquid object with the following
 attributes:
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -102,10 +103,14 @@ attributes:
     </tr>
   </tbody>
 </table>
+</div>
 
 <div class="note info">
   <h5>Pagination does not support tags or categories</h5>
-  <p>Pagination pages through every post in the <code>posts</code> variable regardless of variables defined in the YAML Front Matter of each. It does not currently allow paging over groups of posts linked by a common tag or category.</p>
+  <p>Pagination pages through every post in the <code>posts</code>
+  variable regardless of variables defined in the YAML Front Matter of
+  each. It does not currently allow paging over groups of posts linked
+  by a common tag or category.</p>
 </div>
 
 ## Render the paginated Posts

data/site/_posts/2012-07-01-permalinks.md

@@ -17,6 +17,7 @@ permalink is defined as `/:categories/:year/:month/:day/:title.html`.
 
 ## Template variables
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -87,9 +88,11 @@ permalink is defined as `/:categories/:year/:month/:day/:title.html`.
     </tr>
   </tbody>
 </table>
+</div>
 
 ## Built-in permalink styles
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -124,11 +127,13 @@ permalink is defined as `/:categories/:year/:month/:day/:title.html`.
     </tr>
   </tbody>
 </table>
+</div>
 
 ## Permalink style examples
 
 Given a post named: `/2009-04-29-slap-chop.textile`
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -171,3 +176,4 @@ Given a post named: `/2009-04-29-slap-chop.textile`
     </tr>
   </tbody>
 </table>
+</div>

data/site/_posts/2012-07-01-plugins.md

@@ -80,6 +80,7 @@ using the `category_index.html` layout.
 
 Generators are only required to implement one method:
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -98,6 +99,7 @@ Generators are only required to implement one method:
     </tr>
   </tbody>
 </table>
+</div>
 
 ## Converters
 
@@ -139,6 +141,7 @@ end
 
 Converters should implement at a minimum 3 methods:
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -178,6 +181,7 @@ Converters should implement at a minimum 3 methods:
     </tr>
   </tbody>
 </table>
+</div>
 
 In our example, `UpcaseConverter#matches` checks if our filename extension is
 `.upcase`, and will render using the converter if it is. It will call
@@ -212,6 +216,7 @@ Liquid::Template.register_tag('render_time', Jekyll::RenderTimeTag)
 
 At a minimum, liquid tags must implement:
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -230,6 +235,7 @@ At a minimum, liquid tags must implement:
     </tr>
   </tbody>
 </table>
+</div>
 
 You must also register the custom tag with the Liquid template engine as
 follows:
@@ -286,6 +292,7 @@ Liquid::Template.register_filter(Jekyll::AssetFilter)
 
 There are two flags to be aware of when writing a plugin:
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -325,6 +332,7 @@ There are two flags to be aware of when writing a plugin:
     </tr>
   </tbody>
 </table>
+</div>
 
 To use one of the example plugins above as an illustration, here is how you’d
 specify these two flags:
@@ -379,7 +387,7 @@ There are a few useful, prebuilt plugins at the following locations:
 - [Full-text search by Pascal Widdershoven](https://github.com/PascalW/jekyll_indextank): Add full-text search to your Jekyll site with this plugin and a bit of JavaScript.
 - [Stylus Converter](https://gist.github.com/988201) Convert .styl to .css.
 - [Embed.ly client by Robert Böhnke](https://github.com/robb/jekyll-embedly-client) Autogenerate embeds from URLs using oEmbed.
-- [Logarithmic Tag Cloud](https://gist.github.com/2290195): Flexible. Logarithmic distribution. Usage eg: `{{ "{% tag_cloud font-size: 50 - 150%, threshold: 2 " }}%}`. Documentation inline.
+- [Logarithmic Tag Cloud](https://gist.github.com/2290195): Flexible. Logarithmic distribution. Documentation inline.
 - [Related Posts by Lawrence Woodman](https://github.com/LawrenceWoodman/related_posts-jekyll_plugin): Overrides `site.related_posts` to use categories to assess relationship
 - [AliasGenerator by Thomas Mango](https://github.com/tsmango/jekyll_alias_generator): Generates redirect pages for posts when an alias configuration is specified in the YAML Front Matter.
 - [FlickrSetTag by Thomas Mango](https://github.com/tsmango/jekyll_flickr_set_tag): Generates image galleries from Flickr sets.

data/site/_posts/2012-07-01-resources.md

@@ -2,16 +2,13 @@
 layout: docs
 title: Resources
 prev_section: sites
+next_section: upgrading
 ---
 
 Jekyll’s growing use is producing a wide variety of tutorials, frameworks, extensions, examples, and other resources that can be very helpful. Below is a collection of links to some of the most popular Jekyll resources.
 
 ### Jekyll tips & tricks, and examples
 
-- [A simple way to add draft posts](https://gist.github.com/2870636)
-
-  No plugins required.
-
 - [Tips for working with GitHub Pages Integration](https://gist.github.com/2890453)
 
   Code example reuse, and keeping documentation up to date.

data/site/_posts/2012-07-01-structure.md

@@ -9,7 +9,7 @@ Jekyll is, at its core, a text transformation engine. The concept behind the
 system is this: you give it text written in your favorite markup language, be
 that Markdown, Textile, or just plain HTML, and it churns that through a layout
 or series of layout files. Throughout that process you can tweak how you want
-the site URLs to look, what data gets displayed in the layout and more. This is
+the site URLs to look, what data gets displayed in the layout, and more. This is
 all done through editing text files, and the static web site is the final
 product.
 
@@ -33,6 +33,7 @@ A basic Jekyll site usually looks something like this:
 
 An overview of what each of these does:
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -153,3 +154,4 @@ An overview of what each of these does:
     </tr>
   </tbody>
 </table>
+</div>

data/site/_posts/2012-07-01-templates.md

@@ -13,6 +13,7 @@ common tasks easier.
 
 ## Filters
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -143,6 +144,7 @@ common tasks easier.
     </tr>
   </tbody>
 </table>
+</div>
 
 ## Tags
 
@@ -231,4 +233,3 @@ You can also use this tag to create a link to a post in Markdown as follows:
 [Name of Link]({% post_url 2010-07-21-name-of-post %})
 {% endraw %}
 {% endhighlight %}
-

data/site/_posts/2012-07-01-troubleshooting.md

@@ -50,7 +50,23 @@ On Debian or Ubuntu, you may need to add /var/lib/gems/1.8/bin/ to your path in
 
 ## Base-URL Problems
 
-If you are using base-url option like `jekyll serve --baseurl '/blog'` then make sure that you access the site at `http://localhost:4000/blog/index.html`. Just accessing `http://localhost:4000/blog` will not work.
+If you are using base-url option like:
+
+{% highlight bash %}
+jekyll serve --baseurl '/blog'
+{% endhighlight %}
+
+… then make sure that you access the site at:
+
+{% highlight bash %}
+http://localhost:4000/blog/index.html
+{% endhighlight %}
+
+It won’t work to just access:
+
+{% highlight bash %}
+http://localhost:4000/blog
+{% endhighlight %}
 
 ## Configuration problems
 
@@ -74,7 +90,9 @@ problems.
 If your link has characters that need to be escaped, you need to use
 this syntax:
 
-`![Alt text](http://yuml.me/diagram/class/[Project]->[Task])`
+{% highlight text %}
+![Alt text](http://yuml.me/diagram/class/[Project]->[Task])
+{% endhighlight %}
 
 If you have an empty tag, i.e. `<script src="js.js"></script>`, Maruku
 transforms this into `<script src="js.js" />`. This causes problems in

data/site/_posts/2012-07-01-upgrading.md

@@ -0,0 +1,104 @@
+---
+layout: docs
+title: Upgrading
+prev_section: resources
+---
+
+Upgrading from an older version of Jekyll? A few things have changed in 1.0.0
+that you'll want to know about.
+
+
+<div class="note feature">
+  <h5 markdown="1">Diving in</h5>
+  <p markdown="1">Want to get a new Jekyll site up and running quickly? Simply
+   run <code>jekyll new SITENAME</code> to create a new folder with a bare bones
+   Jekyll site.</p>
+</div>
+
+### The Jekyll Command
+
+For better clarity, Jekyll now accepts the commands `build` and `serve`.
+Whereas before you might simply run the command `jekyll` to generate a site
+and `jekyll --server` to view it locally, now use the subcommands `jekyll build`
+and `jekyll serve` to do the same. And if you want Jekyll to automatically
+rebuild each time a file changes, just add the `--watch` flag at the end.
+
+<div class="note info">
+  <h5 markdown="1">Watching and Serving</h5>
+  <p markdown="1">With the new subcommands, the way sites are previewed locally
+   changed a bit. Instead of specifying `server: true` in the site's
+   configuration file, use `jekyll serve`. The same hold's true for
+   `watch: true`. Instead, use the `--watch` flag with either `jekyll serve`
+    or `jekyll build`.</p>
+</div>
+
+### Custom Config File
+
+Rather than passing individual flags via the command line, you can now pass an
+entire custom Jekyll config file. This helps to distinguish between
+environments, or lets you programmatically override user-specified defaults.
+Simply add the `--config` flag to the `jekyll` command, followed by the path
+to one or more config files (comma-deliminated, no spaces).
+
+#### As a result, the following command line flags are now deprecated:
+
+* `--no-server`
+* `--no-auto`
+* `--auto` (now `--watch`)
+* `--server`
+* `--url=`
+* `--maruku`, `--rdiscount`, and `--redcarpet`
+* `--pygments`
+* `--permalink=`
+* `--paginate`
+
+<div class="note info">
+  <h5 markdown="1">The `--config` explicitly specifies your configuration file(s)</h5>
+  <p markdown="1">If you use the `--config` flag, Jekyll will ignore your
+    `config.yml` file. Want to merge a custom configuration with the normal
+    configuration? No problem. Jekyll will accept more than one custom config
+    file via the command line. Config files cascade from right to left, such
+    that if I run `jekyll serve --config config.yml,config-dev.yml`,
+    the values in the config files on the right (`config-dev.yml`) overwrite
+    those on the left (`config.yml`) when both contain the same key.</p>
+</div>
+
+### Draft posts
+
+Jekyll now lets you write draft posts, and allows you to easily preview how
+they will look prior to publishing. To start a draft, simply create a folder
+called `_drafts` in your site's source directory (e.g., alongside `_posts`),
+and add a new markdown file to it. To preview your new post, simply run the
+`Jekyll serve` command with the `--drafts` flag.
+
+<div class="note info">
+  <h5 markdown="1">Drafts don't have dates</h5>
+  <p markdown="1">Unlike posts, drafts don't have a date, since they haven't
+  been published yet. Rather than naming your draft something like
+  `2013-07-01-my-draft-post.md`, simply name the file what you'd like your
+  post to eventually be titled, here `my-draft-post.md`.</p>
+</div>
+
+### Baseurl
+
+Often, you'll want the ability to run a Jekyll site in multiple places, such as
+previewing locally before pushing to GitHub Pages. Jekyll 1.0 makes that
+easier with the new `--baseurl` flag. To take advantage of this feature, first
+add the production `baseurl` to your site's `_config.yml` file. Then,
+throughout the site, simply prefix relative URLs with `{{ site.baseurl }}`.
+When you're ready to preview your site locally, pass along the `--baseurl` flag
+with your local baseurl (most likely `/`) to `jekyll serve` and Jekyll will
+swap in whatever you've passed along, ensuring all your links work as you'd
+expect in both environments.
+
+
+<div class="note warning">
+  <h5 markdown="1">All page and post URLs contain leading slashes</h5>
+  <p markdown="1">If you use the method described above, please remember
+  that the URLs for all posts and pages contain a leading slash. Therefore,
+  concatenating the site baseurl and the post/page url where
+  `site.baseurl = /` and `post.url = /2013/06/05/my-fun-post/` will
+  result in two leading slashes, which will break links. It is thus
+  suggested that prefixing with `site.baseurl` only be used when the
+  `baseurl` is something other than the default of `/`.</p>
+</div>

data/site/_posts/2012-07-01-usage.md

@@ -20,7 +20,7 @@ $ jekyll build --source <source> --destination <destination>
 
 $ jekyll build --watch
 # => The current folder will be generated into ./_site,
-#    and watch for changes and regenerate automatically.
+#    watched for changes, and regenerated automatically.
 {% endhighlight %}
 
 Jekyll also comes with a built-in development server that will allow you to

data/site/_posts/2012-07-01-variables.md

@@ -13,11 +13,12 @@ following is a reference of the available data.
 
 ## Global Variables
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
-      <td>Variable</td>
-      <td>Description</td>
+      <th>Variable</th>
+      <th>Description</th>
     </tr>
   </thead>
   <tbody>
@@ -61,14 +62,16 @@ following is a reference of the available data.
     </tr>
   </tbody>
 </table>
+</div>
 
 ## Site Variables
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
-      <td>Variable</td>
-      <td>Description</td>
+      <th>Variable</th>
+      <th>Description</th>
     </tr>
   </thead>
   <tbody>
@@ -132,14 +135,16 @@ following is a reference of the available data.
     </tr>
   </tbody>
 </table>
+</div>
 
 ## Page Variables
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
-      <td>Variable</td>
-      <td>Description</td>
+      <th>Variable</th>
+      <th>Description</th>
     </tr>
   </thead>
   <tbody>
@@ -171,7 +176,8 @@ following is a reference of the available data.
       <td><p><code>page.url</code></p></td>
       <td><p>
 
-        The URL of the Post without the domain. e.g.
+        The URL of the Post without the domain, but
+        with a leading slash, e.g.
         <code>/2008/12/14/my-post.html</code>
 
       </p></td>
@@ -229,6 +235,7 @@ following is a reference of the available data.
     </tr>
   </tbody>
 </table>
+</div>
 
 <div class="note">
   <h5>ProTip™: Use custom front-matter</h5>
@@ -244,11 +251,12 @@ following is a reference of the available data.
 
 ## Paginator
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
-      <td>Variable</td>
-      <td>Description</td>
+      <th>Variable</th>
+      <th>Description</th>
     </tr>
   </thead>
   <tbody>
@@ -290,6 +298,7 @@ following is a reference of the available data.
     </tr>
   </tbody>
 </table>
+</div>
 
 <div class="note info">
   <h5>Paginator variable availability</h5>

data/site/css/gridism.css

@@ -0,0 +1,110 @@
+/*
+ * Gridism
+ * A simple, responsive, and handy CSS grid by @cobyism
+ * https://github.com/cobyism/gridism
+ */
+
+/* Preserve some sanity */
+.grid,
+.unit {
+  -webkit-box-sizing: border-box;
+  -moz-box-sizing: border-box;
+  box-sizing: border-box;
+}
+
+/* Set up some rules to govern the grid */
+.grid {
+  display: block;
+  clear: both;
+}
+.grid .unit {
+  float: left;
+  width: 100%;
+  padding: 10px;
+}
+
+/* This ensures the outer gutters are equal to the (doubled) inner gutters. */
+.grid .unit:first-child { padding-left: 20px; }
+.grid .unit:last-child { padding-right: 20px; }
+
+/* Nested grids already have padding though, so let’s nuke it */
+.unit .unit:first-child { padding-left: 0; }
+.unit .unit:last-child { padding-right: 0; }
+.unit .grid:first-child > .unit { padding-top: 0; }
+.unit .grid:last-child > .unit { padding-bottom: 0; }
+
+/* Let people nuke the gutters/padding completely in a couple of ways */
+.no-gutters .unit,
+.unit.no-gutters {
+  padding: 0 !important;
+}
+
+/* Wrapping at a maximum width is optional */
+.wrap .grid,
+.grid.wrap {
+  max-width: 978px;
+  margin: 0 auto;
+}
+
+/* Width classes also have shorthand versions numbered as fractions
+ * For example: for a grid unit 1/3 (one third) of the parent width,
+ * simply apply class="w-1-3" to the element. */
+.grid .whole,          .grid .w-1-1 { width: 100%; }
+.grid .half,           .grid .w-1-2 { width: 50%; }
+.grid .one-third,      .grid .w-1-3 { width: 33.3332%; }
+.grid .two-thirds,     .grid .w-2-3 { width: 66.6665%; }
+.grid .one-quarter,    .grid .w-1-4 { width: 25%; }
+.grid .three-quarters, .grid .w-3-4 { width: 75%; }
+.grid .one-fifth,      .grid .w-1-5 { width: 20%; }
+.grid .two-fifths,     .grid .w-2-5 { width: 40%; }
+.grid .three-fifths,   .grid .w-3-5 { width: 60%; }
+.grid .four-fifths,    .grid .w-4-5 { width: 80%; }
+.grid .golden-small,   .grid .w-g-s { width: 38.2716%; } /* Golden section: smaller piece */
+.grid .golden-large,   .grid .w-g-l { width: 61.7283%; } /* Golden section: larger piece */
+
+/* Utility classes */
+.align-center { text-align: center; }
+.align-left   { text-align: left; }
+.align-right  { text-align: right; }
+.pull-left    { float: left; }
+.pull-right   { float: right; }
+
+.show-on-mobiles {
+  display: none;
+}
+
+/* Responsive Stuff */
+@media screen and (max-width: 568px) {
+  /* Stack anything that isn’t full-width on smaller screens */
+  .grid .unit {
+    width: 100% !important;
+    padding-left: 20px;
+    padding-right: 20px;
+  }
+  .unit .grid .unit {
+    padding-left: 0px;
+    padding-right: 0px;
+  }
+
+  /* Sometimes, you just want to be different on small screens */
+  .center-on-mobiles {
+    text-align: center !important;
+  }
+  .hide-on-mobiles {
+    display: none !important;
+  }
+  .show-on-mobiles {
+    display: block !important;
+  }
+  a .show-on-mobiles {
+    display: inline !important;
+  }
+}
+
+/* Expand the wrap a bit further on larger screens */
+/*@media screen and (min-width: 1180px) {
+  .wrap .grid {
+    max-width: 1180px;
+    margin: 0 auto;
+  }
+}*/