jekyll 1.0.0.rc1 → 1.0.0

data/site/_includes/docs_contents.html

@@ -1,4 +1,4 @@
-<div class="grid2">
+<div class="unit one-fifth hide-on-mobiles">
   <aside>
     <h4>Getting Started</h4>
     <ul>
@@ -77,6 +77,9 @@
       <li class="{% if page.title == "Resources" %}current{% endif %}">
         <a href="{{ site.url }}/docs/resources">Resources</a>
       </li>
+      <li class="{% if page.title == "Upgrading" %}current{% endif %}">
+        <a href="{{ site.url }}/docs/upgrading">Upgrading</a>
+      </li>
     </ul>
   </aside>
 </div>

data/site/_includes/docs_contents_mobile.html

@@ -0,0 +1,36 @@
+<div class="docs-nav-mobile unit whole show-on-mobiles">
+  <select onchange="if (this.value) window.location.href=this.value">
+    <option value="">Navigate the docs…</option>
+    <optgroup label="Getting started">
+      <option value="{{ site.url }}/docs/home">Welcome</option>
+      <option value="{{ site.url }}/docs/installation">Installation</option>
+      <option value="{{ site.url }}/docs/usage">Basic Usage</option>
+      <option value="{{ site.url }}/docs/structure">Directory structure</option>
+      <option value="{{ site.url }}/docs/configuration">Configuration</option>
+    </optgroup>
+    <optgroup label="Your Content">
+      <option value="{{ site.url }}/docs/frontmatter">Front-matter</option>
+      <option value="{{ site.url }}/docs/posts">Writing posts</option>
+      <option value="{{ site.url }}/docs/pages">Creating pages</option>
+      <option value="{{ site.url }}/docs/variables">Variables</option>
+      <option value="{{ site.url }}/docs/migrations">Blog migrations</option>
+    </optgroup>
+    <optgroup label="Customization">
+      <option value="{{ site.url }}/docs/templates">Templates</option>
+      <option value="{{ site.url }}/docs/permalinks">Permalinks</option>
+      <option value="{{ site.url }}/docs/pagination">Pagination</option>
+      <option value="{{ site.url }}/docs/plugins">Plugins</option>
+      <option value="{{ site.url }}/docs/extras">Extras</option>
+    </optgroup>
+    <optgroup label="Deployment">
+      <option value="{{ site.url }}/docs/github-pages">GitHub Pages</option>
+      <option value="{{ site.url }}/docs/deployment-methods">Other methods</option>
+    </optgroup>
+    <optgroup label="Miscellaneous">
+      <option value="{{ site.url }}/docs/contributing">Contributing</option>
+      <option value="{{ site.url }}/docs/troubleshooting">Troubleshooting</option>
+      <option value="{{ site.url }}/docs/sites">Sites using Jekyll</option>
+      <option value="{{ site.url }}/docs/resources">Resources</option>
+    </optgroup>
+  <select>
+</div>

data/site/_includes/footer.html

@@ -1,15 +1,15 @@
 <footer>
-  <div class="content">
-    <div class="grid4 first">
-      <p>By <a href="http://tom.preston-werner.com">Tom Preston-Werner</a>, <a href="http://quaran.to/">Nick Quaranto</a>, and many more <a href="https://github.com/mojombo/jekyll/graphs/contributors">awesome contributors</a>.</p>
+  <div class="grid">
+    <div class="unit one-third center-on-mobiles">
+      <p>By <a href="http://tom.preston-werner.com">Tom Preston-Werner</a>, <a href="http://quaran.to/">Nick Quaranto</a>, and many more <a href="https://github.com/mojombo/jekyll/graphs/contributors">awesome&nbsp;contributors</a>.</p>
     </div>
-    <div class="grid8 align-right">
-      <p>Proudly hosted by</p>
-      <a href="https://github.com">
-        <img src="{{ site.url }}/img/footer-logo.png" alt="GitHub • Social coding">
-      </a>
+    <div class="unit two-thirds align-right center-on-mobiles">
+      <p>
+        Proudly hosted by
+        <a href="https://github.com">
+          <img src="{{ site.url }}/img/footer-logo.png" alt="GitHub • Social coding">
+        </a>
+      </p>
     </div>
-    <div class="clear"></div>
   </div>
 </footer>
-<div class="clear"></div>

data/site/_includes/header.html

@@ -1,6 +1,9 @@
 <header>
-  <div class="content">
-    <div class="grid3 first">
+  <nav class="mobile-nav show-on-mobiles">
+    {% include primary-nav-items.html %}
+  </nav>
+  <div class="grid">
+    <div class="unit one-third center-on-mobiles">
       <h1>
         <a href="{{ site.url }}/">
           <span>Jekyll</span>
@@ -8,19 +11,8 @@
         </a>
       </h1>
     </div>
-    <nav class="grid6">
-      <ul>
-        <li {% if page.overview %}class="current"{% endif %}>
-          <a href="{{ site.url }}/">Overview</a>
-        </li>
-        <li {% unless page.overview %}class="current"{% endunless %}>
-          <a href="{{ site.url }}/docs">Documentation</a>
-        </li>
-        <li class="">
-          <a href="https://github.com/mojombo/jekyll">View on GitHub</a>
-        </li>
-      </ul>
+    <nav class="main-nav unit two-thirds hide-on-mobiles">
+      {% include primary-nav-items.html %}
     </nav>
-    <div class="clear"></div>
   </div>
 </header>

data/site/_includes/primary-nav-items.html

@@ -0,0 +1,11 @@
+<ul>
+  <li class="{% if page.overview %}current{% endif %}">
+    <a href="{{ site.url }}/">Overview</a>
+  </li>
+  <li class="{% unless page.overview %}current{% endunless %}">
+    <a href="{{ site.url }}/docs">Doc<span class="show-on-mobiles">s</span><span class="hide-on-mobiles">umentation</span></a>
+  </li>
+  <li class="">
+    <a href="https://github.com/mojombo/jekyll"><span class="hide-on-mobiles">View on </span>GitHub</a>
+  </li>
+</ul>

data/site/_includes/top.html

@@ -3,10 +3,11 @@
 <head>
   <meta charset="UTF-8">
   <title>{{ page.title }}</title>
+  <meta name="viewport" content="width=device-width,initial-scale=1">
   <link href='http://fonts.googleapis.com/css?family=Lato:100,300,400,700,900,100italic,300italic,400italic,700italic,900italic' rel='stylesheet' type='text/css'>
   <link href='http://fonts.googleapis.com/css?family=Arizonia' rel='stylesheet' type='text/css'>
   <link rel="stylesheet" href="{{ site.url }}/css/normalize.css" />
-  <link rel="stylesheet" href="{{ site.url }}/css/grid.css" />
+  <link rel="stylesheet" href="{{ site.url }}/css/gridism.css" />
   <link rel="stylesheet" href="{{ site.url }}/css/style.css" />
   <link rel="stylesheet" href="{{ site.url }}/css/pygments.css" />
   <link rel="icon" type="image/x-icon" href="{{ site.url }}/favicon.png" />

data/site/_layouts/default.html

@@ -1,6 +1,6 @@
 {% include top.html %}
 
-<body>
+<body class="wrap">
   {% include header.html %}
 
   {{ content }}

data/site/_layouts/docs.html

@@ -3,9 +3,11 @@ layout: default
 ---
 
   <section class="docs">
-    <div class="content">
+    <div class="grid">
 
-      <div class="grid10 first">
+      {% include docs_contents_mobile.html %}
+
+      <div class="unit four-fifths">
         <article>
           <h1>{{ page.title }}</h1>
           {{ content }}

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

@@ -19,6 +19,7 @@ The table below lists the available settings for Jekyll, and the various <code
 class="option">options</code> (specifed in the configuration file) and <code
 class="flag">flags</code> (specified on the command-line) that control them.
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -99,9 +100,11 @@ class="flag">flags</code> (specified on the command-line) that control them.
     </tr>
   </tbody>
 </table>
+</div>
 
 ### Build Command Options
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -169,6 +172,7 @@ class="flag">flags</code> (specified on the command-line) that control them.
     </tr>
   </tbody>
 </table>
+</div>
 
 ### Serve Command Options
 
@@ -176,6 +180,7 @@ In addition to the options below, the `serve` sub-command can accept any of the
 for the `build` sub-command, which are then applied to the site build which occurs right
 before your site is served.
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -207,7 +212,7 @@ before your site is served.
     <tr class='setting'>
       <td>
         <p class='name'><strong>Base URL</strong></p>
-        <p class='description'>Serve website with the given base URL</p>
+        <p class='description'>Serve the website from the given base URL</p>
       </td>
       <td class="align-center">
         <p><code class="option">baseurl: URL</code></p>
@@ -216,6 +221,7 @@ before your site is served.
     </tr>
   </tbody>
 </table>
+</div>
 
 <div class="note warning">
   <h5>Do not use tabs in configuration files</h5>
@@ -236,24 +242,28 @@ source:      .
 destination: ./_site
 plugins:     ./_plugins
 layouts:     ./_layouts
+include:     ['.htaccess']
+exclude:     []
 keep_files:  ['.git','.svn']
+timezone:    nil
 
 future:      true
-pygments:    false
+show_drafts: nil
+limit_posts: 0
+pygments:    true
 
-markdown:      maruku
 permalink:     date
-include:       ['.htaccess']
 paginate_path: 'page:num'
 
-markdown_ext: markdown,mkd,mkdn,md
-textile_ext: textile
+markdown:      maruku
+markdown_ext:  markdown,mkd,mkdn,md
+textile_ext:   textile
 
 excerpt_separator: "\n\n"
 
 safe:        false
-watch:       false
-server:      false
+watch:       false    # deprecated
+server:      false    # deprecated
 host:        0.0.0.0
 port:        4000
 baseurl:     /

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

@@ -14,9 +14,9 @@ following in mind:
   [RR](http://github.com/btakita/rr/tree/master).
 * If it's a brand new feature, make sure to create a new
   [Cucumber](https://github.com/cucumber/cucumber/) feature and reuse steps
-  where appropriate. Also, whipping up some documentation in your fork's wiki
-  would be appreciated, and once merged it will be transferred over to the main
-  wiki.
+  where appropriate. Also, whipping up some documentation in your fork's `site`
+  directory would be appreciated, and once merged it will also appear in
+  the next update of the main site.
 * If your contribution adds or changes any Jekyll behavior, make sure to update
   the documentation. It lives in `site/_posts`. If the docs are missing
   information, please feel free to add it in. Great docs make a great project!
@@ -56,12 +56,28 @@ Workflow
 Here's the most direct way to get your work merged into the project:
 
 * Fork the project.
-* Clone down your fork: `git clone git://github.com/<username>/jekyll.git`
-* Create a topic branch to contain your change: `git checkout -b my_awesome_feature`
+* Clone down your fork:
+
+{% highlight bash %}
+git clone git://github.com/<username>/jekyll.git
+{% endhighlight %}
+
+* Create a topic branch to contain your change:
+
+{% highlight bash %}
+git checkout -b my_awesome_feature
+{% endhighlight %}
+
+
 * Hack away, add tests. Not necessarily in that order.
 * Make sure everything still passes by running `rake`.
 * If necessary, rebase your commits into logical chunks, without errors.
-* Push the branch up: `git push origin my_awesome_feature`
+* Push the branch up:
+
+{% highlight bash %}
+git push origin my_awesome_feature
+{% endhighlight %}
+
 * Create a pull request against mojombo/jekyll and describe what your change
   does and the why you think it should be merged.
 

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

@@ -41,8 +41,9 @@ $ pip install pygments
   <p>
     Homebrew doesn’t symlink the executables for you. For the Homebrew default
     Cellar location and Python 2.7, be sure to add `/usr/local/share/python` to
-    your `PATH`. For more information, check out [the Homebrew
-    wiki](https://github.com/mxcl/homebrew/wiki/Homebrew-and-Python).
+    your `PATH`. For more information, check out
+    <a href="https://github.com/mxcl/homebrew/wiki/Homebrew-and-Python">the
+    Homebrew wiki</a>.
   </p>
 </div>
 

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

@@ -35,8 +35,10 @@ relies on.
 
 ## Predefined Global Variables
 
-There are a number of predefined global variables that you can set in the front-matter of a page or post.
+There are a number of predefined global variables that you can set in the
+front-matter of a page or post.
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -53,7 +55,7 @@ There are a number of predefined global variables that you can set in the front-
         <p>
 
           If set, this specifies the layout file to use. Use the layout file
-          name without file extension. Layout files must be placed in the
+          name without the file extension. Layout files must be placed in the
           <code>_layouts</code> directory.
 
         </p>
@@ -118,6 +120,7 @@ There are a number of predefined global variables that you can set in the front-
     </tr>
   </tbody>
 </table>
+</div>
 
 
 ## Custom Variables
@@ -141,6 +144,7 @@ title:
 
 These are available out-of-the-box to be used in the front-matter for a post.
 
+<div class="mobile-side-scroller">
 <table>
   <thead>
     <tr>
@@ -162,3 +166,4 @@ These are available out-of-the-box to be used in the front-matter for a post.
     </tr>
   </tbody>
 </table>
+</div>

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

@@ -4,11 +4,11 @@ title: Welcome
 next_section: installation
 ---
 
-This site aims to be a comprehensive guide to Jekyll. We’ll cover everything
-from getting your site up and running, creating and managing your content,
+This site aims to be a comprehensive guide to Jekyll. We’ll cover topics such
+as getting your site up and running, creating and managing your content,
 customizing the way your site works and looks, deploying to various
-environments, as well as some advice on participating in the future development
-of Jekyll itself.
+environments, and give you some advice on participating in the future
+development of Jekyll itself.
 
 ## So what is Jekyll, exactly?
 

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

@@ -8,7 +8,7 @@ next_section: usage
 Getting Jekyll installed and ready-to-go should only take a few minutes. If it
 ever becomes a pain in the ass, please [file an
 issue](https://github.com/mojombo/jekyll/issues/new) (or submit a pull request)
-describing the issue you encountered, and how we might make the process easier.
+describing the issue you encountered and how we might make the process easier.
 
 ### Requirements
 
@@ -39,11 +39,11 @@ simply run the following command to install Jekyll:
 $ gem install jekyll
 {% endhighlight %}
 
-All Jekyll’s gem dependencies are automatically installed by the above command,
-so you won’t have to worry about them at all. If you have problems installing
-Jekyll, check out the [troubleshooting](../troubleshooting) page or [report an
-issue](https://github.com/mojombo/jekyll/issues/new) so the Jekyll community can
-improve the experience for everyone.
+All of Jekyll’s gem dependencies are automatically installed by the above
+command, so you won’t have to worry about them at all. If you have problems
+installing Jekyll, check out the [troubleshooting](../troubleshooting) page or
+[report an issue](https://github.com/mojombo/jekyll/issues/new) so the Jekyll
+community can improve the experience for everyone.
 
 ## Optional Extras
 

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

@@ -7,9 +7,9 @@ next_section: templates
 
 If you’re switching to Jekyll from another blogging system, Jekyll’s importers
 can help you with the move. Most methods listed on this page require read access
-to the database to generate posts from your old system. Each method generates
-`.markdown` posts in the `_posts` directory based on the entries in the foreign
-system.
+to the database from your old system to generate posts for Jekyll. Each method
+generates `.markdown` posts in the `_posts` directory based on the entries in
+the foreign system.
 
 ## Preparing for migrations
 
@@ -72,7 +72,11 @@ $ ruby -rubygems -e 'require "jekyll/migrators/wordpress";
     Jekyll::WordPress.process("database", "user", "pass")'
 {% endhighlight %}
 
-If you are using Webfaction and have to set up an [SSH tunnel](http://docs.webfaction.com/user-guide/databases.html?highlight=mysql#starting-an-ssh-tunnel-with-ssh), be sure to make the hostname (`127.0.0.1`) explicit, otherwise MySQL may block your access based on `localhost` and `127.0.0.1` not being equivalent in its authentication system:
+If you are using Webfaction and have to set up an [SSH
+tunnel](http://docs.webfaction.com/user-guide/databases.html?highlight=mysql#starting-an-ssh-tunnel-with-ssh),
+be sure to make the hostname (`127.0.0.1`) explicit, otherwise MySQL may block
+your access based on `localhost` and `127.0.0.1` not being equivalent in its
+authentication system:
 
 {% highlight bash %}
 $ ruby -rubygems -e 'require "jekyll/migrators/wordpress";
@@ -81,15 +85,27 @@ $ ruby -rubygems -e 'require "jekyll/migrators/wordpress";
 
 ### Further Wordpress migration alternatives
 
-While the above methods work, they do not import much of the metadata that is usually stored in Wordpress posts and pages. If you need to export things like pages, tags, custom fields, image attachments and so on, the following resources might be useful to you:
-
-- [Exitwp](https://github.com/thomasf/exitwp) is a configurable tool written in Python for migrating one or more Wordpress blogs into Jekyll (Markdown) format while keeping as much metadata as possible. Exitwp also downloads attachments and pages.
-- [A great article](http://vitobotta.com/how-to-migrate-from-wordpress-to-jekyll/) with a step-by-step guide for migrating a Wordpress blog to Jekyll while keeping most of the structure and metadata.
-- [wpXml2Jekyll](https://github.com/theaob/wpXml2Jekyll) is an executable windows application for creating Markdown posts from your Wordpress XML file.
+While the above methods work, they do not import much of the metadata that is
+usually stored in Wordpress posts and pages. If you need to export things like
+pages, tags, custom fields, image attachments and so on, the following resources
+might be useful to you:
+
+- [Exitwp](https://github.com/thomasf/exitwp) is a configurable tool written in
+  Python for migrating one or more Wordpress blogs into Jekyll (Markdown) format
+  while keeping as much metadata as possible. Exitwp also downloads attachments
+  and pages.
+- [A great
+  article](http://vitobotta.com/how-to-migrate-from-wordpress-to-jekyll/) with a
+  step-by-step guide for migrating a Wordpress blog to Jekyll while keeping most
+  of the structure and metadata.
+- [wpXml2Jekyll](https://github.com/theaob/wpXml2Jekyll) is an executable
+  windows application for creating Markdown posts from your Wordpress XML file.
 
 ## Drupal
 
-If you’re migrating from [Drupal](http://drupal.org), there is [a migrator](https://github.com/mojombo/jekyll/blob/master/lib/jekyll/migrators/drupal.rb) for you too:
+If you’re migrating from [Drupal](http://drupal.org), there is [a
+migrator](https://github.com/mojombo/jekyll/blob/master/lib/jekyll/migrators/drupal.rb)
+for you too:
 
 {% highlight bash %}
 $ ruby -rubygems -e 'require "jekyll/migrators/drupal";
@@ -98,7 +114,9 @@ $ ruby -rubygems -e 'require "jekyll/migrators/drupal";
 
 <div class="note warning">
   <h5>Warning: Drupal Version Compatibility</h5>
-  <p>This migrator was written for Drupal 6.1 and may not work as expected on future versions of Drupal. Please update it and send us a pull request if necessary.</p>
+  <p>This migrator was written for Drupal 6.1 and may not work as expected with
+  newer versions of Drupal. Please update it and send us a pull request if
+  necessary.</p>
 </div>
 
 ## Movable Type
@@ -119,7 +137,7 @@ $ ruby -rubygems -e 'require "jekyll/migrators/typo";
     Jekyll::Typo.process("database", "user", "pass")'
 {% endhighlight %}
 
-This code also has only been tested with Typo version 4+.
+This code has only been tested with Typo version 4+.
 
 ## TextPattern
 
@@ -130,7 +148,12 @@ $ ruby -rubygems -e 'require "jekyll/migrators/textpattern";
     Jekyll::TextPattern.process("database_name", "username", "password", "hostname")'
 {% endhighlight %}
 
-You will need to run the above from the parent directory of your `_import` folder. For example, if `_import` is located in `/path/source/_import`, you will need to run this code from `/path/source`. The hostname defaults to `localhost`, all other variables are required. You may need to adjust the code used to filter entries. Left alone, it will attempt to pull all entries that are live or sticky.
+You will need to run the above from the parent directory of your `_import`
+folder. For example, if `_import` is located in `/path/source/_import`, you will
+need to run this code from `/path/source`. The hostname defaults to `localhost`,
+all other variables are required. You may need to adjust the code used to filter
+entries. Left alone, it will attempt to pull all entries that are live or
+sticky.
 
 ## Mephisto
 
@@ -150,11 +173,22 @@ $ ruby -rubygems -e 'require "jekyll/migrators/mephisto";
 
 ## Blogger (Blogspot)
 
-To import posts from Blogger, see [this post about migrating from Blogger to Jekyll](http://coolaj86.info/articles/migrate-from-blogger-to-jekyll.html). If that doesn’t work for you, you might want to try some of the following alternatives:
-
-- [@kennym](https://github.com/kennym) created a [little migration script](https://gist.github.com/1115810), because the solutions in the previous article didn't work out for him.
-- [@ngauthier](https://github.com/ngauthier) created [another importer](https://gist.github.com/1506614) that imports comments, and does so via blogger’s archive instead of the RSS feed.
-- [@juniorz](https://github.com/juniorz) created [yet another importer](https://gist.github.com/1564581) that works for [Octopress](http://octopress.org). It is like [@ngauthier’s version](https://gist.github.com/1506614) but separates drafts from posts, as well as importing tags and permalinks.
+To import posts from Blogger, see [this post about migrating from Blogger to
+Jekyll](http://coolaj86.info/articles/migrate-from-blogger-to-jekyll.html). If
+that doesn’t work for you, you might want to try some of the following
+alternatives:
+
+- [@kennym](https://github.com/kennym) created a [little migration
+  script](https://gist.github.com/1115810), because the solutions in the
+  previous article didn't work out for him.
+- [@ngauthier](https://github.com/ngauthier) created [another
+  importer](https://gist.github.com/1506614) that imports comments, and does so
+  via blogger’s archive instead of the RSS feed.
+- [@juniorz](https://github.com/juniorz) created [yet another
+  importer](https://gist.github.com/1564581) that works for
+  [Octopress](http://octopress.org). It is like [@ngauthier’s
+  version](https://gist.github.com/1506614) but separates drafts from posts, as
+  well as importing tags and permalinks.
 
 ## Posterous
 
@@ -165,14 +199,17 @@ $ ruby -rubygems -e 'require "jekyll/migrators/posterous";
     Jekyll::Posterous.process("my_email", "my_pass")'
 {% endhighlight %}
 
-For any other Posterous blog on your account, you will need to specify the `blog_id` for the blog:
+For any other Posterous blog on your account, you will need to specify the
+`blog_id` for the blog:
 
 {% highlight bash %}
 $ ruby -rubygems -e 'require "jekyll/migrators/posterous";
     Jekyll::Posterous.process("my_email", "my_pass", "blog_id")'
 {% endhighlight %}
 
-There is also an [alternative Posterous migrator](https://github.com/pepijndevos/jekyll/blob/patch-1/lib/jekyll/migrators/posterous.rb) that maintains permalinks and attempts to import images too.
+There is also an [alternative Posterous
+migrator](https://github.com/pepijndevos/jekyll/blob/patch-1/lib/jekyll/migrators/posterous.rb)
+that maintains permalinks and attempts to import images too.
 
 ## Tumblr
 
@@ -183,9 +220,12 @@ $ ruby -rubygems -e 'require "jekyll/migrators/tumblr";
     Jekyll::Tumblr.process("http://www.your_blog_url.com", true)'
 {% endhighlight %}
 
-There is also [a modified Tumblr migrator](https://github.com/stephenmcd/jekyll/blob/master/lib/jekyll/migrators/tumblr.rb) that exports posts as Markdown and preserves post tags.
+There is also [a modified Tumblr
+migrator](https://github.com/stephenmcd/jekyll/blob/master/lib/jekyll/migrators/tumblr.rb)
+that exports posts as Markdown and preserves post tags.
 
-The migrator above requires the `json` gem and Python's `html2text` to be installed as follows:
+The migrator above requires the `json` gem and Python's `html2text` to be
+installed as follows:
 
 {% highlight bash %}
 $ gem install json
@@ -201,4 +241,5 @@ $ ruby -rubygems -e 'require "jekyll/migrators/tumblr";
 
 ## Other Systems
 
-If you have a system that there isn’t currently a migrator for, you should consider writing one and sending us a pull request.
+If you have a system for which there is currently no migrator, consider writing
+one and sending us a pull request.