public class Hello {
- public static void Main() {
- Console.WriteLine("Hello, World! This is a super long line to test the functionality of pygments code highlighting.");
- }
-}
public class Hello {
- public static void Main() {
- Console.WriteLine("Hello, World! This is a super long line to test the functionality of pygments code highlighting.");
- }
-}
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/CNAME b/CNAME
old mode 100644
new mode 100755
index 7824d69..f501cde
--- a/CNAME
+++ b/CNAME
@@ -1 +1 @@
-recoding.cn
\ No newline at end of file
+jekyllrb.com
diff --git a/LICENSE b/LICENSE
deleted file mode 100755
index d338381..0000000
--- a/LICENSE
+++ /dev/null
@@ -1,19 +0,0 @@
-The MIT License (MIT)
-
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/README b/README
new file mode 100755
index 0000000..60b411c
--- /dev/null
+++ b/README
@@ -0,0 +1 @@
+Jekyll's awesome website.
diff --git a/README.md b/README.md
deleted file mode 100644
index 5199417..0000000
--- a/README.md
+++ /dev/null
@@ -1,6 +0,0 @@
-# scriptExplorer's Blog
-
-## License
-- [MIT License](/LICENSE) - Code written by me
-
-## Acknowledgements
diff --git a/_config.yml b/_config.yml
new file mode 100755
index 0000000..c4123d6
--- /dev/null
+++ b/_config.yml
@@ -0,0 +1,16 @@
+---
+markdown: kramdown
+baseurl: /
+highlighter: pygments
+relative_permalinks: false
+permalink: "/news/:year/:month/:day/:title/"
+excerpt_separator: ''
+gauges_id: 503c5af6613f5d0f19000027
+google_analytics_id: UA-50755011-1
+repository: https://github.com/scriptExplorer/scriptexplorer.github.io
+help_url: https://github.com/jekyll/jekyll-help
+collections:
+ docs:
+ output: true
+sass:
+ style: compressed
diff --git a/_data/docs.yml b/_data/docs.yml
new file mode 100755
index 0000000..474f73f
--- /dev/null
+++ b/_data/docs.yml
@@ -0,0 +1,46 @@
+- title: Getting Started
+ docs:
+ - home
+ - quickstart
+ - installation
+ - usage
+ - structure
+ - configuration
+
+- title: Your Content
+ docs:
+ - frontmatter
+ - posts
+ - drafts
+ - pages
+ - variables
+ - collections
+ - datafiles
+ - assets
+ - migrations
+
+- title: Customization
+ docs:
+ - templates
+ - permalinks
+ - pagination
+ - plugins
+ - extras
+
+- title: Deployment
+ docs:
+ - github-pages
+ - deployment-methods
+ - continuous-integration
+
+- title: Miscellaneous
+ docs:
+ - troubleshooting
+ - sites
+ - resources
+ - upgrading
+
+- title: Meta
+ docs:
+ - contributing
+ - history
diff --git a/_docs/assets.md b/_docs/assets.md
new file mode 100755
index 0000000..c2965bd
--- /dev/null
+++ b/_docs/assets.md
@@ -0,0 +1,82 @@
+---
+layout: docs
+title: Assets
+prev_section: datafiles
+next_section: migrations
+permalink: /docs/assets/
+---
+
+Jekyll provides built-in support for Sass and CoffeeScript. In order to use
+them, create a file with the proper extension name (one of `.sass`, `.scss`,
+or `.coffee`) and start the file with two lines of triple dashes, like this:
+
+{% highlight sass %}
+---
+---
+
+// start content
+.my-definition
+ font-size: 1.2em
+{% endhighlight %}
+
+Jekyll treats these files the same as a regular page, in that the output file
+will be placed in the same directory that it came from. For instance, if you
+have a file named `css/styles.scss` in your site's source folder, Jekyll
+will process it and put it in your site's destination folder under
+`css/styles.css`.
+
+
+
Jekyll processes all Liquid filters and tags in asset files
+
If you are using Mustache
+ or another JavaScript templating language that conflicts with
+ the Liquid template syntax, you
+ will need to place {% raw %} and
+ {% endraw %} tags around your code.
+
+
+## Sass/SCSS
+
+Jekyll allows you to customize your Sass conversion in certain ways.
+
+Place all your partials in your `sass_dir`, which defaults to
+`/_sass`. Place your main SCSS or Sass files in the place you want
+them to be in the output file, such as `/css`. For an example, take
+a look at [this example site using Sass support in Jekyll][example-sass].
+
+If you are using Sass `@import` statements, you'll need to ensure that your
+`sass_dir` is set to the base directory that contains your Sass files. You
+can do that thusly:
+
+{% highlight yaml %}
+sass:
+ sass_dir: _sass
+{% endhighlight %}
+
+The Sass converter will default the `sass_dir` configuration option to
+`_sass`.
+
+[example-sass]: https://github.com/jekyll/jekyll-sass-converter/tree/master/example
+
+
+
The sass_dir is only used by Sass
+
+
+ Note that the sass_dir becomes the load path for Sass imports,
+ nothing more. This means that Jekyll does not know about these files
+ directly, so any files here should not contain the YAML Front Matter as
+ described above nor will they be transformed as described above. This
+ folder should only contain imports.
+
+
+
+
+You may also specify the output style with the `style` option in your
+`_config.yml` file:
+
+{% highlight yaml %}
+sass:
+ style: :compressed
+{% endhighlight %}
+
+These are passed to Sass, so any output style options Sass supports are valid
+here, too.
diff --git a/_docs/collections.md b/_docs/collections.md
new file mode 100755
index 0000000..a132dc6
--- /dev/null
+++ b/_docs/collections.md
@@ -0,0 +1,275 @@
+---
+layout: docs
+title: Collections
+prev_section: variables
+next_section: datafiles
+permalink: /docs/collections/
+---
+
+
+
Collections support is unstable and may change
+
+ This is an experimental feature and that the API may likely change until the feature stabilizes.
+
+
+
+Not everything is a post or a page. Maybe you want to document the various methods in your open source project, members of a team, or talks at a conference. Collections allow you to define a new type of document that behave like Pages or Posts do normally, but also have their own unique properties and namespace.
+
+## Using Collections
+
+### Step 1: Tell Jekyll to read in your collection
+
+Add the following to your site's `_config.yml` file, replacing `my_collection` with the name of your collection:
+
+{% highlight yaml %}
+collections:
+- my_collection
+{% endhighlight %}
+
+You can optionally specify metadata for your collection in the configuration:
+
+{% highlight yaml %}
+collections:
+ my_collection:
+ foo: bar
+{% endhighlight %}
+
+### Step 2: Add your content
+
+Create a corresponding folder (e.g. `/_my_collection`) and add documents.
+YAML Front Matter is read in as data if it exists, if not, then everything is just stuck in the Document's `content` attribute.
+
+Note: the folder must be named identically to the collection you defined in your `_config.yml` file, with the addition of the preceding `_` character.
+
+### Step 3: Optionally render your collection's documents into independent files
+
+If you'd like Jekyll to create a public-facing, rendered version of each document in your collection, set the `output` key to `true` in your collection metadata in your `_config.yml`:
+
+{% highlight yaml %}
+collections:
+ my_collection:
+ output: true
+{% endhighlight %}
+
+This will produce a file for each document in the collection.
+For example, if you have `_my_collection/some_subdir/some_doc.md`,
+it will be rendered using Liquid and the Markdown converter of your
+choice and written out to `/my_collection/some_subdir/some_doc.html`.
+
+As for posts with [Permalinks](../permalinks/), document URL can be customized by setting a `permalink` metadata to the collection:
+
+{% highlight yaml %}
+collections:
+ my_collection:
+ output: true
+ permalink: /awesome/:path/
+{% endhighlight %}
+
+For example, if you have `_my_collection/some_subdir/some_doc.md`, it will be written out to `/awesome/some_subdir/some_doc/index.html`.
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
+
collection
+
+
+
Label of the containing collection.
+
+
+
+
+
path
+
+
+
Path to the document relative to the collection's directory.
+
+
+
+
+
name
+
+
+
The document's base filename, with every sequence of spaces and non-alphanumeric characters replaced by a hyphen.
+
+
+
+
+
title
+
+
+
The document's lowercase title (as defined in its front matter), with every sequence of spaces and non-alphanumeric characters replaced by a hyphen. If the document does not define a title in its front matter, this is equivalent to name.
+
+
+
+
+
output_ext
+
+
+
Extension of the output file.
+
+
+
+
+
+
+## Liquid Attributes
+
+### Collections
+
+Each collection is accessible via the `site` Liquid variable. For example, if you want to access the `albums` collection found in `_albums`, you'd use `site.albums`. Each collection is itself an array of documents (e.g. `site.albums` is an array of documents, much like `site.pages` and `site.posts`). See below for how to access attributes of those documents.
+
+The collections are also available under `site.collections`, with the metadata you specified in your `_config.yml` (if present) and the following information:
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
+
label
+
+
+
+ The name of your collection, e.g. my_collection.
+
+ The path to the collections's source directory, relative to the site source.
+
+
+
+
+
+
directory
+
+
+
+ The full path to the collections's source directory.
+
+
+
+
+
+
output
+
+
+
+ Whether the collection's documents will be output as individual files.
+
+
+
+
+
+
+
+
+### Documents
+
+In addition to any YAML Front Matter provided in the document's corresponding file, each document has the following attributes:
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
+
content
+
+
+
+ The (unrendered) content of the document. If no YAML Front Matter is provided,
+ this is the entirety of the file contents. If YAML Front Matter
+ is used, then this is all the contents of the file after the terminating
+ `---` of the front matter.
+
+
+
+
+
+
output
+
+
+
+ The rendered output of the document, based on the content.
+
+
+
+
+
+
path
+
+
+
+ The full path to the document's source file.
+
+
+
+
+
+
relative_path
+
+
+
+ The path to the document's source file relative to the site source.
+
+
+
+
+
+
url
+
+
+
+ The URL of the rendered collection. The file is only written to the
+ destination when the name of the collection to which it belongs is
+ included in the render key in the site's configuration file.
+
+
+
+
+
+
collection
+
+
+
+ The name of the document's collection.
+
+
+
+
+
+
diff --git a/_docs/configuration.md b/_docs/configuration.md
new file mode 100755
index 0000000..e1d176f
--- /dev/null
+++ b/_docs/configuration.md
@@ -0,0 +1,613 @@
+---
+layout: docs
+title: Configuration
+prev_section: structure
+next_section: frontmatter
+permalink: /docs/configuration/
+---
+
+Jekyll allows you to concoct your sites in any way you can dream up, and it’s
+thanks to the powerful and flexible configuration options that this is possible.
+These options can either be specified in a `_config.yml` file placed in your
+site’s root directory, or can be specified as flags for the `jekyll` executable
+in the terminal.
+
+## Configuration Settings
+
+### Global Configuration
+
+The table below lists the available settings for Jekyll, and the various options (specified in the configuration file) and flags (specified on the command-line) that control them.
+
+
+
+
+
+
Setting
+
+ Options and Flags
+
+
+
+
+
+
+
Site Source
+
Change the directory where Jekyll will read files
+
+
+
source: DIR
+
-s, --source DIR
+
+
+
+
+
Site Destination
+
Change the directory where Jekyll will write files
+ Exclude directories and/or files from the
+ conversion. These exclusions are relative to the site's
+ source directory and cannot be outside the source directory.
+
+
+
+
exclude: [DIR, FILE, ...]
+
+
+
+
+
Include
+
+ Force inclusion of directories and/or files in the conversion.
+ .htaccess is a good example since dotfiles are excluded
+ by default.
+
+
+
+
include: [DIR, FILE, ...]
+
+
+
+
+
Keep files
+
+ When clobbering the site destination, keep the selected files.
+ Useful for files that are not generated by jekyll; e.g. files or
+ assets that are generated by your build tool.
+ The paths are relative to the destination.
+
+
+
+
keep_files: [DIR, FILE, ...]
+
+
+
+
+
Time Zone
+
+ Set the time zone for site generation. This sets the TZ
+ environment variable, which Ruby uses to handle time and date
+ creation and manipulation. Any entry from the
+ IANA Time Zone
+ Database is valid, e.g. America/New_York. A list of all
+ available values can be found
+ here. The default is the local time zone, as set by your operating system.
+
+
+
+
timezone: TIMEZONE
+
+
+
+
+
Encoding
+
+ Set the encoding of files by name. Only available for Ruby
+ 1.9 or later).
+ The default value is utf-8 starting in 2.0.0,
+ and nil before 2.0.0, which will yield the Ruby
+ default of ASCII-8BIT.
+ Available encodings can be shown by the
+ command ruby -e 'puts Encoding::list.join("\n")'.
+
+ The contents of <destination> are automatically
+ cleaned when the site is built. Files or folders that are not
+ created by your site will be removed. Do not use an important
+ location for <destination>; instead, use it as
+ a staging area and copy files from there to your web server.
+
+
+
+### Build Command Options
+
+
+
+
+
+
Setting
+
Options and Flags
+
+
+
+
+
+
Regeneration
+
Enable auto-regeneration of the site when files are modified.
+
+
+
-w, --watch
+
+
+
+
+
Configuration
+
Specify config files instead of using _config.yml automatically. Settings in later files override settings in earlier files.
+
+
+
--config FILE1[,FILE2,...]
+
+
+
+
+
Drafts
+
Process and render draft posts.
+
+
+
--drafts
+
+
+
+
+
Future
+
Publish posts with a future date.
+
+
+
future: BOOL
+
--future
+
+
+
+
+
LSI
+
Produce an index for related posts.
+
+
+
lsi: BOOL
+
--lsi
+
+
+
+
+
Limit Posts
+
Limit the number of posts to parse and publish.
+
+
+
limit_posts: NUM
+
--limit_posts NUM
+
+
+
+
+
Force polling
+
Force watch to use polling.
+
+
+
--force_polling
+
+
+
+
+
Verbose output
+
Print verbose output.
+
+
+
-V, --verbose
+
+
+
+
+
Silence Output
+
Silence the normal output from Jekyll
+ during a build
+
+
+
-q, --quiet
+
+
+
+
+
+
+### Serve Command Options
+
+In addition to the options below, the `serve` sub-command can accept any of the options
+for the `build` sub-command, which are then applied to the site build which occurs right
+before your site is served.
+
+
+
+
+
+
Setting
+
Options and Flags
+
+
+
+
+
+
Local Server Port
+
Listen on the given port.
+
+
+
port: PORT
+
--port PORT
+
+
+
+
+
Local Server Hostname
+
Listen at the given hostname.
+
+
+
host: HOSTNAME
+
--host HOSTNAME
+
+
+
+
+
Base URL
+
Serve the website from the given base URL
+
+
+
baseurl: URL
+
--baseurl URL
+
+
+
+
+
Detach
+
Detach the server from the terminal
+
+
+
detach: BOOL
+
-B, --detach
+
+
+
+
+
Skips the initial site build.
+
Skips the initial site build which occurs before the server is started.
+
+
+
--skip-initial-build
+
+
+
+
+
+
+
+
Do not use tabs in configuration files
+
+ This will either lead to parsing errors, or Jekyll will revert to the
+ default settings. Use spaces instead.
+
+
+
+## Front Matter defaults
+
+Using [YAML Front Matter](../frontmatter/) is one way that you can specify configuration in the pages and posts for your site. Setting things like a default layout, or customizing the title, or specifying a more precise date/time for the post can all be added to your page or post front matter.
+
+Often times, you will find that you are repeating a lot of configuration options. Setting the same layout in each file, adding the same category - or categories - to a post, etc. You can even add custom variables like author names, which might be the same for the majority of posts on your blog.
+
+Instead of repeating this configuration each time you create a new post or page, Jekyll provides a way to set these defaults in the site configuration. To do this, you can specify site-wide defaults using the `defaults` key in the `_config.yml` file in your projects root directory.
+
+The `defaults` key holds an array of scope/values pairs that define what defaults should be set for a particular file path, and optionally, a file type in that path.
+
+Let's say that you want to add a default layout to all pages and posts in your site. You would add this to your `_config.yml` file:
+
+{% highlight yaml %}
+defaults:
+ -
+ scope:
+ path: "" # an empty string here means all files in the project
+ values:
+ layout: "default"
+{% endhighlight %}
+
+Here, we are scoping the `values` to any file that exists in the scopes path. Since the path is set as an empty string, it will apply to **all files** in your project. You probably don't want to set a layout on every file in your project - like css files, for example - so you can also specify a `type` value under the `scope` key.
+
+{% highlight yaml %}
+defaults:
+ -
+ scope:
+ path: "" # an empty string here means all files in the project
+ type: "posts" # previously `post` in Jekyll 2.2.
+ values:
+ layout: "default"
+{% endhighlight %}
+
+Now, this will only set the layout for files where the type is `posts`.
+The different types that are available to you are `pages`, `posts`, `drafts` or any collection in your site. While `type` is optional, you must specify a value for `path` when creating a `scope/values` pair.
+
+As mentioned earlier, you can set multiple scope/values pairs for `defaults`.
+
+{% highlight yaml %}
+defaults:
+ -
+ scope:
+ path: ""
+ type: "posts"
+ values:
+ layout: "my-site"
+ -
+ scope:
+ path: "projects"
+ type: "pages"
+ values:
+ layout: "project" # overrides previous default layout
+ author: "Mr. Hyde"
+{% endhighlight %}
+
+With these defaults, all posts would use the `my-site` layout. Any html files that exist in the `projects/` folder will use the `project` layout, if it exists. Those files will also have the `page.author` [liquid variable](../variables/) set to `Mr. Hyde` as well as have the category for the page set to `project`.
+
+{% highlight yaml %}
+collections:
+ - my_collection:
+ output: true
+
+defaults:
+ -
+ scope:
+ path: ""
+ type: "my_collection" # a collection in your site, in plural form
+ values:
+ layout: "default"
+{% endhighlight %}
+
+In this example the `layout` is set to `default` inside the [collection](../collections) with the name `my_collection`.
+
+### Precedence
+
+Jekyll will apply all of the configuration settings you specify in the `defaults` section of your `_config.yml` file. However, you can choose to override settings from other scope/values pair by specifying a more specific path for the scope.
+
+You can see that in the last example above. First, we set the default layout to `my-site`. Then, using a more specific path, we set the default layout for files in the `projects/` path to `project`. This can be done with any value that you would set in the page or post front matter.
+
+Finally, if you set defaults in the site configuration by adding a `defaults` section to your `_config.yml` file, you can override those settings in a post or page file. All you need to do is specify the settings in the post or page front matter. For example:
+
+{% highlight yaml %}
+# In _config.yml
+...
+defaults:
+ -
+ scope:
+ path: "projects"
+ type: "pages"
+ values:
+ layout: "project"
+ author: "Mr. Hyde"
+ category: "project"
+...
+{% endhighlight %}
+
+{% highlight yaml %}
+# In projects/foo_project.md
+---
+author: "John Smith"
+layout: "foobar"
+---
+The post text goes here...
+{% endhighlight %}
+
+The `projects/foo_project.md` would have the `layout` set to `foobar` instead of `project` and the `author` set to `John Smith` instead of `Mr. Hyde` when the site is built.
+
+## Default Configuration
+
+Jekyll runs with the following configuration options by default. Unless
+alternative settings for these options are explicitly specified in the
+configuration file or on the command-line, Jekyll will run using these options.
+
+
+
There are two unsupported kramdown options
+
+ Please note that both remove_block_html_tags and
+ remove_span_html_tags are currently unsupported in Jekyll due to the
+ fact that they are not included within the kramdown HTML converter.
+
+
+
+{% highlight yaml %}
+# Where things are
+source: .
+destination: ./_site
+plugins: ./_plugins
+layouts: ./_layouts
+data_source: ./_data
+collections: null
+
+# Handling Reading
+safe: false
+include: [".htaccess"]
+exclude: []
+keep_files: [".git", ".svn"]
+encoding: "utf-8"
+markdown_ext: "markdown,mkdown,mkdn,mkd,md"
+textile_ext: "textile"
+
+# Filtering Content
+show_drafts: null
+limit_posts: 0
+future: true
+unpublished: false
+
+# Plugins
+whitelist: []
+gems: []
+
+# Conversion
+markdown: kramdown
+highlighter: pygments
+lsi: false
+excerpt_separator: "\n\n"
+
+# Serving
+detach: false
+port: 4000
+host: 0.0.0.0
+baseurl: "" # does not include hostname
+
+# Backwards-compatibility
+relative_permalinks: false
+
+# Outputting
+permalink: date
+paginate_path: /page:num
+timezone: null
+
+quiet: false
+defaults: []
+
+# Markdown Processors
+maruku:
+ use_tex: false
+ use_divs: false
+ png_engine: blahtex
+ png_dir: images/latex
+ png_url: /images/latex
+ fenced_code_blocks: true
+
+rdiscount:
+ extensions: []
+
+redcarpet:
+ extensions: []
+
+kramdown:
+ auto_ids: true
+ footnote_nr: 1
+ entity_output: as_char
+ toc_levels: 1..6
+ smart_quotes: lsquo,rsquo,ldquo,rdquo
+ use_coderay: false
+
+ coderay:
+ coderay_wrap: div
+ coderay_line_numbers: inline
+ coderay_line_number_start: 1
+ coderay_tab_width: 4
+ coderay_bold_every: 10
+ coderay_css: style
+
+redcloth:
+ hard_breaks: true
+{% endhighlight %}
+
+## Markdown Options
+
+The various Markdown renderers supported by Jekyll sometimes have extra options available.
+
+### Redcarpet
+
+Redcarpet can be configured by providing an `extensions` sub-setting, whose value should be an array of strings. Each string should be the name of one of the `Redcarpet::Markdown` class's extensions; if present in the array, it will set the corresponding extension to `true`.
+
+Jekyll handles two special Redcarpet extensions:
+
+- `no_fenced_code_blocks` --- By default, Jekyll sets the `fenced_code_blocks` extension (for delimiting code blocks with triple tildes or triple backticks) to `true`, probably because GitHub's eager adoption of them is starting to make them inescapable. Redcarpet's normal `fenced_code_blocks` extension is inert when used with Jekyll; instead, you can use this inverted version of the extension for disabling fenced code.
+
+Note that you can also specify a language for highlighting after the first delimiter:
+
+ ```ruby
+ # ...ruby code
+ ```
+
+With both fenced code blocks and highlighter enabled, this will statically highlight the code; without any syntax highlighter, it will add a `class="LANGUAGE"` attribute to the `` element, which can be used as a hint by various JavaScript code highlighting libraries.
+
+- `smart` --- This pseudo-extension turns on SmartyPants, which converts straight quotes to curly quotes and runs of hyphens to em (`---`) and en (`--`) dashes.
+
+All other extensions retain their usual names from Redcarpet, and no renderer options aside from `smart` can be specified in Jekyll. [A list of available extensions can be found in the Redcarpet README file.][redcarpet_extensions] Make sure you're looking at the README for the right version of Redcarpet: Jekyll currently uses v2.2.x, and extensions like `footnotes` and `highlight` weren't added until after version 3.0.0. The most commonly used extensions are:
+
+- `tables`
+- `no_intra_emphasis`
+- `autolink`
+
+[redcarpet_extensions]: https://github.com/vmg/redcarpet/blob/v2.2.2/README.markdown#and-its-like-really-simple-to-use
+
+### Kramdown
+
+In addition to the defaults mentioned above, you can also turn on recognition of Github Flavored Markdown by passing an `input` option with a value of "GFM".
+
+For example, in your `_config.yml`:
+
+ kramdown:
+ input: GFM
+
+### Custom Markdown Processors
+
+If you're interested in creating a custom markdown processor, you're in luck! Create a new class in the `Jekyll::Converters::Markdown` namespace:
+
+{% highlight ruby %}
+class Jekyll::Converters::Markdown::MyCustomProcessor
+ def initialize(config)
+ require 'funky_markdown'
+ @config = config
+ rescue LoadError
+ STDERR.puts 'You are missing a library required for Markdown. Please run:'
+ STDERR.puts ' $ [sudo] gem install funky_markdown'
+ raise FatalException.new("Missing dependency: funky_markdown")
+ end
+
+ def convert(content)
+ ::FunkyMarkdown.new(content).convert
+ end
+end
+{% endhighlight %}
+
+Once you've created your class and have it properly setup either as a plugin in the `_plugins` folder or as a gem, specify it in your `_config.yml`:
+
+{% highlight yaml %}
+markdown: MyCustomProcessor
+{% endhighlight %}
diff --git a/_docs/continuous-integration.md b/_docs/continuous-integration.md
new file mode 100755
index 0000000..0e2b3a5
--- /dev/null
+++ b/_docs/continuous-integration.md
@@ -0,0 +1,177 @@
+---
+layout: docs
+title: Continuous Integration
+prev_section: deployment-methods
+next_section: troubleshooting
+permalink: /docs/continuous-integration/
+---
+
+You can easily test your website build against one or more versions of Ruby.
+The following guide will show you how to set up a free build environment on
+[Travis][0], with [GitHub][1] integration for pull requests. Paid
+alternatives exist for private repositories.
+
+[0]: https://travis-ci.org/
+[1]: https://github.com/
+
+## 1. Enabling Travis and GitHub
+
+Enabling Travis builds for your GitHub repository is pretty simple:
+
+1. Go to your profile on travis-ci.org: https://travis-ci.org/profile/username
+2. Find the repository for which you're interested in enabling builds.
+3. Click the slider on the right so it says "ON" and is a dark grey.
+4. Optionally configure the build by clicking on the wrench icon. Further
+ configuration happens in your `.travis.yml` file. More details on that
+ below.
+
+## 2. The Test Script
+
+The simplest test script simply runs `jekyll build` and ensures that Jekyll
+doesn't fail to build the site. It doesn't check the resulting site, but it
+does ensure things are built properly.
+
+When testing Jekyll output, there is no better tool than [html-proofer][2].
+This tool checks your resulting site to ensure all links and images exist.
+Utilize it either with the convenient `htmlproof` command-line executable,
+or write a Ruby script which utilizes the gem.
+
+### The HTML Proofer Executable
+
+{% highlight bash %}
+#!/usr/bin/env bash
+set -e # halt script on error
+
+bundle exec jekyll build
+bundle exec htmlproof ./_site
+{% endhighlight %}
+
+Some options can be specified via command-line switches. Check out the
+`html-proofer` README for more information about these switches, or run
+`htmlproof --help` locally.
+
+### The HTML Proofer Library
+
+You can also invoke `html-proofer` in Ruby scripts (e.g. in a Rakefile):
+
+{% highlight ruby %}
+#!/usr/bin/env ruby
+
+require 'html/proofer'
+HTML::Proofer.new("./_site").run
+{% endhighlight %}
+
+Options are given as a second argument to `.new`, and are encoded in a
+symbol-keyed Ruby Hash. More information about the configuration options,
+check out `html-proofer`'s README file.
+
+[2]: https://github.com/gjtorikian/html-proofer
+
+## 3. Configuring Your Travis Builds
+
+This file is used to configure your Travis builds. Because Jekyll is built
+with Ruby and requires RubyGems to install, we use the Ruby language build
+environment. Below is a sample `.travis.yml` file, and what follows that is
+an explanation of each line.
+
+{% highlight yaml %}
+language: ruby
+rvm:
+- 2.1
+script: ./script/cibuild
+
+# branch whitelist
+branches:
+ only:
+ - gh-pages # test the gh-pages branch
+ - /pages-(.*)/ # test every branch which starts with "pages-"
+
+env:
+ global:
+ - NOKOGIRI_USE_SYSTEM_LIBRARIES=true # speeds up installation of html-proofer
+{% endhighlight %}
+
+Ok, now for an explanation of each line:
+
+{% highlight yaml %}
+language: ruby
+{% endhighlight %}
+
+This line tells Travis to use a Ruby build container. It gives your script
+access to Bundler, RubyGems, and a Ruby runtime.
+
+{% highlight yaml %}
+rvm:
+- 2.1
+{% endhighlight %}
+
+RVM is a popular Ruby Version Manager (like rbenv, chruby, etc). This
+directive tells Travis the Ruby version to use when running your test
+script.
+
+{% highlight yaml %}
+script: ./script/cibuild
+{% endhighlight %}
+
+Travis allows you to run any arbitrary shell script to test your site. One
+convention is to put all scripts for your project in the `script`
+directory, and to call your test script `cibuild`. This line is completely
+customizable. If your script won't change much, you can write your test
+incantation here directly:
+
+{% highlight yaml %}
+script: jekyll build && htmlproof ./_site
+{% endhighlight %}
+
+The `script` directive can be absolutely any valid shell command.
+
+{% highlight yaml %}
+# branch whitelist
+branches:
+ only:
+ - gh-pages # test the gh-pages branch
+ - /pages-(.*)/ # test every branch which starts with "pages-"
+{% endhighlight %}
+
+You want to ensure the Travis builds for your site are being run only on
+the branch or branches which contain your site. One means of ensuring this
+isolation is including a branch whitelist in your Travis configuration
+file. By specifying the `gh-pages` branch, you will ensure the associated
+test script (discussed above) is only executed on site branches. If you use
+a pull request flow for proposing changes, you may wish to enforce a
+convention for your builds such that all branches containing edits are
+prefixed, exemplified above with the `/pages-(.*)/` regular expression.
+
+The `branches` directive is completely optional.
+
+{% highlight yaml %}
+env:
+ global:
+ - NOKOGIRI_USE_SYSTEM_LIBRARIES=true # speeds up installation of html-proofer
+{% endhighlight %}
+
+Using `html-proofer`? You'll want this environment variable. Nokogiri, used
+to parse HTML files in your compiled site, comes bundled with libraries
+which it must compile each time it is installed. Luckily, you can
+dramatically decrease the install time of Nokogiri by setting the
+environment variable `NOKOGIRI_USE_SYSTEM_LIBRARIES` to `true`.
+
+## 4. Gotchas
+
+### Exclude `vendor`
+
+Travis bundles all gems in the `vendor` directory on its build servers,
+which Jekyll will mistakenly read and explode on. To avoid this, exclude
+`vendor` in your `_config.yml`:
+
+{% highlight yaml %}
+exclude: [vendor]
+{% endhighlight %}
+
+### Questions?
+
+This entire guide is open-source. Go ahead and [edit it][3] if you have a
+fix or [ask for help][4] if you run into trouble and need some help.
+
+[3]: https://github.com/jekyll/jekyll/edit/master/site/_docs/continuous-integration.md
+[4]: https://github.com/jekyll/jekyll-help#how-do-i-ask-a-question
diff --git a/_docs/contributing.md b/_docs/contributing.md
new file mode 100755
index 0000000..e3dbe80
--- /dev/null
+++ b/_docs/contributing.md
@@ -0,0 +1,133 @@
+---
+layout: docs
+title: Contributing
+prev_section: upgrading
+next_section: history
+permalink: /docs/contributing/
+---
+
+So you've got an awesome idea to throw into Jekyll. Great! Please keep the
+following in mind:
+
+* If you're creating a small fix or patch to an existing feature, just a simple
+ test will do. Please stay in the confines of the current test suite and use
+ [Shoulda](https://github.com/thoughtbot/shoulda/tree/master) and
+ [RR](https://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 `site`
+ would be appreciated, and once merged it will be transferred over to the main
+ `site`, jekyllrb.com.
+* If your contribution changes any Jekyll behavior, make sure to update the
+ documentation. It lives in `site/docs`. If the docs are missing information,
+ please feel free to add it in. Great docs make a great project!
+* Please follow the [GitHub Ruby Styleguide](https://github.com/styleguide/ruby)
+ when modifying Ruby code.
+* Please do your best to submit **small pull requests**. The easier the proposed
+ change is to review, the more likely it will be merged.
+* When submitting a pull request, please make judicious use of the pull request
+ body. A description of what changes were made, the motivations behind the
+ changes and [any tasks completed or left to complete](http://git.io/gfm-tasks)
+ will also speed up review time.
+
+
+
Contributions will not be accepted without tests
+
+ If you’re creating a small fix or patch to an existing feature, just
+ a simple test will do.
+
+
+
+Test Dependencies
+-----------------
+
+To run the test suite and build the gem you'll need to install Jekyll's
+dependencies. Jekyll uses Bundler, so a quick run of the `bundle` command and
+you're all set!
+
+{% highlight bash %}
+$ bundle
+{% endhighlight %}
+
+Before you start, run the tests and make sure that they pass (to confirm your
+environment is configured properly):
+
+{% highlight bash %}
+$ bundle exec rake test
+$ bundle exec rake features
+{% endhighlight %}
+
+Workflow
+--------
+
+Here's the most direct way to get your work merged into the project:
+
+* Fork the project.
+* Clone down your fork:
+
+{% highlight bash %}
+git clone git://github.com//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:
+
+{% highlight bash %}
+git push origin my_awesome_feature
+{% endhighlight %}
+
+* Create a pull request against jekyll/jekyll:master and describe what your
+ change does and the why you think it should be merged.
+
+Updating Documentation
+----------------------
+
+We want the Jekyll documentation to be the best it can be. We've
+open-sourced our docs and we welcome any pull requests if you find it
+lacking.
+
+You can find the documentation for jekyllrb.com in the
+[site]({{ site.repository }}/tree/master/site) directory of
+Jekyll's repo on GitHub.com.
+
+All documentation pull requests should be directed at `master`. Pull
+requests directed at another branch will not be accepted.
+
+The [Jekyll wiki]({{ site.repository }}/wiki) on GitHub
+can be freely updated without a pull request as all
+GitHub users have access.
+
+If you want to add your plugin to the [list of plugins](/docs/plugins/#available-plugins),
+please submit a pull request modifying the [plugins page source
+file]({{ site.repository }}/blob/master/site/_docs/plugins.md) by adding a
+link to your plugin under the proper subheading depending upon its type.
+
+Gotchas
+-------
+
+* If you want to bump the gem version, please put that in a separate commit.
+ This way, the maintainers can control when the gem gets released.
+* Try to keep your patch(es) based from the latest commit on jekyll/jekyll.
+ The easier it is to apply your work, the less work the maintainers have to do,
+ which is always a good thing.
+* Please don't tag your GitHub issue with \[fix\], \[feature\], etc. The maintainers
+ actively read the issues and will label it once they come across it.
+
+
+
Let us know what could be better!
+
+ Both using and hacking on Jekyll should be fun, simple, and easy, so if for
+ some reason you find it’s a pain, please create an issue on
+ GitHub describing your experience so we can make it better.
+
+
diff --git a/_docs/datafiles.md b/_docs/datafiles.md
new file mode 100755
index 0000000..7088fec
--- /dev/null
+++ b/_docs/datafiles.md
@@ -0,0 +1,118 @@
+---
+layout: docs
+title: Data Files
+prev_section: collections
+next_section: assets
+permalink: /docs/datafiles/
+---
+
+In addition to the [built-in variables](../variables/) available from Jekyll,
+you can specify your own custom data that can be accessed via the [Liquid
+templating system](https://wiki.github.com/shopify/liquid/liquid-for-designers).
+
+Jekyll supports loading data from [YAML](http://yaml.org/), [JSON](http://www.json.org/),
+and [CSV](https://en.wikipedia.org/wiki/Comma-separated_values) files located in the `_data` directory.
+Note that CSV files *must* contain a header row.
+
+This powerful feature allows you to avoid repetition in your templates and to
+set site specific options without changing `_config.yml`.
+
+Plugins/themes can also leverage Data Files to set configuration variables.
+
+## The Data Folder
+
+As explained on the [directory structure](../structure/) page, the `_data`
+folder is where you can store additional data for Jekyll to use when generating
+your site. These files must be YAML files (using either the `.yml`, `.yaml`, `.json`
+or `csv` extension) and they will be accessible via `site.data`.
+
+## Example: List of members
+
+Here is a basic example of using Data Files to avoid copy-pasting large chunks of
+code in your Jekyll templates:
+
+In `_data/members.yml`:
+
+{% highlight yaml %}
+- name: Tom Preston-Werner
+ github: mojombo
+
+- name: Parker Moore
+ github: parkr
+
+- name: Liu Fengyun
+ github: liufengyun
+{% endhighlight %}
+
+Or `_data/members.csv`:
+
+{% highlight text %}
+name,github
+Tom Preston-Werner,mojombo
+Parker Moore,parkr
+Liu Fengyun,liufengyun
+{% endhighlight %}
+
+This data can be accessed via `site.data.members` (notice that the filename
+determines the variable name).
+
+You can now render the list of members in a template:
+
+{% highlight html %}
+{% raw %}
+
+{% endraw %}
+{% endhighlight %}
+
+## Example: Organizations
+
+Data files can also be placed in sub-folders of the `_data` folder. Each folder level will be added to a variable's namespace. The example below shows how GitHub organizations could be defined separately in a file under the `orgs` folder:
+
+In `_data/orgs/jekyll.yml`:
+
+{% highlight yaml %}
+username: jekyll
+name: Jekyll
+members:
+ - name: Tom Preston-Werner
+ github: mojombo
+
+ - name: Parker Moore
+ github: parkr
+{% endhighlight %}
+
+In `_data/orgs/doeorg.yml`:
+
+{% highlight yaml %}
+username: doeorg
+name: Doe Org
+members:
+ - name: John Doe
+ github: jdoe
+{% endhighlight %}
+
+The organizations can then be accessed via `site.data.orgs`, followed by the file name:
+
+{% highlight html %}
+{% raw %}
+
+{% for org_hash in site.data.orgs %}
+{% assign org = org_hash[1] %}
+
+{% endraw %}
+{% endhighlight %}
diff --git a/_docs/deployment-methods.md b/_docs/deployment-methods.md
new file mode 100755
index 0000000..2ab929b
--- /dev/null
+++ b/_docs/deployment-methods.md
@@ -0,0 +1,127 @@
+---
+layout: docs
+title: Deployment methods
+prev_section: github-pages
+next_section: continuous-integration
+permalink: /docs/deployment-methods/
+---
+
+Sites built using Jekyll can be deployed in a large number of ways due to the static nature of the generated output. A few of the most common deployment techniques are described below.
+
+## Web hosting providers (FTP)
+
+Just about any traditional web hosting provider will let you upload files to their servers over FTP. To upload a Jekyll site to a web host using FTP, simply run the `jekyll` command and copy the generated `_site` folder to the root folder of your hosting account. This is most likely to be the `httpdocs` or `public_html` folder on most hosting providers.
+
+### FTP using Glynn
+
+There is a project called [Glynn](https://github.com/dmathieu/glynn), which lets you easily generate your Jekyll powered website’s static files and
+send them to your host through FTP.
+
+## Self-managed web server
+
+If you have direct access yourself to the deployment web server yourself, the process is essentially the same, except you might have other methods available to you (such as `scp`, or even direct filesystem access) for transferring the files. Just remember to make sure the contents of the generated `_site` folder get placed in the appropriate web root directory for your web server.
+
+## Automated methods
+
+There are also a number of ways to easily automate the deployment of a Jekyll site. If you’ve got another method that isn’t listed below, we’d love it if you [contributed](../contributing/) so that everyone else can benefit too.
+
+### Git post-update hook
+
+If you store your Jekyll site in [Git](http://git-scm.com/) (you are using version control, right?), it’s pretty easy to automate the
+deployment process by setting up a post-update hook in your Git
+repository, [like
+this](http://web.archive.org/web/20091223025644/http://www.taknado.com/en/2009/03/26/deploying-a-jekyll-generated-site/).
+
+### Git post-receive hook
+
+To have a remote server handle the deploy for you every time you push changes using Git, you can create a user account which has all the public keys that are authorized to deploy in its `authorized_keys` file. With that in place, setting up the post-receive hook is done as follows:
+
+{% highlight bash %}
+laptop$ ssh deployer@example.com
+server$ mkdir myrepo.git
+server$ cd myrepo.git
+server$ git --bare init
+server$ cp hooks/post-receive.sample hooks/post-receive
+server$ mkdir /var/www/myrepo
+{% endhighlight %}
+
+Next, add the following lines to hooks/post-receive and be sure Jekyll is
+installed on the server:
+
+{% highlight bash %}
+GIT_REPO=$HOME/myrepo.git
+TMP_GIT_CLONE=$HOME/tmp/myrepo
+PUBLIC_WWW=/var/www/myrepo
+
+git clone $GIT_REPO $TMP_GIT_CLONE
+jekyll build -s $TMP_GIT_CLONE -d $PUBLIC_WWW
+rm -Rf $TMP_GIT_CLONE
+exit
+{% endhighlight %}
+
+Finally, run the following command on any users laptop that needs to be able to
+deploy using this hook:
+
+{% highlight bash %}
+laptops$ git remote add deploy deployer@example.com:~/myrepo.git
+{% endhighlight %}
+
+Deploying is now as easy as telling nginx or Apache to look at
+`/var/www/myrepo` and running the following:
+
+{% highlight bash %}
+laptops$ git push deploy master
+{% endhighlight %}
+
+### Jekyll-hook
+
+You can also use jekyll-hook, a server that listens for webhook posts from
+GitHub, generates a website with Jekyll, and moves it somewhere to be
+published. Use this to run your own GitHub Pages-style web server.
+
+This method is useful if you need to serve your websites behind a firewall,
+need extra server-level features like HTTP basic authentication or want to
+host your site directly on a CDN or file host like S3.
+
+Setup steps are fully documented
+[in the `jekyll-hook` repo](https://github.com/developmentseed/jekyll-hook).
+
+### Rake
+
+Another way to deploy your Jekyll site is to use [Rake](https://github.com/jimweirich/rake), [HighLine](https://github.com/JEG2/highline), and
+[Net::SSH](https://github.com/net-ssh/net-ssh). A more complex example of deploying Jekyll with Rake that deals with multiple branches can be found in [Git Ready](https://github.com/gitready/gitready/blob/cdfbc4ec5321ff8d18c3ce936e9c749dbbc4f190/Rakefile).
+
+### rsync
+
+Once you’ve generated the `_site` directory, you can easily rsync it using a `tasks/deploy` shell script similar to [this deploy script here](https://github.com/henrik/henrik.nyh.se/blob/master/tasks/deploy). You’d obviously need to change the values to reflect your site’s details. There is even [a matching TextMate command](http://gist.github.com/214959) that will help you run
+this script from within Textmate.
+
+
+## Rack-Jekyll
+
+[Rack-Jekyll](https://github.com/adaoraul/rack-jekyll/) is an easy way to deploy your site on any Rack server such as Amazon EC2, Slicehost, Heroku, and so forth. It also can run with [shotgun](https://github.com/rtomayko/shotgun/), [rackup](https://github.com/rack/rack), [mongrel](https://github.com/mongrel/mongrel), [unicorn](https://github.com/defunkt/unicorn/), and [others](https://github.com/adaoraul/rack-jekyll#readme).
+
+Read [this post](http://blog.crowdint.com/2010/08/02/instant-blog-using-jekyll-and-heroku.html) on how to deploy to Heroku using Rack-Jekyll.
+
+## Jekyll-Admin for Rails
+
+If you want to maintain Jekyll inside your existing Rails app, [Jekyll-Admin](https://github.com/zkarpinski/Jekyll-Admin) contains drop in code to make this possible. See Jekyll-Admin’s [README](https://github.com/zkarpinski/Jekyll-Admin/blob/master/README) for more details.
+
+## Amazon S3
+
+If you want to host your site in Amazon S3, you can do so with
+[s3_website](https://github.com/laurilehmijoki/s3_website) application. It will
+push your site to Amazon S3 where it can be served like any web server,
+dynamically scaling to almost unlimited traffic. This approach has the
+benefit of being about the cheapest hosting option available for
+low-volume blogs as you only pay for what you use.
+
+## OpenShift
+
+If you'd like to deploy your site to an OpenShift gear, there's [a cartridge
+for that](https://github.com/openshift-cartridges/openshift-jekyll-cartridge).
+
+
+
ProTip™: Use GitHub Pages for zero-hassle Jekyll hosting
+
GitHub Pages are powered by Jekyll behind the scenes, so if you’re looking for a zero-hassle, zero-cost solution, GitHub Pages are a great way to host your Jekyll-powered website for free.
+
diff --git a/_docs/drafts.md b/_docs/drafts.md
new file mode 100755
index 0000000..959964d
--- /dev/null
+++ b/_docs/drafts.md
@@ -0,0 +1,21 @@
+---
+layout: docs
+title: Working with drafts
+prev_section: posts
+next_section: pages
+permalink: /docs/drafts/
+---
+
+Drafts are posts without a date. They're posts you're still working on and don't want to
+publish yet. To get up and running with drafts, create a `_drafts` folder in your site's
+root (as described in the [site structure](/docs/structure/) section) and create your
+first draft:
+
+{% highlight text %}
+|-- _drafts/
+| |-- a-draft-post.md
+{% endhighlight %}
+
+To preview your site with drafts, simply run `jekyll serve` or `jekyll build` with
+the `--drafts` switch. Each will be assigned the value modification time of the draft file
+for its date, and thus you will see currently edited drafts as the latest posts.
diff --git a/_docs/extras.md b/_docs/extras.md
new file mode 100755
index 0000000..5bdf2c7
--- /dev/null
+++ b/_docs/extras.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+title: Extras
+prev_section: plugins
+next_section: github-pages
+permalink: /docs/extras/
+---
+
+There are a number of (optional) extra features that Jekyll supports that you
+may want to install, depending on how you plan to use Jekyll.
+
+## Math Support
+
+Kramdown comes with optional support for LaTeX to PNG rendering via [MathJax](http://www.mathjax.org/) within math blocks. See the Kramdown documentation on [math blocks](http://kramdown.gettalong.org/syntax.html#math-blocks) and [math support](http://kramdown.gettalong.org/converter/html.html#math-support) for more details.
+
+## Alternative Markdown Processors
+
+See the Markdown section on the [configuration page](/docs/configuration/#markdown-options) for instructions on how to use and configure alternative Markdown processors, as well as how to create [custom processors](/docs/configuration/#custom-markdown-processors).
diff --git a/_docs/frontmatter.md b/_docs/frontmatter.md
new file mode 100755
index 0000000..998be54
--- /dev/null
+++ b/_docs/frontmatter.md
@@ -0,0 +1,191 @@
+---
+layout: docs
+title: Front Matter
+prev_section: configuration
+next_section: posts
+permalink: /docs/frontmatter/
+---
+
+The front matter is where Jekyll starts to get really cool. Any file that
+contains a [YAML](http://yaml.org/) front matter block will be processed by
+Jekyll as a special file. The front matter must be the first thing in the file
+and must take the form of valid YAML set between triple-dashed lines. Here is a
+basic example:
+
+{% highlight yaml %}
+---
+layout: post
+title: Blogging Like a Hacker
+---
+{% endhighlight %}
+
+Between these triple-dashed lines, you can set predefined variables (see below
+for a reference) or even create custom ones of your own. These variables will
+then be available to you to access using Liquid tags both further down in the
+file and also in any layouts or includes that the page or post in question
+relies on.
+
+
+
UTF-8 Character Encoding Warning
+
+ If you use UTF-8 encoding, make sure that no BOM header
+ characters exist in your files or very, very bad things will happen to
+ Jekyll. This is especially relevant if you’re running
+ Jekyll on Windows.
+
+
+
+
+
ProTip™: Front Matter Variables Are Optional
+
+ If you want to use Liquid tags and variables but
+ don’t need anything in your front matter, just leave it empty! The set of
+ triple-dashed lines with nothing in between will still get Jekyll to process
+ your file. (This is useful for things like CSS and RSS feeds!)
+
+
+
+## Predefined Global Variables
+
+There are a number of predefined global variables that you can set in the
+front matter of a page or post.
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
+
layout
+
+
+
+
+ If set, this specifies the layout file to use. Use the layout file
+ name without the file extension. Layout files must be placed in the
+ _layouts directory.
+
+
+
+
+
+
+
permalink
+
+
+
+
+ If you need your processed blog post URLs to be something other than
+ the default /year/month/day/title.html then you can set
+ this variable and it will be used as the final URL.
+
+
+
+
+
+
+
published
+
+
+
+ Set to false if you don’t want a specific post to show up when the
+ site is generated.
+
+
+
+
+
+
category
+
categories
+
+
+
+
+ Instead of placing posts inside of folders, you can specify one or
+ more categories that the post belongs to. When the site is generated
+ the post will act as though it had been set with these categories
+ normally. Categories (plural key) can be specified as a YAML list or a
+ space-separated string.
+
+
+
+
+
+
+
tags
+
+
+
+
+ Similar to categories, one or multiple tags can be added to a post.
+ Also like categories, tags can be specified as a YAML list or a space-
+ separated string.
+
+
+
+
+
+
+
+
+
+## Custom Variables
+
+Any variables in the front matter that are not predefined are mixed into the
+data that is sent to the Liquid templating engine during the conversion. For
+instance, if you set a title, you can use that in your layout to set the page
+title:
+
+{% highlight html %}
+
+
+
+ {% raw %}{{ page.title }}{% endraw %}
+
+
+ ...
+{% endhighlight %}
+
+## Predefined Variables for Posts
+
+These are available out-of-the-box to be used in the front matter for a post.
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
+
date
+
+
+
+ A date here overrides the date from the name of the post. This can be
+ used to ensure correct sorting of posts.
+
+
+
+
+
+
+
+
+
ProTip™: Don't repeat yourself
+
+ If you don't want to repeat your frequently used front matter variables over and over,
+ just define defaults
+ for them and only override them where necessary (or not at all). This works both for predefined
+ and custom variables.
+
+
diff --git a/_docs/github-pages.md b/_docs/github-pages.md
new file mode 100755
index 0000000..83af0b3
--- /dev/null
+++ b/_docs/github-pages.md
@@ -0,0 +1,126 @@
+---
+layout: docs
+title: GitHub Pages
+prev_section: extras
+next_section: deployment-methods
+permalink: /docs/github-pages/
+---
+
+[GitHub Pages](http://pages.github.com) are public web pages for users,
+organizations, and repositories, that are freely hosted on GitHub's
+`github.io` domain or on a custom domain name of your choice. GitHub Pages are
+powered by Jekyll behind the scenes, so in addition to supporting regular HTML
+content, they’re also a great way to host your Jekyll-powered website for free.
+
+## Deploying Jekyll to GitHub Pages
+
+GitHub Pages work by looking at certain branches of repositories on GitHub.
+There are two basic types available: user/organization pages and project pages.
+The way to deploy these two types of sites are nearly identical, except for a
+few minor details.
+
+
+
Use the github-pages gem
+
+ Our friends at GitHub have provided the
+ github-pages
+ gem which is used to manage Jekyll and its dependencies on
+ GitHub Pages. Using it in your projects means that when you deploy
+ your site to GitHub Pages, you will not be caught by unexpected
+ differences between various versions of the gems. To use the
+ currently-deployed version of the gem in your project, add the
+ following to your Gemfile:
+
+{% highlight ruby %}
+source 'https://rubygems.org'
+
+require 'json'
+require 'open-uri'
+versions = JSON.parse(open('https://pages.github.com/versions.json').read)
+
+gem 'github-pages', versions['github-pages']
+{% endhighlight %}
+
+ This will ensure that when you run bundle install, you
+ have the correct version of the github-pages gem.
+
+
+
+### User and Organization Pages
+
+User and organization pages live in a special GitHub repository dedicated to
+only the GitHub Pages files. This repository must be named after the account
+name. For example, [@mojombo’s user page
+repository](https://github.com/mojombo/mojombo.github.io) has the name
+`mojombo.github.io`.
+
+Content from the `master` branch of your repository will be used to build and
+publish the GitHub Pages site, so make sure your Jekyll site is stored there.
+
+
+
Custom domains do not affect repository names
+
+ GitHub Pages are initially configured to live under the
+ username.github.io subdomain, which is why repositories must
+ be named this way even if a custom domain is being used.
+
+
+
+### Project Pages
+
+Unlike user and organization Pages, Project Pages are kept in the same
+repository as the project they are for, except that the website content is
+stored in a specially named `gh-pages` branch. The content of this branch will
+be rendered using Jekyll, and the output will become available under a subpath
+of your user pages subdomain, such as `username.github.io/project` (unless a
+custom domain is specified—see below).
+
+The Jekyll project repository itself is a perfect example of this branch
+structure—the [master branch]({{ site.repository }}) contains the
+actual software project for Jekyll, however the Jekyll website (that you’re
+looking at right now) is contained in the [gh-pages
+branch]({{ site.repository }}/tree/gh-pages) of the same repository.
+
+
+
Source Files Must be in the Root Directory
+
+Github Pages overrides the “Site Source” configuration value, so if you locate your files anywhere other than the root directory, your site may not build correctly.
+
+
+
+
+### Project Page URL Structure
+
+Sometimes it's nice to preview your Jekyll site before you push your `gh-pages`
+branch to GitHub. However, the subdirectory-like URL structure GitHub uses for
+Project Pages complicates the proper resolution of URLs. Here is an approach to
+utilizing the GitHub Project Page URL structure (`username.github.io/project-name/`)
+whilst maintaining the ability to preview your Jekyll site locally.
+
+1. In `_config.yml`, set the `baseurl` option to `/project-name` -- note the
+ leading slash and the **absence** of a trailing slash.
+2. When referencing JS or CSS files, do it like this:
+ `{% raw %}{{ site.baseurl }}/path/to/css.css{% endraw %}` -- note the slash
+ immediately following the variable (just before "path").
+3. When doing permalinks or internal links, do it like this:
+ `{% raw %}{{ site.baseurl }}{{ post.url }}{% endraw %}` -- note that there
+ is **no** slash between the two variables.
+4. Finally, if you'd like to preview your site before committing/deploying using
+ `jekyll serve`, be sure to pass an **empty string** to the `--baseurl` option,
+ so that you can view everything at `localhost:4000` normally (without
+ `/project-name` at the beginning): `jekyll serve --baseurl ''`
+
+This way you can preview your site locally from the site root on localhost,
+but when GitHub generates your pages from the gh-pages branch all the URLs
+will start with `/project-name` and resolve properly.
+
+
+
GitHub Pages Documentation, Help, and Support
+
+ For more information about what you can do with GitHub Pages, as well as for
+ troubleshooting guides, you should check out GitHub’s Pages Help
+ section. If all else fails, you should contact GitHub Support.
+
+
diff --git a/_docs/history.md b/_docs/history.md
new file mode 100755
index 0000000..036a4c9
--- /dev/null
+++ b/_docs/history.md
@@ -0,0 +1,1750 @@
+---
+layout: docs
+title: History
+permalink: "/docs/history/"
+prev_section: contributing
+---
+
+## 2.5.2 / 2014-11-17
+{: #v2-5-2}
+
+### Minor Enhancements
+{: #minor-enhancements-v2-5-2}
+
+- `post_url` should match `post.name` instead of slugs and dates ([#3058]({{ site.repository }}/issues/3058))
+
+### Bug Fixes
+{: #bug-fixes-v2-5-2}
+
+- Fix bundle require for `:jekyll_plugins` ([#3119]({{ site.repository }}/issues/3119))
+- Remove duplicate regexp phrase: `^\A` ([#3089]({{ site.repository }}/issues/3089))
+- Remove duplicate `Conversion error:` message in `Convertible` ([#3088]({{ site.repository }}/issues/3088))
+- Print full conversion error message in `Renderer#convert` ([#3090]({{ site.repository }}/issues/3090))
+
+### Site Enhancements
+{: #site-enhancements-v2-5-2}
+
+- Change variable names in Google Analytics script ([#3093]({{ site.repository }}/issues/3093))
+- Mention CSV files in the docs for data files ([#3101]({{ site.repository }}/issues/3101))
+- Add trailing slash to `paginate_path` example. ([#3091]({{ site.repository }}/issues/3091))
+- Get rid of noifniof (`excerpt_separator`) ([#3094]({{ site.repository }}/issues/3094))
+- Sass improvements, around nesting mostly. ([#3123]({{ site.repository }}/issues/3123))
+- Add webmentions.io plugin to the list of third-party plugins ([#3127]({{ site.repository }}/issues/3127))
+- Add Sass mixins and use them. ([#2904]({{ site.repository }}/issues/2904))
+- Slightly compress jekyll-sticker.jpg. ([#3133]({{ site.repository }}/issues/3133))
+- Update gridism and separate out related but custom styles. ([#3132]({{ site.repository }}/issues/3132))
+- Add remote-include plugin to list of third-party plugins ([#3136]({{ site.repository }}/issues/3136))
+
+
+## 2.5.1 / 2014-11-09
+{: #v2-5-1}
+
+### Bug Fixes
+{: #bug-fixes-v2-5-1}
+
+- Fix path sanitation bug related to Windows drive names ([#3077]({{ site.repository }}/issues/3077))
+
+### Development Fixes
+{: #development-fixes-v2-5-1}
+
+- Add development time dependencies on minitest and test-unit to gemspec for cygwin ([#3064]({{ site.repository }}/issues/3064))
+- Use Travis's built-in caching. ([#3075]({{ site.repository }}/issues/3075))
+
+
+## 2.5.0 / 2014-11-06
+{: #v2-5-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v2-5-0}
+
+- Require gems in `:jekyll_plugins` Gemfile group unless `JEKYLL_NO_BUNDLER_REQUIRE` is specified in the environment. ([#2865]({{ site.repository }}/issues/2865))
+- Centralize path sanitation in the `Site` object ([#2882]({{ site.repository }}/issues/2882))
+- Allow placeholders in permalinks ([#3031]({{ site.repository }}/issues/3031))
+- Allow users to specify the log level via `JEKYLL_LOG_LEVEL`. ([#3067]({{ site.repository }}/issues/3067))
+- Fancy Indexing with WEBrick ([#3018]({{ site.repository }}/issues/3018))
+- Allow Enumerables to be used with `where` filter. ([#2986]({{ site.repository }}/issues/2986))
+- Meta descriptions in the site template now use `page.excerpt` if it's available ([#2964]({{ site.repository }}/issues/2964))
+- Change indentation in `head.html` of site template to 2 spaces from 4 ([#2973]({{ site.repository }}/issues/2973))
+- Use a `$content-width` variable instead of a fixed value in the site template CSS ([#2972]({{ site.repository }}/issues/2972))
+- Strip newlines in site template `` description. ([#2982]({{ site.repository }}/issues/2982))
+- Add link to atom feed in `head` of site template files ([#2996]({{ site.repository }}/issues/2996))
+- Performance optimizations ([#2994]({{ site.repository }}/issues/2994))
+- Use `Hash#each_key` instead of `Hash#keys.each` to speed up iteration
+ over hash keys. ([#3017]({{ site.repository }}/issues/3017))
+- Further minor performance enhancements. ([#3022]({{ site.repository }}/issues/3022))
+- Add 'b' and 's' aliases for build and serve, respectively ([#3065]({{ site.repository }}/issues/3065))
+
+### Bug Fixes
+{: #bug-fixes-v2-5-0}
+
+- Fix Rouge's RedCarpet plugin interface integration ([#2951]({{ site.repository }}/issues/2951))
+- Remove `--watch` from the site template blog post since it defaults
+ to watching in in 2.4.0 ([#2922]({{ site.repository }}/issues/2922))
+- Fix code for media query mixin in site template ([#2946]({{ site.repository }}/issues/2946))
+- Allow post URL's to have `.htm` extensions ([#2925]({{ site.repository }}/issues/2925))
+- `Utils.slugify`: Don't create new objects when gsubbing ([#2997]({{ site.repository }}/issues/2997))
+- The jsonify filter should deep-convert to Liquid when given an Array. ([#3032]({{ site.repository }}/issues/3032))
+- Apply `jsonify` filter to Hashes deeply and effectively ([#3063]({{ site.repository }}/issues/3063))
+- Use `127.0.0.1` as default host instead of `0.0.0.0` ([#3053]({{ site.repository }}/issues/3053))
+- In the case that a Gemfile does not exist, ensure Jekyll doesn't fail on requiring the Gemfile group ([#3066]({{ site.repository }}/issues/3066))
+
+### Development Fixes
+{: #development-fixes-v2-5-0}
+
+- Fix a typo in the doc block for `Jekyll::URL.escape_path` ([#3052]({{ site.repository }}/issues/3052))
+- Add integration test for `jekyll new --blank` in TestUnit ([#2913]({{ site.repository }}/issues/2913))
+- Add unit test for `jekyll new --force` logic ([#2929]({{ site.repository }}/issues/2929))
+- Update outdated comment for `Convertible#transform` ([#2957]({{ site.repository }}/issues/2957))
+- Add Hakiri badge to README. ([#2953]({{ site.repository }}/issues/2953))
+- Add some simple benchmarking tools. ([#2993]({{ site.repository }}/issues/2993))
+
+### Site Enhancements
+{: #site-enhancements-v2-5-0}
+
+- `NOKOGIRI_USE_SYSTEM_LIBRARIES=true` **decreases** installation time. ([#3040]({{ site.repository }}/issues/3040))
+- Add FormKeep to resources as Jekyll form backend ([#3010]({{ site.repository }}/issues/3010))
+- Fixing a mistake in the name of the new Liquid tag ([#2969]({{ site.repository }}/issues/2969))
+- Update Font Awesome to v4.2.0. ([#2898]({{ site.repository }}/issues/2898))
+- Fix link to [#2895]({{ site.repository }}/issues/2895) in 2.4.0 release post. ([#2899]({{ site.repository }}/issues/2899))
+- Add Big Footnotes for Kramdown plugin to list of third-party plugins ([#2916]({{ site.repository }}/issues/2916))
+- Remove warning regarding GHP use of singular types for front matter defaults ([#2919]({{ site.repository }}/issues/2919))
+- Fix quote character typo in site documentation for templates ([#2917]({{ site.repository }}/issues/2917))
+- Point Liquid links to Liquid’s Github wiki ([#2887]({{ site.repository }}/issues/2887))
+- Add HTTP Basic Auth (.htaccess) plugin to list of third-party plugins ([#2931]({{ site.repository }}/issues/2931))
+- (Minor) Grammar & `_config.yml` filename fixes ([#2911]({{ site.repository }}/issues/2911))
+- Added `mathml.rb` to the list of third-party plugins. ([#2937]({{ site.repository }}/issues/2937))
+- Add `--force_polling` to the list of configuration options ([#2943]({{ site.repository }}/issues/2943))
+- Escape unicode characters in site CSS ([#2906]({{ site.repository }}/issues/2906))
+- Add note about using the github-pages gem via pages.github.com/versions.json ([#2939]({{ site.repository }}/issues/2939))
+- Update usage documentation to reflect 2.4 auto-enabling of `--watch`. ([#2954]({{ site.repository }}/issues/2954))
+- Add `--skip-initial-build` to configuration docs ([#2949]({{ site.repository }}/issues/2949))
+- Fix a minor typo in Templates docs page ([#2959]({{ site.repository }}/issues/2959))
+- Add a ditaa-ditaa plugin under Other section on the Plugins page ([#2967]({{ site.repository }}/issues/2967))
+- Add `build/serve -V` option to configuration documentation ([#2948]({{ site.repository }}/issues/2948))
+- Add 'Jekyll Twitter Plugin' to list of third-party plugins ([#2979]({{ site.repository }}/issues/2979))
+- Docs: Update normalize.css to v3.0.2. ([#2981]({{ site.repository }}/issues/2981))
+- Fix typo in Continuous Integration documentation ([#2984]({{ site.repository }}/issues/2984))
+- Clarify behavior of `:categories` in permalinks ([#3011]({{ site.repository }}/issues/3011))
+
+
+## 2.4.0 / 2014-09-09
+{: #v2-4-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v2-4-0}
+
+- Support a new `relative_include` tag ([#2870]({{ site.repository }}/issues/2870))
+- Auto-enable watch on 'serve' ([#2858]({{ site.repository }}/issues/2858))
+- Render Liquid in CoffeeScript files ([#2830]({{ site.repository }}/issues/2830))
+- Array Liquid filters: `push`, `pop`, `unshift`, `shift` ([#2895]({{ site.repository }}/issues/2895))
+- Add `:title` to collection URL template fillers ([#2864]({{ site.repository }}/issues/2864))
+- Add support for CSV files in the `_data` directory ([#2761]({{ site.repository }}/issues/2761))
+- Add the `name` variable to collection permalinks ([#2799]({{ site.repository }}/issues/2799))
+- Add `inspect` liquid filter. ([#2867]({{ site.repository }}/issues/2867))
+- Add a `slugify` Liquid filter ([#2880]({{ site.repository }}/issues/2880))
+
+### Bug Fixes
+{: #bug-fixes-v2-4-0}
+
+- Use `Jekyll.sanitized_path` when adding static files to Collections ([#2849]({{ site.repository }}/issues/2849))
+- Fix encoding of `main.scss` in site template ([#2771]({{ site.repository }}/issues/2771))
+- Fix orientation bugs in default site template ([#2862]({{ site.repository }}/issues/2862))
+
+### Development Fixes
+{: #development-fixes-v2-4-0}
+
+- Update simplecov gem to 0.9 ([#2748]({{ site.repository }}/issues/2748))
+- Remove `docs/` dir ([#2768]({{ site.repository }}/issues/2768))
+- add class `<< self` idiom to `New` command ([#2817]({{ site.repository }}/issues/2817))
+- Allow Travis to 'parallelize' our tests ([#2859]({{ site.repository }}/issues/2859))
+- Fix test for Liquid rendering in Sass ([#2856]({{ site.repository }}/issues/2856))
+- Fixing "vertycal" typo in site template's `_base.scss` ([#2889]({{ site.repository }}/issues/2889))
+
+### Site Enhancements
+{: #site-enhancements-v2-4-0}
+
+- Document the `name` variable for collection permalinks ([#2829]({{ site.repository }}/issues/2829))
+- Adds info about installing jekyll in current dir ([#2839]({{ site.repository }}/issues/2839))
+- Remove deprecated `jekyll-projectlist` plugin from list of third-party
+ plugins ([#2742]({{ site.repository }}/issues/2742))
+- Remove tag plugins that are built in to Jekyll ([#2751]({{ site.repository }}/issues/2751))
+- Add `markdown-writer` package for Atom Editor to list of third-party
+ plugins ([#2763]({{ site.repository }}/issues/2763))
+- Fix typo in site documentation for collections ([#2764]({{ site.repository }}/issues/2764))
+- Fix minor typo on plugins docs page ([#2765]({{ site.repository }}/issues/2765))
+- Replace markdown with HTML in `sass_dir` note on assets page ([#2791]({{ site.repository }}/issues/2791))
+- Fixed "bellow" typo in datafiles docs ([#2879]({{ site.repository }}/issues/2879))
+- Fix code/markdown issue in documentation for variables ([#2877]({{ site.repository }}/issues/2877))
+- Remove Good Include third-party plugin from plugins page ([#2881]({{ site.repository }}/issues/2881))
+- Add some more docs on `include_relative` ([#2884]({{ site.repository }}/issues/2884))
+
+
+## 2.3.0 / 2014-08-10
+{: #v2-3-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v2-3-0}
+
+- Allow Convertibles to be converted by >= 1 converters ([#2704]({{ site.repository }}/issues/2704))
+- Allow Sass files to be rendered in Liquid, but never place them in layouts. ([#2733]({{ site.repository }}/issues/2733))
+- Add `jekyll help` command ([#2707]({{ site.repository }}/issues/2707))
+- Use `.scss` for `site_template` styles. ([#2667]({{ site.repository }}/issues/2667))
+- Don't require the `scope` key in front matter defaults ([#2659]({{ site.repository }}/issues/2659))
+- No longer set `permalink: pretty` in the `_config.yml` for the site template ([#2680]({{ site.repository }}/issues/2680))
+- Rework site template to utilize Sass ([#2687]({{ site.repository }}/issues/2687))
+- Notify the user when auto-regeneration is disabled. ([#2696]({{ site.repository }}/issues/2696))
+- Allow partial variables in include tag filename argument ([#2693]({{ site.repository }}/issues/2693))
+- Move instances of `Time.parse` into a Utils method ([#2682]({{ site.repository }}/issues/2682))
+- Ignore subfolders in the `_posts` folder ([#2705]({{ site.repository }}/issues/2705)) REVERTS ([#2633]({{ site.repository }}/issues/2633))
+- Front Matter default types should always be pluralized ([#2732]({{ site.repository }}/issues/2732))
+- Read in static files into `collection.files` as `StaticFile`s ([#2737]({{ site.repository }}/issues/2737))
+- Add `sassify` and `scssify` Liquid filters ([#2739]({{ site.repository }}/issues/2739))
+- Replace `classifier` gem with `classifier-reborn` ([#2721]({{ site.repository }}/issues/2721))
+
+### Bug Fixes
+{: #bug-fixes-v2-3-0}
+
+- Use only the last extname when multiple converters exist ([#2722]({{ site.repository }}/issues/2722))
+- Call `#to_liquid` before calling `#to_json` in jsonify filter ([#2729]({{ site.repository }}/issues/2729))
+- Use non padded config in `strftime` to avoid parse string twice ([#2673]({{ site.repository }}/issues/2673))
+- Replace deprecated Ruby methods with undeprecated ones ([#2664]({{ site.repository }}/issues/2664))
+- Catch errors when parsing Post `date` front matter value & produce nice error message ([#2649]({{ site.repository }}/issues/2649))
+- Allow static files in Collections ([#2615]({{ site.repository }}/issues/2615))
+- Fixed typo in `Deprecator#gracefully_require` error message ([#2694]({{ site.repository }}/issues/2694))
+- Remove preemptive loading of the 'classifier' gem. ([#2697]({{ site.repository }}/issues/2697))
+- Use case-insensitive checking for the file extensions when loading config files ([#2718]({{ site.repository }}/issues/2718))
+- When Reading Documents, Respect `encoding` Option ([#2720]({{ site.repository }}/issues/2720))
+- Refactor based on jekyll-watch clean-up. ([#2716]({{ site.repository }}/issues/2716))
+- `Document#to_s` should produce just the content of the document ([#2731]({{ site.repository }}/issues/2731))
+
+### Development Fixes
+{: #development-fixes-v2-3-0}
+
+- Only include lib files in the gem ([#2671]({{ site.repository }}/issues/2671))
+- Fix `git diff` command in `proof` script ([#2672]({{ site.repository }}/issues/2672))
+- Make default rake task a multitask so tests run in parallel ([#2735]({{ site.repository }}/issues/2735))
+
+### Site Enhancements
+{: #site-enhancements-v2-3-0}
+
+- Use Sass and a Docs Collection ([#2651]({{ site.repository }}/issues/2651))
+- Add `latest_version.txt` file to the site ([#2740]({{ site.repository }}/issues/2740))
+- Be more ambiguous about `page.content`. But more transparent. ([#2522]({{ site.repository }}/issues/2522))
+- Streamlining front matter wording (instead of front-matter/frontmatter) ([#2674]({{ site.repository }}/issues/2674))
+- Add note that source directory cannot be modified in GitHub Pages ([#2669]({{ site.repository }}/issues/2669))
+- Fix links from [#2669]({{ site.repository }}/issues/2669) to be actual HTML. Whoops. ([#2679]({{ site.repository }}/issues/2679))
+- Add link to `jekyll-slim` in list of third-party plugins ([#2689]({{ site.repository }}/issues/2689))
+- Add Barry Clark's Smashing Magazine tutorial to resources page ([#2688]({{ site.repository }}/issues/2688))
+- Reorganize and update default configuration settings ([#2456]({{ site.repository }}/issues/2456))
+- Fixing indentation in the configuration docs about Redcarpet exts ([#2717]({{ site.repository }}/issues/2717))
+- Use `null` in YAML instead of `nil` in default config list ([#2719]({{ site.repository }}/issues/2719))
+- Fix typo in Continuous Integration docs ([#2708]({{ site.repository }}/issues/2708))
+
+
+## 2.2.0 / 2014-07-29
+{: #v2-2-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v2-2-0}
+
+- Throw a warning if the specified layout does not exist ([#2620]({{ site.repository }}/issues/2620))
+- Whitelist Pygments options in safe mode ([#2642]({{ site.repository }}/issues/2642))
+
+### Bug Fixes
+{: #bug-fixes-v2-2-0}
+
+- Remove unnecessary `Jekyll::Tags::IncludeTag#blank?` method ([#2625]({{ site.repository }}/issues/2625))
+- Categories in the path are ignored ([#2633]({{ site.repository }}/issues/2633))
+
+### Development Fixes
+{: #development-fixes-v2-2-0}
+
+- Refactoring Errors & Requires of Third-Party stuff ([#2591]({{ site.repository }}/issues/2591))
+- Add further tests for categories ([#2584]({{ site.repository }}/issues/2584))
+- Proof site with html-proofer on change ([#2605]({{ site.repository }}/issues/2605))
+- Fix up bug in [#2605]({{ site.repository }}/issues/2605) which caused proofing the site not to function ([#2608]({{ site.repository }}/issues/2608))
+- Use `bundle exec` in `script/proof` ([#2610]({{ site.repository }}/issues/2610))
+
+### Site Enhancements
+{: #site-enhancements-v2-2-0}
+
+- Update Kramdown urls ([#2588]({{ site.repository }}/issues/2588))
+- Add `Jekyll::AutolinkEmail` and `Jekyll::GitMetadata` to the list of
+ third-party plugins ([#2596]({{ site.repository }}/issues/2596))
+- Fix a bunch of broken links in the site ([#2601]({{ site.repository }}/issues/2601))
+- Replace dead links with working links ([#2611]({{ site.repository }}/issues/2611))
+- Add jekyll-hook to deployment methods ([#2617]({{ site.repository }}/issues/2617))
+- Added kramdown-with-pygments plugin to the list of third-party plugins ([#2623]({{ site.repository }}/issues/2623))
+- Update outdated "Extras" page and remove duplicate documentation ([#2622]({{ site.repository }}/issues/2622))
+- Add co2 plugin to list of third-party plugins ([#2639]({{ site.repository }}/issues/2639))
+- Attempt to clarify the way Sass imports happen ([#2642]({{ site.repository }}/issues/2642))
+
+
+## 2.1.1 / 2014-07-01
+{: #v2-1-1}
+
+### Bug Fixes
+{: #bug-fixes-v2-1-1}
+
+- Patch read vulnerabilities for data & confirm none for layouts ([#2563]({{ site.repository }}/issues/2563))
+- Update Maruku dependency to allow use of the latest version ([#2576]({{ site.repository }}/issues/2576))
+- Remove conditional assignment from document URL to prevent stale urls ([#2575]({{ site.repository }}/issues/2575))
+
+### Site Enhancements
+{: #site-enhancements-v2-1-1}
+
+- Add vertical margin to `highlight` to separate code blocks ([#2558]({{ site.repository }}/issues/2558))
+- Add `html_pages` to Variables docs ([#2567]({{ site.repository }}/issues/2567))
+- Fixed broken link to Permalinks page ([#2572]({{ site.repository }}/issues/2572))
+- Update link to Windows installation guide ([#2578]({{ site.repository }}/issues/2578))
+
+
+## 2.1.0 / 2014-06-28
+{: #v2-1-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v2-1-0}
+
+- Bump to the latest Liquid version, 2.6.1 ([#2495]({{ site.repository }}/issues/2495))
+- Add support for JSON files in the `_data` directory ([#2369]({{ site.repository }}/issues/2369))
+- Allow subclasses to override `EXCERPT_ATTRIBUTES_FOR_LIQUID` ([#2408]({{ site.repository }}/issues/2408))
+- Add `Jekyll.env` and `jekyll.environment` (the Liquid var) ([#2417]({{ site.repository }}/issues/2417))
+- Use `_config.yaml` or `_config.yml` (`.yml` takes precedence) ([#2406]({{ site.repository }}/issues/2406))
+- Override collection url template ([#2418]({{ site.repository }}/issues/2418))
+- Allow subdirectories in `_data` ([#2395]({{ site.repository }}/issues/2395))
+- Extract Pagination Generator into gem: `jekyll-paginate` ([#2455]({{ site.repository }}/issues/2455))
+- Utilize `date_to_rfc822` filter in site template ([#2437]({{ site.repository }}/issues/2437))
+- Add categories, last build datetime, and generator to site template
+ feed ([#2438]({{ site.repository }}/issues/2438))
+- Configurable, replaceable Logger-compliant logger ([#2444]({{ site.repository }}/issues/2444))
+- Extract `gist` tag into a separate gem ([#2469]({{ site.repository }}/issues/2469))
+- Add `collection` attribute to `Document#to_liquid` to access the
+ document's collection label. ([#2436]({{ site.repository }}/issues/2436))
+- Upgrade listen to `2.7.6 <= x < 3.0.0` ([#2492]({{ site.repository }}/issues/2492))
+- Allow configuration of different Twitter and GitHub usernames in site template ([#2485]({{ site.repository }}/issues/2485))
+- Bump Pygments to v0.6.0 ([#2504]({{ site.repository }}/issues/2504))
+- Front matter defaults for documents in collections ([#2419]({{ site.repository }}/issues/2419))
+- Include files with a url which ends in `/` in the `site.html_pages` list ([#2524]({{ site.repository }}/issues/2524))
+- Make `highlight` tag use `language-` prefix in CSS class ([#2511]({{ site.repository }}/issues/2511))
+- Lookup item property via `item#to_liquid` before `#data` or `#[]` in filters ([#2493]({{ site.repository }}/issues/2493))
+- Skip initial build of site on serve with flag ([#2477]({{ site.repository }}/issues/2477))
+- Add support for `hl_lines` in `highlight` tag ([#2532]({{ site.repository }}/issues/2532))
+- Spike out `--watch` flag into a separate gem ([#2550]({{ site.repository }}/issues/2550))
+
+### Bug Fixes
+{: #bug-fixes-v2-1-0}
+
+- Liquid `sort` filter should sort even if one of the values is `nil` ([#2345]({{ site.repository }}/issues/2345))
+- Remove padding on `pre code` in the site template CSS ([#2383]({{ site.repository }}/issues/2383))
+- Set `log_level` earlier to silence info level configuration output ([#2393]({{ site.repository }}/issues/2393))
+- Only list pages which have `title` in site template ([#2411]({{ site.repository }}/issues/2411))
+- Accept `Numeric` values for dates, not `Number` values ([#2377]({{ site.repository }}/issues/2377))
+- Prevent code from overflowing container in site template ([#2429]({{ site.repository }}/issues/2429))
+- Encode URLs in UTF-8 when escaping and unescaping ([#2420]({{ site.repository }}/issues/2420))
+- No Layouts or Liquid for Asset Files ([#2431]({{ site.repository }}/issues/2431))
+- Allow front matter defaults to set post categories ([#2373]({{ site.repository }}/issues/2373))
+- Fix command in subcommand deprecation warning ([#2457]({{ site.repository }}/issues/2457))
+- Keep all parent directories of files/dirs in `keep_files` ([#2458]({{ site.repository }}/issues/2458))
+- When using RedCarpet and Rouge without Rouge installed, fixed erroneous
+ error which stated that redcarpet was missing, not rouge. ([#2464]({{ site.repository }}/issues/2464))
+- Ignore *all* directories and files that merit it on auto-generation ([#2459]({{ site.repository }}/issues/2459))
+- Before copying file, explicitly remove the old one ([#2535]({{ site.repository }}/issues/2535))
+- Merge file system categories with categories from YAML. ([#2531]({{ site.repository }}/issues/2531))
+- Deep merge front matter defaults ([#2490]({{ site.repository }}/issues/2490))
+- Ensure exclude and include arrays are arrays of strings ([#2542]({{ site.repository }}/issues/2542))
+- Allow collections to have dots in their filenames ([#2552]({{ site.repository }}/issues/2552))
+- Collections shouldn't try to read in directories as files ([#2552]({{ site.repository }}/issues/2552))
+- Be quiet very quickly. ([#2520]({{ site.repository }}/issues/2520))
+
+### Development Fixes
+{: #development-fixes-v2-1-0}
+
+- Test Ruby 2.1.2 instead of 2.1.1 ([#2374]({{ site.repository }}/issues/2374))
+- Add test for sorting UTF-8 characters ([#2384]({{ site.repository }}/issues/2384))
+- Use `https` for GitHub links in documentation ([#2470]({{ site.repository }}/issues/2470))
+- Remove coverage reporting with Coveralls ([#2494]({{ site.repository }}/issues/2494))
+- Fix a bit of missing TomDoc to `Jekyll::Commands::Build#build` ([#2554]({{ site.repository }}/issues/2554))
+
+### Site Enhancements
+{: #site-enhancements-v2-1-0}
+
+- Set `timezone` to `America/Los_Angeles` ([#2394]({{ site.repository }}/issues/2394))
+- Improve JavaScript in `anchor_links.html` ([#2368]({{ site.repository }}/issues/2368))
+- Remove note on Quickstart page about default markdown converter ([#2387]({{ site.repository }}/issues/2387))
+- Remove broken link in extras.md to a Maruku fork ([#2401]({{ site.repository }}/issues/2401))
+- Update Font Awesome to v4.1.0. ([#2410]({{ site.repository }}/issues/2410))
+- Fix broken link on Installation page to Templates page ([#2421]({{ site.repository }}/issues/2421))
+- Prevent table from extending parent width in permalink style table ([#2424]({{ site.repository }}/issues/2424))
+- Add collections to info about pagination support ([#2389]({{ site.repository }}/issues/2389))
+- Add `jekyll_github_sample` plugin to list of third-party plugins ([#2463]({{ site.repository }}/issues/2463))
+- Clarify documentation around front matter defaults and add details
+ about defaults for collections. ([#2439]({{ site.repository }}/issues/2439))
+- Add Jekyll Project Version Tag to list of third-party plugins ([#2468]({{ site.repository }}/issues/2468))
+- Use `https` for GitHub links across whole site ([#2470]({{ site.repository }}/issues/2470))
+- Add StickerMule + Jekyll post ([#2476]({{ site.repository }}/issues/2476))
+- Add Jekyll Asset Pipeline Reborn to list of third-party plugins ([#2479]({{ site.repository }}/issues/2479))
+- Add link to jekyll-compress-html to list of third-party plugins ([#2514]({{ site.repository }}/issues/2514))
+- Add Piwigo Gallery to list of third-party plugins ([#2526]({{ site.repository }}/issues/2526))
+- Set `show_drafts` to `false` in default configuration listing ([#2536]({{ site.repository }}/issues/2536))
+- Provide an updated link for Windows installation instructions ([#2544]({{ site.repository }}/issues/2544))
+- Remove `url` from configuration docs ([#2547]({{ site.repository }}/issues/2547))
+- Documentation for Continuous Integration for your Jekyll Site ([#2432]({{ site.repository }}/issues/2432))
+
+
+## 2.0.3 / 2014-05-08
+{: #v2-0-3}
+
+### Bug Fixes
+{: #bug-fixes-v2-0-3}
+
+- Properly prefix links in site template with URL or baseurl depending upon
+ need. ([#2319]({{ site.repository }}/issues/2319))
+- Update gist tag comments and error message to require username ([#2326]({{ site.repository }}/issues/2326))
+- Fix `permalink` setting in site template ([#2331]({{ site.repository }}/issues/2331))
+- Don't fail if any of the path objects are nil ([#2325]({{ site.repository }}/issues/2325))
+- Instantiate all descendants for converters and generators, not just
+ direct subclasses ([#2334]({{ site.repository }}/issues/2334))
+- Replace all instances of `site.name` with `site.title` in site template ([#2324]({{ site.repository }}/issues/2324))
+- `Jekyll::Filters#time` now accepts UNIX timestamps in string or number form ([#2339]({{ site.repository }}/issues/2339))
+- Use `item_property` for `where` filter so it doesn't break on collections ([#2359]({{ site.repository }}/issues/2359))
+- Rescue errors thrown so `--watch` doesn't fail ([#2364]({{ site.repository }}/issues/2364))
+
+### Site Enhancements
+{: #site-enhancements-v2-0-3}
+
+- Add missing "as" to assets docs page ([#2337]({{ site.repository }}/issues/2337))
+- Update docs to reflect new `baseurl` default ([#2341]({{ site.repository }}/issues/2341))
+- Add links to headers who have an ID. ([#2342]({{ site.repository }}/issues/2342))
+- Use symbol instead of HTML number in `upgrading.md` ([#2351]({{ site.repository }}/issues/2351))
+- Fix link to front matter defaults docs ([#2353]({{ site.repository }}/issues/2353))
+- Fix for `History.markdown` in order to fix history page in docs ([#2363]({{ site.repository }}/issues/2363))
+
+
+## 2.0.2 / 2014-05-07
+{: #v2-0-2}
+
+### Bug Fixes
+{: #bug-fixes-v2-0-2}
+
+- Correct use of `url` and `baseurl` in the site template. ([#2317]({{ site.repository }}/issues/2317))
+- Default `baseurl` to `""` ([#2317]({{ site.repository }}/issues/2317))
+
+### Site Enhancements
+{: #site-enhancements-v2-0-2}
+
+- Correct docs for the `gist` plugin so it always includes the username. ([#2314]({{ site.repository }}/issues/2314))
+- Clarify new (defaults, `where` filter) features in docs ([#2316]({{ site.repository }}/issues/2316))
+
+
+## 2.0.1 / 2014-05-06
+{: #v2-0-1}
+
+### Bug Fixes
+{: #bug-fixes-v2-0-1}
+
+- Require `kramdown` gem instead of `maruku` gem
+
+
+## 2.0.0 / 2014-05-06
+{: #v2-0-0}
+
+### Major Enhancements
+{: #major-enhancements-v2-0-0}
+- Add "Collections" feature ([#2199]({{ site.repository }}/issues/2199))
+- Add gem-based plugin whitelist to safe mode ([#1657]({{ site.repository }}/issues/1657))
+- Replace the commander command line parser with a more robust
+ solution for our needs called `mercenary` ([#1706]({{ site.repository }}/issues/1706))
+- Remove support for Ruby 1.8.x ([#1780]({{ site.repository }}/issues/1780))
+- Move to jekyll/jekyll from mojombo/jekyll ([#1817]({{ site.repository }}/issues/1817))
+- Allow custom markdown processors ([#1872]({{ site.repository }}/issues/1872))
+- Provide support for the Rouge syntax highlighter ([#1859]({{ site.repository }}/issues/1859))
+- Provide support for Sass ([#1932]({{ site.repository }}/issues/1932))
+- Provide a 300% improvement when generating sites that use
+ `Post#next` or `Post#previous` ([#1983]({{ site.repository }}/issues/1983))
+- Provide support for CoffeeScript ([#1991]({{ site.repository }}/issues/1991))
+- Replace Maruku with Kramdown as Default Markdown Processor ([#1988]({{ site.repository }}/issues/1988))
+- Expose `site.static_files` to Liquid ([#2075]({{ site.repository }}/issues/2075))
+- Complete redesign of the template site generated by `jekyll new` ([#2050]({{ site.repository }}/issues/2050))
+- Update Listen from 1.x to 2.x ([#2097]({{ site.repository }}/issues/2097))
+- Front matter defaults ([#2205]({{ site.repository }}/issues/2205))
+- Deprecate `relative_permalinks` configuration option (default to `false`) ([#2307]({{ site.repository }}/issues/2307))
+- Exclude files based on prefix as well as `fnmatch?` ([#2303]({{ site.repository }}/issues/2303))
+
+### Minor Enhancements
+{: #minor-enhancements-v2-0-0}
+- Move the EntryFilter class into the Jekyll module to avoid polluting the
+ global namespace ([#1800]({{ site.repository }}/issues/1800))
+- Add `group_by` Liquid filter create lists of items grouped by a common
+ property's value ([#1788]({{ site.repository }}/issues/1788))
+- Add support for Maruku's `fenced_code_blocks` option ([#1799]({{ site.repository }}/issues/1799))
+- Update Redcarpet dependency to ~> 3.0 ([#1815]({{ site.repository }}/issues/1815))
+- Automatically sort all pages by name ([#1848]({{ site.repository }}/issues/1848))
+- Better error message when time is not parseable ([#1847]({{ site.repository }}/issues/1847))
+- Allow `include` tag variable arguments to use filters ([#1841]({{ site.repository }}/issues/1841))
+- `post_url` tag should raise `ArgumentError` for invalid name ([#1825]({{ site.repository }}/issues/1825))
+- Bump dependency `mercenary` to `~> 0.2.0` ([#1879]({{ site.repository }}/issues/1879))
+- Bump dependency `safe_yaml` to `~> 1.0` ([#1886]({{ site.repository }}/issues/1886))
+- Allow sorting of content by custom properties ([#1849]({{ site.repository }}/issues/1849))
+- Add `--quiet` flag to silence output during build and serve ([#1898]({{ site.repository }}/issues/1898))
+- Add a `where` filter to filter arrays based on a key/value pair
+ ([#1875]({{ site.repository }}/issues/1875))
+- Route 404 errors to a custom 404 page in development ([#1899]({{ site.repository }}/issues/1899))
+- Excludes are now relative to the site source ([#1916]({{ site.repository }}/issues/1916))
+- Bring MIME Types file for `jekyll serve` to complete parity with GH Pages
+ servers ([#1993]({{ site.repository }}/issues/1993))
+- Adding Breakpoint to make new site template more responsive ([#2038]({{ site.repository }}/issues/2038))
+- Default to using the UTF-8 encoding when reading files. ([#2031]({{ site.repository }}/issues/2031))
+- Update Redcarpet dependency to ~> 3.1 ([#2044]({{ site.repository }}/issues/2044))
+- Remove support for Ruby 1.9.2 ([#2045]({{ site.repository }}/issues/2045))
+- Add `.mkdown` as valid Markdown extension ([#2048]({{ site.repository }}/issues/2048))
+- Add `index.xml` to the list of WEBrick directory index files ([#2041]({{ site.repository }}/issues/2041))
+- Make the `layouts` config key relative to CWD or to source ([#2058]({{ site.repository }}/issues/2058))
+- Update Kramdown to `~> 1.3` ([#1894]({{ site.repository }}/issues/1894))
+- Remove unnecessary references to `self` ([#2090]({{ site.repository }}/issues/2090))
+- Update to Mercenary v0.3.x ([#2085]({{ site.repository }}/issues/2085))
+- Ship Sass support as a separate gem ([#2098]({{ site.repository }}/issues/2098))
+- Extract core extensions into a Utils module ([#2112]({{ site.repository }}/issues/2112))
+- Refactor CLI & Commands For Greater Happiness ([#2143]({{ site.repository }}/issues/2143))
+- Provide useful error when Pygments returns `nil` and error out ([#2148]({{ site.repository }}/issues/2148))
+- Add support for unpublished drafts ([#2164]({{ site.repository }}/issues/2164))
+- Add `force_polling` option to the `serve` command ([#2165]({{ site.repository }}/issues/2165))
+- Clean up the `` in the site template ([#2186]({{ site.repository }}/issues/2186))
+- Permit YAML blocks to end with three dots to better conform with the
+ YAML spec ([#2110]({{ site.repository }}/issues/2110))
+- Use `File.exist?` instead of deprecated `File.exists?` ([#2214]({{ site.repository }}/issues/2214))
+- Require newline after start of YAML Front Matter header ([#2211]({{ site.repository }}/issues/2211))
+- Add the ability for pages to be marked as `published: false` ([#1492]({{ site.repository }}/issues/1492))
+- Add `Jekyll::LiquidExtensions` with `.lookup_variable` method for easy
+ looking up of variable values in a Liquid context. ([#2253]({{ site.repository }}/issues/2253))
+- Remove literal lang name from class ([#2292]({{ site.repository }}/issues/2292))
+- Return `utf-8` encoding in header for webrick error page response ([#2289]({{ site.repository }}/issues/2289))
+- Make template site easier to customize ([#2268]({{ site.repository }}/issues/2268))
+- Add two-digit year to permalink template option ([#2301]({{ site.repository }}/issues/2301))
+- Add `site.documents` to Liquid payload (list of all docs) ([#2295]({{ site.repository }}/issues/2295))
+- Take into account missing values in the Liquid sort filter ([#2299]({{ site.repository }}/issues/2299))
+
+### Bug Fixes
+{: #bug-fixes-v2-0-0}
+- Don't allow nil entries when loading posts ([#1796]({{ site.repository }}/issues/1796))
+- Remove the scrollbar that's always displayed in new sites generated
+ from the site template ([#1805]({{ site.repository }}/issues/1805))
+- Add `#path` to required methods in `Jekyll::Convertible` ([#1866]({{ site.repository }}/issues/1866))
+- Default Maruku fenced code blocks to ON for 2.0.0-dev ([#1831]({{ site.repository }}/issues/1831))
+- Change short opts for host and port for `jekyll docs` to be consistent with
+ other subcommands ([#1877]({{ site.repository }}/issues/1877))
+- Fix typos ([#1910]({{ site.repository }}/issues/1910))
+- Lock Maruku at 0.7.0 to prevent bugs caused by Maruku 0.7.1 ([#1958]({{ site.repository }}/issues/1958))
+- Fixes full path leak to source directory when using include tag ([#1951]({{ site.repository }}/issues/1951))
+- Don't generate pages that aren't being published ([#1931]({{ site.repository }}/issues/1931))
+- Use `SafeYAML.load` to avoid conflicts with other projects ([#1982]({{ site.repository }}/issues/1982))
+- Relative posts should never fail to build ([#1976]({{ site.repository }}/issues/1976))
+- Remove executable bits of non executable files ([#2056]({{ site.repository }}/issues/2056))
+- `#path` for a draft is now `_drafts` instead of `_posts` ([#2042]({{ site.repository }}/issues/2042))
+- Patch a couple show-stopping security vulnerabilities ([#1946]({{ site.repository }}/issues/1946))
+- Sanitize paths uniformly, in a Windows-friendly way ([#2065]({{ site.repository }}/issues/2065), [#2109]({{ site.repository }}/issues/2109))
+- Update gem build steps to work correctly on Windows ([#2118]({{ site.repository }}/issues/2118))
+- Remove obsolete `normalize_options` method call from `bin/jekyll` ([#2121]({{ site.repository }}/issues/2121)).
+- Remove `+` characters from Pygments lexer names when adding as a CSS
+ class ([#994]({{ site.repository }}/issues/994))
+- Remove some code that caused Ruby interpreter warnings ([#2178]({{ site.repository }}/issues/2178))
+- Only strip the drive name if it begins the string ([#2175]({{ site.repository }}/issues/2175))
+- Remove default post with invalid date from site template ([#2200]({{ site.repository }}/issues/2200))
+- Fix `Post#url` and `Page#url` escape ([#1568]({{ site.repository }}/issues/1568))
+- Strip newlines from the {% raw %}`{% highlight %}`{% endraw %} block content ([#1823]({{ site.repository }}/issues/1823))
+- Load in `rouge` only when it's been requested as the highlighter ([#2189]({{ site.repository }}/issues/2189))
+- Convert input to string before XML escaping (`xml_escape` liquid filter) ([#2244]({{ site.repository }}/issues/2244))
+- Modify configuration key for Collections and reset properly. ([#2238]({{ site.repository }}/issues/2238))
+- Avoid duplicated output using `highlight` tag ([#2264]({{ site.repository }}/issues/2264))
+- Only use Jekyll.logger for output ([#2307]({{ site.repository }}/issues/2307))
+- Close the file descriptor in `has_yaml_header?` ([#2310]({{ site.repository }}/issues/2310))
+- Add `output` to `Document` liquid output hash ([#2309]({{ site.repository }}/issues/2309))
+
+### Development Fixes
+{: #development-fixes-v2-0-0}
+- Add a link to the site in the README.md file ([#1795]({{ site.repository }}/issues/1795))
+- Add in History and site changes from `v1-stable` branch ([#1836]({{ site.repository }}/issues/1836))
+- Testing additions on the Excerpt class ([#1893]({{ site.repository }}/issues/1893))
+- Fix the `highlight` tag feature ([#1859]({{ site.repository }}/issues/1859))
+- Test Jekyll under Ruby 2.1.0 ([#1900]({{ site.repository }}/issues/1900))
+- Add script/cibuild for fun and profit ([#1912]({{ site.repository }}/issues/1912))
+- Use `Forwardable` for delegation between `Excerpt` and `Post`
+ ([#1927]({{ site.repository }}/issues/1927))
+- Rename `read_things` to `read_content` ([#1928]({{ site.repository }}/issues/1928))
+- Add `script/branding` script for ASCII art lovin' ([#1936]({{ site.repository }}/issues/1936))
+- Update the README to reflect the repo move ([#1943]({{ site.repository }}/issues/1943))
+- Add the project vision to the README ([#1935]({{ site.repository }}/issues/1935))
+- Speed up Travis CI builds by using Rebund ([#1985]({{ site.repository }}/issues/1985))
+- Use Yarp as a Gem proxy for Travis CI ([#1984]({{ site.repository }}/issues/1984))
+- Remove Yarp as a Gem proxy for Travis CI ([#2004]({{ site.repository }}/issues/2004))
+- Move the reading of layouts into its own class ([#2020]({{ site.repository }}/issues/2020))
+- Test Sass import ([#2009]({{ site.repository }}/issues/2009))
+- Switch Maruku and Kramdown in lists of Runtime vs. Development dependencies ([#2049]({{ site.repository }}/issues/2049))
+- Clean up the gemspec for the project ([#2095]({{ site.repository }}/issues/2095))
+- Add Japanese translation of README and CONTRIBUTING docs. ([#2081]({{ site.repository }}/issues/2081))
+- Re-align the tables in Cucumber ([#2108]({{ site.repository }}/issues/2108))
+- Trim trailing spaces and convert tabs to spaces ([#2122]({{ site.repository }}/issues/2122))
+- Fix the failing Travis scenarios due to Cucumber issues ([#2155]({{ site.repository }}/issues/2155))
+- Wrap `bundle install` in `travis_retry` to retry when RubyGems fails ([#2160]({{ site.repository }}/issues/2160))
+- Refactor tags and categories ([#1639]({{ site.repository }}/issues/1639))
+- Extract plugin management into its own class ([#2197]({{ site.repository }}/issues/2197))
+- Add missing tests for `Command` ([#2216]({{ site.repository }}/issues/2216))
+- Update `rr` link in CONTRIBUTING doc ([#2247]({{ site.repository }}/issues/2247))
+- Streamline Cucumber execution of `jekyll` subcommands ([#2258]({{ site.repository }}/issues/2258))
+- Refactor `Commands::Serve`. ([#2269]({{ site.repository }}/issues/2269))
+- Refactor `highlight` tag ([#2154]({{ site.repository }}/issues/2154))
+- Update `Util` hash functions with latest from Rails ([#2273]({{ site.repository }}/issues/2273))
+- Workaround for Travis bug ([#2290]({{ site.repository }}/issues/2290))
+
+### Site Enhancements
+{: #site-enhancements-v2-0-0}
+- Document Kramdown's GFM parser option ([#1791]({{ site.repository }}/issues/1791))
+- Move CSS to includes & update normalize.css to v2.1.3 ([#1787]({{ site.repository }}/issues/1787))
+- Minify CSS only in production ([#1803]({{ site.repository }}/issues/1803))
+- Fix broken link to installation of Ruby on Mountain Lion blog post on
+ Troubleshooting docs page ([#1797]({{ site.repository }}/issues/1797))
+- Fix issues with 1.4.1 release blog post ([#1804]({{ site.repository }}/issues/1804))
+- Add note about deploying to OpenShift ([#1812]({{ site.repository }}/issues/1812))
+- Collect all Windows-related docs onto one page ([#1818]({{ site.repository }}/issues/1818))
+- Fixed typo in datafiles doc page ([#1854]({{ site.repository }}/issues/1854))
+- Clarify how to access `site` in docs ([#1864]({{ site.repository }}/issues/1864))
+- Add closing `` tag to `context.registers[:site]` note ([#1867]({{ site.repository }}/issues/1867))
+- Fix link to [@mojombo](https://github.com/mojombo)'s site source ([#1897]({{ site.repository }}/issues/1897))
+- Add `paginate: nil` to default configuration in docs ([#1896]({{ site.repository }}/issues/1896))
+- Add link to our License in the site footer ([#1889]({{ site.repository }}/issues/1889))
+- Add a charset note in "Writing Posts" doc page ([#1902]({{ site.repository }}/issues/1902))
+- Disallow selection of path and prompt in bash examples
+- Add jekyll-compass to the plugin list ([#1923]({{ site.repository }}/issues/1923))
+- Add note in Posts docs about stripping `
` tags from excerpt ([#1933]({{ site.repository }}/issues/1933))
+- Add additional info about the new exclude behavior ([#1938]({{ site.repository }}/issues/1938))
+- Linkify 'awesome contributors' to point to the contributors graph on
+ GitHub ([#1940]({{ site.repository }}/issues/1940))
+- Update `docs/sites.md` link to GitHub Training materials ([#1949]({{ site.repository }}/issues/1949))
+- Update `master` with the release info from 1.4.3 ([#1947]({{ site.repository }}/issues/1947))
+- Define docs nav in datafile ([#1953]({{ site.repository }}/issues/1953))
+- Clarify the docs around the naming convention for posts ([#1971]({{ site.repository }}/issues/1971))
+- Add missing `next` and `previous` docs for post layouts and templates ([#1970]({{ site.repository }}/issues/1970))
+- Add note to `Writing posts` page about how to strip html from excerpt ([#1962]({{ site.repository }}/issues/1962))
+- Add `jekyll-humanize` plugin to plugin list ([#1998]({{ site.repository }}/issues/1998))
+- Add `jekyll-font-awesome` plugin to plugin list ([#1999]({{ site.repository }}/issues/1999))
+- Add `sublime-jekyll` to list of Editor plugins ([#2001]({{ site.repository }}/issues/2001))
+- Add `vim-jekyll` to the list of Editor plugins ([#2005]({{ site.repository }}/issues/2005))
+- Fix non-semantic nesting of `p` tags in `news_item` layout ([#2013]({{ site.repository }}/issues/2013))
+- Document destination folder cleaning ([#2016]({{ site.repository }}/issues/2016))
+- Updated instructions for NearlyFreeSpeech.NET installation ([#2015]({{ site.repository }}/issues/2015))
+- Update link to rack-jekyll on "Deployment Methods" page ([#2047]({{ site.repository }}/issues/2047))
+- Fix typo in /docs/configuration ([#2073]({{ site.repository }}/issues/2073))
+- Fix count in docs for `site.static_files` ([#2077]({{ site.repository }}/issues/2077))
+- Update configuration docs to indicate utf-8 is the default for 2.0.0
+ and ASCII for 1.9.3 ([#2074]({{ site.repository }}/issues/2074))
+- Add info about unreleased feature to the site ([#2061]({{ site.repository }}/issues/2061))
+- Add whitespace to liquid example in GitHub Pages docs ([#2084]({{ site.repository }}/issues/2084))
+- Clarify the way Sass and CoffeeScript files are read in and output ([#2067]({{ site.repository }}/issues/2067))
+- Add lyche gallery tag plugin link to list of plugins ([#2094]({{ site.repository }}/issues/2094))
+- Add Jekyll Pages Directory plugin to list of plugins ([#2096]({{ site.repository }}/issues/2096))
+- Update Configuration docs page with new markdown extension ([#2102]({{ site.repository }}/issues/2102))
+- Add `jekyll-image-set` to the list of third-party plugins ([#2105]({{ site.repository }}/issues/2105))
+- Losslessly compress images ([#2128]({{ site.repository }}/issues/2128))
+- Update normalize.css to 3.0.0 ([#2126]({{ site.repository }}/issues/2126))
+- Update modernizr to v2.7.1 ([#2129]({{ site.repository }}/issues/2129))
+- Add `jekyll-ordinal` to list of third-party plugins ([#2150]({{ site.repository }}/issues/2150))
+- Add `jekyll_figure` to list of third-party plugins ([#2158]({{ site.repository }}/issues/2158))
+- Clarify the documentation for safe mode ([#2163]({{ site.repository }}/issues/2163))
+- Some HTML tidying ([#2130]({{ site.repository }}/issues/2130))
+- Remove modernizr and use html5shiv.js directly for IE less than v9 ([#2131]({{ site.repository }}/issues/2131))
+- Remove unused images ([#2187]({{ site.repository }}/issues/2187))
+- Use `array_to_sentence_string` filter when outputting news item
+ categories ([#2191]({{ site.repository }}/issues/2191))
+- Add link to Help repo in primary navigation bar ([#2177]({{ site.repository }}/issues/2177))
+- Switch to using an ico file for the shortcut icon ([#2193]({{ site.repository }}/issues/2193))
+- Use numbers to specify font weights and only bring in font weights used ([#2185]({{ site.repository }}/issues/2185))
+- Add a link to the list of all tz database time zones ([#1824]({{ site.repository }}/issues/1824))
+- Clean-up and improve documentation `feed.xml` ([#2192]({{ site.repository }}/issues/2192))
+- Remove duplicate entry in list of third-party plugins ([#2206]({{ site.repository }}/issues/2206))
+- Reduce the whitespace in the favicon. ([#2213]({{ site.repository }}/issues/2213))
+- Add `jekyll-page-collections` to list of third-party plugins ([#2215]({{ site.repository }}/issues/2215))
+- Add a cross-reference about `post_url` ([#2243]({{ site.repository }}/issues/2243))
+- Add `jekyll-live-tiles` to list of third-party plugins ([#2250]({{ site.repository }}/issues/2250))
+- Fixed broken link to GitHub training material site source ([#2257]({{ site.repository }}/issues/2257))
+- Update link to help repo, now called `jekyll-help` ([#2277]({{ site.repository }}/issues/2277))
+- Fix capitalization of 'Jekyll' on Deployment Methods page ([#2291]({{ site.repository }}/issues/2291))
+- Include plugins by sonnym in list of third-party plugins ([#2297]({{ site.repository }}/issues/2297))
+- Add deprecated articles keeper filter to list of third-party plugins ([#2300]({{ site.repository }}/issues/2300))
+- Simplify and improve our CSS. ([#2127]({{ site.repository }}/issues/2127))
+- Use black text color for the mobile navbar ([#2306]({{ site.repository }}/issues/2306))
+- Use the built in date filter and `site.time` for the copyright year. ([#2305]({{ site.repository }}/issues/2305))
+- Update html5shiv to v3.7.2 ([#2304]({{ site.repository }}/issues/2304))
+- Add 2.0.0 release post ([#2298]({{ site.repository }}/issues/2298))
+- Add docs for custom markdown processors ([#2298]({{ site.repository }}/issues/2298))
+- Add docs for `where` and `group_by` Liquid filters ([#2298]({{ site.repository }}/issues/2298))
+- Remove notes in docs for unreleased features ([#2309]({{ site.repository }}/issues/2309))
+
+
+## 1.5.1 / 2014-03-27
+{: #v1-5-1}
+
+### Bug Fixes
+{: #bug-fixes-v1-5-1}
+
+- Only strip the drive name if it begins the string ([#2176]({{ site.repository }}/issues/2176))
+
+
+## 1.5.0 / 2014-03-24
+{: #v1-5-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v1-5-0}
+
+- Loosen `safe_yaml` dependency to `~> 1.0` ([#2167]({{ site.repository }}/issues/2167))
+- Bump `safe_yaml` dependency to `~> 1.0.0` ([#1942]({{ site.repository }}/issues/1942))
+
+### Bug Fixes
+{: #bug-fixes-v1-5-0}
+
+- Fix issue where filesystem traversal restriction broke Windows ([#2167]({{ site.repository }}/issues/2167))
+- Lock `maruku` at `0.7.0` ([#2167]({{ site.repository }}/issues/2167))
+
+### Development Fixes
+{: #development-fixes-v1-5-0}
+
+- Lock `cucumber` at `1.3.11` ([#2167]({{ site.repository }}/issues/2167))
+
+
+## 1.4.3 / 2014-01-13
+{: #v1-4-3}
+
+### Bug Fixes
+{: #bug-fixes-v1-4-3}
+- Patch show-stopping security vulnerabilities ([#1944]({{ site.repository }}/issues/1944))
+
+
+## 1.4.2 / 2013-12-16
+{: #v1-4-2}
+
+### Bug Fixes
+{: #bug-fixes-v1-4-2}
+- Turn on Maruku fenced code blocks by default ([#1830]({{ site.repository }}/issues/1830))
+
+
+## 1.4.1 / 2013-12-09
+{: #v1-4-1}
+
+### Bug Fixes
+{: #bug-fixes-v1-4-1}
+- Don't allow nil entries when loading posts ([#1796]({{ site.repository }}/issues/1796))
+
+
+## 1.4.0 / 2013-12-07
+{: #v1-4-0}
+
+### Major Enhancements
+{: #major-enhancements-v1-4-0}
+- Add support for TOML config files ([#1765]({{ site.repository }}/issues/1765))
+
+### Minor Enhancements
+{: #minor-enhancements-v1-4-0}
+- Sort plugins as a way to establish a load order ([#1682]({{ site.repository }}/issues/1682))
+- Update Maruku to 0.7.0 ([#1775]({{ site.repository }}/issues/1775))
+
+### Bug Fixes
+{: #bug-fixes-v1-4-0}
+- Add a space between two words in a Pagination warning message ([#1769]({{ site.repository }}/issues/1769))
+- Upgrade `toml` gem to `v0.1.0` to maintain compat with Ruby 1.8.7 ([#1778]({{ site.repository }}/issues/1778))
+
+### Development Fixes
+{: #development-fixes-v1-4-0}
+- Remove some whitespace in the code ([#1755]({{ site.repository }}/issues/1755))
+- Remove some duplication in the reading of posts and drafts ([#1779]({{ site.repository }}/issues/1779))
+
+### Site Enhancements
+{: #site-enhancements-v1-4-0}
+- Fixed case of a word in the Jekyll v1.3.0 release post ([#1762]({{ site.repository }}/issues/1762))
+- Fixed the mime type for the favicon ([#1772]({{ site.repository }}/issues/1772))
+
+
+## 1.3.1 / 2013-11-26
+{: #v1-3-1}
+
+### Minor Enhancements
+{: #minor-enhancements-v1-3-1}
+- Add a `--prefix` option to passthrough for the importers ([#1669]({{ site.repository }}/issues/1669))
+- Push the paginator plugin lower in the plugin priority order so
+ other plugins run before it ([#1759]({{ site.repository }}/issues/1759))
+
+### Bug Fixes
+{: #bug-fixes-v1-3-1}
+- Fix the include tag when ran in a loop ([#1726]({{ site.repository }}/issues/1726))
+- Fix errors when using `--watch` on 1.8.7 ([#1730]({{ site.repository }}/issues/1730))
+- Specify where the include is called from if an included file is
+ missing ([#1746]({{ site.repository }}/issues/1746))
+
+### Development Fixes
+{: #development-fixes-v1-3-1}
+- Extract `Site#filter_entries` into its own object ([#1697]({{ site.repository }}/issues/1697))
+- Enable Travis' bundle caching ([#1734]({{ site.repository }}/issues/1734))
+- Remove trailing whitespace in some files ([#1736]({{ site.repository }}/issues/1736))
+- Fix a duplicate test name ([#1754]({{ site.repository }}/issues/1754))
+
+### Site Enhancements
+{: #site-enhancements-v1-3-1}
+- Update link to example Rakefile to point to specific commit ([#1741]({{ site.repository }}/issues/1741))
+- Fix drafts docs to indicate that draft time is based on file modification
+ time, not `Time.now` ([#1695]({{ site.repository }}/issues/1695))
+- Add `jekyll-monthly-archive-plugin` and `jekyll-category-archive-plugin` to
+ list of third-party plugins ([#1693]({{ site.repository }}/issues/1693))
+- Add `jekyll-asset-path-plugin` to list of third-party plugins ([#1670]({{ site.repository }}/issues/1670))
+- Add `emoji-for-jekyll` to list of third-part plugins ([#1708]({{ site.repository }}/issues/1708))
+- Fix previous section link on plugins page to point to pagination page ([#1707]({{ site.repository }}/issues/1707))
+- Add `org-mode` converter plugin to third-party plugins ([#1711]({{ site.repository }}/issues/1711))
+- Point "Blog migrations" page to http://import.jekyllrb.com ([#1732]({{ site.repository }}/issues/1732))
+- Add docs for `post_url` when posts are in subdirectories ([#1718]({{ site.repository }}/issues/1718))
+- Update the docs to point to `example.com` ([#1448]({{ site.repository }}/issues/1448))
+
+
+## 1.3.0 / 2013-11-04
+{: #v1-3-0}
+
+### Major Enhancements
+{: #major-enhancements-v1-3-0}
+- Add support for adding data as YAML files under a site's `_data`
+ directory ([#1003]({{ site.repository }}/issues/1003))
+- Allow variables to be used with `include` tags ([#1495]({{ site.repository }}/issues/1495))
+- Allow using gems for plugin management ([#1557]({{ site.repository }}/issues/1557))
+
+### Minor Enhancements
+{: #minor-enhancements-v1-3-0}
+- Decrease the specificity in the site template CSS ([#1574]({{ site.repository }}/issues/1574))
+- Add `encoding` configuration option ([#1449]({{ site.repository }}/issues/1449))
+- Provide better error handling for Jekyll's custom Liquid tags
+ ([#1514]({{ site.repository }}/issues/1514))
+- If an included file causes a Liquid error, add the path to the
+ include file that caused the error to the error message ([#1596]({{ site.repository }}/issues/1596))
+- If a layout causes a Liquid error, change the error message so that
+ we know it comes from the layout ([#1601]({{ site.repository }}/issues/1601))
+- Update Kramdown dependency to `~> 1.2` ([#1610]({{ site.repository }}/issues/1610))
+- Update `safe_yaml` dependency to `~> 0.9.7` ([#1602]({{ site.repository }}/issues/1602))
+- Allow layouts to be in subfolders like includes ([#1622]({{ site.repository }}/issues/1622))
+- Switch to listen for site watching while serving ([#1589]({{ site.repository }}/issues/1589))
+- Add a `json` liquid filter to be used in sites ([#1651]({{ site.repository }}/issues/1651))
+- Point people to the migration docs when the `jekyll-import` gem is
+ missing ([#1662]({{ site.repository }}/issues/1662))
+
+### Bug Fixes
+{: #bug-fixes-v1-3-0}
+- Fix up matching against source and destination when the two
+ locations are similar ([#1556]({{ site.repository }}/issues/1556))
+- Fix the missing `pathname` require in certain cases ([#1255]({{ site.repository }}/issues/1255))
+- Use `+` instead of `Array#concat` when building `Post` attribute list ([#1571]({{ site.repository }}/issues/1571))
+- Print server address when launching a server ([#1586]({{ site.repository }}/issues/1586))
+- Downgrade to Maruku `~> 0.6.0` in order to avoid changes in rendering ([#1598]({{ site.repository }}/issues/1598))
+- Fix error with failing include tag when variable was file name ([#1613]({{ site.repository }}/issues/1613))
+- Downcase lexers before passing them to pygments ([#1615]({{ site.repository }}/issues/1615))
+- Capitalize the short verbose switch because it conflicts with the
+ built-in Commander switch ([#1660]({{ site.repository }}/issues/1660))
+- Fix compatibility with 1.8.x ([#1665]({{ site.repository }}/issues/1665))
+- Fix an error with the new file watching code due to library version
+ incompatibilities ([#1687]({{ site.repository }}/issues/1687))
+
+### Development Fixes
+{: #development-fixes-v1-3-0}
+- Add coverage reporting with Coveralls ([#1539]({{ site.repository }}/issues/1539))
+- Refactor the Liquid `include` tag ([#1490]({{ site.repository }}/issues/1490))
+- Update launchy dependency to `~> 2.3` ([#1608]({{ site.repository }}/issues/1608))
+- Update rr dependency to `~> 1.1` ([#1604]({{ site.repository }}/issues/1604))
+- Update cucumber dependency to `~> 1.3` ([#1607]({{ site.repository }}/issues/1607))
+- Update coveralls dependency to `~> 0.7.0` ([#1606]({{ site.repository }}/issues/1606))
+- Update rake dependency to `~> 10.1` ([#1603]({{ site.repository }}/issues/1603))
+- Clean up `site.rb` comments to be more concise/uniform ([#1616]({{ site.repository }}/issues/1616))
+- Use the master branch for the build badge in the readme ([#1636]({{ site.repository }}/issues/1636))
+- Refactor Site#render ([#1638]({{ site.repository }}/issues/1638))
+- Remove duplication in command line options ([#1637]({{ site.repository }}/issues/1637))
+- Add tests for all the coderay options ([#1543]({{ site.repository }}/issues/1543))
+- Improve some of the Cucumber test code ([#1493]({{ site.repository }}/issues/1493))
+- Improve comparisons of timestamps by ignoring the seconds ([#1582]({{ site.repository }}/issues/1582))
+
+### Site Enhancements
+{: #site-enhancements-v1-3-0}
+- Fix params for `JekyllImport::WordPress.process` arguments ([#1554]({{ site.repository }}/issues/1554))
+- Add `jekyll-suggested-tweet` to list of third-party plugins ([#1555]({{ site.repository }}/issues/1555))
+- Link to Liquid's docs for tags and filters ([#1553]({{ site.repository }}/issues/1553))
+- Add note about installing Xcode on the Mac in the Installation docs ([#1561]({{ site.repository }}/issues/1561))
+- Simplify/generalize pagination docs ([#1577]({{ site.repository }}/issues/1577))
+- Add documentation for the new data sources feature ([#1503]({{ site.repository }}/issues/1503))
+- Add more information on how to create generators ([#1590]({{ site.repository }}/issues/1590), [#1592]({{ site.repository }}/issues/1592))
+- Improve the instructions for mimicking GitHub Flavored Markdown
+ ([#1614]({{ site.repository }}/issues/1614))
+- Add `jekyll-import` warning note of missing dependencies ([#1626]({{ site.repository }}/issues/1626))
+- Fix grammar in the Usage section ([#1635]({{ site.repository }}/issues/1635))
+- Add documentation for the use of gems as plugins ([#1656]({{ site.repository }}/issues/1656))
+- Document the existence of a few additional plugins ([#1405]({{ site.repository }}/issues/1405))
+- Document that the `date_to_string` always returns a two digit day ([#1663]({{ site.repository }}/issues/1663))
+- Fix navigation in the "Working with Drafts" page ([#1667]({{ site.repository }}/issues/1667))
+- Fix an error with the data documentation ([#1691]({{ site.repository }}/issues/1691))
+
+
+## 1.2.1 / 2013-09-14
+{: #v1-2-1}
+
+### Minor Enhancements
+{: #minor-enhancements-v1-2-1}
+- Print better messages for detached server. Mute output on detach. ([#1518]({{ site.repository }}/issues/1518))
+- Disable reverse lookup when running `jekyll serve` ([#1363]({{ site.repository }}/issues/1363))
+- Upgrade RedCarpet dependency to `~> 2.3.0` ([#1515]({{ site.repository }}/issues/1515))
+- Upgrade to Liquid `>= 2.5.2, < 2.6` ([#1536]({{ site.repository }}/issues/1536))
+
+### Bug Fixes
+{: #bug-fixes-v1-2-1}
+- Fix file discrepancy in gemspec ([#1522]({{ site.repository }}/issues/1522))
+- Force rendering of Include tag ([#1525]({{ site.repository }}/issues/1525))
+
+### Development Fixes
+{: #development-fixes-v1-2-1}
+- Add a rake task to generate a new release post ([#1404]({{ site.repository }}/issues/1404))
+- Mute LSI output in tests ([#1531]({{ site.repository }}/issues/1531))
+- Update contributor documentation ([#1537]({{ site.repository }}/issues/1537))
+
+### Site Enhancements
+{: #site-enhancements-v1-2-1}
+- Fix a couple of validation errors on the site ([#1511]({{ site.repository }}/issues/1511))
+- Make navigation menus reusable ([#1507]({{ site.repository }}/issues/1507))
+- Fix link to History page from Release v1.2.0 notes post.
+- Fix markup in History file for command line options ([#1512]({{ site.repository }}/issues/1512))
+- Expand 1.2 release post title to 1.2.0 ([#1516]({{ site.repository }}/issues/1516))
+
+
+## 1.2.0 / 2013-09-06
+{: #v1-2-0}
+
+### Major Enhancements
+{: #major-enhancements-v1-2-0}
+- Disable automatically-generated excerpts when `excerpt_separator` is `""`. ([#1386]({{ site.repository }}/issues/1386))
+- Add checking for URL conflicts when running `jekyll doctor` ([#1389]({{ site.repository }}/issues/1389))
+
+### Minor Enhancements
+{: #minor-enhancements-v1-2-0}
+- Catch and fix invalid `paginate` values ([#1390]({{ site.repository }}/issues/1390))
+- Remove superfluous `div.container` from the default html template for
+ `jekyll new` ([#1315]({{ site.repository }}/issues/1315))
+- Add `-D` short-form switch for the drafts option ([#1394]({{ site.repository }}/issues/1394))
+- Update the links in the site template for Twitter and GitHub ([#1400]({{ site.repository }}/issues/1400))
+- Update dummy email address to example.com domain ([#1408]({{ site.repository }}/issues/1408))
+- Update normalize.css to v2.1.2 and minify; add rake task to update
+ normalize.css with greater ease. ([#1430]({{ site.repository }}/issues/1430))
+- Add the ability to detach the server ran by `jekyll serve` from it's
+ controlling terminal ([#1443]({{ site.repository }}/issues/1443))
+- Improve permalink generation for URLs with special characters ([#944]({{ site.repository }}/issues/944))
+- Expose the current Jekyll version to posts and pages via a new
+ `jekyll.version` variable ([#1481]({{ site.repository }}/issues/1481))
+
+### Bug Fixes
+{: #bug-fixes-v1-2-0}
+- Markdown extension matching matches only exact matches ([#1382]({{ site.repository }}/issues/1382))
+- Fixed NoMethodError when message passed to `Stevenson#message` is nil ([#1388]({{ site.repository }}/issues/1388))
+- Use binary mode when writing file ([#1364]({{ site.repository }}/issues/1364))
+- Fix 'undefined method `encoding` for "mailto"' errors w/ Ruby 1.8 and
+ Kramdown > 0.14.0 ([#1397]({{ site.repository }}/issues/1397))
+- Do not force the permalink to be a dir if it ends on .html ([#963]({{ site.repository }}/issues/963))
+- When a Liquid Exception is caught, show the full path rel. to site source ([#1415]({{ site.repository }}/issues/1415))
+- Properly read in the config options when serving the docs locally
+ ([#1444]({{ site.repository }}/issues/1444))
+- Fixed `--layouts` option for `build` and `serve` commands ([#1458]({{ site.repository }}/issues/1458))
+- Remove kramdown as a runtime dependency since it's optional ([#1498]({{ site.repository }}/issues/1498))
+- Provide proper error handling for invalid file names in the include
+ tag ([#1494]({{ site.repository }}/issues/1494))
+
+### Development Fixes
+{: #development-fixes-v1-2-0}
+- Remove redundant argument to
+ Jekyll::Commands::New#scaffold_post_content ([#1356]({{ site.repository }}/issues/1356))
+- Add new dependencies to the README ([#1360]({{ site.repository }}/issues/1360))
+- Fix link to contributing page in README ([#1424]({{ site.repository }}/issues/1424))
+- Update TomDoc in Pager#initialize to match params ([#1441]({{ site.repository }}/issues/1441))
+- Refactor `Site#cleanup` into `Jekyll::Site::Cleaner` class ([#1429]({{ site.repository }}/issues/1429))
+- Several other small minor refactorings ([#1341]({{ site.repository }}/issues/1341))
+- Ignore `_site` in jekyllrb.com deploy ([#1480]({{ site.repository }}/issues/1480))
+- Add Gem version and dependency badge to README ([#1497]({{ site.repository }}/issues/1497))
+
+### Site Enhancements
+{: #site-enhancements-v1-2-0}
+- Add info about new releases ([#1353]({{ site.repository }}/issues/1353))
+- Update plugin list with jekyll-rss plugin ([#1354]({{ site.repository }}/issues/1354))
+- Update the site list page with Ruby's official site ([#1358]({{ site.repository }}/issues/1358))
+- Add `jekyll-ditaa` to list of third-party plugins ([#1370]({{ site.repository }}/issues/1370))
+- Add `postfiles` to list of third-party plugins ([#1373]({{ site.repository }}/issues/1373))
+- For internal links, use full path including trailing `/` ([#1411]({{ site.repository }}/issues/1411))
+- Use curly apostrophes in the docs ([#1419]({{ site.repository }}/issues/1419))
+- Update the docs for Redcarpet in Jekyll ([#1418]({{ site.repository }}/issues/1418))
+- Add `pluralize` and `reading_time` filters to docs ([#1439]({{ site.repository }}/issues/1439))
+- Fix markup for the Kramdown options ([#1445]({{ site.repository }}/issues/1445))
+- Fix typos in the History file ([#1454]({{ site.repository }}/issues/1454))
+- Add trailing slash to site's post URL ([#1462]({{ site.repository }}/issues/1462))
+- Clarify that `--config` will take multiple files ([#1474]({{ site.repository }}/issues/1474))
+- Fix docs/templates.md private gist example ([#1477]({{ site.repository }}/issues/1477))
+- Use `site.repository` for Jekyll's GitHub URL ([#1463]({{ site.repository }}/issues/1463))
+- Add `jekyll-pageless-redirects` to list of third-party plugins ([#1486]({{ site.repository }}/issues/1486))
+- Clarify that `date_to_xmlschema` returns an ISO 8601 string ([#1488]({{ site.repository }}/issues/1488))
+- Add `jekyll-good-include` to list of third-party plugins ([#1491]({{ site.repository }}/issues/1491))
+- XML escape the blog post title in our feed ([#1501]({{ site.repository }}/issues/1501))
+- Add `jekyll-toc-generator` to list of third-party plugins ([#1506]({{ site.repository }}/issues/1506))
+
+
+## 1.1.2 / 2013-07-25
+{: #v1-1-2}
+
+### Bug Fixes
+{: #bug-fixes-v1-1-2}
+- Require Liquid 2.5.1 ([#1349]({{ site.repository }}/issues/1349))
+
+
+## 1.1.1 / 2013-07-24
+{: #v1-1-1}
+
+### Minor Enhancements
+{: #minor-enhancements-v1-1-1}
+- Remove superfluous `table` selector from main.css in `jekyll new` template ([#1328]({{ site.repository }}/issues/1328))
+- Abort with non-zero exit codes ([#1338]({{ site.repository }}/issues/1338))
+
+### Bug Fixes
+{: #bug-fixes-v1-1-1}
+- Fix up the rendering of excerpts ([#1339]({{ site.repository }}/issues/1339))
+
+### Site Enhancements
+{: #site-enhancements-v1-1-1}
+- Add Jekyll Image Tag to the plugins list ([#1306]({{ site.repository }}/issues/1306))
+- Remove erroneous statement that `site.pages` are sorted alphabetically.
+- Add info about the `_drafts` directory to the directory structure
+ docs ([#1320]({{ site.repository }}/issues/1320))
+- Improve the layout of the plugin listing by organizing it into
+ categories ([#1310]({{ site.repository }}/issues/1310))
+- Add generator-jekyllrb and grunt-jekyll to plugins page ([#1330]({{ site.repository }}/issues/1330))
+- Mention Kramdown as option for markdown parser on Extras page ([#1318]({{ site.repository }}/issues/1318))
+- Update Quick-Start page to include reminder that all requirements must be installed ([#1327]({{ site.repository }}/issues/1327))
+- Change filename in `include` example to an HTML file so as not to indicate that Jekyll
+ will automatically convert them. ([#1303]({{ site.repository }}/issues/1303))
+- Add an RSS feed for commits to Jekyll ([#1343]({{ site.repository }}/issues/1343))
+
+
+## 1.1.0 / 2013-07-14
+{: #v1-1-0}
+
+### Major Enhancements
+{: #major-enhancements-v1-1-0}
+- Add `docs` subcommand to read Jekyll's docs when offline. ([#1046]({{ site.repository }}/issues/1046))
+- Support passing parameters to templates in `include` tag ([#1204]({{ site.repository }}/issues/1204))
+- Add support for Liquid tags to post excerpts ([#1302]({{ site.repository }}/issues/1302))
+
+### Minor Enhancements
+{: #minor-enhancements-v1-1-0}
+- Search the hierarchy of pagination path up to site root to determine template page for
+ pagination. ([#1198]({{ site.repository }}/issues/1198))
+- Add the ability to generate a new Jekyll site without a template ([#1171]({{ site.repository }}/issues/1171))
+- Use redcarpet as the default markdown engine in newly generated
+ sites ([#1245]({{ site.repository }}/issues/1245), [#1247]({{ site.repository }}/issues/1247))
+- Add `redcarpet` as a runtime dependency so `jekyll build` works out-of-the-box for new
+ sites. ([#1247]({{ site.repository }}/issues/1247))
+- In the generated site, remove files that will be replaced by a
+ directory ([#1118]({{ site.repository }}/issues/1118))
+- Fail loudly if a user-specified configuration file doesn't exist ([#1098]({{ site.repository }}/issues/1098))
+- Allow for all options for Kramdown HTML Converter ([#1201]({{ site.repository }}/issues/1201))
+
+### Bug Fixes
+{: #bug-fixes-v1-1-0}
+- Fix pagination in subdirectories. ([#1198]({{ site.repository }}/issues/1198))
+- Fix an issue with directories and permalinks that have a plus sign
+ (+) in them ([#1215]({{ site.repository }}/issues/1215))
+- Provide better error reporting when generating sites ([#1253]({{ site.repository }}/issues/1253))
+- Latest posts first in non-LSI `related_posts` ([#1271]({{ site.repository }}/issues/1271))
+
+### Development Fixes
+{: #development-fixes-v1-1-0}
+- Merge the theme and layout Cucumber steps into one step ([#1151]({{ site.repository }}/issues/1151))
+- Restrict activesupport dependency to pre-4.0.0 to maintain compatibility with `<= 1.9.2`
+- Include/exclude deprecation handling simplification ([#1284]({{ site.repository }}/issues/1284))
+- Convert README to Markdown. ([#1267]({{ site.repository }}/issues/1267))
+- Refactor Jekyll::Site ([#1144]({{ site.repository }}/issues/1144))
+
+### Site Enhancements
+{: #site-enhancements-v1-1-0}
+- Add "News" section for release notes, along with an RSS feed ([#1093]({{ site.repository }}/issues/1093), [#1285]({{ site.repository }}/issues/1285), [#1286]({{ site.repository }}/issues/1286))
+- Add "History" page.
+- Restructured docs sections to include "Meta" section.
+- Add message to "Templates" page that specifies that Python must be installed in order
+ to use Pygments. ([#1182]({{ site.repository }}/issues/1182))
+- Update link to the official Maruku repo ([#1175]({{ site.repository }}/issues/1175))
+- Add documentation about `paginate_path` to "Templates" page in docs ([#1129]({{ site.repository }}/issues/1129))
+- Give the quick-start guide its own page ([#1191]({{ site.repository }}/issues/1191))
+- Update ProTip on Installation page in docs to point to all the info about Pygments and
+ the 'highlight' tag. ([#1196]({{ site.repository }}/issues/1196))
+- Run `site/img` through ImageOptim (thanks [@qrush](https://github.com/qrush)!) ([#1208]({{ site.repository }}/issues/1208))
+- Added Jade Converter to `site/docs/plugins` ([#1210]({{ site.repository }}/issues/1210))
+- Fix location of docs pages in Contributing pages ([#1214]({{ site.repository }}/issues/1214))
+- Add ReadInXMinutes plugin to the plugin list ([#1222]({{ site.repository }}/issues/1222))
+- Remove plugins from the plugin list that have equivalents in Jekyll
+ proper ([#1223]({{ site.repository }}/issues/1223))
+- Add jekyll-assets to the plugin list ([#1225]({{ site.repository }}/issues/1225))
+- Add jekyll-pandoc-mulitple-formats to the plugin list ([#1229]({{ site.repository }}/issues/1229))
+- Remove dead link to "Using Git to maintain your blog" ([#1227]({{ site.repository }}/issues/1227))
+- Tidy up the third-party plugins listing ([#1228]({{ site.repository }}/issues/1228))
+- Update contributor information ([#1192]({{ site.repository }}/issues/1192))
+- Update URL of article about Blogger migration ([#1242]({{ site.repository }}/issues/1242))
+- Specify that RedCarpet is the default for new Jekyll sites on Quickstart page ([#1247]({{ site.repository }}/issues/1247))
+- Added `site.pages` to Variables page in docs ([#1251]({{ site.repository }}/issues/1251))
+- Add Youku and Tudou Embed link on Plugins page. ([#1250]({{ site.repository }}/issues/1250))
+- Add note that `gist` tag supports private gists. ([#1248]({{ site.repository }}/issues/1248))
+- Add `jekyll-timeago` to list of third-party plugins. ([#1260]({{ site.repository }}/issues/1260))
+- Add `jekyll-swfobject` to list of third-party plugins. ([#1263]({{ site.repository }}/issues/1263))
+- Add `jekyll-picture-tag` to list of third-party plugins. ([#1280]({{ site.repository }}/issues/1280))
+- Update the GitHub Pages documentation regarding relative URLs
+ ([#1291]({{ site.repository }}/issues/1291))
+- Update the S3 deployment documentation ([#1294]({{ site.repository }}/issues/1294))
+- Add suggestion for Xcode CLT install to troubleshooting page in docs ([#1296]({{ site.repository }}/issues/1296))
+- Add 'Working with drafts' page to docs ([#1289]({{ site.repository }}/issues/1289))
+- Add information about time zones to the documentation for a page's
+ date ([#1304]({{ site.repository }}/issues/1304))
+
+
+## 1.0.3 / 2013-06-07
+{: #v1-0-3}
+
+### Minor Enhancements
+{: #minor-enhancements-v1-0-3}
+- Add support to gist tag for private gists. ([#1189]({{ site.repository }}/issues/1189))
+- Fail loudly when Maruku errors out ([#1190]({{ site.repository }}/issues/1190))
+- Move the building of related posts into their own class ([#1057]({{ site.repository }}/issues/1057))
+- Removed trailing spaces in several places throughout the code ([#1116]({{ site.repository }}/issues/1116))
+- Add a `--force` option to `jekyll new` ([#1115]({{ site.repository }}/issues/1115))
+- Convert IDs in the site template to classes ([#1170]({{ site.repository }}/issues/1170))
+
+### Bug Fixes
+{: #bug-fixes-v1-0-3}
+- Fix typo in Stevenson constant "ERROR". ([#1166]({{ site.repository }}/issues/1166))
+- Rename Jekyll::Logger to Jekyll::Stevenson to fix inheritance issue ([#1106]({{ site.repository }}/issues/1106))
+- Exit with a non-zero exit code when dealing with a Liquid error ([#1121]({{ site.repository }}/issues/1121))
+- Make the `exclude` and `include` options backwards compatible with
+ versions of Jekyll prior to 1.0 ([#1114]({{ site.repository }}/issues/1114))
+- Fix pagination on Windows ([#1063]({{ site.repository }}/issues/1063))
+- Fix the application of Pygments' Generic Output style to Go code
+ ([#1156]({{ site.repository }}/issues/1156))
+
+### Site Enhancements
+{: #site-enhancements-v1-0-3}
+- Add a Pro Tip to docs about front matter variables being optional ([#1147]({{ site.repository }}/issues/1147))
+- Add changelog to site as History page in /docs/ ([#1065]({{ site.repository }}/issues/1065))
+- Add note to Upgrading page about new config options in 1.0.x ([#1146]({{ site.repository }}/issues/1146))
+- Documentation for `date_to_rfc822` and `uri_escape` ([#1142]({{ site.repository }}/issues/1142))
+- Documentation highlight boxes shouldn't show scrollbars if not necessary ([#1123]({{ site.repository }}/issues/1123))
+- Add link to jekyll-minibundle in the doc's plugins list ([#1035]({{ site.repository }}/issues/1035))
+- Quick patch for importers documentation
+- Fix prefix for WordpressDotCom importer in docs ([#1107]({{ site.repository }}/issues/1107))
+- Add jekyll-contentblocks plugin to docs ([#1068]({{ site.repository }}/issues/1068))
+- Make code bits in notes look more natural, more readable ([#1089]({{ site.repository }}/issues/1089))
+- Fix logic for `relative_permalinks` instructions on Upgrading page ([#1101]({{ site.repository }}/issues/1101))
+- Add docs for post excerpt ([#1072]({{ site.repository }}/issues/1072))
+- Add docs for gist tag ([#1072]({{ site.repository }}/issues/1072))
+- Add docs indicating that Pygments does not need to be installed
+ separately ([#1099]({{ site.repository }}/issues/1099), [#1119]({{ site.repository }}/issues/1119))
+- Update the migrator docs to be current ([#1136]({{ site.repository }}/issues/1136))
+- Add the Jekyll Gallery Plugin to the plugin list ([#1143]({{ site.repository }}/issues/1143))
+
+### Development Fixes
+{: #development-fixes-v1-0-3}
+- Use Jekyll.logger instead of Jekyll::Stevenson to log things ([#1149]({{ site.repository }}/issues/1149))
+- Fix pesky Cucumber infinite loop ([#1139]({{ site.repository }}/issues/1139))
+- Do not write posts with timezones in Cucumber tests ([#1124]({{ site.repository }}/issues/1124))
+- Use ISO formatted dates in Cucumber features ([#1150]({{ site.repository }}/issues/1150))
+
+
+## 1.0.2 / 2013-05-12
+{: #v1-0-2}
+
+### Major Enhancements
+{: #major-enhancements-v1-0-2}
+- Add `jekyll doctor` command to check site for any known compatibility problems ([#1081]({{ site.repository }}/issues/1081))
+- Backwards-compatibilize relative permalinks ([#1081]({{ site.repository }}/issues/1081))
+
+### Minor Enhancements
+{: #minor-enhancements-v1-0-2}
+- Add a `data-lang=""` attribute to Redcarpet code blocks ([#1066]({{ site.repository }}/issues/1066))
+- Deprecate old config `server_port`, match to `port` if `port` isn't set ([#1084]({{ site.repository }}/issues/1084))
+- Update pygments.rb version to 0.5.0 ([#1061]({{ site.repository }}/issues/1061))
+- Update Kramdown version to 1.0.2 ([#1067]({{ site.repository }}/issues/1067))
+
+### Bug Fixes
+{: #bug-fixes-v1-0-2}
+- Fix issue when categories are numbers ([#1078]({{ site.repository }}/issues/1078))
+- Catching that Redcarpet gem isn't installed ([#1059]({{ site.repository }}/issues/1059))
+
+### Site Enhancements
+{: #site-enhancements-v1-0-2}
+- Add documentation about `relative_permalinks` ([#1081]({{ site.repository }}/issues/1081))
+- Remove pygments-installation instructions, as pygments.rb is bundled with it ([#1079]({{ site.repository }}/issues/1079))
+- Move pages to be Pages for realz ([#985]({{ site.repository }}/issues/985))
+- Updated links to Liquid documentation ([#1073]({{ site.repository }}/issues/1073))
+
+
+## 1.0.1 / 2013-05-08
+{: #v1-0-1}
+
+### Minor Enhancements
+{: #minor-enhancements-v1-0-1}
+- Do not force use of `toc_token` when using `generate_tok` in RDiscount ([#1048]({{ site.repository }}/issues/1048))
+- Add newer `language-` class name prefix to code blocks ([#1037]({{ site.repository }}/issues/1037))
+- Commander error message now preferred over process abort with incorrect args ([#1040]({{ site.repository }}/issues/1040))
+
+### Bug Fixes
+{: #bug-fixes-v1-0-1}
+- Make Redcarpet respect the pygments configuration option ([#1053]({{ site.repository }}/issues/1053))
+- Fix the index build with LSI ([#1045]({{ site.repository }}/issues/1045))
+- Don't print deprecation warning when no arguments are specified. ([#1041]({{ site.repository }}/issues/1041))
+- Add missing `` to site template used by `new` subcommand, fixed typos in code ([#1032]({{ site.repository }}/issues/1032))
+
+### Site Enhancements
+{: #site-enhancements-v1-0-1}
+- Changed https to http in the GitHub Pages link ([#1051]({{ site.repository }}/issues/1051))
+- Remove CSS cruft, fix typos, fix HTML errors ([#1028]({{ site.repository }}/issues/1028))
+- Removing manual install of Pip and Distribute ([#1025]({{ site.repository }}/issues/1025))
+- Updated URL for Markdown references plugin ([#1022]({{ site.repository }}/issues/1022))
+
+### Development Fixes
+{: #development-fixes-v1-0-1}
+- Markdownify history file ([#1027]({{ site.repository }}/issues/1027))
+- Update links on README to point to new jekyllrb.com ([#1018]({{ site.repository }}/issues/1018))
+
+
+## 1.0.0 / 2013-05-06
+{: #v1-0-0}
+
+### Major Enhancements
+{: #major-enhancements-v1-0-0}
+- Add `jekyll new` subcommand: generate a Jekyll scaffold ([#764]({{ site.repository }}/issues/764))
+- Refactored Jekyll commands into subcommands: build, serve, and migrate. ([#690]({{ site.repository }}/issues/690))
+- Removed importers/migrators from main project, migrated to jekyll-import sub-gem ([#793]({{ site.repository }}/issues/793))
+- Added ability to render drafts in `_drafts` folder via command line ([#833]({{ site.repository }}/issues/833))
+- Add ordinal date permalink style (/:categories/:year/:y_day/:title.html) ([#928]({{ site.repository }}/issues/928))
+
+### Minor Enhancements
+{: #minor-enhancements-v1-0-0}
+- Site template HTML5-ified ([#964]({{ site.repository }}/issues/964))
+- Use post's directory path when matching for the `post_url` tag ([#998]({{ site.repository }}/issues/998))
+- Loosen dependency on Pygments so it's only required when it's needed ([#1015]({{ site.repository }}/issues/1015))
+- Parse strings into Time objects for date-related Liquid filters ([#1014]({{ site.repository }}/issues/1014))
+- Tell the user if there is no subcommand specified ([#1008]({{ site.repository }}/issues/1008))
+- Freak out if the destination of `jekyll new` exists and is non-empty ([#981]({{ site.repository }}/issues/981))
+- Add `timezone` configuration option for compilation ([#957]({{ site.repository }}/issues/957))
+- Add deprecation messages for pre-1.0 CLI options ([#959]({{ site.repository }}/issues/959))
+- Refactor and colorize logging ([#959]({{ site.repository }}/issues/959))
+- Refactor Markdown parsing ([#955]({{ site.repository }}/issues/955))
+- Added application/vnd.apple.pkpass to mime.types served by WEBrick ([#907]({{ site.repository }}/issues/907))
+- Move template site to default markdown renderer ([#961]({{ site.repository }}/issues/961))
+- Expose new attribute to Liquid via `page`: `page.path` ([#951]({{ site.repository }}/issues/951))
+- Accept multiple config files from command line ([#945]({{ site.repository }}/issues/945))
+- Add page variable to liquid custom tags and blocks ([#413]({{ site.repository }}/issues/413))
+- Add `paginator.previous_page_path` and `paginator.next_page_path` ([#942]({{ site.repository }}/issues/942))
+- Backwards compatibility for 'auto' ([#821]({{ site.repository }}/issues/821), [#934]({{ site.repository }}/issues/934))
+- Added date_to_rfc822 used on RSS feeds ([#892]({{ site.repository }}/issues/892))
+- Upgrade version of pygments.rb to 0.4.2 ([#927]({{ site.repository }}/issues/927))
+- Added short month (e.g. "Sep") to permalink style options for posts ([#890]({{ site.repository }}/issues/890))
+- Expose site.baseurl to Liquid templates ([#869]({{ site.repository }}/issues/869))
+- Adds excerpt attribute to posts which contains first paragraph of content ([#837]({{ site.repository }}/issues/837))
+- Accept custom configuration file via CLI ([#863]({{ site.repository }}/issues/863))
+- Load in GitHub Pages MIME Types on `jekyll serve` ([#847]({{ site.repository }}/issues/847), [#871]({{ site.repository }}/issues/871))
+- Improve debugability of error message for a malformed highlight tag ([#785]({{ site.repository }}/issues/785))
+- Allow symlinked files in unsafe mode ([#824]({{ site.repository }}/issues/824))
+- Add 'gist' Liquid tag to core ([#822]({{ site.repository }}/issues/822), [#861]({{ site.repository }}/issues/861))
+- New format of Jekyll output ([#795]({{ site.repository }}/issues/795))
+- Reinstate `--limit_posts` and `--future` switches ([#788]({{ site.repository }}/issues/788))
+- Remove ambiguity from command descriptions ([#815]({{ site.repository }}/issues/815))
+- Fix SafeYAML Warnings ([#807]({{ site.repository }}/issues/807))
+- Relaxed Kramdown version to 0.14 ([#808]({{ site.repository }}/issues/808))
+- Aliased `jekyll server` to `jekyll serve`. ([#792]({{ site.repository }}/issues/792))
+- Updated gem versions for Kramdown, Rake, Shoulda, Cucumber, and RedCarpet. ([#744]({{ site.repository }}/issues/744))
+- Refactored Jekyll subcommands into Jekyll::Commands submodule, which now contains them ([#768]({{ site.repository }}/issues/768))
+- Rescue from import errors in Wordpress.com migrator ([#671]({{ site.repository }}/issues/671))
+- Massively accelerate LSI performance ([#664]({{ site.repository }}/issues/664))
+- Truncate post slugs when importing from Tumblr ([#496]({{ site.repository }}/issues/496))
+- Add glob support to include, exclude option ([#743]({{ site.repository }}/issues/743))
+- Layout of Page or Post defaults to 'page' or 'post', respectively ([#580]({{ site.repository }}/issues/580))
+ REPEALED by ([#977]({{ site.repository }}/issues/977))
+- "Keep files" feature ([#685]({{ site.repository }}/issues/685))
+- Output full path & name for files that don't parse ([#745]({{ site.repository }}/issues/745))
+- Add source and destination directory protection ([#535]({{ site.repository }}/issues/535))
+- Better YAML error message ([#718]({{ site.repository }}/issues/718))
+- Bug Fixes
+- Paginate in subdirectories properly ([#1016]({{ site.repository }}/issues/1016))
+- Ensure post and page URLs have a leading slash ([#992]({{ site.repository }}/issues/992))
+- Catch all exceptions, not just StandardError descendents ([#1007]({{ site.repository }}/issues/1007))
+- Bullet-proof `limit_posts` option ([#1004]({{ site.repository }}/issues/1004))
+- Read in YAML as UTF-8 to accept non-ASCII chars ([#836]({{ site.repository }}/issues/836))
+- Fix the CLI option `--plugins` to actually accept dirs and files ([#993]({{ site.repository }}/issues/993))
+- Allow 'excerpt' in YAML front matter to override the extracted excerpt ([#946]({{ site.repository }}/issues/946))
+- Fix cascade problem with site.baseurl, site.port and site.host. ([#935]({{ site.repository }}/issues/935))
+- Filter out directories with valid post names ([#875]({{ site.repository }}/issues/875))
+- Fix symlinked static files not being correctly built in unsafe mode ([#909]({{ site.repository }}/issues/909))
+- Fix integration with directory_watcher 1.4.x ([#916]({{ site.repository }}/issues/916))
+- Accepting strings as arguments to jekyll-import command ([#910]({{ site.repository }}/issues/910))
+- Force usage of older directory_watcher gem as 1.5 is broken ([#883]({{ site.repository }}/issues/883))
+- Ensure all Post categories are downcase ([#842]({{ site.repository }}/issues/842), [#872]({{ site.repository }}/issues/872))
+- Force encoding of the rdiscount TOC to UTF8 to avoid conversion errors ([#555]({{ site.repository }}/issues/555))
+- Patch for multibyte URI problem with `jekyll serve` ([#723]({{ site.repository }}/issues/723))
+- Order plugin execution by priority ([#864]({{ site.repository }}/issues/864))
+- Fixed Page#dir and Page#url for edge cases ([#536]({{ site.repository }}/issues/536))
+- Fix broken `post_url` with posts with a time in their YAML front matter ([#831]({{ site.repository }}/issues/831))
+- Look for plugins under the source directory ([#654]({{ site.repository }}/issues/654))
+- Tumblr Migrator: finds `_posts` dir correctly, fixes truncation of long
+ post names ([#775]({{ site.repository }}/issues/775))
+- Force Categories to be Strings ([#767]({{ site.repository }}/issues/767))
+- Safe YAML plugin to prevent vulnerability ([#777]({{ site.repository }}/issues/777))
+- Add SVG support to Jekyll/WEBrick. ([#407]({{ site.repository }}/issues/407), [#406]({{ site.repository }}/issues/406))
+- Prevent custom destination from causing continuous regen on watch ([#528]({{ site.repository }}/issues/528), [#820]({{ site.repository }}/issues/820), [#862]({{ site.repository }}/issues/862))
+
+### Site Enhancements
+{: #site-enhancements-v1-0-0}
+- Responsify ([#860]({{ site.repository }}/issues/860))
+- Fix spelling, punctuation and phrasal errors ([#989]({{ site.repository }}/issues/989))
+- Update quickstart instructions with `new` command ([#966]({{ site.repository }}/issues/966))
+- Add docs for page.excerpt ([#956]({{ site.repository }}/issues/956))
+- Add docs for page.path ([#951]({{ site.repository }}/issues/951))
+- Clean up site docs to prepare for 1.0 release ([#918]({{ site.repository }}/issues/918))
+- Bring site into master branch with better preview/deploy ([#709]({{ site.repository }}/issues/709))
+- Redesigned site ([#583]({{ site.repository }}/issues/583))
+
+### Development Fixes
+{: #development-fixes-v1-0-0}
+- Exclude Cucumber 1.2.4, which causes tests to fail in 1.9.2 ([#938]({{ site.repository }}/issues/938))
+- Added "features:html" rake task for debugging purposes, cleaned up
+ Cucumber profiles ([#832]({{ site.repository }}/issues/832))
+- Explicitly require HTTPS rubygems source in Gemfile ([#826]({{ site.repository }}/issues/826))
+- Changed Ruby version for development to 1.9.3-p374 from p362 ([#801]({{ site.repository }}/issues/801))
+- Including a link to the GitHub Ruby style guide in CONTRIBUTING.md ([#806]({{ site.repository }}/issues/806))
+- Added script/bootstrap ([#776]({{ site.repository }}/issues/776))
+- Running Simplecov under 2 conditions: ENV(COVERAGE)=true and with Ruby version
+ of greater than 1.9 ([#771]({{ site.repository }}/issues/771))
+- Switch to Simplecov for coverage report ([#765]({{ site.repository }}/issues/765))
+
+
+## 0.12.1 / 2013-02-19
+{: #v0-12-1}
+
+### Minor Enhancements
+{: #minor-enhancements-v0-12-1}
+- Update Kramdown version to 0.14.1 ([#744]({{ site.repository }}/issues/744))
+- Test Enhancements
+- Update Rake version to 10.0.3 ([#744]({{ site.repository }}/issues/744))
+- Update Shoulda version to 3.3.2 ([#744]({{ site.repository }}/issues/744))
+- Update Redcarpet version to 2.2.2 ([#744]({{ site.repository }}/issues/744))
+
+
+## 0.12.0 / 2012-12-22
+{: #v0-12-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v0-12-0}
+- Add ability to explicitly specify included files ([#261]({{ site.repository }}/issues/261))
+- Add `--default-mimetype` option ([#279]({{ site.repository }}/issues/279))
+- Allow setting of RedCloth options ([#284]({{ site.repository }}/issues/284))
+- Add `post_url` Liquid tag for internal post linking ([#369]({{ site.repository }}/issues/369))
+- Allow multiple plugin dirs to be specified ([#438]({{ site.repository }}/issues/438))
+- Inline TOC token support for RDiscount ([#333]({{ site.repository }}/issues/333))
+- Add the option to specify the paginated url format ([#342]({{ site.repository }}/issues/342))
+- Swap out albino for pygments.rb ([#569]({{ site.repository }}/issues/569))
+- Support Redcarpet 2 and fenced code blocks ([#619]({{ site.repository }}/issues/619))
+- Better reporting of Liquid errors ([#624]({{ site.repository }}/issues/624))
+- Bug Fixes
+- Allow some special characters in highlight names
+- URL escape category names in URL generation ([#360]({{ site.repository }}/issues/360))
+- Fix error with `limit_posts` ([#442]({{ site.repository }}/issues/442))
+- Properly select dotfile during directory scan ([#363]({{ site.repository }}/issues/363), [#431]({{ site.repository }}/issues/431), [#377]({{ site.repository }}/issues/377))
+- Allow setting of Kramdown `smart_quotes` ([#482]({{ site.repository }}/issues/482))
+- Ensure front matter is at start of file ([#562]({{ site.repository }}/issues/562))
+
+
+## 0.11.2 / 2011-12-27
+{: #v0-11-2}
+- Bug Fixes
+- Fix gemspec
+
+
+## 0.11.1 / 2011-12-27
+{: #v0-11-1}
+- Bug Fixes
+- Fix extra blank line in highlight blocks ([#409]({{ site.repository }}/issues/409))
+- Update dependencies
+
+
+## 0.11.0 / 2011-07-10
+{: #v0-11-0}
+
+### Major Enhancements
+{: #major-enhancements-v0-11-0}
+- Add command line importer functionality ([#253]({{ site.repository }}/issues/253))
+- Add Redcarpet Markdown support ([#318]({{ site.repository }}/issues/318))
+- Make markdown/textile extensions configurable ([#312]({{ site.repository }}/issues/312))
+- Add `markdownify` filter
+
+### Minor Enhancements
+{: #minor-enhancements-v0-11-0}
+- Switch to Albino gem
+- Bundler support
+- Use English library to avoid hoops ([#292]({{ site.repository }}/issues/292))
+- Add Posterous importer ([#254]({{ site.repository }}/issues/254))
+- Fixes for Wordpress importer ([#274]({{ site.repository }}/issues/274), [#252]({{ site.repository }}/issues/252), [#271]({{ site.repository }}/issues/271))
+- Better error message for invalid post date ([#291]({{ site.repository }}/issues/291))
+- Print formatted fatal exceptions to stdout on build failure
+- Add Tumblr importer ([#323]({{ site.repository }}/issues/323))
+- Add Enki importer ([#320]({{ site.repository }}/issues/320))
+- Bug Fixes
+- Secure additional path exploits
+
+
+## 0.10.0 / 2010-12-16
+{: #v0-10-0}
+- Bug Fixes
+- Add `--no-server` option.
+
+
+## 0.9.0 / 2010-12-15
+{: #v0-9-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v0-9-0}
+- Use OptionParser's `[no-]` functionality for better boolean parsing.
+- Add Drupal migrator ([#245]({{ site.repository }}/issues/245))
+- Complain about YAML and Liquid errors ([#249]({{ site.repository }}/issues/249))
+- Remove orphaned files during regeneration ([#247]({{ site.repository }}/issues/247))
+- Add Marley migrator ([#28]({{ site.repository }}/issues/28))
+
+
+## 0.8.0 / 2010-11-22
+{: #v0-8-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v0-8-0}
+- Add wordpress.com importer ([#207]({{ site.repository }}/issues/207))
+- Add `--limit-posts` cli option ([#212]({{ site.repository }}/issues/212))
+- Add `uri_escape` filter ([#234]({{ site.repository }}/issues/234))
+- Add `--base-url` cli option ([#235]({{ site.repository }}/issues/235))
+- Improve MT migrator ([#238]({{ site.repository }}/issues/238))
+- Add kramdown support ([#239]({{ site.repository }}/issues/239))
+- Bug Fixes
+- Fixed filename basename generation ([#208]({{ site.repository }}/issues/208))
+- Set mode to UTF8 on Sequel connections ([#237]({{ site.repository }}/issues/237))
+- Prevent `_includes` dir from being a symlink
+
+
+## 0.7.0 / 2010-08-24
+{: #v0-7-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v0-7-0}
+- Add support for rdiscount extensions ([#173]({{ site.repository }}/issues/173))
+- Bug Fixes
+- Highlight should not be able to render local files
+- The site configuration may not always provide a 'time' setting ([#184]({{ site.repository }}/issues/184))
+
+
+## 0.6.2 / 2010-06-25
+{: #v0-6-2}
+- Bug Fixes
+- Fix Rakefile 'release' task (tag pushing was missing origin)
+- Ensure that RedCloth is loaded when textilize filter is used ([#183]({{ site.repository }}/issues/183))
+- Expand source, destination, and plugin paths ([#180]({{ site.repository }}/issues/180))
+- Fix `page.url` to include full relative path ([#181]({{ site.repository }}/issues/181))
+
+
+## 0.6.1 / 2010-06-24
+{: #v0-6-1}
+- Bug Fixes
+- Fix Markdown Pygments prefix and suffix ([#178]({{ site.repository }}/issues/178))
+
+
+## 0.6.0 / 2010-06-23
+{: #v0-6-0}
+
+### Major Enhancements
+{: #major-enhancements-v0-6-0}
+- Proper plugin system ([#19]({{ site.repository }}/issues/19), [#100]({{ site.repository }}/issues/100))
+- Add safe mode so unsafe converters/generators can be added
+- Maruku is now the only processor dependency installed by default.
+ Other processors will be lazy-loaded when necessary (and prompt the
+ user to install them when necessary) ([#57]({{ site.repository }}/issues/57))
+
+### Minor Enhancements
+{: #minor-enhancements-v0-6-0}
+- Inclusion/exclusion of future dated posts ([#59]({{ site.repository }}/issues/59))
+- Generation for a specific time ([#59]({{ site.repository }}/issues/59))
+- Allocate `site.time` on render not per site_payload invocation ([#59]({{ site.repository }}/issues/59))
+- Pages now present in the site payload and can be used through the
+ `site.pages` and `site.html_pages` variables
+- Generate phase added to site#process and pagination is now a generator
+- Switch to RakeGem for build/test process
+- Only regenerate static files when they have changed ([#142]({{ site.repository }}/issues/142))
+- Allow arbitrary options to Pygments ([#31]({{ site.repository }}/issues/31))
+- Allow URL to be set via command line option ([#147]({{ site.repository }}/issues/147))
+- Bug Fixes
+- Render highlighted code for non markdown/textile pages ([#116]({{ site.repository }}/issues/116))
+- Fix highlighting on Ruby 1.9 ([#65]({{ site.repository }}/issues/65))
+- Fix extension munging when pretty permalinks are enabled ([#64]({{ site.repository }}/issues/64))
+- Stop sorting categories ([#33]({{ site.repository }}/issues/33))
+- Preserve generated attributes over front matter ([#119]({{ site.repository }}/issues/119))
+- Fix source directory binding using `Dir.pwd` ([#75]({{ site.repository }}/issues/75))
+
+
+## 0.5.7 / 2010-01-12
+{: #v0-5-7}
+
+### Minor Enhancements
+{: #minor-enhancements-v0-5-7}
+- Allow overriding of post date in the front matter ([#62]({{ site.repository }}/issues/62), [#38]({{ site.repository }}/issues/38))
+- Bug Fixes
+- Categories isn't always an array ([#73]({{ site.repository }}/issues/73))
+- Empty tags causes error in read_posts ([#84]({{ site.repository }}/issues/84))
+- Fix pagination to adhere to read/render/write paradigm
+- Test Enhancement
+- Cucumber features no longer use site.posts.first where a better
+ alternative is available
+
+
+## 0.5.6 / 2010-01-08
+{: #v0-5-6}
+- Bug Fixes
+- Require redcloth >= 4.2.1 in tests ([#92]({{ site.repository }}/issues/92))
+- Don't break on triple dashes in yaml front matter ([#93]({{ site.repository }}/issues/93))
+
+### Minor Enhancements
+{: #minor-enhancements-v0-5-6}
+- Allow .mkd as markdown extension
+- Use $stdout/err instead of constants ([#99]({{ site.repository }}/issues/99))
+- Properly wrap code blocks ([#91]({{ site.repository }}/issues/91))
+- Add javascript mime type for webrick ([#98]({{ site.repository }}/issues/98))
+
+
+## 0.5.5 / 2010-01-08
+{: #v0-5-5}
+- Bug Fixes
+- Fix pagination % 0 bug ([#78]({{ site.repository }}/issues/78))
+- Ensure all posts are processed first ([#71]({{ site.repository }}/issues/71))
+
+
+## NOTE
+- After this point I will no longer be giving credit in the history;
+ that is what the commit log is for.
+
+
+## 0.5.4 / 2009-08-23
+{: #v0-5-4}
+- Bug Fixes
+- Do not allow symlinks (security vulnerability)
+
+
+## 0.5.3 / 2009-07-14
+{: #v0-5-3}
+- Bug Fixes
+- Solving the permalink bug where non-html files wouldn't work
+ ([@jeffrydegrande](https://github.com/jeffrydegrande))
+
+
+## 0.5.2 / 2009-06-24
+{: #v0-5-2}
+- Enhancements
+- Added --paginate option to the executable along with a paginator object
+ for the payload ([@calavera](https://github.com/calavera))
+- Upgraded RedCloth to 4.2.1, which makes `` tags work once
+ again.
+- Configuration options set in config.yml are now available through the
+ site payload ([@vilcans](https://github.com/vilcans))
+- Posts can now have an empty YAML front matter or none at all
+ (@ bahuvrihi)
+- Bug Fixes
+- Fixing Ruby 1.9 issue that requires `#to_s` on the err object
+ ([@Chrononaut](https://github.com/Chrononaut))
+- Fixes for pagination and ordering posts on the same day ([@ujh](https://github.com/ujh))
+- Made pages respect permalinks style and permalinks in yml front matter
+ ([@eugenebolshakov](https://github.com/eugenebolshakov))
+- Index.html file should always have index.html permalink
+ ([@eugenebolshakov](https://github.com/eugenebolshakov))
+- Added trailing slash to pretty permalink style so Apache is happy
+ ([@eugenebolshakov](https://github.com/eugenebolshakov))
+- Bad markdown processor in config fails sooner and with better message
+ (@ gcnovus)
+- Allow CRLFs in yaml front matter ([@juretta](https://github.com/juretta))
+- Added Date#xmlschema for Ruby versions < 1.9
+
+
+## 0.5.1 / 2009-05-06
+{: #v0-5-1}
+
+### Major Enhancements
+{: #major-enhancements-v0-5-1}
+- Next/previous posts in site payload ([@pantulis](https://github.com/pantulis), [@tomo](https://github.com/tomo))
+- Permalink templating system
+- Moved most of the README out to the GitHub wiki
+- Exclude option in configuration so specified files won't be brought over
+ with generated site ([@duritong](https://github.com/duritong))
+- Bug Fixes
+- Making sure config.yaml references are all gone, using only config.yml
+- Fixed syntax highlighting breaking for UTF-8 code ([@henrik](https://github.com/henrik))
+- Worked around RDiscount bug that prevents Markdown from getting parsed
+ after highlight ([@henrik](https://github.com/henrik))
+- CGI escaped post titles ([@Chrononaut](https://github.com/Chrononaut))
+
+
+## 0.5.0 / 2009-04-07
+{: #v0-5-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v0-5-0}
+- Ability to set post categories via YAML ([@qrush](https://github.com/qrush))
+- Ability to set prevent a post from publishing via YAML ([@qrush](https://github.com/qrush))
+- Add textilize filter ([@willcodeforfoo](https://github.com/willcodeforfoo))
+- Add 'pretty' permalink style for wordpress-like urls ([@dysinger](https://github.com/dysinger))
+- Made it possible to enter categories from YAML as an array ([@Chrononaut](https://github.com/Chrononaut))
+- Ignore Emacs autosave files ([@Chrononaut](https://github.com/Chrononaut))
+- Bug Fixes
+- Use block syntax of popen4 to ensure that subprocesses are properly disposed ([@jqr](https://github.com/jqr))
+- Close open4 streams to prevent zombies ([@rtomayko](https://github.com/rtomayko))
+- Only query required fields from the WP Database ([@ariejan](https://github.com/ariejan))
+- Prevent `_posts` from being copied to the destination directory ([@bdimcheff](https://github.com/bdimcheff))
+- Refactors
+- Factored the filtering code into a method ([@Chrononaut](https://github.com/Chrononaut))
+- Fix tests and convert to Shoulda ([@qrush](https://github.com/qrush), [@technicalpickles](https://github.com/technicalpickles))
+- Add Cucumber acceptance test suite ([@qrush](https://github.com/qrush), [@technicalpickles](https://github.com/technicalpickles))
+
+
+## 0.4.1
+
+### Minor Enhancements
+{: #minor-enhancements-v--}
+- Changed date format on wordpress converter (zeropadding) ([@dysinger](https://github.com/dysinger))
+- Bug Fixes
+- Add Jekyll binary as executable to gemspec ([@dysinger](https://github.com/dysinger))
+
+
+## 0.4.0 / 2009-02-03
+{: #v0-4-0}
+
+### Major Enhancements
+{: #major-enhancements-v0-4-0}
+- Switch to Jeweler for packaging tasks
+
+### Minor Enhancements
+{: #minor-enhancements-v0-4-0}
+- Type importer ([@codeslinger](https://github.com/codeslinger))
+- `site.topics` accessor ([@baz](https://github.com/baz))
+- Add `array_to_sentence_string` filter ([@mchung](https://github.com/mchung))
+- Add a converter for textpattern ([@PerfectlyNormal](https://github.com/PerfectlyNormal))
+- Add a working Mephisto / MySQL converter ([@ivey](https://github.com/ivey))
+- Allowing .htaccess files to be copied over into the generated site ([@briandoll](https://github.com/briandoll))
+- Add option to not put file date in permalink URL ([@mreid](https://github.com/mreid))
+- Add line number capabilities to highlight blocks ([@jcon](https://github.com/jcon))
+- Bug Fixes
+- Fix permalink behavior ([@cavalle](https://github.com/cavalle))
+- Fixed an issue with pygments, markdown, and newlines ([@zpinter](https://github.com/zpinter))
+- Ampersands need to be escaped ([@pufuwozu](https://github.com/pufuwozu), [@ap](https://github.com/ap))
+- Test and fix the site.categories hash ([@zzot](https://github.com/zzot))
+- Fix site payload available to files ([@matrix9180](https://github.com/matrix9180))
+
+
+## 0.3.0 / 2008-12-24
+{: #v0-3-0}
+
+### Major Enhancements
+{: #major-enhancements-v0-3-0}
+- Added `--server` option to start a simple WEBrick server on destination
+ directory ([@johnreilly](https://github.com/johnreilly) and [@mchung](https://github.com/mchung))
+
+### Minor Enhancements
+{: #minor-enhancements-v0-3-0}
+- Added post categories based on directories containing `_posts` ([@mreid](https://github.com/mreid))
+- Added post topics based on directories underneath `_posts`
+- Added new date filter that shows the full month name ([@mreid](https://github.com/mreid))
+- Merge Post's YAML front matter into its to_liquid payload ([@remi](https://github.com/remi))
+- Restrict includes to regular files underneath `_includes`
+- Bug Fixes
+- Change YAML delimiter matcher so as to not chew up 2nd level markdown
+ headers ([@mreid](https://github.com/mreid))
+- Fix bug that meant page data (such as the date) was not available in
+ templates ([@mreid](https://github.com/mreid))
+- Properly reject directories in `_layouts`
+
+
+## 0.2.1 / 2008-12-15
+{: #v0-2-1}
+- Major Changes
+- Use Maruku (pure Ruby) for Markdown by default ([@mreid](https://github.com/mreid))
+- Allow use of RDiscount with `--rdiscount` flag
+
+### Minor Enhancements
+{: #minor-enhancements-v0-2-1}
+- Don't load directory_watcher unless it's needed ([@pjhyett](https://github.com/pjhyett))
+
+
+## 0.2.0 / 2008-12-14
+{: #v0-2-0}
+- Major Changes
+- related_posts is now found in `site.related_posts`
+
+
+## 0.1.6 / 2008-12-13
+{: #v0-1-6}
+- Major Features
+- Include files in `_includes` with {% raw %}`{% include x.textile %}`{% endraw %}
+
+
+## 0.1.5 / 2008-12-12
+{: #v0-1-5}
+
+### Major Enhancements
+{: #major-enhancements-v0-1-5}
+- Code highlighting with Pygments if `--pygments` is specified
+- Disable true LSI by default, enable with `--lsi`
+
+### Minor Enhancements
+{: #minor-enhancements-v0-1-5}
+- Output informative message if RDiscount is not available ([@JackDanger](https://github.com/JackDanger))
+- Bug Fixes
+- Prevent Jekyll from picking up the output directory as a source ([@JackDanger](https://github.com/JackDanger))
+- Skip `related_posts` when there is only one post ([@JackDanger](https://github.com/JackDanger))
+
+
+## 0.1.4 / 2008-12-08
+{: #v0-1-4}
+- Bug Fixes
+- DATA does not work properly with rubygems
+
+
+## 0.1.3 / 2008-12-06
+{: #v0-1-3}
+- Major Features
+- Markdown support ([@vanpelt](https://github.com/vanpelt))
+- Mephisto and CSV converters ([@vanpelt](https://github.com/vanpelt))
+- Code hilighting ([@vanpelt](https://github.com/vanpelt))
+- Autobuild
+- Bug Fixes
+- Accept both `\r\n` and `\n` in YAML header ([@vanpelt](https://github.com/vanpelt))
+
+
+## 0.1.2 / 2008-11-22
+{: #v0-1-2}
+- Major Features
+- Add a real "related posts" implementation using Classifier
+- Command Line Changes
+- Allow cli to be called with 0, 1, or 2 args intuiting dir paths
+ if they are omitted
+
+
+## 0.1.1 / 2008-11-22
+{: #v0-1-1}
+- Minor Additions
+- Posts now support introspectional data e.g. {% raw %}`{{ page.url }}`{% endraw %}
+
+
+## 0.1.0 / 2008-11-05
+{: #v0-1-0}
+- First release
+- Converts posts written in Textile
+- Converts regular site pages
+- Simple copy of binary files
+
+
+## 0.0.0 / 2008-10-19
+{: #v0-0-0}
+- Birthday!
diff --git a/_docs/index.md b/_docs/index.md
new file mode 100755
index 0000000..27b2da2
--- /dev/null
+++ b/_docs/index.md
@@ -0,0 +1,58 @@
+---
+layout: docs
+title: Welcome
+next_section: quickstart
+permalink: /docs/home/
+---
+
+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, and give you some advice on participating in the future
+development of Jekyll itself.
+
+## So what is Jekyll, exactly?
+
+Jekyll is a simple, blog-aware, static site generator. It takes a template
+directory containing raw text files in various formats, runs it through
+[Markdown](http://daringfireball.net/projects/markdown/) (or
+[Textile](http://redcloth.org/textile)) and
+[Liquid](https://github.com/Shopify/liquid/wiki)
+converters, and spits out a complete, ready-to-publish static website suitable
+for serving with your favorite web server. Jekyll also happens to be the engine
+behind [GitHub Pages](http://pages.github.com), which means you can use Jekyll
+to host your project’s page, blog, or website from GitHub’s servers **for
+free**.
+
+## Helpful Hints
+
+Throughout this guide there are a number of small-but-handy pieces of
+information that can make using Jekyll easier, more interesting, and less
+hazardous. Here’s what to look out for.
+
+
+
ProTips™ help you get more from Jekyll
+
These are tips and tricks that will help you be a Jekyll wizard!
+
+
+
+
Notes are handy pieces of information
+
These are for the extra tidbits sometimes necessary to understand
+ Jekyll.
+
+
+
+
Warnings help you not blow things up
+
Be aware of these messages if you wish to avoid certain death.
+
+
+
+
You'll see this by a feature that hasn't been released
+
Some pieces of this website are for future versions of Jekyll that
+ are not yet released.
+
+
+If you come across anything along the way that we haven’t covered, or if you
+know of a tip you think others would find handy, please [file an
+issue]({{ site.repository }}/issues/new) and we’ll see about
+including it in this guide.
diff --git a/_docs/installation.md b/_docs/installation.md
new file mode 100755
index 0000000..058879e
--- /dev/null
+++ b/_docs/installation.md
@@ -0,0 +1,107 @@
+---
+layout: docs
+title: Installation
+prev_section: quickstart
+next_section: usage
+permalink: /docs/installation/
+---
+
+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]({{ site.repository }}/issues/new) (or submit a pull request)
+describing the issue you encountered and how we might make the process easier.
+
+### Requirements
+
+Installing Jekyll is easy and straight-forward, but there are a few requirements
+you’ll need to make sure your system has before you start.
+
+- [Ruby](http://www.ruby-lang.org/en/downloads/) (including development
+ headers)
+- [RubyGems](http://rubygems.org/pages/download)
+- Linux, Unix, or Mac OS X
+- [NodeJS](http://nodejs.org), or another JavaScript runtime (for
+ CoffeeScript support).
+
+
+
Running Jekyll on Windows
+
+ While Windows is not officially supported, it is possible to get it running
+ on Windows. Special instructions can be found on our
+ Windows-specific docs page.
+
+
+
+## Install with RubyGems
+
+The best way to install Jekyll is via
+[RubyGems](http://rubygems.org/pages/download). At the terminal prompt,
+simply run the following command to install Jekyll:
+
+{% highlight bash %}
+$ gem install jekyll
+{% endhighlight %}
+
+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]({{ site.repository }}/issues/new) so the Jekyll
+community can improve the experience for everyone.
+
+
+
Installing Xcode Command-Line Tools
+
+ If you run into issues installing Jekyll's dependencies which make use of
+ native extensions and are using Mac OS X, you will need to install Xcode
+ and the Command-Line Tools it ships with. Download in
+ Preferences → Downloads → Components.
+
+
+
+## Pre-releases
+
+In order to install a pre-release, make sure you have all the requirements
+installed properly and run:
+
+{% highlight bash %}
+gem install jekyll --pre
+{% endhighlight %}
+
+This will install the latest pre-release. If you want a particular pre-release,
+use the `-v` switch to indicate the version you'd like to install:
+
+{% highlight bash %}
+gem install jekyll -v '2.0.0.alpha.1'
+{% endhighlight %}
+
+If you'd like to install a development version of Jekyll, the process is a bit
+more involved. This gives you the advantage of having the latest and greatest,
+but may be unstable.
+
+{% highlight bash %}
+$ git clone git://github.com/jekyll/jekyll.git
+$ cd jekyll
+$ script/bootstrap
+$ bundle exec rake build
+$ ls pkg/*.gem | head -n 1 | xargs gem install -l
+{% endhighlight %}
+
+## Optional Extras
+
+There are a number of (optional) extra features that Jekyll supports that you
+may want to install, depending on how you plan to use Jekyll. These extras
+include LaTeX support, and the use of alternative content rendering engines.
+Check out [the extras page](../extras/) for more information.
+
+
+
ProTip™: Enable Syntax Highlighting
+
+ If you’re the kind of person who is using Jekyll, then chances are you’ll
+ want to enable syntax highlighting using Pygments
+ or Rouge. You should really
+ check out how to
+ do that before you go any farther.
+
+
+
+Now that you’ve got everything installed, let’s get to work!
diff --git a/_docs/migrations.md b/_docs/migrations.md
new file mode 100755
index 0000000..a080c6c
--- /dev/null
+++ b/_docs/migrations.md
@@ -0,0 +1,11 @@
+---
+layout: docs
+title: Blog migrations
+prev_section: assets
+next_section: templates
+permalink: /docs/migrations/
+---
+
+If you’re switching to Jekyll from another blogging system, Jekyll’s importers
+can help you with the move. To learn more about importing your site to Jekyll,
+visit our [`jekyll-import` docs site](http://import.jekyllrb.com/docs/home/).
diff --git a/_docs/pages.md b/_docs/pages.md
new file mode 100755
index 0000000..e7b837f
--- /dev/null
+++ b/_docs/pages.md
@@ -0,0 +1,86 @@
+---
+layout: docs
+title: Creating pages
+prev_section: drafts
+next_section: variables
+permalink: /docs/pages/
+---
+
+In addition to [writing posts](../posts/), another thing you may want to do with
+your Jekyll site is create static pages. By taking advantage of the way Jekyll
+copies files and directories, this is easy to do.
+
+## Homepage
+
+Just about every web server configuration you come across will look for an HTML
+file called `index.html` (by convention) in the site's root folder and display
+that as the homepage. Unless the web server you’re using is configured to look
+for some different filename as the default, this file will turn into the
+homepage of your Jekyll-generated site.
+
+
+
ProTip™: Use layouts on your homepage
+
+ Any HTML file on your site can use layouts and/or includes, even the
+ homepage. Common content, like headers and footers, make excellent
+ candidates for extraction into a layout.
+
+
+
+## Where additional pages live
+
+Where you put HTML files for pages depends on how you want the pages to work.
+There are two main ways of creating pages:
+
+- Place named HTML files for each page in your site's root folder.
+- 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.
+
+### Named HTML files
+
+The simplest way of adding a page is just to add an HTML file in the root
+directory with a suitable name for the page you want to create. For a site with
+a homepage, an about page, and a contact page, here’s what the root directory
+and associated URLs might look like:
+
+{% highlight bash %}
+.
+|-- _config.yml
+|-- _includes/
+|-- _layouts/
+|-- _posts/
+|-- _site/
+|-- about.html # => http://example.com/about.html
+|-- index.html # => http://example.com/
+└── contact.html # => http://example.com/contact.html
+{% endhighlight %}
+
+### Named folders containing index HTML files
+
+There is nothing wrong with the above method, however some people like to keep
+their URLs free from things like filename extensions. To achieve clean URLs for
+pages using Jekyll, you simply need to create a folder for each top-level page
+you want, and then place an `index.html` file in each page’s folder. This way
+the page URL ends up being the folder name, and the web server will serve up the
+respective `index.html` file. Here's an example of what this structure might
+look like:
+
+{% highlight bash %}
+.
+├── _config.yml
+├── _includes/
+├── _layouts/
+├── _posts/
+├── _site/
+├── about/
+| └── index.html # => http://example.com/about/
+├── contact/
+| └── index.html # => http://example.com/contact/
+└── index.html # => http://example.com/
+{% endhighlight %}
+
+This approach may not suit everyone, but for people who like clean URLs it’s
+simple and it works. In the end the decision is yours!
diff --git a/_docs/pagination.md b/_docs/pagination.md
new file mode 100755
index 0000000..3bb7d13
--- /dev/null
+++ b/_docs/pagination.md
@@ -0,0 +1,212 @@
+---
+layout: docs
+title: Pagination
+prev_section: permalinks
+next_section: plugins
+permalink: /docs/pagination/
+---
+
+With many websites—especially blogs—it’s very common to break the main listing
+of posts up into smaller lists and display them over multiple pages. Jekyll has
+pagination built-in, so you can automatically generate the appropriate files and
+folders you need for paginated listings.
+
+
+
Pagination only works within HTML files
+
+ Pagination does not work with Markdown or Textile files in your Jekyll site.
+ It will only work when used within HTML files. Since you’ll likely be using
+ this for the list of Posts, this shouldn’t be an issue.
+
+
+
+## Enable pagination
+
+To enable pagination for your blog, add a line to the `_config.yml` file that
+specifies how many items should be displayed per page:
+
+{% highlight yaml %}
+paginate: 5
+{% endhighlight %}
+
+The number should be the maximum number of Posts you’d like to be displayed per-
+page in the generated site.
+
+You may also specify where the destination of the pagination pages:
+
+{% highlight yaml %}
+paginate_path: "blog/page:num/"
+{% endhighlight %}
+
+This will read in `blog/index.html`, send it each pagination page in Liquid as `paginator`
+and write the output to `blog/page:num/`, where `:num` is the pagination page number,
+starting with `2`. If a site has 12 posts and specifies `paginate: 5`, Jekyll will write
+`blog/index.html` with the first 5 posts, `blog/page2/index.html` with the next 5 posts
+and `blog/page3/index.html` with the last 2 posts into the destination directory.
+
+## Liquid Attributes Available
+
+The pagination plugin exposes the `paginator` liquid object with the following
+attributes:
+
+
+
+
+
+
Attribute
+
Description
+
+
+
+
+
page
+
current page number
+
+
+
per_page
+
number of posts per page
+
+
+
posts
+
a list of posts for the current page
+
+
+
total_posts
+
total number of posts in the site
+
+
+
total_pages
+
number of pagination pages
+
+
+
previous_page
+
+
+ page number of the previous pagination page,
+ or nil if no previous page exists
+
+
+
+
+
previous_page_path
+
+
+ path of previous pagination page,
+ or nil if no previous page exists
+
+
+
+
+
next_page
+
+
+ page number of the next pagination page,
+ or nil if no subsequent page exists
+
+
+
+
+
next_page_path
+
+
+ path of next pagination page,
+ or nil if no subsequent page exists
+
+
+
+
+
+
+
+
+
Pagination does not support tags or categories
+
Pagination pages through every post in the posts
+ 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. It cannot include any collection of
+ documents because it is restricted to posts.
+
+
+## Render the paginated Posts
+
+The next thing you need to do is to actually display your posts in a list using
+the `paginator` variable that will now be available to you. You’ll probably want
+to do this in one of the main pages of your site. Here’s one example of a simple
+way of rendering paginated Posts in a HTML file:
+
+{% highlight html %}
+{% raw %}
+---
+layout: default
+title: My Blog
+---
+
+
+{% for post in paginator.posts %}
+
+ {% if paginator.previous_page %}
+ Previous
+ {% else %}
+ Previous
+ {% endif %}
+ Page: {{ paginator.page }} of {{ paginator.total_pages }}
+ {% if paginator.next_page %}
+ Next
+ {% else %}
+ Next
+ {% endif %}
+
+{% endraw %}
+{% endhighlight %}
+
+
+
Beware the page one edge-case
+
+ Jekyll does not generate a ‘page1’ folder, so the above code will not work
+ when a /page1 link is produced. See below for a way to handle
+ this if it’s a problem for you.
+
+
+
+The following HTML snippet should handle page one, and render a list of each
+page with links to all but the current page.
+
+{% highlight html %}
+{% raw %}
+{% if paginator.total_pages > 1 %}
+
+{% endif %}
+{% endraw %}
+{% endhighlight %}
diff --git a/_docs/permalinks.md b/_docs/permalinks.md
new file mode 100755
index 0000000..dbcee2e
--- /dev/null
+++ b/_docs/permalinks.md
@@ -0,0 +1,199 @@
+---
+layout: docs
+title: Permalinks
+prev_section: templates
+next_section: pagination
+permalink: /docs/permalinks/
+---
+
+Jekyll supports a flexible way to build your site’s URLs. You can specify the
+permalinks for your site through the [Configuration](../configuration/) or in the
+[YAML Front Matter](../frontmatter/) for each post. You’re free to choose one of
+the built-in styles to create your links or craft your own. The default style is
+`date`.
+
+Permalinks are constructed by creating a template URL where dynamic elements are
+represented by colon-prefixed keywords. For example, the default `date`
+permalink is defined as `/:categories/:year/:month/:day/:title.html`.
+
+## Template variables
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
+
year
+
+
+
Year from the Post’s filename
+
+
+
+
+
month
+
+
+
Month from the Post’s filename
+
+
+
+
+
i_month
+
+
+
Month from the Post’s filename without leading zeros.
+
+
+
+
+
day
+
+
+
Day from the Post’s filename
+
+
+
+
+
i_day
+
+
+
Day from the Post’s filename without leading zeros.
+
+
+
+
+
short_year
+
+
+
Year from the Post’s filename without the century.
+
+
+
+
+
title
+
+
+
Title from the Post’s filename
+
+
+
+
+
categories
+
+
+
+ The specified categories for this Post. If a post has multiple
+ categories, Jekyll will create a hierarchy (e.g. /category1/category2).
+ Also Jekyll automatically parses out double slashes in the URLs,
+ so if no categories are present, it will ignore this.
+
+
+
+
+
+
+
+## Built-in permalink styles
+
+**Note:** these may only apply to posts, not to pages, collections or
+static files. For example, `pretty` changes page permalinks from
+`/:path/:basename:output_ext` to `/:page/:basename/` if the page is HTML,
+thus "prettyifying" the page permalink. The `date`, `none`, and all custom
+values do not apply to pages. No permalink style applies to static files,
+and collections have their own means of specifying permalinks. It's all
+rather confusing but check out [Issue #2691](https://github.com/jekyll/jekyll/issues/2691)
+for more background on the subject, and submit a PR if you're adventurous
+enough to fix it all!
+
+
+
+
+
+
Permalink Style
+
URL Template
+
+
+
+
+
+
date
+
+
+
/:categories/:year/:month/:day/:title.html
+
+
+
+
+
pretty
+
+
+
/:categories/:year/:month/:day/:title/
+
+
+
+
+
none
+
+
+
/:categories/:title.html
+
+
+
+
+
+
+## Permalink style examples
+
+Given a post named: `/2009-04-29-slap-chop.textile`
+
+
+
+
+
+
URL Template
+
Resulting Permalink URL
+
+
+
+
+
+
None specified, or permalink: date
+
+
+
/2009/04/29/slap-chop.html
+
+
+
+
+
pretty
+
+
+
/2009/04/29/slap-chop/index.html
+
+
+
+
+
/:month-:day-:year/:title.html
+
+
+
/04-29-2009/slap-chop.html
+
+
+
+
+
/blog/:year/:month/:day/:title
+
+
+
/blog/2009/04/29/slap-chop/index.html
+
+
+
+
+
diff --git a/_docs/plugins.md b/_docs/plugins.md
new file mode 100755
index 0000000..95f57fb
--- /dev/null
+++ b/_docs/plugins.md
@@ -0,0 +1,633 @@
+---
+layout: docs
+title: Plugins
+prev_section: pagination
+next_section: extras
+permalink: /docs/plugins/
+---
+
+Jekyll has a plugin system with hooks that allow you to create custom generated
+content specific to your site. You can run custom code for your site without
+having to modify the Jekyll source itself.
+
+
+
Plugins on GitHub Pages
+
+ GitHub Pages is powered by Jekyll,
+ however all Pages sites are generated using the --safe option
+ to disable custom plugins for security reasons. Unfortunately, this means
+ your plugins won’t work if you’re deploying to GitHub Pages.
+ You can still use GitHub Pages to publish your site, but you’ll need to
+ convert the site locally and push the generated static files to your GitHub
+ repository instead of the Jekyll source files.
+
+
+
+## Installing a plugin
+
+You have 3 options for installing plugins:
+
+1. In your site source root, make a `_plugins` directory. Place your plugins here.
+ Any file ending in `*.rb` inside this directory will be loaded before Jekyll
+ generates your site.
+2. In your `_config.yml` file, add a new array with the key `gems` and the values
+ of the gem names of the plugins you'd like to use. An example:
+
+ gems: [jekyll-test-plugin, jekyll-jsonify, jekyll-assets]
+ # This will require each of these gems automatically.
+3. Add the relevant plugins to a Bundler group in your `Gemfile`. An
+ example:
+
+ group :jekyll_plugins do
+ gem "my-jekyll-plugin"
+ end
+
+
+
+ _plugins and gems
+ can be used simultaneously
+
+
+ You may use both of the aforementioned plugin options simultaneously in the
+ same site if you so choose. Use of one does not restrict the use of the other
+
+
+
+In general, plugins you make will fall into one of three categories:
+
+1. Generators
+2. Converters
+3. Tags
+
+## Generators
+
+You can create a generator when you need Jekyll to create additional content
+based on your own rules.
+
+A generator is a subclass of `Jekyll::Generator` that defines a `generate`
+method, which receives an instance of
+[`Jekyll::Site`]({{ site.repository }}/blob/master/lib/jekyll/site.rb).
+
+Generation is triggered for its side-effects, the return value of `generate` is
+ignored. Jekyll does not assume any particular side-effect to happen, it just
+runs the method.
+
+Generators run after Jekyll has made an inventory of the existing content, and
+before the site is generated. Pages with YAML Front Matters are stored as
+instances of
+[`Jekyll::Page`]({{ site.repository }}/blob/master/lib/jekyll/page.rb)
+and are available via `site.pages`. Static files become instances of
+[`Jekyll::StaticFile`]({{ site.repository }}/blob/master/lib/jekyll/static_file.rb)
+and are available via `site.static_files`. See
+[the Variables documentation page](/docs/variables/) and
+[`Jekyll::Site`]({{ site.repository }}/blob/master/lib/jekyll/site.rb)
+for more details.
+
+For instance, a generator can inject values computed at build time for template
+variables. In the following example the template `reading.html` has two
+variables `ongoing` and `done` that we fill in the generator:
+
+{% highlight ruby %}
+module Reading
+ class Generator < Jekyll::Generator
+ def generate(site)
+ ongoing, done = Book.all.partition(&:ongoing?)
+
+ reading = site.pages.detect {|page| page.name == 'reading.html'}
+ reading.data['ongoing'] = ongoing
+ reading.data['done'] = done
+ end
+ end
+end
+{% endhighlight %}
+
+This is a more complex generator that generates new pages:
+
+{% highlight ruby %}
+module Jekyll
+
+ class CategoryPage < Page
+ def initialize(site, base, dir, category)
+ @site = site
+ @base = base
+ @dir = dir
+ @name = 'index.html'
+
+ self.process(@name)
+ self.read_yaml(File.join(base, '_layouts'), 'category_index.html')
+ self.data['category'] = category
+
+ category_title_prefix = site.config['category_title_prefix'] || 'Category: '
+ self.data['title'] = "#{category_title_prefix}#{category}"
+ end
+ end
+
+ class CategoryPageGenerator < Generator
+ safe true
+
+ def generate(site)
+ if site.layouts.key? 'category_index'
+ dir = site.config['category_dir'] || 'categories'
+ site.categories.each_key do |category|
+ site.pages << CategoryPage.new(site, site.source, File.join(dir, category), category)
+ end
+ end
+ end
+ end
+
+end
+{% endhighlight %}
+
+In this example, our generator will create a series of files under the
+`categories` directory for each category, listing the posts in each category
+using the `category_index.html` layout.
+
+Generators are only required to implement one method:
+
+
+
+
+
+
Method
+
Description
+
+
+
+
+
+
generate
+
+
+
Generates content as a side-effect.
+
+
+
+
+
+
+## Converters
+
+If you have a new markup language you’d like to use with your site, you can
+include it by implementing your own converter. Both the Markdown and Textile
+markup languages are implemented using this method.
+
+
+
Remember your YAML Front Matter
+
+ Jekyll will only convert files that have a YAML header at the top, even for
+ converters you add using a plugin.
+
+
+
+Below is a converter that will take all posts ending in `.upcase` and process
+them using the `UpcaseConverter`:
+
+{% highlight ruby %}
+module Jekyll
+ class UpcaseConverter < Converter
+ safe true
+ priority :low
+
+ def matches(ext)
+ ext =~ /^\.upcase$/i
+ end
+
+ def output_ext(ext)
+ ".html"
+ end
+
+ def convert(content)
+ content.upcase
+ end
+ end
+end
+{% endhighlight %}
+
+Converters should implement at a minimum 3 methods:
+
+
+
+
+
+
Method
+
Description
+
+
+
+
+
+
matches
+
+
+ Does the given extension match this converter’s list of acceptable
+ extensions? Takes one argument: the file’s extension (including the
+ dot). Must return true if it matches, false
+ otherwise.
+
+
+
+
+
output_ext
+
+
+ The extension to be given to the output file (including the dot).
+ Usually this will be ".html".
+
+
+
+
+
convert
+
+
+ Logic to do the content conversion. Takes one argument: the raw content
+ of the file (without YAML Front Matter). Must return a String.
+
+
+
+
+
+
+In our example, `UpcaseConverter#matches` checks if our filename extension is
+`.upcase`, and will render using the converter if it is. It will call
+`UpcaseConverter#convert` to process the content. In our simple converter we’re
+simply uppercasing the entire content string. Finally, when it saves the page,
+it will do so with a `.html` extension.
+
+## Command
+
+As of version 2.5.0, Jekyll can be extended with plugins which provide
+subcommands for the `jekyll` executable. This is possible by including the
+relevant plugins in a `Gemfile` group called `:jekyll_plugins`:
+
+{% highlight ruby %}
+group :jekyll_plugins do
+ gem "my_fancy_jekyll_plugin"
+end
+{% endhighlight %}
+
+Each `Command` must be a subclass of the `Jekyll::Command` class and must
+contain one class method: `init_with_program`. An example:
+
+{% highlight ruby %}
+class MyNewCommand < Jekyll::Command
+ class << self
+ def init_with_program(prog)
+ prog.command(:new) do |c|
+ c.syntax "new [options]"
+ c.description 'Create a new Jekyll site.'
+
+ c.option 'dest', '-d DEST, 'Where the site should go.'
+
+ c.action do |args, options|
+ Jekyll::Site.new_site_at(options['dest'])
+ end
+ end
+ end
+ end
+end
+{% endhighlight %}
+
+Commands should implement this single class method:
+
+
+
+
+
+
Method
+
Description
+
+
+
+
+
+
init_with_program
+
+
+ This method accepts one parameter, the
+ Mercenary::Program
+ instance, which is the Jekyll program itself. Upon the program,
+ commands may be created using the above syntax. For more details,
+ visit the Mercenary repository on GitHub.com.
+
+
+
+
+
+
+## Tags
+
+If you’d like to include custom liquid tags in your site, you can do so by
+hooking into the tagging system. Built-in examples added by Jekyll include the
+`highlight` and `include` tags. Below is an example of a custom liquid tag that
+will output the time the page was rendered:
+
+{% highlight ruby %}
+module Jekyll
+ class RenderTimeTag < Liquid::Tag
+
+ def initialize(tag_name, text, tokens)
+ super
+ @text = text
+ end
+
+ def render(context)
+ "#{@text} #{Time.now}"
+ end
+ end
+end
+
+Liquid::Template.register_tag('render_time', Jekyll::RenderTimeTag)
+{% endhighlight %}
+
+At a minimum, liquid tags must implement:
+
+
+
+
+
+
Method
+
Description
+
+
+
+
+
+
render
+
+
+
Outputs the content of the tag.
+
+
+
+
+
+
+You must also register the custom tag with the Liquid template engine as
+follows:
+
+{% highlight ruby %}
+Liquid::Template.register_tag('render_time', Jekyll::RenderTimeTag)
+{% endhighlight %}
+
+In the example above, we can place the following tag anywhere in one of our
+pages:
+
+{% highlight ruby %}
+{% raw %}
+
{% render_time page rendered at: %}
+{% endraw %}
+{% endhighlight %}
+
+And we would get something like this on the page:
+
+{% highlight html %}
+
page rendered at: Tue June 22 23:38:47 –0500 2010
+{% endhighlight %}
+
+### Liquid filters
+
+You can add your own filters to the Liquid template system much like you can add
+tags above. Filters are simply modules that export their methods to liquid. All
+methods will have to take at least one parameter which represents the input of
+the filter. The return value will be the output of the filter.
+
+{% highlight ruby %}
+module Jekyll
+ module AssetFilter
+ def asset_url(input)
+ "http://www.example.com/#{input}?#{Time.now.to_i}"
+ end
+ end
+end
+
+Liquid::Template.register_filter(Jekyll::AssetFilter)
+{% endhighlight %}
+
+
+
ProTip™: Access the site object using Liquid
+
+ Jekyll lets you access the site object through the
+ context.registers feature of Liquid at context.registers[:site]. For example, you can
+ access the global configuration file _config.yml using
+ context.registers[:site].config.
+
+
+
+### Flags
+
+There are two flags to be aware of when writing a plugin:
+
+
+
+
+
+
Flag
+
Description
+
+
+
+
+
+
safe
+
+
+
+ A boolean flag that informs Jekyll whether this plugin may be safely
+ executed in an environment where arbitrary code execution is not
+ allowed. This is used by GitHub Pages to determine which core plugins
+ may be used, and which are unsafe to run. If your plugin does not
+ allow for arbitrary code execution, set this to true.
+ GitHub Pages still won’t load your plugin, but if you submit it for
+ inclusion in core, it’s best for this to be correct!
+
+
+
+
+
+
priority
+
+
+
+ This flag determines what order the plugin is loaded in. Valid values
+ are: :lowest, :low, :normal,
+ :high, and :highest. Highest priority
+ matches are applied first, lowest priority are applied last.
+
+
+
+
+
+
+
+To use one of the example plugins above as an illustration, here is how you’d
+specify these two flags:
+
+{% highlight ruby %}
+module Jekyll
+ class UpcaseConverter < Converter
+ safe true
+ priority :low
+ ...
+ end
+end
+{% endhighlight %}
+
+## Available Plugins
+
+You can find a few useful plugins at the following locations:
+
+#### Generators
+
+- [ArchiveGenerator by Ilkka Laukkanen](https://gist.github.com/707909): Uses [this archive page](https://gist.github.com/707020) to generate archives.
+- [LESS.js Generator by Andy Fowler](https://gist.github.com/642739): Renders LESS.js files during generation.
+- [Version Reporter by Blake Smith](https://gist.github.com/449491): Creates a version.html file containing the Jekyll version.
+- [Sitemap.xml Generator by Michael Levin](https://github.com/kinnetica/jekyll-plugins): Generates a sitemap.xml file by traversing all of the available posts and pages.
+- [Full-text search by Pascal Widdershoven](https://github.com/PascalW/jekyll_indextank): Adds full-text search to your Jekyll site with a plugin and a bit of JavaScript.
+- [AliasGenerator by Thomas Mango](https://github.com/tsmango/jekyll_alias_generator): Generates redirect pages for posts when an alias is specified in the YAML Front Matter.
+- [Pageless Redirect Generator by Nick Quinlan](https://github.com/nquinlan/jekyll-pageless-redirects): Generates redirects based on files in the Jekyll root, with support for htaccess style redirects.
+- [RssGenerator by Assaf Gelber](https://github.com/agelber/jekyll-rss): Automatically creates an RSS 2.0 feed from your posts.
+- [Monthly archive generator by Shigeya Suzuki](https://github.com/shigeya/jekyll-monthly-archive-plugin): Generator and template which renders monthly archive like MovableType style, based on the work by Ilkka Laukkanen and others above.
+- [Category archive generator by Shigeya Suzuki](https://github.com/shigeya/jekyll-category-archive-plugin): Generator and template which renders category archive like MovableType style, based on Monthly archive generator.
+- [Emoji for Jekyll](https://github.com/yihangho/emoji-for-jekyll): Seamlessly enable emoji for all posts and pages.
+- [Compass integration for Jekyll](https://github.com/mscharley/jekyll-compass): Easily integrate Compass and Sass with your Jekyll website.
+- [Pages Directory by Ben Baker-Smith](https://github.com/bbakersmith/jekyll-pages-directory): Defines a `_pages` directory for page files which routes its output relative to the project root.
+- [Page Collections by Jeff Kolesky](https://github.com/jeffkole/jekyll-page-collections): Generates collections of pages with functionality that resembles posts.
+- [Windows 8.1 Live Tile Generation by Matt Sheehan](https://github.com/sheehamj13/jekyll-live-tiles): Generates Internet Explorer 11 config.xml file and Tile Templates for pinning your site to Windows 8.1.
+- [Jekyll::AutolinkEmail by Ivan Tse](https://github.com/ivantsepp/jekyll-autolink_email): Autolink your emails.
+- [Jekyll::GitMetadata by Ivan Tse](https://github.com/ivantsepp/jekyll-git_metadata): Expose Git metadata for your templates.
+- [Jekyll Http Basic Auth Plugin](https://gist.github.com/snrbrnjna/422a4b7e017192c284b3): Plugin to manage http basic auth for jekyll generated pages and directories.
+
+#### Converters
+
+- [Slim plugin](https://github.com/slim-template/jekyll-slim): Slim converter and includes for Jekyll with support for Liquid tags.
+- [Jade plugin by John Papandriopoulos](https://github.com/snappylabs/jade-jekyll-plugin): Jade converter for Jekyll.
+- [HAML plugin by Sam Z](https://gist.github.com/517556): HAML converter for Jekyll.
+- [HAML-Sass Converter by Adam Pearson](https://gist.github.com/481456): Simple HAML-Sass converter for Jekyll. [Fork](https://gist.github.com/528642) by Sam X.
+- [Sass SCSS Converter by Mark Wolfe](https://gist.github.com/960150): Sass converter which uses the new CSS compatible syntax, based Sam X’s fork above.
+- [LESS Converter by Jason Graham](https://gist.github.com/639920): Convert LESS files to CSS.
+- [LESS Converter by Josh Brown](https://gist.github.com/760265): Simple LESS converter.
+- [Upcase Converter by Blake Smith](https://gist.github.com/449463): An example Jekyll converter.
+- [CoffeeScript Converter by phaer](https://gist.github.com/959938): A [CoffeeScript](http://coffeescript.org) to Javascript converter.
+- [Markdown References by Olov Lassus](https://github.com/olov/jekyll-references): Keep all your markdown reference-style link definitions in one \_references.md file.
+- [Stylus Converter](https://gist.github.com/988201): Convert .styl to .css.
+- [ReStructuredText Converter](https://github.com/xdissent/jekyll-rst): Converts ReST documents to HTML with Pygments syntax highlighting.
+- [Jekyll-pandoc-plugin](https://github.com/dsanson/jekyll-pandoc-plugin): Use pandoc for rendering markdown.
+- [Jekyll-pandoc-multiple-formats](https://github.com/fauno/jekyll-pandoc-multiple-formats) by [edsl](https://github.com/edsl): Use pandoc to generate your site in multiple formats. Supports pandoc’s markdown extensions.
+- [Transform Layouts](https://gist.github.com/1472645): Allows HAML layouts (you need a HAML Converter plugin for this to work).
+- [Org-mode Converter](https://gist.github.com/abhiyerra/7377603): Org-mode converter for Jekyll.
+- [Customized Kramdown Converter](https://github.com/mvdbos/kramdown-with-pygments): Enable Pygments syntax highlighting for Kramdown-parsed fenced code blocks.
+- [Bigfootnotes Plugin](https://github.com/TheFox/jekyll-bigfootnotes): Enables big footnotes for Kramdown.
+
+#### Filters
+
+- [Truncate HTML](https://github.com/MattHall/truncatehtml) by [Matt Hall](http://codebeef.com): A Jekyll filter that truncates HTML while preserving markup structure.
+- [Domain Name Filter by Lawrence Woodman](https://github.com/LawrenceWoodman/domain_name-liquid_filter): Filters the input text so that just the domain name is left.
+- [Summarize Filter by Mathieu Arnold](https://gist.github.com/731597): Remove markup after a `
` tag.
+- [i18n_filter](https://github.com/gacha/gacha.id.lv/blob/master/_plugins/i18n_filter.rb): Liquid filter to use I18n localization.
+- [Smilify](https://github.com/SaswatPadhi/jekyll_smilify) by [SaswatPadhi](https://github.com/SaswatPadhi): Convert text emoticons in your content to themeable smiley pics.
+- [Read in X Minutes](https://gist.github.com/zachleat/5792681) by [zachleat](https://github.com/zachleat): Estimates the reading time of a string (for blog post content).
+- [Jekyll-timeago](https://github.com/markets/jekyll-timeago): Converts a time value to the time ago in words.
+- [pluralize](https://github.com/bdesham/pluralize): Easily combine a number and a word into a gramatically-correct amount like “1 minute” or “2 minute**s**”.
+- [reading_time](https://github.com/bdesham/reading_time): Count words and estimate reading time for a piece of text, ignoring HTML elements that are unlikely to contain running text.
+- [Table of Content Generator](https://github.com/dafi/jekyll-toc-generator): Generate the HTML code containing a table of content (TOC), the TOC can be customized in many way, for example you can decide which pages can be without TOC.
+- [jekyll-humanize](https://github.com/23maverick23/jekyll-humanize): This is a port of the Django app humanize which adds a "human touch" to data. Each method represents a Fluid type filter that can be used in your Jekyll site templates. Given that Jekyll produces static sites, some of the original methods do not make logical sense to port (e.g. naturaltime).
+- [Jekyll-Ordinal](https://github.com/PatrickC8t/Jekyll-Ordinal): Jekyll liquid filter to output a date ordinal such as "st", "nd", "rd", or "th".
+- [Deprecated articles keeper](https://github.com/kzykbys/JekyllPlugins) by [Kazuya Kobayashi](http://blog.kazuya.co/): A simple Jekyll filter which monitor how old an article is.
+- [Jekyll-jalali](https://github.com/mehdisadeghi/jekyll-jalali) by [Mehdi Sadeghi](http://mehdix.ir): A simple Gregorian to Jalali date converter filter.
+
+#### Tags
+
+- [Asset Path Tag](https://github.com/samrayner/jekyll-asset-path-plugin) by [Sam Rayner](http://www.samrayner.com/): Allows organisation of assets into subdirectories by outputting a path for a given file relative to the current post or page.
+- [Delicious Plugin by Christian Hellsten](https://github.com/christianhellsten/jekyll-plugins): Fetches and renders bookmarks from delicious.com.
+- [Ultraviolet Plugin by Steve Alex](https://gist.github.com/480380): Jekyll tag for the [Ultraviolet](https://github.com/grosser/ultraviolet) code highligher.
+- [Tag Cloud Plugin by Ilkka Laukkanen](https://gist.github.com/710577): Generate a tag cloud that links to tag pages.
+- [GIT Tag by Alexandre Girard](https://gist.github.com/730347): Add Git activity inside a list.
+- [MathJax Liquid Tags by Jessy Cowan-Sharp](https://gist.github.com/834610): Simple liquid tags for Jekyll that convert inline math and block equations to the appropriate MathJax script tags.
+- [Non-JS Gist Tag by Brandon Tilley](https://gist.github.com/1027674) A Liquid tag that embeds Gists and shows code for non-JavaScript enabled browsers and readers.
+- [Render Time Tag by Blake Smith](https://gist.github.com/449509): Displays the time a Jekyll page was generated.
+- [Status.net/OStatus Tag by phaer](https://gist.github.com/912466): Displays the notices in a given status.net/ostatus feed.
+- [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. Documentation inline.
+- [oEmbed Tag by Tammo van Lessen](https://gist.github.com/1455726): Enables easy content embedding (e.g. from YouTube, Flickr, Slideshare) via oEmbed.
+- [FlickrSetTag by Thomas Mango](https://github.com/tsmango/jekyll_flickr_set_tag): Generates image galleries from Flickr sets.
+- [Tweet Tag by Scott W. Bradley](https://github.com/scottwb/jekyll-tweet-tag): Liquid tag for [Embedded Tweets](https://dev.twitter.com/docs/embedded-tweets) using Twitter’s shortcodes.
+- [Jekyll Twitter Plugin](https://github.com/rob-murray/jekyll-twitter-plugin): A Liquid tag plugin that renders Tweets from Twitter API. Currently supports the [oEmbed](https://dev.twitter.com/rest/reference/get/statuses/oembed) API.
+- [Jekyll-contentblocks](https://github.com/rustygeldmacher/jekyll-contentblocks): Lets you use Rails-like content_for tags in your templates, for passing content from your posts up to your layouts.
+- [Generate YouTube Embed](https://gist.github.com/1805814) by [joelverhagen](https://github.com/joelverhagen): Jekyll plugin which allows you to embed a YouTube video in your page with the YouTube ID. Optionally specify width and height dimensions. Like “oEmbed Tag” but just for YouTube.
+- [Jekyll-beastiepress](https://github.com/okeeblow/jekyll-beastiepress): FreeBSD utility tags for Jekyll sites.
+- [Jsonball](https://gist.github.com/1895282): Reads json files and produces maps for use in Jekyll files.
+- [Bibjekyll](https://github.com/pablooliveira/bibjekyll): Render BibTeX-formatted bibliographies/citations included in posts and pages using bibtex2html.
+- [Jekyll-citation](https://github.com/archome/jekyll-citation): Render BibTeX-formatted bibliographies/citations included in posts and pages (pure Ruby).
+- [Jekyll Dribbble Set Tag](https://github.com/ericdfields/Jekyll-Dribbble-Set-Tag): Builds Dribbble image galleries from any user.
+- [Debbugs](https://gist.github.com/2218470): Allows posting links to Debian BTS easily.
+- [Refheap_tag](https://github.com/aburdette/refheap_tag): Liquid tag that allows embedding pastes from [refheap](https://refheap.com).
+- [Jekyll-devonly_tag](https://gist.github.com/2403522): A block tag for including markup only during development.
+- [JekyllGalleryTag](https://github.com/redwallhp/JekyllGalleryTag) by [redwallhp](https://github.com/redwallhp): Generates thumbnails from a directory of images and displays them in a grid.
+- [Youku and Tudou Embed](https://gist.github.com/Yexiaoxing/5891929): Liquid plugin for embedding Youku and Tudou videos.
+- [Jekyll-swfobject](https://github.com/sectore/jekyll-swfobject): Liquid plugin for embedding Adobe Flash files (.swf) using [SWFObject](http://code.google.com/p/swfobject/).
+- [Jekyll Picture Tag](https://github.com/robwierzbowski/jekyll-picture-tag): Easy responsive images for Jekyll. Based on the proposed [``](http://picture.responsiveimages.org/) element, polyfilled with Scott Jehl’s [Picturefill](https://github.com/scottjehl/picturefill).
+- [Jekyll Image Tag](https://github.com/robwierzbowski/jekyll-image-tag): Better images for Jekyll. Save image presets, generate resized images, and add classes, alt text, and other attributes.
+- [Ditaa Tag](https://github.com/matze/jekyll-ditaa) by [matze](https://github.com/matze): Renders ASCII diagram art into PNG images and inserts a figure tag.
+- [Jekyll Suggested Tweet](https://github.com/davidensinger/jekyll-suggested-tweet) by [David Ensinger](https://github.com/davidensinger/): A Liquid tag for Jekyll that allows for the embedding of suggested tweets via Twitter’s Web Intents API.
+- [Jekyll Date Chart](https://github.com/GSI/jekyll_date_chart) by [GSI](https://github.com/GSI): Block that renders date line charts based on textile-formatted tables.
+- [Jekyll Image Encode](https://github.com/GSI/jekyll_image_encode) by [GSI](https://github.com/GSI): Tag that renders base64 codes of images fetched from the web.
+- [Jekyll Quick Man](https://github.com/GSI/jekyll_quick_man) by [GSI](https://github.com/GSI): Tag that renders pretty links to man page sources on the internet.
+- [jekyll-font-awesome](https://gist.github.com/23maverick23/8532525): Quickly and easily add Font Awesome icons to your posts.
+- [Lychee Gallery Tag](https://gist.github.com/tobru/9171700) by [tobru](https://github.com/tobru): Include [Lychee](http://lychee.electerious.com/) albums into a post. For an introduction, see [Jekyll meets Lychee - A Liquid Tag plugin](https://tobrunet.ch/articles/jekyll-meets-lychee-a-liquid-tag-plugin/)
+- [Image Set/Gallery Tag](https://github.com/callmeed/jekyll-image-set) by [callmeed](https://github.com/callmeed): Renders HTML for an image gallery from a folder in your Jekyll site. Just pass it a folder name and class/tag options.
+- [jekyll_figure](https://github.com/lmullen/jekyll_figure): Generate figures and captions with links to the figure in a variety of formats
+- [Jekyll Github Sample Tag](https://github.com/bwillis/jekyll-github-sample): A liquid tag to include a sample of a github repo file in your Jekyll site.
+- [Jekyll Project Version Tag](https://github.com/rob-murray/jekyll-version-plugin): A Liquid tag plugin that renders a version identifier for your Jekyll site sourced from the git repository containing your code.
+- [Piwigo Gallery](https://github.com/AlessandroLorenzi/piwigo_gallery) by [Alessandro Lorenzi](http://www.alorenzi.eu/): Jekyll plugin to generate thumbnails from a Piwigo gallery and display them with a Liquid tag
+- [mathml.rb](https://github.com/tmthrgd/jekyll-plugins) by [Tom Thorogood](http://tomthorogood.co.uk/): A plugin to convert TeX mathematics into MathML for display.
+- [webmention_io.rb](https://github.com/aarongustafson/jekyll-webmention_io) by [Aaron Gustafson](http://aaron-gustafson.com/): A plugin to enable [webmention](http://indiewebcamp.com/webmention) integration using [Webmention.io](http://webmention.io). Includes an optional JavaScript for updating webmentions automatically between publishes and, if available, in realtime using WebSockets.
+- [Jekyll 500px Embed](https://github.com/lkorth/jekyll-500px-embed) by [Luke Korth](https://lukekorth.com/). A Liquid tag plugin that embeds [500px](https://500px.com/) photos.
+
+#### Collections
+
+- [Jekyll Plugins by Recursive Design](http://recursive-design.com/projects/jekyll-plugins/): Plugins to generate Project pages from GitHub readmes, a Category page, and a Sitemap generator.
+- [Company website and blog plugins](https://github.com/flatterline/jekyll-plugins) by Flatterline, a [Ruby on Rails development company](http://flatterline.com/): Portfolio/project page generator, team/individual page generator, an author bio liquid tag for use on posts, and a few other smaller plugins.
+- [Jekyll plugins by Aucor](https://github.com/aucor/jekyll-plugins): Plugins for trimming unwanted newlines/whitespace and sorting pages by weight attribute.
+
+#### Other
+
+- [ditaa-ditaa](https://github.com/tmthrgd/ditaa-ditaa) by [Tom Thorogood](http://tomthorogood.co.uk/): a drastic revision of jekyll-ditaa that renders diagrams drawn using ASCII art into PNG images.
+- [Pygments Cache Path by Raimonds Simanovskis](https://github.com/rsim/blog.rayapps.com/blob/master/_plugins/pygments_cache_patch.rb): Plugin to cache syntax-highlighted code from Pygments.
+- [Draft/Publish Plugin by Michael Ivey](https://gist.github.com/49630): Save posts as drafts.
+- [Growl Notification Generator by Tate Johnson](https://gist.github.com/490101): Send Jekyll notifications to Growl.
+- [Growl Notification Hook by Tate Johnson](https://gist.github.com/525267): Better alternative to the above, but requires his “hook” fork.
+- [Related Posts by Lawrence Woodman](https://github.com/LawrenceWoodman/related_posts-jekyll_plugin): Overrides `site.related_posts` to use categories to assess relationship.
+- [Tiered Archives by Eli Naeher](https://gist.github.com/88cda643aa7e3b0ca1e5): Create tiered template variable that allows you to group archives by year and month.
+- [Jekyll-localization](https://github.com/blackwinter/jekyll-localization): Jekyll plugin that adds localization features to the rendering engine.
+- [Jekyll-rendering](https://github.com/blackwinter/jekyll-rendering): Jekyll plugin to provide alternative rendering engines.
+- [Jekyll-pagination](https://github.com/blackwinter/jekyll-pagination): Jekyll plugin to extend the pagination generator.
+- [Jekyll-tagging](https://github.com/pattex/jekyll-tagging): Jekyll plugin to automatically generate a tag cloud and tag pages.
+- [Jekyll-scholar](https://github.com/inukshuk/jekyll-scholar): Jekyll extensions for the blogging scholar.
+- [Jekyll-asset_bundler](https://github.com/moshen/jekyll-asset_bundler): Bundles and minifies JavaScript and CSS.
+- [Jekyll-assets](http://ixti.net/jekyll-assets/) by [ixti](https://github.com/ixti): Rails-alike assets pipeline (write assets in CoffeeScript, Sass, LESS etc; specify dependencies for automatic bundling using simple declarative comments in assets; minify and compress; use JST templates; cache bust; and many-many more).
+- [JAPR](https://github.com/kitsched/japr): Jekyll Asset Pipeline Reborn - Powerful asset pipeline for Jekyll that collects, converts and compresses JavaScript and CSS assets.
+- [File compressor](https://gist.github.com/2758691) by [mytharcher](https://github.com/mytharcher): Compress HTML and JavaScript files on site build.
+- [Jekyll-minibundle](https://github.com/tkareine/jekyll-minibundle): Asset bundling and cache busting using external minification tool of your choice. No gem dependencies.
+- [Singlepage-jekyll](https://github.com/JCB-K/singlepage-jekyll) by [JCB-K](https://github.com/JCB-K): Turns Jekyll into a dynamic one-page website.
+- [generator-jekyllrb](https://github.com/robwierzbowski/generator-jekyllrb): A generator that wraps Jekyll in [Yeoman](http://yeoman.io/), a tool collection and workflow for builing modern web apps.
+- [grunt-jekyll](https://github.com/dannygarcia/grunt-jekyll): A straightforward [Grunt](http://gruntjs.com/) plugin for Jekyll.
+- [jekyll-postfiles](https://github.com/indirect/jekyll-postfiles): Add `_postfiles` directory and {% raw %}`{{ postfile }}`{% endraw %} tag so the files a post refers to will always be right there inside your repo.
+- [A layout that compresses HTML](https://github.com/penibelst/jekyll-compress-html) by [Anatol Broder](http://penibelst.de/): Github Pages compatible, configurable way to compress HTML files on site build.
+- [Jekyll CO₂](https://github.com/wdenton/jekyll-co2): Generates HTML showing the monthly change in atmospheric CO₂ at the Mauna Loa observatory in Hawaii.
+- [remote-include](http://www.northfieldx.co.uk/remote-include/): Includes files using remote URLs
+
+#### Editors
+
+- [sublime-jekyll](https://github.com/23maverick23/sublime-jekyll): A Sublime Text package for Jekyll static sites. This package should help creating Jekyll sites and posts easier by providing access to key template tags and filters, as well as common completions and a current date/datetime command (for dating posts). You can install this package manually via GitHub, or via [Package Control](https://sublime.wbond.net/packages/Jekyll).
+- [vim-jekyll](https://github.com/parkr/vim-jekyll): A vim plugin to generate
+ new posts and run `jekyll build` all without leaving vim.
+- [markdown-writer](https://atom.io/packages/markdown-writer): An Atom package for Jekyll. It can create new posts/drafts, manage tags/categories, insert link/images and add many useful key mappings.
+
+
+
Jekyll Plugins Wanted
+
+ If you have a Jekyll plugin that you would like to see added to this list,
+ you should read the contributing page to find
+ out how to make that happen.
+
+
diff --git a/_docs/posts.md b/_docs/posts.md
new file mode 100755
index 0000000..504ea2f
--- /dev/null
+++ b/_docs/posts.md
@@ -0,0 +1,216 @@
+---
+layout: docs
+title: Writing posts
+prev_section: frontmatter
+next_section: drafts
+permalink: /docs/posts/
+---
+
+One of Jekyll’s best aspects is that it is “blog aware”. What does this mean,
+exactly? Well, simply put, it means that blogging is baked into Jekyll’s
+functionality. If you write articles and publish them online, this means that
+you can publish and maintain a blog simply by managing a folder of text-files on
+your computer. Compared to the hassle of configuring and maintaining databases
+and web-based CMS systems, this will be a welcome change!
+
+## The Posts Folder
+
+As explained on the [directory structure](../structure/) page, the `_posts`
+folder is where your blog posts will live. These files can be either
+[Markdown](http://daringfireball.net/projects/markdown/) or
+[Textile](http://redcloth.org/textile) formatted text files, and as long as
+they have [YAML Front Matter](../frontmatter/), they will be converted from their
+source format into an HTML page that is part of your static site.
+
+### Creating Post Files
+
+To create a new post, all you need to do is create a new file in the `_posts`
+directory. How you name files in this folder is important. Jekyll requires blog
+post files to be named according to the following format:
+
+{% highlight bash %}
+YEAR-MONTH-DAY-title.MARKUP
+{% endhighlight %}
+
+Where `YEAR` is a four-digit number, `MONTH` and `DAY` are both two-digit
+numbers, and `MARKUP` is the file extension representing the format used in the
+file. For example, the following are examples of valid post filenames:
+
+{% highlight bash %}
+2011-12-31-new-years-eve-is-awesome.md
+2012-09-12-how-to-write-a-blog.textile
+{% endhighlight %}
+
+
+
ProTip™: Link to other posts
+
+ Use the post_url
+ tag to link to other posts without having to worry about the URL's
+ breaking when the site permalink style changes.
+
+
+
+### Content Formats
+
+All blog post files must begin with [YAML Front Matter](../frontmatter/). After
+that, it's simply a matter of deciding which format you prefer. Jekyll supports
+two popular content markup formats:
+[Markdown](http://daringfireball.net/projects/markdown/) and
+[Textile](http://redcloth.org/textile). These formats each have their own way
+of marking up different types of content within a post, so you should
+familiarize yourself with these formats and decide which one best suits your
+needs.
+
+
+
Be aware of character sets
+
+ Content processors can modify certain characters to make them look nicer.
+ For example, the smart extension in Redcarpet converts standard,
+ ASCII quotation characters to curly, Unicode ones. In order for the browser
+ to display those characters properly, define the charset meta value by
+ including <meta charset="utf-8"> in the
+ <head> of your layout.
+
+
+
+## Including images and resources
+
+Chances are, at some point, you'll want to include images, downloads, or other
+digital assets along with your text content. While the syntax for linking to
+these resources differs between Markdown and Textile, the problem of working out
+where to store these files in your site is something everyone will face.
+
+Because of Jekyll’s flexibility, there are many solutions to how to do this. One
+common solution is to create a folder in the root of the project directory
+called something like `assets` or `downloads`, into which any images, downloads
+or other resources are placed. Then, from within any post, they can be linked to
+using the site’s root as the path for the asset to include. Again, this will
+depend on the way your site’s (sub)domain and path are configured, but here some
+examples (in Markdown) of how you could do this using the `site.url` variable in
+a post.
+
+Including an image asset in a post:
+
+{% highlight text %}
+… which is shown in the screenshot below:
+
+{% endhighlight %}
+
+Linking to a PDF for readers to download:
+
+{% highlight text %}
+… you can [get the PDF]({% raw %}{{ site.url }}{% endraw %}/assets/mydoc.pdf) directly.
+{% endhighlight %}
+
+
+
ProTip™: Link using just the site root URL
+
+ You can skip the {% raw %}{{ site.url }}{% endraw %} variable
+ if you know your site will only ever be displayed at the
+ root URL of your domain. In this case you can reference assets directly with
+ just /path/file.jpg.
+
+
+
+## Displaying an index of posts
+
+It’s all well and good to have posts in a folder, but a blog is no use unless
+you have a list of posts somewhere. Creating an index of posts on another page
+(or in a [template](../templates/)) is easy, thanks to the [Liquid template
+language](http://wiki.shopify.com/Liquid) and its tags. Here’s a basic example of how
+to create a list of links to your blog posts:
+
+{% highlight html %}
+
+ {% raw %}{% for post in site.posts %}{% endraw %}
+
+{% endhighlight %}
+
+Of course, you have full control over how (and where) you display your posts,
+and how you structure your site. You should read more about [how templates
+work](../templates/) with Jekyll if you want to know more.
+
+Note that the `post` variable only exists inside the `for` loop above. If
+you wish to access the currently-rendering page/posts's variables (the
+variables of the post/page that has the `for` loop in it), use the `page`
+variable instead.
+
+## Post excerpts
+
+Each post automatically takes the first block of text, from the beginning of the content
+to the first occurrence of `excerpt_separator`, and sets it as the `post.excerpt`.
+Take the above example of an index of posts. Perhaps you want to include
+a little hint about the post's content by adding the first paragraph of each of your
+posts:
+
+{% highlight html %}
+
+ {% raw %}{% for post in site.posts %}{% endraw %}
+
+{% endhighlight %}
+
+Because Jekyll grabs the first paragraph you will not need to wrap the excerpt in `p` tags,
+which is already done for you. These tags can be removed with the following if you'd prefer:
+
+{% highlight html %}
+{% raw %}{{ post.excerpt | remove: '
' | remove: '
' }}{% endraw %}
+{% endhighlight %}
+
+If you don't like the automatically-generated post excerpt, it can be overridden by adding
+`excerpt` to your post's YAML Front Matter. Completely disable it by setting
+your `excerpt_separator` to `""`.
+
+Also, as with any output generated by Liquid tags, you can pass the `| strip_html` flag to remove any html tags in the output. This is particularly helpful if you wish to output a post excerpt as a `meta="description"` tag within the post `head`, or anywhere else having html tags along with the content is not desirable.
+
+## Highlighting code snippets
+
+Jekyll also has built-in support for syntax highlighting of code snippets using
+either Pygments or Rouge, and including a code snippet in any post is easy. Just
+use the dedicated Liquid tag as follows:
+
+{% highlight text %}
+{% raw %}{% highlight ruby %}{% endraw %}
+def show
+ @widget = Widget(params[:id])
+ respond_to do |format|
+ format.html # show.html.erb
+ format.json { render json: @widget }
+ end
+end
+{% raw %}{% endhighlight %}{% endraw %}
+{% endhighlight %}
+
+And the output will look like this:
+
+{% highlight ruby %}
+def show
+ @widget = Widget(params[:id])
+ respond_to do |format|
+ format.html # show.html.erb
+ format.json { render json: @widget }
+ end
+end
+{% endhighlight %}
+
+
+
ProTip™: Show line numbers
+
+ You can make code snippets include line-numbers by adding the word
+ linenos to the end of the opening highlight tag like this:
+ {% raw %}{% highlight ruby linenos %}{% endraw %}.
+
+
+
+These basics should be enough to get you started writing your first posts. When
+you’re ready to dig into what else is possible, you might be interested in doing
+things like [customizing post permalinks](../permalinks/) or using [custom
+variables](../variables/) in your posts and elsewhere on your site.
diff --git a/_docs/quickstart.md b/_docs/quickstart.md
new file mode 100755
index 0000000..66cd945
--- /dev/null
+++ b/_docs/quickstart.md
@@ -0,0 +1,28 @@
+---
+layout: docs
+title: Quick-start guide
+prev_section: home
+next_section: installation
+permalink: /docs/quickstart/
+---
+
+For the impatient, here's how to get a boilerplate Jekyll site up and running.
+
+{% highlight bash %}
+~ $ gem install jekyll
+~ $ jekyll new myblog
+~ $ cd myblog
+~/myblog $ jekyll serve
+# => Now browse to http://localhost:4000
+{% endhighlight %}
+
+If you wish to install jekyll into the current directory, you can do so by alternatively running `jekyll new .` instead of a new directory name.
+
+That's nothing, though. The real magic happens when you start creating blog
+posts, using the front matter to control templates and layouts, and taking
+advantage of all the awesome configuration options Jekyll makes available.
+
+If you're running into problems, ensure you have all the [requirements
+installed][Installation].
+
+[Installation]: /docs/installation/
diff --git a/_docs/resources.md b/_docs/resources.md
new file mode 100755
index 0000000..cc95d06
--- /dev/null
+++ b/_docs/resources.md
@@ -0,0 +1,46 @@
+---
+layout: docs
+title: Resources
+prev_section: sites
+next_section: upgrading
+permalink: /docs/resources/
+---
+
+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
+
+- [Tips for working with GitHub Pages Integration](https://gist.github.com/2890453)
+
+ Code example reuse, and keeping documentation up to date.
+
+- [Use FormKeep for Jekyll form backend and webhooks](https://formkeep.com/)
+- [Use Simple Form to integrate a simple contact
+ form](http://getsimpleform.com/)
+- [JekyllBootstrap.com](http://jekyllbootstrap.com)
+
+ Provides detailed explanations, examples, and helper-code to make
+ getting started with Jekyll easier.
+
+### Tutorials
+
+#### Integrating Jekyll with Git
+
+- [Blogging with Git, Emacs and Jekyll](http://metajack.im/2009/01/23/blogging-with-git-emacs-and-jekyll/)
+
+#### Other hacks
+
+- [Integrating Twitter with Jekyll](http://www.justkez.com/integrating-twitter-with-jekyll/)
+ > “Having migrated Justkez.com to be based on Jekyll, I was pondering how I might include my recent twitterings on the front page of the site. In the WordPress world, this would have been done via a plugin which may or may not have hung the loading of the page, might have employed caching, but would certainly have had some overheads. … Not in Jekyll.”
+- [‘My Jekyll Fork’, by Mike West](http://mikewest.org/2009/11/my-jekyll-fork)
+ > “Jekyll is a well-architected throwback to a time before WordPress, when men were men, and HTML was static. I like the ideas it espouses, and have made a few improvements to it’s core. Here, I’ll point out some highlights of my fork in the hopes that they see usage beyond this site.”
+- [‘About this Website’, by Carter Allen](http://cartera.me/2010/08/12/about-this-website/)
+ > “Jekyll is everything that I ever wanted in a blogging engine. Really. It isn’t perfect, but what’s excellent about it is that if there’s something wrong, I know exactly how it works and how to fix it. It runs on the your machine only, and is essentially an added”build" step between you and the browser. I coded this entire site in TextMate using standard HTML5 and CSS3, and then at the end I added just a few little variables to the markup. Presto-chango, my site is built and I am at peace with the world.”
+- [‘Build A Blog With Jekyll And GitHub Pages’, by Barry Clark](http://www.smashingmagazine.com/2014/08/01/build-blog-jekyll-github-pages/)
+ > “I recently migrated my blog from WordPress to Jekyll, a fantastic website generator that’s designed for building minimal, static blogs to be hosted on GitHub Pages. The simplicity of Jekyll’s theming layer and writing workflow is fantastic; however, setting up my website took a lot longer than expected. In this article we'll walk through: the quickest way to set up a Jekyll powered blog, how to avoid common problems with using Jekyll, how to import your content from Wordpress, and more.”
+- [Generating a Tag Cloud in Jekyll](http://www.justkez.com/generating-a-tag-cloud-in-jekyll/)
+A guide to implementing a tag cloud and per-tag content pages using Jekyll.
+
+- A way to [extend Jekyll](https://github.com/rfelix/jekyll_ext) without forking and modifying the Jekyll gem codebase and some [portable Jekyll extensions](https://wiki.github.com/rfelix/jekyll_ext/extensions) that can be reused and shared.
+
+- [Using your Rails layouts in Jekyll](http://numbers.brighterplanet.com/2010/08/09/sharing-rails-views-with-jekyll)
diff --git a/_docs/sites.md b/_docs/sites.md
new file mode 100755
index 0000000..4e57aba
--- /dev/null
+++ b/_docs/sites.md
@@ -0,0 +1,29 @@
+---
+layout: docs
+title: Sites using Jekyll
+prev_section: troubleshooting
+next_section: resources
+permalink: /docs/sites/
+---
+
+It’s interesting to see what designs and features others have come up
+with. Below are some Jekyll-powered blogs which were hand-picked for
+learning purposes.
+
+- [Tom Preston-Werner](http://tom.preston-werner.com/)
+ ([source](https://github.com/mojombo/mojombo.github.io))
+- [Nick Quaranto](http://quaran.to/)
+ ([source](https://github.com/qrush/qrush.github.com))
+- [Roger Chapman](http://rogchap.com/)
+ ([source](https://github.com/rogchap/rogchap.github.com))
+- [GitHub Official Teaching Materials](http://training.github.com)
+ ([source](https://github.com/github/training.github.com/tree/7049d7532a6856411e34046aedfce43a4afaf424))
+- [Rasmus Andersson](http://rsms.me/)
+ ([source](https://github.com/rsms/rsms.github.com))
+- [Scott Chacon](http://schacon.github.com)
+ ([source](https://github.com/schacon/schacon.github.com))
+
+If you would like to explore more examples, you can find a list of sites
+and their sources on the ["Sites" page in the Jekyll wiki][jekyll-sites].
+
+[jekyll-sites]: {{ site.repository }}/wiki/Sites
diff --git a/_docs/structure.md b/_docs/structure.md
new file mode 100755
index 0000000..2dca3e6
--- /dev/null
+++ b/_docs/structure.md
@@ -0,0 +1,190 @@
+---
+layout: docs
+title: Directory structure
+prev_section: usage
+next_section: configuration
+permalink: /docs/structure/
+---
+
+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
+all done through editing text files, and the static web site is the final
+product.
+
+A basic Jekyll site usually looks something like this:
+
+{% highlight bash %}
+.
+├── _config.yml
+├── _drafts
+| ├── begin-with-the-crazy-ideas.textile
+| └── on-simplicity-in-technology.markdown
+├── _includes
+| ├── footer.html
+| └── header.html
+├── _layouts
+| ├── default.html
+| └── post.html
+├── _posts
+| ├── 2007-10-29-why-every-programmer-should-play-nethack.textile
+| └── 2009-04-26-barcamp-boston-4-roundup.textile
+├── _data
+| └── members.yml
+├── _site
+└── index.html
+{% endhighlight %}
+
+An overview of what each of these does:
+
+
+
+
+
+
File / Directory
+
Description
+
+
+
+
+
+
_config.yml
+
+
+
+
+ Stores configuration data. Many of
+ these options can be specified from the command line executable but
+ it’s easier to specify them here so you don’t have to remember them.
+
+
+
+
+
+
+
_drafts
+
+
+
+
+ Drafts are unpublished posts. The format of these files is without a date: title.MARKUP. Learn how to work with drafts.
+
+
+
+
+
+
+
_includes
+
+
+
+
+ These are the partials that can be mixed and matched by your layouts
+ and posts to facilitate reuse. The liquid tag
+ {% raw %}{% include file.ext %}{% endraw %}
+ can be used to include the partial in
+ _includes/file.ext.
+
+
+
+
+
+
+
_layouts
+
+
+
+
+ These are the templates that wrap posts. Layouts are chosen on a post-
+ by-post basis in the YAML Front Matter,
+ which is described in the next section. The liquid tag
+ {% raw %}{{ content }}{% endraw %}
+ is used to inject content into the web page.
+
+
+
+
+
+
+
_posts
+
+
+
+
+ Your dynamic content, so to speak. The naming convention of these files is
+ important, and must follow the format:
+ YEAR-MONTH-DAY-title.MARKUP.
+ The permalinks can be customized for each
+ post, but the date and markup language are determined solely by the
+ file name.
+
+
+
+
+
+
+
_data
+
+
+
+
+ Well-formatted site data should be placed here. The jekyll engine will
+ autoload all yaml files (ends with .yml or .yaml)
+ in this directory. If there's a file members.yml under the directory,
+ then you can access contents of the file through site.data.members.
+
+
+
+
+
+
+
_site
+
+
+
+
+ This is where the generated site will be placed (by default) once
+ Jekyll is done transforming it. It’s probably a good idea to add this
+ to your .gitignore file.
+
+
+
+
+
+
+
index.html and other HTML, Markdown, Textile files
+
+
+
+
+ Provided that the file has a YAML Front
+ Matter section, it will be transformed by Jekyll. The same will
+ happen for any .html, .markdown,
+ .md, or .textile file in your site’s root
+ directory or directories not listed above.
+
+
+
+
+
+
+
Other Files/Folders
+
+
+
+
+ Every other directory and file except for those listed above—such as
+ css and images folders,
+ favicon.ico files, and so forth—will be copied verbatim
+ to the generated site. There are plenty of sites
+ already using Jekyll if you’re curious to see how they’re laid
+ out.
+
+
+
+
+
+
+
diff --git a/_docs/templates.md b/_docs/templates.md
new file mode 100755
index 0000000..2cd7461
--- /dev/null
+++ b/_docs/templates.md
@@ -0,0 +1,416 @@
+---
+layout: docs
+title: Templates
+prev_section: migrations
+next_section: permalinks
+permalink: /docs/templates/
+---
+
+Jekyll uses the [Liquid](https://github.com/Shopify/liquid/wiki) templating language to
+process templates. All of the standard Liquid [tags](https://github.com/Shopify/liquid/wiki/Liquid-for-Designers#tags) and
+[filters](https://github.com/Shopify/liquid/wiki/Liquid-for-Designers#standard-filters) are
+supported. Jekyll even adds a few handy filters and tags of its own to make
+common tasks easier.
+
+## Filters
+
+
+
+## Tags
+
+### Includes
+
+If you have small page fragments that you wish to include in multiple places on
+your site, you can use the `include` tag.
+
+{% highlight ruby %}
+{% raw %}{% include footer.html %}{% endraw %}
+{% endhighlight %}
+
+Jekyll expects all include files to be placed in an `_includes` directory at the
+root of your source directory. This will embed the contents of
+`/_includes/footer.html` into the calling file.
+
+
+
ProTip™: Use variables as file name
+
+
+ The name of the file you wish to embed can be literal (as in the example above),
+ or you can use a variable, using liquid-like variable syntax as in
+ {% raw %}{% include {{my_variable}} %}{% endraw %}.
+
+
+
+
+You can also pass parameters to an include:
+
+{% highlight ruby %}
+{% raw %}{% include footer.html param="value" %}{% endraw %}
+{% endhighlight %}
+
+These parameters are available via Liquid in the include:
+
+{% highlight ruby %}
+{% raw %}{{ include.param }}{% endraw %}
+{% endhighlight %}
+
+#### Including files relative to another file
+
+You can also choose to include file fragments relative to the current file:
+
+{% highlight ruby %}
+{% raw %}{% include_relative somedir/footer.html %}{% endraw %}
+{% endhighlight %}
+
+You won't need to place your included content within the `_includes` directory. Instead,
+the inclusion is specifically relative to the file where the tag is being used. For example,
+if `_posts/2014-09-03-my-file.markdown` uses the `include_relative` tag, the included file
+must be within the `_posts` directory, or one of it's subdirectories. You cannot include
+files in other locations.
+
+All the other capabilities of the `include` tag are available to the `include_relative` tag,
+such as using variables.
+
+### Code snippet highlighting
+
+Jekyll has built in support for syntax highlighting of [over 100
+languages](http://pygments.org/languages/) thanks to
+[Pygments](http://pygments.org/). To use Pygments, you must have Python installed
+on your system and set `highlighter` to `pygments` in your site's configuration
+file.
+
+Alternatively, you can use [Rouge](https://github.com/jayferd/rouge) to highlight
+your code snippets. It doesn't support as many languages as Pygments does but
+it should fit in most cases and it's written in pure Ruby ; you don't need Python
+on your system!
+
+To render a code block with syntax highlighting, surround your code as follows:
+
+{% highlight text %}
+{% raw %}
+{% highlight ruby %}
+def foo
+ puts 'foo'
+end
+{% endhighlight %}
+{% endraw %}
+{% endhighlight %}
+
+The argument to the `highlight` tag (`ruby` in the example above) is the
+language identifier. To find the appropriate identifier to use for the language
+you want to highlight, look for the “short name” on the [Pygments' Lexers
+page](http://pygments.org/docs/lexers/) or the [Rouge
+wiki](https://github.com/jayferd/rouge/wiki/List-of-supported-languages-and-lexers).
+
+#### Line numbers
+
+There is a second argument to `highlight` called `linenos` that is optional.
+Including the `linenos` argument will force the highlighted code to include line
+numbers. For instance, the following code block would include line numbers next
+to each line:
+
+{% highlight text %}
+{% raw %}
+{% highlight ruby linenos %}
+def foo
+ puts 'foo'
+end
+{% endhighlight %}
+{% endraw %}
+{% endhighlight %}
+
+#### Stylesheets for syntax highlighting
+
+In order for the highlighting to show up, you’ll need to include a highlighting
+stylesheet. For an example stylesheet you can look at
+[syntax.css](https://github.com/mojombo/tpw/tree/master/css/syntax.css). These
+are the same styles as used by GitHub and you are free to use them for your own
+site. If you use `linenos`, you might want to include an additional CSS class
+definition for the `.lineno` class in `syntax.css` to distinguish the line
+numbers from the highlighted code.
+
+### Post URL
+
+If you would like to include a link to a post on your site, the `post_url` tag
+will generate the correct permalink URL for the post you specify.
+
+{% highlight text %}
+{% raw %}
+{% post_url 2010-07-21-name-of-post %}
+{% endraw %}
+{% endhighlight %}
+
+If you organize your posts in subdirectories, you need to include subdirectory
+path to the post:
+
+{% highlight text %}
+{% raw %}
+{% post_url /subdir/2010-07-21-name-of-post %}
+{% endraw %}
+{% endhighlight %}
+
+There is no need to include the file extension when using the `post_url` tag.
+
+You can also use this tag to create a link to a post in Markdown as follows:
+
+{% highlight text %}
+{% raw %}
+[Name of Link]({% post_url 2010-07-21-name-of-post %})
+{% endraw %}
+{% endhighlight %}
+
+### Gist
+
+Use the `gist` tag to easily embed a GitHub Gist onto your site. This works with public or secret gists:
+
+{% highlight text %}
+{% raw %}
+{% gist parkr/931c1c8d465a04042403 %}
+{% endraw %}
+{% endhighlight %}
+
+You may also optionally specify the filename in the gist to display:
+
+{% highlight text %}
+{% raw %}
+{% gist parkr/931c1c8d465a04042403 jekyll-private-gist.markdown %}
+{% endraw %}
+{% endhighlight %}
diff --git a/_docs/troubleshooting.md b/_docs/troubleshooting.md
new file mode 100755
index 0000000..1402309
--- /dev/null
+++ b/_docs/troubleshooting.md
@@ -0,0 +1,154 @@
+---
+layout: docs
+title: Troubleshooting
+prev_section: deployment-methods
+next_section: sites
+permalink: /docs/troubleshooting/
+---
+
+If you ever run into problems installing or using Jekyll, here are a few tips
+that might be of help. If the problem you’re experiencing isn’t covered below,
+please [report an issue]({{site.help_url}}/issues/new) so the
+Jekyll community can make everyone’s experience better.
+
+## Installation Problems
+
+If you encounter errors during gem installation, you may need to install
+the header files for compiling extension modules for ruby 1.9.1. This
+can be done on Ubuntu or Debian by running:
+
+{% highlight bash %}
+sudo apt-get install ruby1.9.1-dev
+{% endhighlight %}
+
+On Red Hat, CentOS, and Fedora systems you can do this by running:
+
+{% highlight bash %}
+sudo yum install ruby-devel
+{% endhighlight %}
+
+On [NearlyFreeSpeech](http://nearlyfreespeech.net/) you need to run the
+following commands before installing Jekyll:
+
+{% highlight bash %}
+export GEM_HOME=/home/private/gems
+export GEM_PATH=/home/private/gems:/usr/local/lib/ruby/gems/1.8/
+export PATH=$PATH:/home/private/gems/bin
+export RB_USER_INSTALL='true'
+{% endhighlight %}
+
+On OSX, you may need to update RubyGems:
+
+{% highlight bash %}
+sudo gem update --system
+{% endhighlight %}
+
+If you still have issues, you may need to [use XCode to install Command Line
+Tools](http://www.zlu.me/ruby/os%20x/gem/mountain%20lion/2012/02/21/install-native-ruby-gem-in-mountain-lion-preview.html)
+that will allow you to install native gems using the following command:
+
+{% highlight bash %}
+sudo gem install jekyll
+{% endhighlight %}
+
+To install RubyGems on Gentoo:
+
+{% highlight bash %}
+sudo emerge -av dev-ruby/rubygems
+{% endhighlight %}
+
+On Windows, you may need to install [RubyInstaller
+DevKit](https://wiki.github.com/oneclick/rubyinstaller/development-kit).
+
+### Could not find a JavaScript runtime. (ExecJS::RuntimeUnavailable)
+
+This error can occur during the installation of `jekyll-coffeescript` when
+you don't have a proper JavaScript runtime. To solve this, either install
+`execjs` and `therubyracer` gems, or install `nodejs`. Check out
+[issue #2327](https://github.com/jekyll/jekyll/issues/2327) for more info.
+
+## Problems running Jekyll
+
+On Debian or Ubuntu, you may need to add `/var/lib/gems/1.8/bin/` to your path
+in order to have the `jekyll` executable be available in your Terminal.
+
+## Base-URL Problems
+
+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
+
+The order of precedence for conflicting [configuration settings](../configuration/)
+is as follows:
+
+1. Command-line flags
+2. Configuration file settings
+3. Defaults
+
+That is: defaults are overridden by options specified in `_config.yml`,
+and flags specified at the command-line will override all other settings
+specified elsewhere.
+
+## Markup Problems
+
+The various markup engines that Jekyll uses may have some issues. This
+page will document them to help others who may run into the same
+problems.
+
+### Maruku
+
+If your link has characters that need to be escaped, you need to use
+this syntax:
+
+{% highlight text %}
+
+{% endhighlight %}
+
+If you have an empty tag, i.e. ``, Maruku
+transforms this into ``. This causes problems in
+Firefox and possibly other browsers and is [discouraged in
+XHTML.](http://www.w3.org/TR/xhtml1/#C_3) An easy fix is to put a space
+between the opening and closing tags.
+
+### Liquid
+
+The latest version, version 2.0, seems to break the use of `{{ "{{" }}` in
+templates. Unlike previous versions, using `{{ "{{" }}` in 2.0 triggers the
+following error:
+
+{% highlight bash %}
+'{{ "{{" }}' was not properly terminated with regexp: /\}\}/ (Liquid::SyntaxError)
+{% endhighlight %}
+
+### Excerpts
+
+Since v1.0.0, Jekyll has had automatically-generated post excerpts. Since
+v1.1.0, Jekyll also passes these excerpts through Liquid, which can cause
+strange errors where references don't exist or a tag hasn't been closed. If you
+run into these errors, try setting `excerpt_separator: ""` in your
+`_config.yml`, or set it to some nonsense string.
+
+
+
Please report issues you encounter!
+
+ If you come across a bug, please create an issue
+ on GitHub describing the problem and any work-arounds you find so we can
+ document it here for others.
+
+
diff --git a/_docs/upgrading.md b/_docs/upgrading.md
new file mode 100755
index 0000000..3a3f167
--- /dev/null
+++ b/_docs/upgrading.md
@@ -0,0 +1,146 @@
+---
+layout: docs
+title: Upgrading
+prev_section: resources
+next_section: contributing
+permalink: /docs/upgrading/
+---
+
+Upgrading from an older version of Jekyll? A few things have changed in 1.0
+that you'll want to know about.
+
+Before we dive in, go ahead and fetch the latest version of Jekyll:
+
+{% highlight bash %}
+$ gem update jekyll
+{% endhighlight %}
+
+
+
Diving in
+
Want to get a new Jekyll site up and running quickly? Simply
+ run jekyll new SITENAME to create a new folder with a bare bones
+ Jekyll site.
+
+
+### 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.
+
+
+
Watching and Serving
+
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`.
+
+
+### Absolute Permalinks
+
+In Jekyll v1.0, we introduced absolute permalinks for pages in subdirectories.
+Until v2.0, it is **opt-in**. Starting with v2.0, however, absolute permalinks
+will become **opt-out**, meaning Jekyll will default to using absolute permalinks
+instead of relative permalinks.
+
+* To use absolute permalinks, set `relative_permalinks: false` in your configuration file.
+* To continue using relative permalinks, set `relative_permalinks: true` in your configuration file.
+
+
+
Absolute permalinks will be default in v2.0 and on
+
+ Starting with Jekyll v2.0, `relative_permalinks` will default to `false`,
+ meaning all pages will be built using the absolute permalink behaviour.
+ The switch will still exist until v2.0.
+
+
+
+### 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.
+
+
+
Drafts don't have dates
+
+ 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`.
+
+
+### 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-delimited, 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`
+
+
+
The config flag explicitly specifies your configuration file(s)
+
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.
+
+
+### New Config File Options
+
+Jekyll 1.0 introduced several new config file options. Before you upgrade, you
+should check to see if any of these are present in your pre-1.0 config file, and
+if so, make sure that you're using them properly:
+
+* `excerpt_separator`
+* `host`
+* `include`
+* `keep_files`
+* `layouts`
+* `show_drafts`
+* `timezone`
+* `url`
+
+### 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 `{% raw %}{{ site.baseurl }}{% endraw %}`.
+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.
+
+
+
+
All page and post URLs contain leading slashes
+
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 `/`.
+
diff --git a/_docs/usage.md b/_docs/usage.md
new file mode 100755
index 0000000..4959ad4
--- /dev/null
+++ b/_docs/usage.md
@@ -0,0 +1,84 @@
+---
+layout: docs
+title: Basic Usage
+prev_section: installation
+next_section: structure
+permalink: /docs/usage/
+---
+
+The Jekyll gem makes a `jekyll` executable available to you in your Terminal
+window. You can use this command in a number of ways:
+
+{% highlight bash %}
+$ jekyll build
+# => The current folder will be generated into ./_site
+
+$ jekyll build --destination
+# => The current folder will be generated into
+
+$ jekyll build --source --destination
+# => The folder will be generated into
+
+$ jekyll build --watch
+# => The current folder will be generated into ./_site,
+# watched for changes, and regenerated automatically.
+{% endhighlight %}
+
+
+
Destination folders are cleaned on site builds
+
+ The contents of <destination> are automatically
+ cleaned when the site is built. Files or folders that are not
+ created by your site will be removed. Do not use an important
+ location for <destination>; instead, use it as
+ a staging area and copy files from there to your web server.
+
+
+
+Jekyll also comes with a built-in development server that will allow you to
+preview what the generated site will look like in your browser locally.
+
+{% highlight bash %}
+$ jekyll serve
+# => A development server will run at http://localhost:4000/
+# Auto-regeneration: enabled. Use `--no-watch` to disable.
+
+$ jekyll serve --detach
+# => Same as `jekyll serve` but will detach from the current terminal.
+# If you need to kill the server, you can `kill -9 1234` where "1234" is the PID.
+# If you cannot find the PID, then do, `ps aux | grep jekyll` and kill the instance. [Read more](http://unixhelp.ed.ac.uk/shell/jobz5.html).
+{% endhighlight %}
+
+
+
Be aware of default behavior
+
+ As of version 2.4, the serve command will watch for changes automatically. To disable this, you can use jekyll serve --no-watch, which preserves the old behavior.
+
+
+
+{% highlight bash %}
+$ jekyll serve --no-watch
+# => Same as `jekyll serve` but will not watch for changes.
+{% endhighlight %}
+
+These are just a few of the available [configuration options](../configuration/).
+Many configuration options can either be specified as flags on the command line,
+or alternatively (and more commonly) they can be specified in a `_config.yml`
+file at the root of the source directory. Jekyll will automatically use the
+options from this file when run. For example, if you place the following lines
+in your `_config.yml` file:
+
+{% highlight yaml %}
+source: _source
+destination: _deploy
+{% endhighlight %}
+
+Then the following two commands will be equivalent:
+
+{% highlight bash %}
+$ jekyll build
+$ jekyll build --source _source --destination _deploy
+{% endhighlight %}
+
+For more about the possible configuration options, see the
+[configuration](../configuration/) page.
\ No newline at end of file
diff --git a/_docs/variables.md b/_docs/variables.md
new file mode 100755
index 0000000..1c62bf8
--- /dev/null
+++ b/_docs/variables.md
@@ -0,0 +1,383 @@
+---
+layout: docs
+title: Variables
+prev_section: pages
+next_section: collections
+permalink: /docs/variables/
+---
+
+Jekyll traverses your site looking for files to process. Any files with [YAML
+front matter](../frontmatter/) are subject to processing. For each of these
+files, Jekyll makes a variety of data available via the [Liquid templating
+system](https://github.com/Shopify/liquid/wiki). The
+following is a reference of the available data.
+
+## Global Variables
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
site
+
+
+ Sitewide information + configuration settings from
+ _config.yml. See below for details.
+
+
+
+
+
page
+
+
+ Page specific information + the YAML front
+ matter. Custom variables set via the YAML Front Matter will be
+ available here. See below for details.
+
+
+
+
+
content
+
+
+ In layout files, the rendered content of the Post or Page being wrapped.
+ Not defined in Post or Page files.
+
+
+
+
+
paginator
+
+
+ When the paginate configuration option is set, this
+ variable becomes available for use. See Pagination for details.
+
+
+
+
+
+
+
+## Site Variables
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
site.time
+
+
+ The current time (when you run the jekyll command).
+
+
+
+
+
site.pages
+
+
+ A list of all Pages.
+
+
+
+
+
site.posts
+
+
+ A reverse chronological list of all Posts.
+
+
+
+
+
site.related_posts
+
+
+ If the page being processed is a Post, this contains a list of up to ten
+ related Posts. By default, these are low quality but fast to compute.
+ For high quality but slow to compute results, run the
+ jekyll command with the --lsi (latent semantic
+ indexing) option.
+
+
+
+
+
site.static_files
+
+
+ A list of all static files (i.e. files not processed by Jekyll's
+ converters or the Liquid renderer). Each file has three properties:
+ path, modified_time and extname.
+
+
+
+
+
site.html_pages
+
+
+ A list of all HTML Pages.
+
+
+
+
+
site.collections
+
+
+ A list of all the collections.
+
+
+
+
+
site.data
+
+
+ A list containing the data loaded from the YAML files located in the _data directory.
+
+
+
+
+
site.documents
+
+
+ A list of all the documents in every collection.
+
+
+
+
+
site.categories.CATEGORY
+
+
+ The list of all Posts in category CATEGORY.
+
+
+
+
+
site.tags.TAG
+
+
+ The list of all Posts with tag TAG.
+
+
+
+
+
site.[CONFIGURATION_DATA]
+
+
+ All the variables set via the command line and your
+ _config.yml are available through the site
+ variable. For example, if you have url: http://mysite.com
+ in your configuration file, then in your Posts and Pages it will be
+ stored in site.url. Jekyll does not parse changes to
+ _config.yml in watch mode, you must restart
+ Jekyll to see changes to variables.
+
+
+
+
+
+
+
+## Page Variables
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
page.content
+
+
+ The content of the Page, rendered or un-rendered depending upon
+ what Liquid is being processed and what page is.
+
+
+
+
+
page.title
+
+
+ The title of the Page.
+
+
+
+
+
page.excerpt
+
+
+ The un-rendered excerpt of the Page.
+
+
+
+
+
page.url
+
+
+ The URL of the Post without the domain, but
+ with a leading slash, e.g.
+ /2008/12/14/my-post.html
+
+
+
+
+
page.date
+
+
+ The Date assigned to the Post. This can be overridden in a Post’s front
+ matter by specifying a new date/time in the format
+ YYYY-MM-DD HH:MM:SS (assuming UTC), or
+ YYYY-MM-DD HH:MM:SS +/-TTTT (to specify a time zone using
+ an offset from UTC. e.g. 2008-12-14 10:30:00 +0900).
+
+
+
+
+
page.id
+
+
+ An identifier unique to the Post (useful in RSS feeds). e.g.
+ /2008/12/14/my-post
+
+
+
+
+
page.categories
+
+
+ The list of categories to which this post belongs. Categories are
+ derived from the directory structure above the _posts
+ directory. For example, a post at
+ /work/code/_posts/2008-12-24-closures.md would have this
+ field set to ['work', 'code']. These can also be specified
+ in the YAML Front Matter.
+
+
+
+
+
page.tags
+
+
+ The list of tags to which this post belongs. These can be specified in
+ the YAML Front Matter.
+
+
+
+
+
page.path
+
+
+ The path to the raw post or page. Example usage: Linking back to the
+ page or post’s source on GitHub. This can be overridden in the
+ YAML Front Matter.
+
+
+
+
+
page.next
+
+
+ The next post relative to the position of the current post in
+ site.posts. Returns nil for the last entry.
+
+
+
+
+
page.previous
+
+
+ The previous post relative to the position of the current post in
+ site.posts. Returns nil for the first entry.
+
+
+
+
+
+
+
+
+
ProTip™: Use Custom Front Matter
+
+
+ Any custom front matter that you specify will be available under
+ page. For example, if you specify custom_css: true
+ in a page’s front matter, that value will be available as
+ page.custom_css.
+
+
+
+
+## Paginator
+
+
+
+
+
+
Variable
+
Description
+
+
+
+
+
paginator.per_page
+
Number of Posts per page.
+
+
+
paginator.posts
+
Posts available for that page.
+
+
+
paginator.total_posts
+
Total number of Posts.
+
+
+
paginator.total_pages
+
Total number of Pages.
+
+
+
paginator.page
+
The number of the current page.
+
+
+
paginator.previous_page
+
The number of the previous page.
+
+
+
paginator.previous_page_path
+
The path to the previous page.
+
+
+
paginator.next_page
+
The number of the next page.
+
+
+
paginator.next_page_path
+
The path to the next page.
+
+
+
+
+
+
+
Paginator variable availability
+
+
+ These are only available in index files, however they can be located in a
+ subdirectory, such as /blog/index.html.
+
+
+
diff --git a/_docs/windows.md b/_docs/windows.md
new file mode 100755
index 0000000..81e909c
--- /dev/null
+++ b/_docs/windows.md
@@ -0,0 +1,43 @@
+---
+layout: docs
+title: Jekyll on Windows
+prev_section: configuration
+next_section: posts
+permalink: /docs/windows/
+---
+
+While Windows is not an officially-supported platform, it can be used to run
+Jekyll with the proper tweaks. This page aims to collect some of the general
+knowledge and lessons that have been unearthed by Windows users.
+
+## Installation
+
+Julian Thilo has written up instructions to get
+[Jekyll running on Windows][windows-installation] and it seems to work for most.
+
+## Encoding
+
+If you use UTF-8 encoding, make sure that no `BOM` header
+characters exist in your files or very, very bad things will happen to
+Jekyll. This is especially relevant if you're running Jekyll on Windows.
+
+Additionally, you might need to change the code page of the console window to UTF-8
+in case you get a "Liquid Exception: Incompatible character encoding" error during
+the site generation process. It can be done with the following command:
+
+{% highlight bash %}
+$ chcp 65001
+{% endhighlight %}
+
+[windows-installation]: http://jekyll-windows.juthilo.com/
+
+## Auto-regeneration
+
+As of v1.3.0, Jekyll uses the `listen` gem to watch for changes when the
+`--watch` switch is specified during a build or serve. While `listen` has
+built-in support for UNIX systems, it requires an extra gem for compatibility
+with Windows. Add the following to the Gemfile for your site:
+
+{% highlight ruby %}
+gem 'wdm', '~> 0.1.0' if Gem.win_platform?
+{% endhighlight %}
diff --git a/_includes/analytics.html b/_includes/analytics.html
new file mode 100755
index 0000000..5bbfc88
--- /dev/null
+++ b/_includes/analytics.html
@@ -0,0 +1,30 @@
+{% if site.gauges_id %}
+
+
+{% endif %}
+
+{% if site.google_analytics_id %}
+
+
+{% endif %}
diff --git a/_includes/anchor_links.html b/_includes/anchor_links.html
new file mode 100755
index 0000000..08e37b5
--- /dev/null
+++ b/_includes/anchor_links.html
@@ -0,0 +1,32 @@
+
diff --git a/_includes/docs_contents.html b/_includes/docs_contents.html
new file mode 100755
index 0000000..2ac64bb
--- /dev/null
+++ b/_includes/docs_contents.html
@@ -0,0 +1,8 @@
+
+
+
diff --git a/_includes/docs_contents_mobile.html b/_includes/docs_contents_mobile.html
new file mode 100755
index 0000000..b3e0110
--- /dev/null
+++ b/_includes/docs_contents_mobile.html
@@ -0,0 +1,10 @@
+
+
+
diff --git a/_includes/docs_option.html b/_includes/docs_option.html
new file mode 100755
index 0000000..c259397
--- /dev/null
+++ b/_includes/docs_option.html
@@ -0,0 +1,11 @@
+{% assign items = include.items %}
+
+{% for item in items %}
+ {% assign item_url = item | prepend:"/docs/" | append:"/" %}
+
+ {% for p in site.docs %}
+ {% if p.url == item_url %}
+
+ {% endif %}
+ {% endfor %}
+{% endfor %}
diff --git a/_includes/docs_ul.html b/_includes/docs_ul.html
new file mode 100755
index 0000000..366abe9
--- /dev/null
+++ b/_includes/docs_ul.html
@@ -0,0 +1,20 @@
+{% assign items = include.items %}
+
+
+{% for item in items %}
+ {% assign item_url = item | prepend:"/docs/" | append:"/" %}
+
+ {% if item_url == page.url %}
+ {% assign c = "current" %}
+ {% else %}
+ {% assign c = "" %}
+ {% endif %}
+
+ {% for p in site.docs %}
+ {% if p.url == item_url %}
+
+
diff --git a/_posts/2013-05-06-jekyll-1-0-0-released.markdown b/_posts/2013-05-06-jekyll-1-0-0-released.markdown
new file mode 100755
index 0000000..4b8e3be
--- /dev/null
+++ b/_posts/2013-05-06-jekyll-1-0-0-released.markdown
@@ -0,0 +1,23 @@
+---
+layout: news_item
+title: "Jekyll 1.0.0 Released"
+date: "2013-05-06 02:12:52 +0200"
+author: parkr
+version: 1.0.0
+categories: [release]
+---
+
+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 [quite lengthy][history],
+here are the highlights (thanks to [@benbalter](http://twitter.com/BenBalter) for the
+examples and for compiling this list):
+
+- Support for the Gist tag for easily embedding Gists ([example](https://gist.github.com/benbalter/5555251))
+- Automatically generated post excerpts ([example](https://gist.github.com/benbalter/5555369))
+- Save and preview drafts before publishing ([example](https://gist.github.com/benbalter/5555992))
+
+Take a look at the [Upgrading][] page in the docs for more detailed information.
+
+[history]: /docs/history/#v1-0-0
+[Upgrading]: /docs/upgrading/
diff --git a/_posts/2013-05-08-jekyll-1-0-1-released.markdown b/_posts/2013-05-08-jekyll-1-0-1-released.markdown
new file mode 100755
index 0000000..90edcc2
--- /dev/null
+++ b/_posts/2013-05-08-jekyll-1-0-1-released.markdown
@@ -0,0 +1,27 @@
+---
+layout: news_item
+title: "Jekyll 1.0.1 Released"
+date: "2013-05-08 23:46:11 +0200"
+author: parkr
+version: 1.0.1
+categories: [release]
+---
+
+Hot on the trails of v1.0, v1.0.1 is out! Here are the highlights:
+
+* Add newer `language-` class name prefix to code blocks ([#1037][])
+* Commander error message now preferred over process abort with incorrect args ([#1040][])
+* Do not force use of toc_token when using generate_toc in RDiscount ([#1048][])
+* Make Redcarpet respect the pygments configuration option ([#1053][])
+* Fix the index build with LSI ([#1045][])
+* Don't print deprecation warning when no arguments are specified. ([#1041][])
+* Add missing `
` to site template used by `new` subcommand, fixed typos in code ([#1032][])
+
+See the [History][] page for more information on this release.
+
+{% assign issue_numbers = "1037|1040|1048|1053|1045|1041|1032" | split: "|" %}
+{% for issue in issue_numbers %}
+[#{{ issue }}]: {{ site.repository }}/issues/{{ issue }}
+{% endfor %}
+
+[History]: /docs/history/#v1-0-1
diff --git a/_posts/2013-05-12-jekyll-1-0-2-released.markdown b/_posts/2013-05-12-jekyll-1-0-2-released.markdown
new file mode 100755
index 0000000..2a2b97e
--- /dev/null
+++ b/_posts/2013-05-12-jekyll-1-0-2-released.markdown
@@ -0,0 +1,28 @@
+---
+layout: news_item
+title: "Jekyll 1.0.2 Released"
+date: "2013-05-12 14:45:00 +0200"
+author: parkr
+version: 1.0.2
+categories: [release]
+---
+
+v1.0.2 has some key bugfixes that optionally restore some behaviour from pre-1.0
+releases, and fix some other annoying bugs:
+
+* Backwards-compatibilize relative permalinks ([#1081][])
+* Add `jekyll doctor` command to check site for any known compatibility problems ([#1081][])
+* Deprecate old config `server_port`, match to `port` if `port` isn't set ([#1084][])
+* Update pygments.rb and kramdon versions to 0.5.0 and 1.0.2, respectively ([#1061][], [#1067][])
+* Fix issue when post categories are numbers ([#1078][])
+* Add a `data-lang=""` attribute to Redcarpet code blocks ([#1066][])
+* Catching that Redcarpet gem isn't installed ([#1059][])
+
+See the [History][] page for more information on this release.
+
+{% assign issue_numbers = "1059|1061|1066|1067|1078|1081|1084" | split: "|" %}
+{% for issue in issue_numbers %}
+[#{{ issue }}]: {{ site.repository }}/issues/{{ issue }}
+{% endfor %}
+
+[History]: /docs/history/#v1-0-2
diff --git a/_posts/2013-06-07-jekyll-1-0-3-released.markdown b/_posts/2013-06-07-jekyll-1-0-3-released.markdown
new file mode 100755
index 0000000..566ae66
--- /dev/null
+++ b/_posts/2013-06-07-jekyll-1-0-3-released.markdown
@@ -0,0 +1,25 @@
+---
+layout: news_item
+title: "Jekyll 1.0.3 Released"
+date: "2013-06-07 21:02:13 +0200"
+author: parkr
+version: 1.0.3
+categories: [release]
+---
+
+v1.0.3 contains some key enhancements and bug fixes:
+
+- Fail with non-zero exit code when MaRuKu errors ([#1190][]) or Liquid errors ([#1121][])
+- Add support for private gists to `gist` tag ([#1189][])
+- Add `--force` option to `jekyll new` ([#1115][])
+- Fix compatibility with `exclude` and `include` with pre-1.0 Jekyll ([#1114][])
+- Fix pagination issue regarding `File.basename` and `page:num` ([#1063][])
+
+See the [History][] page for more information on this release.
+
+{% assign issue_numbers = "1190|1121|1189|1115|1114|1063" | split: "|" %}
+{% for issue in issue_numbers %}
+[#{{ issue }}]: {{ site.repository }}/issues/{{ issue }}
+{% endfor %}
+
+[History]: /docs/history/#v1-0-3
diff --git a/_posts/2013-07-14-jekyll-1-1-0-released.markdown b/_posts/2013-07-14-jekyll-1-1-0-released.markdown
new file mode 100755
index 0000000..12b3d92
--- /dev/null
+++ b/_posts/2013-07-14-jekyll-1-1-0-released.markdown
@@ -0,0 +1,27 @@
+---
+layout: news_item
+title: "Jekyll 1.1.0 Released"
+date: "2013-07-14 19:38:02 +0200"
+author: parkr
+version: 1.1.0
+categories: [release]
+---
+
+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:
+
+- Add `docs` subcommand to read Jekyll's docs when offline. ([#1046][])
+- Support passing parameters to templates in `include` tag ([#1204][])
+- Add support for Liquid tags to post excerpts ([#1302][])
+- Fix pagination for subdirectories ([#1198][])
+- Provide better error reporting when generating sites ([#1253][])
+- Latest posts first in non-LSI `related_posts` ([#1271][])
+
+See the [GitHub Release][] page for more a more detailed changelog for this release.
+
+{% assign issue_numbers = "1046|1204|1302|1198|1171|1118|1098|1215|1253|1271" | split: "|" %}
+{% for issue in issue_numbers %}
+[#{{ issue }}]: {{ site.repository }}/issues/{{ issue }}
+{% endfor %}
+
+[GitHub Release]: {{ site.repository }}/releases/tag/v1.1.0
diff --git a/_posts/2013-07-24-jekyll-1-1-1-released.markdown b/_posts/2013-07-24-jekyll-1-1-1-released.markdown
new file mode 100755
index 0000000..2d0096b
--- /dev/null
+++ b/_posts/2013-07-24-jekyll-1-1-1-released.markdown
@@ -0,0 +1,31 @@
+---
+layout: news_item
+title: "Jekyll 1.1.1 Released"
+date: "2013-07-24 22:24:14 +0200"
+author: parkr
+version: 1.1.1
+categories: [release]
+---
+
+
+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 ([#1339][]) and non-zero exit codes for invalid commands
+([#1338][]).
+
+To all those affected by the [strange excerpt bug in v1.1.0][#1321], I'm sorry. I think we
+have it all patched up and it should be deployed to [GitHub Pages][gh_pages] in the next
+couple weeks. Thank you for your patience!
+
+If you're checking out v1.1.x for the first time, definitely check out [what shipped with
+v1.1.0!][v1_1_0]
+
+See the [GitHub Release][] page for more a more detailed changelog for this release.
+
+{% assign issue_numbers = "1339|1338|1321" | split: "|" %}
+{% for issue in issue_numbers %}
+[#{{ issue }}]: {{ site.repository }}/issues/{{ issue }}
+{% endfor %}
+
+[GitHub Release]: {{ site.repository }}/releases/tag/v1.1.1
+[gh_pages]: http://pages.github.com
+[v1_1_0]: {{ site.repository }}/releases/tag/v1.1.0
diff --git a/_posts/2013-07-25-jekyll-1-0-4-released.markdown b/_posts/2013-07-25-jekyll-1-0-4-released.markdown
new file mode 100755
index 0000000..635d0e6
--- /dev/null
+++ b/_posts/2013-07-25-jekyll-1-0-4-released.markdown
@@ -0,0 +1,20 @@
+---
+layout: news_item
+title: "Jekyll 1.0.4 Released"
+date: "2013-07-25 09:08:38 +0200"
+author: mattr-
+version: 1.0.4
+categories: [release]
+---
+
+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.
+
+Community and custom plugins extending the `Liquid::Drop` class may inadvertently disclose some system information such as directory structure or software configuration to users with access to the Liquid templating system.
+
+We recommend you upgrade to Jekyll v1.0.4 immediately if you use `Liquid::Drop` plugins on your Jekyll site.
+
+Many thanks for [Ben Balter](https://github.com/benbalter) for alerting us to the problem
+and [submitting a patch][1349] so quickly.
+
+[230]: https://github.com/Shopify/liquid/pull/230
+[1349]: {{ site.repository }}/issues/1349
diff --git a/_posts/2013-07-25-jekyll-1-1-2-released.markdown b/_posts/2013-07-25-jekyll-1-1-2-released.markdown
new file mode 100755
index 0000000..ed16ca7
--- /dev/null
+++ b/_posts/2013-07-25-jekyll-1-1-2-released.markdown
@@ -0,0 +1,20 @@
+---
+layout: news_item
+title: "Jekyll 1.1.2 Released"
+date: "2013-07-25 09:08:38 +0200"
+author: parkr
+version: 1.1.2
+categories: [release]
+---
+
+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.
+
+Community and custom plugins extending the `Liquid::Drop` class may inadvertently disclose some system information such as directory structure or software configuration to users with access to the Liquid templating system.
+
+We recommend you upgrade to Jekyll v1.1.2 immediately if you use `Liquid::Drop` plugins on your Jekyll site.
+
+Many thanks for [Ben Balter](https://github.com/benbalter) for alerting us to the problem
+and [submitting a patch][1349] so quickly.
+
+[230]: https://github.com/Shopify/liquid/pull/230
+[1349]: {{ site.repository }}/issues/1349
diff --git a/_posts/2013-09-06-jekyll-1-2-0-released.markdown b/_posts/2013-09-06-jekyll-1-2-0-released.markdown
new file mode 100755
index 0000000..ae5448c
--- /dev/null
+++ b/_posts/2013-09-06-jekyll-1-2-0-released.markdown
@@ -0,0 +1,23 @@
+---
+layout: news_item
+title: "Jekyll 1.2.0 Released"
+date: "2013-09-06 22:02:41 -0400"
+author: parkr
+version: 1.2.0
+categories: [release]
+---
+
+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.
+
+Here are a few things we think you'll want to know about this release:
+
+* Run `jekyll serve --detach` to boot up a WEBrick server in the background. **Note:** you'll need to run `kill [server_pid]` to shut the server down.
+* You can now **disable automatically-generated excerpts** if you set `excerpt_separator` to `""`.
+* If you're moving around pages and post, you can now check for **URL conflicts** by running `jekyll doctor`.
+* If you're a fan of the drafts feature, you'll be happy to know we've added `-D`, a shortened version of `--drafts`.
+* Permalinks with special characters should now generate without errors.
+* Expose the current Jekyll version as the `jekyll.version` Liquid variable.
+
+For a full run-down, visit our [change log](/docs/history/)!
diff --git a/_posts/2013-09-14-jekyll-1-2-1-released.markdown b/_posts/2013-09-14-jekyll-1-2-1-released.markdown
new file mode 100755
index 0000000..832dbd0
--- /dev/null
+++ b/_posts/2013-09-14-jekyll-1-2-1-released.markdown
@@ -0,0 +1,19 @@
+---
+layout: news_item
+title: 'Jekyll 1.2.1 Released'
+date: 2013-09-14 20:46:50 -0400
+author: parkr
+version: 1.2.1
+categories: [release]
+---
+
+Quick turnover, anyone? A [recent incompatibility with Liquid
+v2.5.2](https://github.com/jekyll/jekyll/pull/1525) produced a nasty bug in
+which `include` tags were not rendered properly within `if` blocks.
+
+This release also includes a better handling of detached servers (prints pid and
+the command for killing the process). **Note**: the `--detach` flag and
+`--watch` flags are presently incompatible in 1.2.x. Fix for that coming soon!
+
+For a full list of the fixes in this release, check out [the change
+log](/docs/history/)!
diff --git a/_posts/2013-10-28-jekyll-1-3-0-rc1-released.markdown b/_posts/2013-10-28-jekyll-1-3-0-rc1-released.markdown
new file mode 100755
index 0000000..5a64cfc
--- /dev/null
+++ b/_posts/2013-10-28-jekyll-1-3-0-rc1-released.markdown
@@ -0,0 +1,19 @@
+---
+layout: news_item
+title: 'Jekyll 1.3.0.rc1 Released'
+date: 2013-10-28 20:14:39 -0500
+author: mattr-
+version: 1.3.0.rc1
+categories: [release]
+---
+
+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.
+
+Please take this prerelease for a spin and [let us
+know](https://github.com/jekyll/jekyll/issues/new) if you run into any
+issues!
+
+
diff --git a/_posts/2013-11-04-jekyll-1-3-0-released.markdown b/_posts/2013-11-04-jekyll-1-3-0-released.markdown
new file mode 100755
index 0000000..1e32511
--- /dev/null
+++ b/_posts/2013-11-04-jekyll-1-3-0-released.markdown
@@ -0,0 +1,43 @@
+---
+layout: news_item
+title: 'Jekyll 1.3.0 Released'
+date: 2013-11-04 21:46:02 -0600
+author: mattr-
+version: 1.3.0
+categories: [release]
+---
+
+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 **huge** release full of all
+sorts of new features, bug fixes, and other things that you're sure to
+love.
+
+Here are a few things we think you'll want to know about this release:
+
+* You can add [arbitrary data][] to the site by adding YAML files under a
+ site's `_data` directory. This will allow you to avoid
+ repetition in your templates and to set site specific options without
+ changing `_config.yml`.
+
+* You can now run `jekyll serve --detach` to boot up a WEBrick server in the
+ background. **Note:** you'll need to run `kill [server_pid]` to shut
+ the server down. When ran, you'll get a process id that you can use in
+ place of `[server_pid]`
+
+* You can now **disable automatically-generated excerpts** if you set
+ `excerpt_separator` to `""`.
+
+* If you're moving pages and posts, you can now check for **URL
+ conflicts** by running `jekyll doctor`.
+
+* If you're a fan of the drafts feature, you'll be happy to know we've
+ added `-D`, a shortened version of `--drafts`.
+
+* Permalinks with special characters should now generate without errors.
+
+* Expose the current Jekyll version as the `jekyll.version` Liquid
+ variable.
+
+For a full run-down, visit our [change log](/docs/history/)!
+
+[arbitrary data]: /docs/datafiles/
diff --git a/_posts/2013-11-26-jekyll-1-3-1-released.markdown b/_posts/2013-11-26-jekyll-1-3-1-released.markdown
new file mode 100755
index 0000000..4b4c37d
--- /dev/null
+++ b/_posts/2013-11-26-jekyll-1-3-1-released.markdown
@@ -0,0 +1,21 @@
+---
+layout: news_item
+title: 'Jekyll 1.3.1 Released'
+date: 2013-11-26 19:52:20 -0600
+author: mattr-
+version: 1.3.1
+categories: [release]
+---
+
+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.
+
+In addition to a couple of other smaller bug fixes, the biggest thing
+we've fixed is an issue with the `--watch` option with Ruby 1.8.7. For a
+full run-down, visit our [change log](/docs/history/)!
+
+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
diff --git a/_posts/2013-12-07-jekyll-1-4-0-released.markdown b/_posts/2013-12-07-jekyll-1-4-0-released.markdown
new file mode 100755
index 0000000..d7a0c14
--- /dev/null
+++ b/_posts/2013-12-07-jekyll-1-4-0-released.markdown
@@ -0,0 +1,30 @@
+---
+layout: news_item
+title: 'Jekyll 1.4.0 Released'
+date: 2013-12-07 13:55:28 -0600
+author: mattr-
+version: 1.4.0
+categories: [release]
+---
+
+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.
+
+Here are a few things we think you'll want to know about this release:
+
+* TOML is now a supported markup language for config files.
+
+* 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.
+
+* Non-`gem` Plugins are now sorted alphabetically by filename before they're
+ processed, which can provide a rudimentary way to establish a load order for
+ plugins.
+
+For a full run-down, visit our [change log](/docs/history/)!
+
+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.
diff --git a/_posts/2013-12-09-jekyll-1-4-1-released.markdown b/_posts/2013-12-09-jekyll-1-4-1-released.markdown
new file mode 100755
index 0000000..509571b
--- /dev/null
+++ b/_posts/2013-12-09-jekyll-1-4-1-released.markdown
@@ -0,0 +1,20 @@
+---
+layout: news_item
+title: 'Jekyll 1.4.1 Released'
+date: 2013-12-09 20:44:13 -0600
+author: mattr-
+version: 1.4.1
+categories: [release]
+---
+
+Another quick turnover, anyone? A [critical
+bug]({{ site.repository }}/issues/1794) in the reading of
+posts snuck itself into the 1.4.0 release.
+
+To address this issue, we're releasing v1.4.1 of Jekyll so that you can
+keep on writing without any problems.
+
+As always, you can find the full list of fixes in this release in the
+[change log](/docs/history/)!
+
+
diff --git a/_posts/2013-12-16-jekyll-1-4-2-released.markdown b/_posts/2013-12-16-jekyll-1-4-2-released.markdown
new file mode 100755
index 0000000..afc9214
--- /dev/null
+++ b/_posts/2013-12-16-jekyll-1-4-2-released.markdown
@@ -0,0 +1,18 @@
+---
+layout: news_item
+title: 'Jekyll 1.4.2 Released'
+date: 2013-12-16 19:48:13 -0500
+author: parkr
+version: 1.4.2
+categories: [release]
+---
+
+This release fixes [a regression][] where Maruku fenced code blocks were turned
+off, instead of the previous default to on. We've added a new default
+configuration to our `maruku` config key: `fenced_code_blocks` and set it to
+default to `true`.
+
+If you do not wish to use Maruku fenced code blocks, you may turn this option
+off in your site's configuration file.
+
+[a regression]: https://github.com/jekyll/jekyll/pull/1830
diff --git a/_posts/2014-01-13-jekyll-1-4-3-released.markdown b/_posts/2014-01-13-jekyll-1-4-3-released.markdown
new file mode 100755
index 0000000..a97bcec
--- /dev/null
+++ b/_posts/2014-01-13-jekyll-1-4-3-released.markdown
@@ -0,0 +1,26 @@
+---
+layout: news_item
+title: 'Jekyll 1.4.3 Released'
+date: 2014-01-13 17:43:32 -0800
+author: benbalter
+version: 1.4.3
+categories: [release]
+---
+
+Jekyll 1.4.3 contains two **critical** 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.
+([See pull request.]({{ site.repository }}/pull/1944))
+
+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.
+
+Versions of Jekyll prior to 1.4.3 may also allow malicious users to write
+arbitrary `.html` 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.
+
+*Maintainer's note: Many thanks to @gregose and @charliesome for discovering
+these vulnerabilities, and to @BenBalter and @alindeman for writing the patch.*
diff --git a/_posts/2014-03-24-jekyll-1-5-0-released.markdown b/_posts/2014-03-24-jekyll-1-5-0-released.markdown
new file mode 100755
index 0000000..5b103dc
--- /dev/null
+++ b/_posts/2014-03-24-jekyll-1-5-0-released.markdown
@@ -0,0 +1,19 @@
+---
+layout: news_item
+title: 'Jekyll 1.5.0 Released'
+date: 2014-03-24 20:37:59 -0400
+author: parkr
+version: 1.5.0
+categories: [release]
+---
+
+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 `safe_yaml` dependency below 1.0 and the
+inability to use Jekyll 1.4.3 on Windows due to a [fun issue with path sanitizing][].
+
+For a full changelog, check out our [history][] page.
+
+Now, back to work on 2.0.0!
+
+[fun issue with path sanitizing]: https://github.com/jekyll/jekyll/issues/1948
+[history]: /docs/history/#v1-5-0
diff --git a/_posts/2014-03-27-jekyll-1-5-1-released.markdown b/_posts/2014-03-27-jekyll-1-5-1-released.markdown
new file mode 100755
index 0000000..e8a4096
--- /dev/null
+++ b/_posts/2014-03-27-jekyll-1-5-1-released.markdown
@@ -0,0 +1,26 @@
+---
+layout: news_item
+title: 'Jekyll 1.5.1 Released'
+date: 2014-03-27 22:43:48 -0400
+author: parkr
+version: 1.5.1
+categories: [release]
+---
+
+The hawk-eyed [@gregose](https://github.com/gregose) spotted a bug in our
+`Jekyll.sanitized_path` code:
+
+{% highlight ruby %}
+> sanitized_path("/tmp/foobar/jail", "..c:/..c:/..c:/etc/passwd")
+=> "/tmp/foobar/jail/../../../etc/passwd"
+{% endhighlight %}
+
+Well, we can't have that! In 1.5.1, you'll instead see:
+
+{% highlight ruby %}
+> sanitized_path("/tmp/foobar/jail", "..c:/..c:/..c:/etc/passwd")
+=> "/tmp/foobar/jail/..c:/..c:/..c:/etc/passwd"
+{% endhighlight %}
+
+Luckily not affecting 1.4.x, this fix will make 1.5.0 that much safer for
+the masses. Thanks, Greg!
diff --git a/_posts/2014-05-06-jekyll-turns-2-0-0.markdown b/_posts/2014-05-06-jekyll-turns-2-0-0.markdown
new file mode 100755
index 0000000..62c1208
--- /dev/null
+++ b/_posts/2014-05-06-jekyll-turns-2-0-0.markdown
@@ -0,0 +1,31 @@
+---
+layout: news_item
+title: 'Jekyll turns 2.0.0'
+author: parkr
+version: 2.0.0
+categories: [release]
+---
+
+A year ago to the day, [we released Jekyll 1.0.0][jekyll-1]. One year later, we present to you the next major version: Jekyll 2.0.0.
+
+Jam-packed with some [highly-requested features and bugfixes galore][changelog], this is the best Jekyll yet. Some notable changes:
+
+1. [Collections](/docs/collections/) - 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!
+2. [Brand new site template](https://github.com/jekyll/jekyll/pull/2050#issuecomment-35938016) (thanks [@jglovier][]!) - Getting started with Jekyll just got a lot easier and a lot more beautiful. Just run `jekyll new ` and you're good to go.
+3. [Native Sass & CoffeeScript support](/docs/assets/) - 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!
+4. [YAML Front Matter defaults](/docs/configuration/#front-matter-defaults) - If you've set `layout: post` more than once in your life, you'll love this new feature: set front matter defaults for a given directory or type.
+5. [Custom markdown processors](/docs/configuration/#custom-markdown-processors) - Always wanted to use your favourite home-grown Markdown converter, but couldn't with Jekyll? Now you can. Simply specify `markdown: MyConverterClass` and you're on your way.
+6. [Addition of `where` and `group_by` Liquid filters](/docs/templates/#filters) - Simplifying your Liquid templates one filter at a time. The `where` filter selects from an array all items within which have a given value for a property. The `group_by` filter groups all items in an array which have the same value for a given property.
+7. [Switch from Maruku to Kramdown as default markdown converter](https://github.com/jekyll/jekyll/pull/1988) - Maruku is dead. We've replaced it with the converter which has the closest feature parity: Kramdown!
+
+Check out our [changelog][] for a complete list of all (200+) changes.
+
+Many thanks to these 183 contributors for making Jekyll 2.0.0 happen:
+
+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.
+
+Happy developing!
+
+[changelog]: /docs/history/
+[@jglovier]: https://github.com/jglovier
+[jekyll-1]: /news/2013/05/06/jekyll-1-0-0-released/
diff --git a/_posts/2014-05-08-jekyll-2-0-3-released.markdown b/_posts/2014-05-08-jekyll-2-0-3-released.markdown
new file mode 100755
index 0000000..ac5e9d7
--- /dev/null
+++ b/_posts/2014-05-08-jekyll-2-0-3-released.markdown
@@ -0,0 +1,18 @@
+---
+layout: news_item
+title: 'Jekyll 2.0.3 Released'
+date: 2014-05-08 22:43:17 -0400
+author: parkr
+version: 2.0.3
+categories: [release]
+---
+
+Hey again! Just wanted to let you know we've released another version of Jekyll, jam-packed with bug fixes.
+
+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!
+
+Thank you to the contributors that contributed code to 2.0.1, 2.0.2, and/or 2.0.3:
+
+Parker Moore, Yi Zeng, Gabe Ortiz, Aaron Broder, Alberto Grespan, gpxl, David Briggs, Kevin Ingersoll, and Troy Swanson.
+
+As always, check out the [changelog](/docs/history/) for more info. Happy Jekylling!
diff --git a/_posts/2014-06-04-jekyll-stickers-1-dollar-stickermule.markdown b/_posts/2014-06-04-jekyll-stickers-1-dollar-stickermule.markdown
new file mode 100755
index 0000000..92b8539
--- /dev/null
+++ b/_posts/2014-06-04-jekyll-stickers-1-dollar-stickermule.markdown
@@ -0,0 +1,19 @@
+---
+layout: news_item
+title: 'Pick Up your $1 Jekyll Sticker'
+date: 2014-06-04 15:46:53 -0400
+author: parkr
+categories: [partners]
+---
+
+
+
+You may have heard that [@cobyism](https://github.com/cobyism)'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.
+
+The StickerMule team says, *"Pine no longer!"* StickerMule has **[discounted the
+price of Jekyll stickers down to $1 and are offering free (domestic)
+shipping](http://www.stickermule.com/marketplace/825-jekyll-stickers)!**
+Go grab one now on the StickerMule marketplace – [they'll look
+swell on your favourite hardware.](https://twitter.com/parkr/status/430826309707902976/photo/1)
diff --git a/_posts/2014-06-28-jekyll-turns-21-i-mean-2-1-0.markdown b/_posts/2014-06-28-jekyll-turns-21-i-mean-2-1-0.markdown
new file mode 100755
index 0000000..0cfb31d
--- /dev/null
+++ b/_posts/2014-06-28-jekyll-turns-21-i-mean-2-1-0.markdown
@@ -0,0 +1,31 @@
+---
+layout: news_item
+title: 'Jekyll Turns 21! Err... I mean 2.1.0.'
+date: 2014-06-28 17:26:59 -0400
+author: parkr
+version: 2.1.0
+categories: [release]
+---
+
+Jekyll's finally [legal to drink in the States](http://en.wikipedia.org/wiki/Legal_drinking_age).
+And he's done a lot of learning in the process! Here are some of the new
+things to look forward to:
+
+- Uses the latest Liquid version (2.6.1) (#2495)
+- Set front matter defaults for collections (#2419)
+- Set a collection-specific URL template (#2418)
+- `pygments.rb` 0.6.0! (#2504)
+- `.json` files in `_data` (#2369)
+- Allow subdirectories in `_data` (#2395)
+- Add support for `hl_lines` in `highlight` tag (#2532)
+- Post categories now merge with directory, front matter, and defaults (#2373)
+- New `--skip_initial_build` flag for `jekyll serve` (#2477)
+- A bajilion bug fixes and site updates!
+
+Let's go party!
+
+*Check out the [full changelog](/docs/history/#v2-1-0) for more.*
+
+Many thanks to these 37 contributors for the 2.1.0 release:
+
+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.
diff --git a/_posts/2014-07-01-jekyll-2-1-1-released.markdown b/_posts/2014-07-01-jekyll-2-1-1-released.markdown
new file mode 100755
index 0000000..8142353
--- /dev/null
+++ b/_posts/2014-07-01-jekyll-2-1-1-released.markdown
@@ -0,0 +1,30 @@
+---
+layout: news_item
+title: 'Jekyll 2.1.1 Released'
+date: 2014-07-01 20:16:43 -0400
+author: parkr
+version: 2.1.1
+categories: [release]
+---
+
+This is a minor release for Jekyll 2.1.0. It fixes a couple bugs and
+introduces fixes for a couple security-related issues.
+
+It covers two security vulnerabilities:
+
+1. One in the reading of data
+2. One in the `layouts` setting
+
+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.
+
+For more, check out [`jekyll/jekyll#2563`](https://github.com/jekyll/jekyll/pull/2563).
+
+Additionally, the dependency on Maruku has been loosened and a bug was
+fixed with document URLs.
+
+As always, check out the [full changelog](/docs/history/) for more info!
+
+Happy Jekylling!
diff --git a/_posts/2014-07-29-jekyll-2-2-0-released.markdown b/_posts/2014-07-29-jekyll-2-2-0-released.markdown
new file mode 100755
index 0000000..9410df6
--- /dev/null
+++ b/_posts/2014-07-29-jekyll-2-2-0-released.markdown
@@ -0,0 +1,19 @@
+---
+layout: news_item
+title: 'Jekyll 2.2.0 Released'
+date: 2014-07-29 18:59:13 -0400
+author: parkr
+version: 2.2.0
+categories: [release]
+---
+
+Jekyll 2.2.0 contains a few key updates:
+
+1. A warning will now fire if you specify a layout in any of your pages or
+ posts that doesn't exist.
+2. Certain Pygments options are now whitelisted in safe mode
+3. Categories in a post's path are now respected (i.e. folders in `_posts`
+ will now work properly).
+
+As always, a full list of the updates are on the
+[history page](/docs/history#v2-2-0). Happy Jekylling!
diff --git a/_posts/2014-08-10-jekyll-2-3-0-released.markdown b/_posts/2014-08-10-jekyll-2-3-0-released.markdown
new file mode 100755
index 0000000..63fe2b4
--- /dev/null
+++ b/_posts/2014-08-10-jekyll-2-3-0-released.markdown
@@ -0,0 +1,41 @@
+---
+layout: news_item
+title: 'Jekyll 2.3.0 Released'
+date: 2014-08-10 20:38:34 -0400
+author: parkr
+version: 2.3.0
+categories: [release]
+---
+
+This latest release of Jekyll includes a slew of enhancements and bug
+fixes. Some of the highlights:
+
+* Strange bug around spacing/indentation should be resolved. [It was a
+ curious bug indeed.](https://github.com/jekyll/jekyll/issues/2676)
+* Pages, Posts, and Drafts can now be converted by multiple converters.
+* Static files can now be safely included in collections. They'll be placed
+ in a `collection.files` array. `collection.docs` still holds exclusively
+ content with YAML front matter.
+* Sass files can once again be rendered by Liquid. However, neither Sass
+ nor CoffeeScript can ever have a layout. Bonus: `scssify` and `sassify`
+ Liquid filters.
+* Partial variables allowed now in the path argument of `include` calls
+* We added a `jekyll help` command. Pass it a subcommand to see more info
+ about that subcommand. Or don't, to see the help for `jekyll` itself.
+* Lots of fixes to the site template we use for `jekyll new`, including
+ converting the CSS into SCSS.
+* The `jsonify` filter will now call `#to_liquid` for you
+* Lots, lots more!
+
+One change deserves special note. In [#2633][], subfolders *inside* a
+`_posts` 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 [#2705][], because it was a change in behaviour that was already
+well-established (at least since Jekyll v0.7.0), and was convenient.
+
+[#2633]: {{ site.repository }}/issues/2633
+[#2705]: {{ site.repository }}/issues/2705
+
+For more excellent CHANGELOG reading material, check out the [History
+page](/docs/history/)! Happy Jekylling!
diff --git a/_posts/2014-09-09-jekyll-2-4-0-released.markdown b/_posts/2014-09-09-jekyll-2-4-0-released.markdown
new file mode 100755
index 0000000..e8dda67
--- /dev/null
+++ b/_posts/2014-09-09-jekyll-2-4-0-released.markdown
@@ -0,0 +1,25 @@
+---
+layout: news_item
+title: 'A Wild Jekyll 2.4.0 Appeared!'
+date: 2014-09-09 21:10:33 -0700
+author: parkr
+version: 2.4.0
+categories: [release]
+---
+
+Well, lookie here! A new release of Jekyll! v2.4.0 contains lots of goodies, including some brilliant new additions:
+
+- A new `relative_include` Liquid tag ([#2870]({{ site.repository }}/issues/2870))
+- Render Liquid in CoffeeScript files ([#2830]({{ site.repository }}/issues/2830))
+- Add 4 new array Liquid filters: `push`, `pop`, `shift`, and `unshift` ([#2895]({{ site.repository }}/pull/2895))
+- Auto-enable watch on 'serve' ([#2858]({{ site.repository }}/issues/2858)). No more `-w`!
+- Add `:title` and `:name` to collection URL template fillers ([#2864]({{ site.repository }}/issues/2864) & [#2799]({{ site.repository }}/issues/2799))
+- Add support for CSV files in the `_data` directory ([#2761]({{ site.repository }}/issues/2761))
+- Add `inspect` liquid filter ([#2867]({{ site.repository }}/issues/2867))
+- Add a `slugify` Liquid filter ([#2880]({{ site.repository }}/issues/2880))
+
+Some other wunderbar bug fixes in there as well. Check out the [full changelog](/docs/history/) for the whole scoop.
+
+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!!
+
+Happy Jekylling!
diff --git a/_posts/2014-11-06-jekylls-midlife-crisis-jekyll-turns-2-5-0.markdown b/_posts/2014-11-06-jekylls-midlife-crisis-jekyll-turns-2-5-0.markdown
new file mode 100755
index 0000000..cc5de7c
--- /dev/null
+++ b/_posts/2014-11-06-jekylls-midlife-crisis-jekyll-turns-2-5-0.markdown
@@ -0,0 +1,47 @@
+---
+layout: news_item
+title: "Jekyll's Mid-Life Crisis (Or, Jekyll turns 2.5.0)"
+date: 2014-11-05 10:48:22 -0800
+author: parkr
+version: 2.5.0
+categories: [release]
+---
+
+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:
+
+* Require plugins in the `:jekyll_plugins` Gemfile group (turned off with an environment variable)
+* YAML Front Matter permalinks can now contain placeholders like `:name`. Check out all the placeholders on the [Permalinks docs page](/docs/permalinks/).
+* The `jsonify` filter now deep-converts arrays to liquid.
+* Shorted `build` and `serve` commands with `b` and `s` aliases, respectively
+* WEBrick will now list your directory if it can't find an index file.
+* Any enumerable can be used with the `where` filter.
+* Performance optimizations thanks to @tmm1's [stackprof](https://github.com/tmm1/stackprof)
+* Fix for Rouge's Redcarpet interface
+* Security auditors will love this: path sanitation has now been centralized.
+* Specify a log level with `JEKYLL_LOG_LEVEL`: debug, info, warn, or error.
+
+...and a whole bunch of other fixes and enhancements you can read more
+about in [the changelog!](/docs/history/)
+
+As always, if you run into issues, please [check the issues]({{ site.repository }}/issues)
+and [create an issue if one doesn't exist for the bug you encountered]({{ site.repository }}/issues/new).
+If you just need some help, the extraordinary [jekyll help team is here for
+you!]({{ site.help_url }})
+
+*When was the [first commit to Jekyll](https://github.com/jekyll/jekyll/commit/d189e05d236769c1e5594af9db4d6eacb86fc16e)?
+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!*
+
+Thanks to the following contributors for making this release possible:
+
+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!
diff --git a/_posts/2014-11-08-jekyll-2-5-1-released.markdown b/_posts/2014-11-08-jekyll-2-5-1-released.markdown
new file mode 100755
index 0000000..3237e48
--- /dev/null
+++ b/_posts/2014-11-08-jekyll-2-5-1-released.markdown
@@ -0,0 +1,29 @@
+---
+layout: news_item
+title: 'Jekyll 2.5.1 Released'
+date: 2014-11-09 09:47:52 -0800
+author: parkr
+version: 2.5.1
+categories: [release]
+---
+
+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.
+
+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 [**Windows Test Force**][] (WTF) which is a group of Jekyll
+users dedicated to making sure all future releases work on Windows *before*
+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.
+
+Happy Jekylling!
+
+[**Windows Test Force**]: https://github.com/jekyll/jekyll/issues/3069
diff --git a/_posts/2014-11-12-jekyll-2-5-2-released.markdown b/_posts/2014-11-12-jekyll-2-5-2-released.markdown
new file mode 100755
index 0000000..3eab899
--- /dev/null
+++ b/_posts/2014-11-12-jekyll-2-5-2-released.markdown
@@ -0,0 +1,18 @@
+---
+layout: news_item
+title: 'Jekyll 2.5.2 Released'
+date: 2014-11-12 18:49:08 -0800
+author: parkr
+version: 2.5.2
+categories: [release]
+---
+
+A very minor release, 2.5.2 fixes a bug with path sanitation that 2.5.1
+introduced. It also improves the `post_url` tag such that it checks the
+posts' name (e.g. `2014-03-03-my-cool-post`) instead of a compiled time and
+name. This fixes issues where posts are created and the day changes based
+on timezone discrepancies.
+
+[Full history here.](/docs/history/)
+
+Happy Jekylling!
diff --git a/_sass/.sass-cache/89a83dca448ff37810b0714f8b03e869032bdae6/normalize.scssc b/_sass/.sass-cache/89a83dca448ff37810b0714f8b03e869032bdae6/normalize.scssc
new file mode 100755
index 0000000..d1af973
Binary files /dev/null and b/_sass/.sass-cache/89a83dca448ff37810b0714f8b03e869032bdae6/normalize.scssc differ
diff --git a/_sass/_font-awesome.scss b/_sass/_font-awesome.scss
new file mode 100755
index 0000000..24ae2b6
--- /dev/null
+++ b/_sass/_font-awesome.scss
@@ -0,0 +1,22 @@
+/*!
+ * Font Awesome 4.2.0 by @davegandy - http://fontawesome.io - @fontawesome
+ * License - http://fontawesome.io/license (Font: SIL OFL 1.1, CSS: MIT License)
+ */
+@font-face {
+ font-family: 'FontAwesome';
+ src: url('../fonts/fontawesome-webfont.eot?v=4.2.0');
+ src: url('../fonts/fontawesome-webfont.eot?#iefix&v=4.2.0') format('embedded-opentype'), url('../fonts/fontawesome-webfont.woff?v=4.2.0') format('woff'), url('../fonts/fontawesome-webfont.ttf?v=4.2.0') format('truetype'), url('../fonts/fontawesome-webfont.svg?v=4.2.0#fontawesomeregular') format('svg');
+ font-weight: normal;
+ font-style: normal;
+}
+.fa {
+ display: inline-block;
+ font: normal normal normal 14px/1 FontAwesome;
+ font-size: inherit;
+ text-rendering: auto;
+ -webkit-font-smoothing: antialiased;
+ -moz-osx-font-smoothing: grayscale;
+}
+.fa-link:before {
+ content: "\f0c1";
+}
diff --git a/_sass/_gridism.scss b/_sass/_gridism.scss
new file mode 100755
index 0000000..61698ef
--- /dev/null
+++ b/_sass/_gridism.scss
@@ -0,0 +1,124 @@
+/*
+ * 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 .one-fourth, .grid .w-1-4 { width: 25%; }
+.grid .three-quarters,
+.grid .three-fourths, .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 */
+
+/* Clearfix after every .grid */
+.grid {
+ *zoom: 1;
+}
+.grid:before, .grid:after {
+ display: table;
+ content: "";
+ line-height: 0;
+}
+.grid:after {
+ clear: both;
+}
+
+/* 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; }
+
+/* A property for a better rendering of images in units: in
+ this way bigger pictures are just resized if the unit
+ becomes smaller */
+.unit img {
+ max-width: 100%;
+}
+
+/* Responsive Stuff */
+@media screen and (max-width: 568px) {
+ /* Stack anything that isn’t full-width on smaller screens
+ and doesn't provide the no-stacking-on-mobiles class */
+ .grid:not(.no-stacking-on-mobiles) > .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;
+ }
+}
+
+/* Expand the wrap a bit further on larger screens */
+@media screen and (min-width: 1180px) {
+ .wider .grid,
+ .grid.wider {
+ max-width: 1180px;
+ margin: 0 auto;
+ }
+}
diff --git a/_sass/_mixins.scss b/_sass/_mixins.scss
new file mode 100755
index 0000000..5b9bb43
--- /dev/null
+++ b/_sass/_mixins.scss
@@ -0,0 +1,38 @@
+@mixin box-shadow($shadow...) {
+ -webkit-box-shadow: $shadow;
+ -moz-box-shadow: $shadow;
+ box-shadow: $shadow;
+}
+
+@mixin border-radius($radius...) {
+ -webkit-border-radius: $radius;
+ -moz-border-radius: $radius;
+ border-radius: $radius;
+}
+
+@mixin border-top-left-radius($radius...) {
+ -webkit-border-top-left-radius: $radius;
+ -moz-border-radius-topleft: $radius;
+ border-top-left-radius: $radius;
+}
+
+@mixin border-top-right-radius($radius...) {
+ -webkit-border-top-right-radius: $radius;
+ -moz-border-radius-topright: $radius;
+ border-top-right-radius: $radius;
+}
+
+@mixin transition($transition...) {
+ -webkit-transition: $transition;
+ -moz-transition: $transition;
+ -o-transition: $transition;
+ transition: $transition;
+}
+
+@mixin user-select($select...) {
+ -webkit-user-select: $select; /* Chrome all / Safari all */
+ -moz-user-select: $select; /* Firefox all */
+ -ms-user-select: $select; /* IE 10+ */
+ -o-user-select: $select;
+ user-select: $select;
+}
diff --git a/_sass/_normalize.scss b/_sass/_normalize.scss
new file mode 100755
index 0000000..f6e0b65
--- /dev/null
+++ b/_sass/_normalize.scss
@@ -0,0 +1 @@
+/*! normalize.css v3.0.2 | MIT License | git.io/normalize */html{font-family:sans-serif;-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%}body{margin:0}article,aside,details,figcaption,figure,footer,header,hgroup,main,menu,nav,section,summary{display:block}audio,canvas,progress,video{display:inline-block;vertical-align:baseline}audio:not([controls]){display:none;height:0}[hidden],template{display:none}a{background-color:transparent}a:active,a:hover{outline:0}abbr[title]{border-bottom:1px dotted}b,strong{font-weight:700}dfn{font-style:italic}h1{font-size:2em;margin:.67em 0}mark{background:#ff0;color:#000}small{font-size:80%}sub,sup{font-size:75%;line-height:0;position:relative;vertical-align:baseline}sup{top:-.5em}sub{bottom:-.25em}img{border:0}svg:not(:root){overflow:hidden}figure{margin:1em 40px}hr{-moz-box-sizing:content-box;box-sizing:content-box;height:0}pre{overflow:auto}code,kbd,pre,samp{font-family:monospace,monospace;font-size:1em}button,input,optgroup,select,textarea{color:inherit;font:inherit;margin:0}button{overflow:visible}button,select{text-transform:none}button,html input[type=button],input[type=reset],input[type=submit]{-webkit-appearance:button;cursor:pointer}button[disabled],html input[disabled]{cursor:default}button::-moz-focus-inner,input::-moz-focus-inner{border:0;padding:0}input{line-height:normal}input[type=checkbox],input[type=radio]{box-sizing:border-box;padding:0}input[type=number]::-webkit-inner-spin-button,input[type=number]::-webkit-outer-spin-button{height:auto}input[type=search]{-webkit-appearance:textfield;-moz-box-sizing:content-box;-webkit-box-sizing:content-box;box-sizing:content-box}input[type=search]::-webkit-search-cancel-button,input[type=search]::-webkit-search-decoration{-webkit-appearance:none}fieldset{border:1px solid silver;margin:0 2px;padding:.35em .625em .75em}legend{border:0;padding:0}textarea{overflow:auto}optgroup{font-weight:700}table{border-collapse:collapse;border-spacing:0}td,th{padding:0}
\ No newline at end of file
diff --git a/_sass/_pygments.scss b/_sass/_pygments.scss
new file mode 100755
index 0000000..2858bcd
--- /dev/null
+++ b/_sass/_pygments.scss
@@ -0,0 +1,78 @@
+.highlight {
+ .hll { background-color: #ffffcc }
+ .c { color: #87ceeb} /* Comment */
+ .err { color: #ffffff} /* Error */
+ .g { color: #ffffff} /* Generic */
+ .k { color: #f0e68c} /* Keyword */
+ .l { color: #ffffff} /* Literal */
+ .n { color: #ffffff} /* Name */
+ .o { color: #ffffff} /* Operator */
+ .x { color: #ffffff} /* Other */
+ .p { color: #ffffff} /* Punctuation */
+ .cm { color: #87ceeb} /* Comment.Multiline */
+ .cp { color: #cd5c5c} /* Comment.Preproc */
+ .c1 { color: #87ceeb} /* Comment.Single */
+ .cs { color: #87ceeb} /* Comment.Special */
+ .gd { color: #0000c0; font-weight: bold; background-color: #008080 } /* Generic.Deleted */
+ .ge { color: #c000c0; text-decoration: underline} /* Generic.Emph */
+ .gr { color: #c0c0c0; font-weight: bold; background-color: #c00000 } /* Generic.Error */
+ .gh { color: #cd5c5c} /* Generic.Heading */
+ .gi { color: #ffffff; background-color: #0000c0 } /* Generic.Inserted */
+ span.go { color: #add8e6; font-weight: bold; background-color: #4d4d4d } /* Generic.Output, qualified with span to prevent applying this style to the Go language, see #1153. */
+ .gp { color: #ffffff} /* Generic.Prompt */
+ .gs { color: #ffffff} /* Generic.Strong */
+ .gu { color: #cd5c5c} /* Generic.Subheading */
+ .gt { color: #c0c0c0; font-weight: bold; background-color: #c00000 } /* Generic.Traceback */
+ .kc { color: #f0e68c} /* Keyword.Constant */
+ .kd { color: #f0e68c} /* Keyword.Declaration */
+ .kn { color: #f0e68c} /* Keyword.Namespace */
+ .kp { color: #f0e68c} /* Keyword.Pseudo */
+ .kr { color: #f0e68c} /* Keyword.Reserved */
+ .kt { color: #bdb76b} /* Keyword.Type */
+ .ld { color: #ffffff} /* Literal.Date */
+ .m { color: #ffffff} /* Literal.Number */
+ .s { color: #ffffff} /* Literal.String */
+ .na { color: #ffffff} /* Name.Attribute */
+ .nb { color: #ffffff} /* Name.Builtin */
+ .nc { color: #ffffff} /* Name.Class */
+ .no { color: #ffa0a0} /* Name.Constant */
+ .nd { color: #ffffff} /* Name.Decorator */
+ .ni { color: #ffdead} /* Name.Entity */
+ .ne { color: #ffffff} /* Name.Exception */
+ .nf { color: #ffffff} /* Name.Function */
+ .nl { color: #ffffff} /* Name.Label */
+ .nn { color: #ffffff} /* Name.Namespace */
+ .nx { color: #ffffff} /* Name.Other */
+ .py { color: #ffffff} /* Name.Property */
+ .nt { color: #f0e68c} /* Name.Tag */
+ .nv { color: #98fb98} /* Name.Variable */
+ .ow { color: #ffffff} /* Operator.Word */
+ .w { color: #ffffff} /* Text.Whitespace */
+ .mf { color: #ffffff} /* Literal.Number.Float */
+ .mh { color: #ffffff} /* Literal.Number.Hex */
+ .mi { color: #ffffff} /* Literal.Number.Integer */
+ .mo { color: #ffffff} /* Literal.Number.Oct */
+ .sb { color: #ffffff} /* Literal.String.Backtick */
+ .sc { color: #ffffff} /* Literal.String.Char */
+ .sd { color: #ffffff} /* Literal.String.Doc */
+ .s2 { color: #ffffff} /* Literal.String.Double */
+ .se { color: #ffffff} /* Literal.String.Escape */
+ .sh { color: #ffffff} /* Literal.String.Heredoc */
+ .si { color: #ffffff} /* Literal.String.Interpol */
+ .sx { color: #ffffff} /* Literal.String.Other */
+ .sr { color: #ffffff} /* Literal.String.Regex */
+ .s1 { color: #ffffff} /* Literal.String.Single */
+ .ss { color: #ffffff} /* Literal.String.Symbol */
+ .bp { color: #ffffff} /* Name.Builtin.Pseudo */
+ .vc { color: #98fb98} /* Name.Variable.Class */
+ .vg { color: #98fb98} /* Name.Variable.Global */
+ .vi { color: #98fb98} /* Name.Variable.Instance */
+ .il { color: #ffffff} /* Literal.Number.Integer.Long */
+ .bash .nv {
+ -webkit-user-select: none;
+ -moz-user-select: none;
+ -ms-user-select: none;
+ -o-user-select: none;
+ user-select: none;
+ }
+}
\ No newline at end of file
diff --git a/_sass/_style.scss b/_sass/_style.scss
new file mode 100755
index 0000000..38bf814
--- /dev/null
+++ b/_sass/_style.scss
@@ -0,0 +1,973 @@
+/* Base */
+
+* {
+ -webkit-box-sizing: border-box;
+ -moz-box-sizing: border-box;
+ box-sizing: border-box;
+}
+
+body {
+ font: 300 21px Lato, 'Helvetica Neue', Helvetica, Arial, sans-serif;
+ color: #ddd;
+ background-color: #333;
+ border-top: 5px solid #fc0;
+ @include box-shadow(inset 0 3px 30px rgba(0,0,0,.3));
+ text-shadow: 0 1px 3px rgba(0,0,0,.5);
+}
+
+.clear {
+ display: block;
+}
+
+.clear:after {
+ content: " ";
+ display: block;
+ height: 0;
+ clear: both;
+ visibility: hidden;
+}
+
+/* Sections */
+
+header,
+section,
+footer {
+ float: left;
+ width: 100%;
+ clear: both;
+}
+
+/* Header */
+
+header {
+
+ h1,
+ nav { display: inline-block; }
+
+ h1 {
+ span { display: none; }
+ }
+}
+
+nav {
+
+ ul {
+ padding: 0;
+ margin: 0;
+ }
+
+ li { display: inline-block; }
+}
+
+.main-nav {
+ margin-top: 52px;
+
+ li {
+ margin-right: 10px;
+
+ a {
+ @include border-radius(5px);
+ font-weight: 900;
+ font-size: 14px;
+ padding: 0.5em 1em;
+ text-shadow: none;
+ text-transform: uppercase;
+ @include transition(all .25s);
+
+ &:hover {
+ background-color: #252525;
+ @include box-shadow(inset 0 1px 3px rgba(0,0,0,.5), 0 1px 0 rgba(255,255,255,.1));
+ text-shadow: 0 1px 3px rgba(0,0,0,.5);
+ }
+ }
+
+ &.current {
+
+ a {
+ background-color: #fc0;
+ color: #222;
+ @include box-shadow(inset 0 1px 0 rgba(255,255,255,.5), 0 1px 5px rgba(0,0,0,.5));
+ text-shadow: 0 1px 0 rgba(255,255,255,.3);
+ }
+ }
+ }
+}
+
+.mobile-nav {
+
+ ul {
+ overflow: hidden;
+ width: 100%;
+ display: table;
+ }
+
+ a {
+ float: left;
+ width: 100%;
+ background-color: #333;
+ color: #fc0;
+ text-align: center;
+ text-transform: uppercase;
+ font-size: 14px;
+ font-weight: 900;
+ padding: 5px;
+ @include border-radius(5px);
+ }
+
+ li {
+ display: table-cell;
+ width: 20%;
+ padding: 8px 2px;
+ }
+
+ .current {
+
+ a {
+ background-color: #fc0;
+ color: #222;
+ @include box-shadow(inset 0 1px 0 rgba(255,255,255,.5), 0 1px 5px rgba(0,0,0,.5));
+ text-shadow: 0 1px 0 rgba(255,255,255,.3);
+ }
+ }
+}
+
+/*
+ * This code is courtesy Ben Balter, modified by Parker Moore for jekyllrb.com
+ * http://ben.balter.com/2014/03/13/pages-anchor-links/
+ */
+.header-link {
+ position: relative;
+ left: 0.5em;
+ opacity: 0;
+ font-size: 0.8em;
+ @include transition(opacity 0.2s ease-in-out 0.1s);
+}
+h2:hover .header-link,
+h3:hover .header-link,
+h4:hover .header-link,
+h5:hover .header-link,
+h6:hover .header-link {
+ opacity: 1;
+}
+
+@media (max-width: 768px) {
+ .main-nav ul {
+ text-align: right;
+ }
+}
+@media (max-width: 830px) {
+ .main-nav {
+ .show-on-mobiles { display: inline; }
+ .hide-on-mobiles { display: none; }
+ }
+}
+
+/* Footer */
+
+footer {
+ background-color: #222;
+ font-size: 16px;
+ padding-bottom: 5px;
+ color: #888;
+ margin-top: 40px;
+
+ a {
+ color: #fff;
+
+ &:hover {
+
+ img { opacity: 1; }
+ }
+ }
+
+ .align-right {
+
+ p { display: inline-block; }
+ }
+
+ img {
+ display: inline-block;
+ position: relative;
+ top: 8px;
+ margin-left: 5px;
+ opacity: .8;
+ padding: 1px;
+ @include transition(opacity .2s);
+ }
+}
+
+@media (max-width: 568px) {
+ footer {
+ .one-third p { margin-bottom: 0; }
+ .two-thirds p { margin-top: -20px; }
+ }
+}
+
+/* Intro */
+
+.intro {
+
+ .unit { padding: 10px 0 40px; }
+
+ p {
+ font-size: 1.75em;
+ line-height: 1em;
+ margin: 0;
+ }
+}
+
+@media (min-width: 569px) {
+ .intro p { font-size: 3.2em; }
+}
+
+/* Quickstart */
+
+.quickstart {
+ background-color: #3F1F1F;
+ color: #fff;
+ margin: 60px 0;
+ @include box-shadow(inset 0 3px 10px rgba(0,0,0,.4));
+
+ .content { padding: 0; }
+
+ h4 {
+ font-size: 24px;
+ line-height: 24px;
+ margin-top: 20px;
+ text-shadow: 0 1px 3px rgba(0,0,0,.8);
+ }
+
+ .code {
+ font-size: 12px;
+ display: block;
+ margin: 0 0 -30px;
+ }
+}
+
+@media (min-width: 768px) {
+ .quickstart {
+
+ .code {
+ font-size: 18px;
+ margin: -30px 0;
+ float: right;
+ }
+
+ h4 {
+ margin: 50px 0 0;
+ text-align: center;
+ }
+ }
+}
+
+/* Code */
+
+.quickstart {
+
+ .code {
+ display: block;
+ padding: 0;
+ font-family: Menlo, Consolas, "Courier New", Courier, "Liberation Mono", monospace;
+ line-height: 1.3em;
+
+ .title {
+ display: block;
+ text-align: center;
+ margin: 0 20px;
+ padding: 5px 0;
+ @include border-radius(5px 5px 0 0);
+ @include box-shadow(0 3px 10px rgba(0,0,0,.5));
+ font: 400 16px/24px 'Helvetica Neue', Helvetica, Arial, sans-serif;
+ color: #444;
+ text-shadow: 0 1px 0 rgba(255,255,255,.5);
+ background-color: #f7f7f7;
+ background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8c3ZnIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjEwMCUiIGhlaWdodD0iMTAwJSIgdmlld0JveD0iMCAwIDEgMSIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSI+CiAgPGxpbmVhckdyYWRpZW50IGlkPSJncmFkLXVjZ2ctZ2VuZXJhdGVkIiBncmFkaWVudFVuaXRzPSJ1c2VyU3BhY2VPblVzZSIgeDE9IjAlIiB5MT0iMCUiIHgyPSIwJSIgeTI9IjEwMCUiPgogICAgPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iI2Y3ZjdmNyIgc3RvcC1vcGFjaXR5PSIxIi8+CiAgICA8c3RvcCBvZmZzZXQ9IjclIiBzdG9wLWNvbG9yPSIjY2ZjZmNmIiBzdG9wLW9wYWNpdHk9IjEiLz4KICAgIDxzdG9wIG9mZnNldD0iMTAwJSIgc3RvcC1jb2xvcj0iI2FhYWFhYSIgc3RvcC1vcGFjaXR5PSIxIi8+CiAgPC9saW5lYXJHcmFkaWVudD4KICA8cmVjdCB4PSIwIiB5PSIwIiB3aWR0aD0iMSIgaGVpZ2h0PSIxIiBmaWxsPSJ1cmwoI2dyYWQtdWNnZy1nZW5lcmF0ZWQpIiAvPgo8L3N2Zz4=);
+ background-image: -webkit-gradient(linear, left top, left bottom, from(#f7f7f7), color-stop(7%, #cfcfcf), to(#aaaaaa));
+ background-image: -webkit-linear-gradient(top, #f7f7f7 0%, #cfcfcf 7%, #aaaaaa 100%);
+ background-image: -moz-linear-gradient(top, #f7f7f7 0%, #cfcfcf 7%, #aaaaaa 100%);
+ background-image: -o-linear-gradient(top, #f7f7f7 0%, #cfcfcf 7%, #aaaaaa 100%);
+ background-image: linear-gradient(top, #f7f7f7 0%,#cfcfcf 7%,#aaaaaa 100%);
+ filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#f7f7f7', endColorstr='#aaaaaa',GradientType=0 );
+ border-bottom: 1px solid #111;
+ }
+
+ .shell {
+ padding: 20px;
+ text-shadow: none;
+ margin: 0 20px;
+ background-color: #3d3d3d;
+ @include border-radius(0 0 5px 5px);
+ @include box-shadow(0 5px 30px rgba(0,0,0,.3));
+ }
+
+ .line {
+ display: block;
+ margin: 0;
+ padding: 0;
+
+ span { display: inline-block; }
+ }
+
+ .path {
+ color: #87ceeb;
+ @include user-select(none);
+ }
+
+ .prompt {
+ color: #cd5c5c;
+ -webkit-user-select: none; /* Chrome all / Safari all */
+ -moz-user-select: none; /* Firefox all */
+ -ms-user-select: none; /* IE 10+ */
+ -o-user-select: none;
+ user-select: none;
+ }
+
+ .command { color: #f0e68c; }
+
+ .output { color: #888; }
+ }
+}
+
+/* Free Hosting */
+
+.free-hosting {
+
+ .pane {
+ background-color: #444;
+ @include border-radius(10px);
+ text-shadow: none;
+ position: relative;
+ padding: 0 20px 30px;
+ }
+
+ img {
+ margin: -30px 0 0;
+ width: 180px;
+ height: 150px;
+ }
+
+ h2 { font-size: 28px; }
+
+ p,
+ a { font-size: 16px; }
+
+ p { margin: .75em 0; }
+}
+
+@media (min-width: 768px) {
+ .free-hosting {
+
+ img {
+ float: left;
+ margin: -20px -30px -30px -50px;
+ width: 300px;
+ height: 251px;
+ }
+
+ .pane-content {
+ margin-top: 35px;
+ padding-right: 30px;
+ }
+
+ p,
+ a { font-size: 18px; }
+
+ .pane:after {
+ content: " ";
+ float: right;
+ background: url(../img/footer-arrow.png) top left no-repeat;
+ width: 73px;
+ height: 186px;
+ position: absolute;
+ right: 0;
+ bottom: -30px;
+ }
+ }
+}
+
+/* Article - Used for both docs and news */
+
+
+article {
+ background-color: #444;
+ @include border-radius(10px);
+ padding: 20px;
+ margin: 0 10px;
+ @include box-shadow(0 3px 10px rgba(0,0,0,.1));
+ font-size: 16px;
+}
+
+@media (max-width: 480px) {
+ article ul { padding-left: 20px; }
+}
+
+@media (max-width: 568px) {
+ article { margin: 0; }
+}
+
+@media (min-width: 768px) {
+ article {
+ padding: 40px 40px 30px;
+ font-size: 21px;
+ }
+}
+
+/* Right-side nav - used by both docs and news */
+
+aside {
+ padding-top: 30px;
+
+ h4 {
+ text-transform: uppercase;
+ font-size: 14px;
+ font-weight: 700;
+ padding: 0 0 10px 30px;
+ margin-left: -30px;
+ display: inline-block;
+ border-bottom: 1px solid #c00;
+ }
+
+ ul {
+ padding-left: 0;
+
+ &:first-child { margin-top: 0; }
+ }
+
+ li {
+ list-style-type: none;
+
+ a {
+ font-size: 16px;
+ position: relative
+ }
+
+ &.current a:before {
+ content: "";
+ border-color: transparent transparent transparent #444;
+ border-style: solid;
+ border-width: 10px;
+ width: 0;
+ height: 0;
+ position: absolute;
+ top: 0;
+ left: -30px;
+ }
+ }
+}
+
+/* Documentation */
+
+.docs {
+
+ article { min-height: 800px; }
+
+ .content { padding: 0; }
+}
+
+.section-nav {
+ text-align: center;
+ padding-top: 40px;
+ position: relative;
+ background: url(../img/article-footer.png) top center no-repeat;
+ margin: 40px -20px 10px;
+
+ > div { width: 49.5%; }
+
+ a,
+ span {
+ color: #fff;
+ font-size: 16px;
+ text-transform: uppercase;
+ font-weight: 700;
+ padding: 8px 12px 10px;
+ @include border-radius(5px);
+ /*border: 1px solid #333;*/
+ @include box-shadow(0 1px 3px rgba(0,0,0,.3), inset 0 1px 1px rgba(255,255,255,.5));
+ background-color: #777;
+ }
+
+ a:hover {
+ color: #fff;
+ background-color: #888;
+ }
+
+ .next,
+ .prev { position: relative; }
+
+ .next:after,
+ .prev:before {
+ font-size: 36px;
+ color: #222;
+ font-weight: 900;
+ text-shadow: 0 1px 0 rgba(255,255,255,.4);
+ position: absolute;
+ top: -7px;
+ }
+
+ .next:after {
+ content: '\203A';
+ right: 10px;
+ }
+
+ .prev:before {
+ content: '\2039';
+ left: 10px;
+ }
+
+ .prev,
+ .prev:hover { padding-left: 30px; }
+
+ .next,
+ .next:hover { padding-right: 30px; }
+
+ .disabled {
+ opacity: .5;
+ cursor: default;
+ }
+}
+
+.docs-nav-mobile select {
+ color: #000;
+ width: 100%;
+}
+
+/* News */
+
+article h2:first-child { margin-top: 0; }
+
+.post-category,
+.post-meta {
+ display: inline-block;
+ vertical-align: middle;
+ font-size: .8em;
+}
+
+.post-category {
+ display: inline-block;
+ margin-left: -30px;
+ padding: 6px 10px 8px;
+ padding-left: 50px;
+ @include border-radius(0 5px 5px 0);
+ position: relative;
+ @include box-shadow(0 1px 5px rgba(0, 0, 0, .3), inset 0 1px 0 rgba(255,255,255,.2), inset 0 -1px 0 rgba(0,0,0,.3));
+ background-color: #9e2812;
+ background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8c3ZnIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjEwMCUiIGhlaWdodD0iMTAwJSIgdmlld0JveD0iMCAwIDEgMSIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSI+CiAgPGxpbmVhckdyYWRpZW50IGlkPSJncmFkLXVjZ2ctZ2VuZXJhdGVkIiBncmFkaWVudFVuaXRzPSJ1c2VyU3BhY2VPblVzZSIgeDE9IjAlIiB5MT0iMCUiIHgyPSIwJSIgeTI9IjEwMCUiPgogICAgPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iIzllMjgxMiIgc3RvcC1vcGFjaXR5PSIxIi8+CiAgICA8c3RvcCBvZmZzZXQ9IjEwMCUiIHN0b3AtY29sb3I9IiM2ZjBkMGQiIHN0b3Atb3BhY2l0eT0iMSIvPgogIDwvbGluZWFyR3JhZGllbnQ+CiAgPHJlY3QgeD0iMCIgeT0iMCIgd2lkdGg9IjEiIGhlaWdodD0iMSIgZmlsbD0idXJsKCNncmFkLXVjZ2ctZ2VuZXJhdGVkKSIgLz4KPC9zdmc+);
+ background-image: -webkit-gradient(linear, left top, left bottom, from(#9e2812), to(#6f0d0d));
+ background-image: -webkit-linear-gradient(top, #9e2812 0%, #6f0d0d 100%);
+ background-image: -moz-linear-gradient(top, #9e2812 0%, #6f0d0d 100%);
+ background-image: -o-linear-gradient(top, #9e2812 0%, #6f0d0d 100%);
+ background-image: linear-gradient(to bottom, #9e2812 0%,#6f0d0d 100%);
+ filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#9e2812', endColorstr='#6f0d0d',GradientType=0 );
+
+ &:before {
+ content: "";
+ position: absolute;
+ top: -10px;
+ left: 0;
+ border-color: transparent #6f0d0d #6f0d0d transparent;
+ border-style: solid;
+ border-width: 5px;
+ width: 0;
+ height: 0;
+ }
+}
+
+.post-content img { max-width: 100% }
+
+.label {
+ float: left;
+ text-transform: uppercase;
+ font-weight: 700;
+ text-shadow: 0 -1px 0 rgba(0,0,0,.5);
+}
+
+@media (max-width: 568px) {
+ .post-category { padding-left: 30px; }
+}
+
+@media (min-width: 768px) {
+ .post-category { margin-left: -50px; }
+}
+
+.avatar {
+ @include border-radius(3px);
+ display: inline-block;
+ vertical-align: middle;
+}
+
+.post-meta {
+ padding: 5px 0;
+ color: #aaa;
+ font-weight: 600;
+ text-shadow: 0 -1px 0 #000;
+}
+
+.post-date,
+.post-author { margin-left: 10px; }
+
+.news article + article {
+ margin-top: -10px;
+ @include border-radius(0 0 10px 10px);
+ border-top: 1px solid #555;
+ @include box-shadow(0 -1px 0 #2f2f2f);
+}
+
+/* Code Highlighting */
+
+
+pre,
+code {
+ white-space: pre;
+ display: inline-block;
+ margin: 0;
+ font: 14px/1.8em Menlo, Consolas, "Courier New", Courier, "Liberation Mono", monospace;
+ padding: 0 0.5em;
+}
+
+@media (min-width: 768px) {
+ pre, code { font-size: 16px; }
+}
+
+.highlight,
+p > pre,
+p > code,
+p > nobr > code,
+li > code,
+h5 > code,
+.note > code {
+ background-color: #333;
+ color: #fff;
+ @include border-radius(5px);
+ @include box-shadow(inset 0 1px 10px rgba(0,0,0,.3),
+ 0 1px 0 rgba(255,255,255,.1),
+ 0 -1px 0 rgba(0,0,0,.5));
+}
+
+.note code {
+ background-color: #333;
+ background-color: rgba(0,0,0,0.2);
+ margin-left: 2.5px;
+ margin-right: 2.5px;
+ font-size: 0.8em;
+}
+
+.highlight {
+ margin: 1em 0;
+ padding: 10px 0;
+ width: 100%;
+ overflow: auto;
+}
+
+/* HTML Elements */
+
+h1, h2, h3, h4, h5, h6 { margin: 0; }
+
+a {
+ color: #fc0;
+ text-decoration: none;
+ @include transition(all .25s);
+
+ &:hover { color: #f90; }
+}
+
+strong { font-weight: 700; }
+
+p { line-height: 1.5em; }
+
+.left { float: left; }
+.right { float: right; }
+.align-right { text-align: right; }
+.align-left { text-align: left; }
+.align-center { text-align: center; }
+
+/* Article HTML */
+
+article {
+
+ h2, h3, h4, h5, h6 { margin: 1em 0; }
+
+ h4 { color: #fff; }
+
+ ul li {
+
+ p { margin: 0; }
+
+ blockquote { margin: 10px 0; }
+ }
+
+ ul li,
+ ol li {
+ line-height: 1.5em;
+ margin-bottom: 0.5em;
+ }
+
+}
+
+h5, h6 {
+ font-size: 1em;
+ font-style: italic;
+}
+
+blockquote {
+ border-left: 2px solid #777;
+ padding-left: 20px;
+ font-style: italic;
+ font-size: 18px;
+ font-weight: 500;
+}
+
+
+/* Tables */
+
+table {
+ width: 100%;
+ background-color: #555;
+ margin: .5em 0;
+ @include border-radius(5px);
+ @include box-shadow(0 1px 3px rgba(0,0,0,.3));
+}
+
+thead {
+ @include border-top-left-radius(5px);
+ @include border-top-right-radius(5px);
+ color: #fff;
+ background-color: #3a3a3a;
+ background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8c3ZnIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjEwMCUiIGhlaWdodD0iMTAwJSIgdmlld0JveD0iMCAwIDEgMSIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSI+CiAgPGxpbmVhckdyYWRpZW50IGlkPSJncmFkLXVjZ2ctZ2VuZXJhdGVkIiBncmFkaWVudFVuaXRzPSJ1c2VyU3BhY2VPblVzZSIgeDE9IjAlIiB5MT0iMCUiIHgyPSIwJSIgeTI9IjEwMCUiPgogICAgPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iIzNhM2EzYSIgc3RvcC1vcGFjaXR5PSIxIi8+CiAgICA8c3RvcCBvZmZzZXQ9IjEwMCUiIHN0b3AtY29sb3I9IiMxZTFlMWUiIHN0b3Atb3BhY2l0eT0iMSIvPgogIDwvbGluZWFyR3JhZGllbnQ+CiAgPHJlY3QgeD0iMCIgeT0iMCIgd2lkdGg9IjEiIGhlaWdodD0iMSIgZmlsbD0idXJsKCNncmFkLXVjZ2ctZ2VuZXJhdGVkKSIgLz4KPC9zdmc+);
+ background-image: -webkit-gradient(linear, left top, left bottom, from(#3a3a3a), to(#1e1e1e));
+ background-image: -webkit-linear-gradient(top, #3a3a3a 0%, #1e1e1e 100%);
+ background-image: -moz-linear-gradient(top, #3a3a3a 0%, #1e1e1e 100%);
+ background-image: -o-linear-gradient(top, #3a3a3a 0%, #1e1e1e 100%);
+ background-image: linear-gradient(to bottom, #3a3a3a 0%,#1e1e1e 100%);
+ filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#3a3a3a', endColorstr='#1e1e1e',GradientType=0 );
+
+ th {
+ position: relative;
+ @include box-shadow(inset 0 1px 0 rgba(255,255,255,.1));
+
+ &:first-child {
+ @include border-top-left-radius(5px);
+ }
+
+ &:last-child {
+ @include border-top-right-radius(5px);
+ }
+ }
+}
+
+td { padding: .5em .75em; }
+
+td p { margin: 0; }
+
+th {
+ text-transform: uppercase;
+ font-size: 16px;
+ padding: .5em .75em;
+ text-shadow: 0 -1px 0 rgba(0,0,0,.9);
+ color: #888;
+}
+
+tbody td {
+ border-top: 1px solid #747474;
+ border-top: 1px solid rgba(0,0,0,.1);
+ @include box-shadow(inset 0 1px 0 rgba(255,255,255,.1));
+ background: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8c3ZnIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjEwMCUiIGhlaWdodD0iMTAwJSIgdmlld0JveD0iMCAwIDEgMSIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSI+CiAgPGxpbmVhckdyYWRpZW50IGlkPSJncmFkLXVjZ2ctZ2VuZXJhdGVkIiBncmFkaWVudFVuaXRzPSJ1c2VyU3BhY2VPblVzZSIgeDE9IjAlIiB5MT0iMCUiIHgyPSIwJSIgeTI9IjEwMCUiPgogICAgPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iI2ZmZmZmZiIgc3RvcC1vcGFjaXR5PSIwLjEiLz4KICAgIDxzdG9wIG9mZnNldD0iMTAwJSIgc3RvcC1jb2xvcj0iI2ZmZmZmZiIgc3RvcC1vcGFjaXR5PSIwIi8+CiAgPC9saW5lYXJHcmFkaWVudD4KICA8cmVjdCB4PSIwIiB5PSIwIiB3aWR0aD0iMSIgaGVpZ2h0PSIxIiBmaWxsPSJ1cmwoI2dyYWQtdWNnZy1nZW5lcmF0ZWQpIiAvPgo8L3N2Zz4=);
+ background-image: -webkit-gradient(linear, left top, left bottom, from(rgba(255,255,255,0.1)), to(rgba(255,255,255,0)));
+ background-image: -webkit-linear-gradient(top, rgba(255,255,255,0.1) 0%, rgba(255,255,255,0) 100%);
+ background-image: -moz-linear-gradient(top, rgba(255,255,255,0.1) 0%, rgba(255,255,255,0) 100%);
+ background-image: -o-linear-gradient(top, rgba(255,255,255,0.1) 0%, rgba(255,255,255,0) 100%);
+ background-image: linear-gradient(to bottom, rgba(255,255,255,0.1) 0%,rgba(255,255,255,0) 100%);
+ filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#1affffff', endColorstr='#00ffffff',GradientType=0 );
+
+ p {
+ font-size: 16px;
+
+ code { font-size: 14px; }
+ }
+}
+
+code.option,
+th .option,
+code.filter,
+th .filter {
+ color: #50B600;
+}
+
+code.flag,
+th .flag,
+code.output,
+th .output {
+ color: #049DCE;
+}
+
+code.option,
+code.flag,
+code.filter,
+code.output {
+ margin-bottom: 2px;
+}
+
+/* Note types */
+
+.note {
+ margin: 30px 0;
+ margin-left: -30px;
+ padding: 20px 20px 24px;
+ padding-left: 50px;
+ @include border-radius(0 5px 5px 0);
+ position: relative;
+ @include box-shadow(0 1px 5px rgba(0, 0, 0, .3), inset 0 1px 0 rgba(255,255,255,.2), inset 0 -1px 0 rgba(0,0,0,.3));
+ background-color: #7e6d42;
+ background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8c3ZnIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjEwMCUiIGhlaWdodD0iMTAwJSIgdmlld0JveD0iMCAwIDEgMSIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSI+CiAgPGxpbmVhckdyYWRpZW50IGlkPSJncmFkLXVjZ2ctZ2VuZXJhdGVkIiBncmFkaWVudFVuaXRzPSJ1c2VyU3BhY2VPblVzZSIgeDE9IjAlIiB5MT0iMCUiIHgyPSIwJSIgeTI9IjEwMCUiPgogICAgPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iIzdlNmQ0MiIgc3RvcC1vcGFjaXR5PSIxIi8+CiAgICA8c3RvcCBvZmZzZXQ9IjEwMCUiIHN0b3AtY29sb3I9IiM1YzRlMzUiIHN0b3Atb3BhY2l0eT0iMSIvPgogIDwvbGluZWFyR3JhZGllbnQ+CiAgPHJlY3QgeD0iMCIgeT0iMCIgd2lkdGg9IjEiIGhlaWdodD0iMSIgZmlsbD0idXJsKCNncmFkLXVjZ2ctZ2VuZXJhdGVkKSIgLz4KPC9zdmc+);
+ background-image: -webkit-gradient(linear, left top, left bottom, from(#7e6d42), to(#5c4e35));
+ background-image: -webkit-linear-gradient(top, #7e6d42 0%, #5c4e35 100%);
+ background-image: -moz-linear-gradient(top, #7e6d42 0%, #5c4e35 100%);
+ background-image: -o-linear-gradient(top, #7e6d42 0%, #5c4e35 100%);
+ background-image: linear-gradient(to bottom, #7e6d42 0%,#5c4e35 100%);
+ filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#7e6d42', endColorstr='#5c4e35',GradientType=0 );
+}
+
+@media (max-width: 568px) {
+ .note { margin-right: -30px; }
+}
+
+@media (min-width: 768px) {
+ .note { margin-left: -50px; }
+}
+
+.note {
+ &:before {
+ content: "";
+ position: absolute;
+ top: -10px;
+ left: 0;
+ border-color: transparent #222 #222 transparent;
+ border-style: solid;
+ border-width: 5px;
+ width: 0;
+ height: 0;
+ }
+
+ h5,
+ p {
+ margin: 0;
+ color: #fff;
+ }
+
+ h5 {
+ line-height: 1.5em;
+ font-weight: 900;
+ font-style: normal;
+ }
+
+ p {
+ font-weight: 400;
+ font-size: .75em;
+ }
+
+ &:after {
+ content: '\2605';
+ color: #fc0;
+ position: absolute;
+ top: 14px;
+ left: 14px;
+ font-size: 28px;
+ font-weight: 700;
+ text-shadow: 0 -1px 0 rgba(0,0,0,.5);
+ }
+}
+
+.info {
+ background-color: #0389aa;
+ background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8c3ZnIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjEwMCUiIGhlaWdodD0iMTAwJSIgdmlld0JveD0iMCAwIDEgMSIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSI+CiAgPGxpbmVhckdyYWRpZW50IGlkPSJncmFkLXVjZ2ctZ2VuZXJhdGVkIiBncmFkaWVudFVuaXRzPSJ1c2VyU3BhY2VPblVzZSIgeDE9IjAlIiB5MT0iMCUiIHgyPSIwJSIgeTI9IjEwMCUiPgogICAgPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iIzAzODlhYSIgc3RvcC1vcGFjaXR5PSIxIi8+CiAgICA8c3RvcCBvZmZzZXQ9IjEwMCUiIHN0b3AtY29sb3I9IiMwMDYxN2YiIHN0b3Atb3BhY2l0eT0iMSIvPgogIDwvbGluZWFyR3JhZGllbnQ+CiAgPHJlY3QgeD0iMCIgeT0iMCIgd2lkdGg9IjEiIGhlaWdodD0iMSIgZmlsbD0idXJsKCNncmFkLXVjZ2ctZ2VuZXJhdGVkKSIgLz4KPC9zdmc+);
+ background-image: -webkit-gradient(linear, left top, left bottom, from(#0389aa), to(#00617f));
+ background-image: -webkit-linear-gradient(top, #0389aa 0%, #00617f 100%);
+ background-image: -moz-linear-gradient(top, #0389aa 0%, #00617f 100%);
+ background-image: -o-linear-gradient(top, #0389aa 0%, #00617f 100%);
+ background-image: linear-gradient(to bottom, #0389aa 0%,#00617f 100%);
+ filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#0389aa', endColorstr='#00617f',GradientType=0 );
+}
+
+.warning {
+ background-color: #9e2812;
+ background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8c3ZnIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjEwMCUiIGhlaWdodD0iMTAwJSIgdmlld0JveD0iMCAwIDEgMSIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSI+CiAgPGxpbmVhckdyYWRpZW50IGlkPSJncmFkLXVjZ2ctZ2VuZXJhdGVkIiBncmFkaWVudFVuaXRzPSJ1c2VyU3BhY2VPblVzZSIgeDE9IjAlIiB5MT0iMCUiIHgyPSIwJSIgeTI9IjEwMCUiPgogICAgPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iIzllMjgxMiIgc3RvcC1vcGFjaXR5PSIxIi8+CiAgICA8c3RvcCBvZmZzZXQ9IjEwMCUiIHN0b3AtY29sb3I9IiM2ZjBkMGQiIHN0b3Atb3BhY2l0eT0iMSIvPgogIDwvbGluZWFyR3JhZGllbnQ+CiAgPHJlY3QgeD0iMCIgeT0iMCIgd2lkdGg9IjEiIGhlaWdodD0iMSIgZmlsbD0idXJsKCNncmFkLXVjZ2ctZ2VuZXJhdGVkKSIgLz4KPC9zdmc+);
+ background-image: -webkit-gradient(linear, left top, left bottom, from(#9e2812), to(#6f0d0d));
+ background-image: -webkit-linear-gradient(top, #9e2812 0%, #6f0d0d 100%);
+ background-image: -moz-linear-gradient(top, #9e2812 0%, #6f0d0d 100%);
+ background-image: -o-linear-gradient(top, #9e2812 0%, #6f0d0d 100%);
+ background-image: linear-gradient(to bottom, #9e2812 0%,#6f0d0d 100%);
+ filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#9e2812', endColorstr='#6f0d0d',GradientType=0 );
+}
+
+.unreleased {
+ background-color: #cd9239;
+ background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8c3ZnIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjEwMCUiIGhlaWdodD0iMTAwJSIgdmlld0JveD0iMCAwIDEgMSIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSI+CiAgPGxpbmVhckdyYWRpZW50IGlkPSJncmFkLXVjZ2ctZ2VuZXJhdGVkIiBncmFkaWVudFVuaXRzPSJ1c2VyU3BhY2VPblVzZSIgeDE9IjAlIiB5MT0iMCUiIHgyPSIwJSIgeTI9IjEwMCUiPgogICAgPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iI2NkOTIzOSIgc3RvcC1vcGFjaXR5PSIxIi8+CiAgICA8c3RvcCBvZmZzZXQ9IjEwMCUiIHN0b3AtY29sb3I9IiNhMjc1MjgiIHN0b3Atb3BhY2l0eT0iMSIvPgogIDwvbGluZWFyR3JhZGllbnQ+CiAgPHJlY3QgeD0iMCIgeT0iMCIgd2lkdGg9IjEiIGhlaWdodD0iMSIgZmlsbD0idXJsKCNncmFkLXVjZ2ctZ2VuZXJhdGVkKSIgLz4KPC9zdmc+);
+ background-image: -webkit-gradient(linear, left top, left bottom, from(rgba(205,146,57,1)), to(rgba(162,117,40,1)));
+ background-image: -webkit-linear-gradient(top, rgba(205,146,57,1) 0%, rgba(162,117,40,1) 100%);
+ background-image: -moz-linear-gradient(top, rgba(205,146,57,1) 0%, rgba(162,117,40,1) 100%);
+ background-image: -o-linear-gradient(top, rgba(205,146,57,1) 0%, rgba(162,117,40,1) 100%);
+ background-image: linear-gradient(to bottom, rgba(205,146,57,1) 0%,rgba(162,117,40,1) 100%);
+ filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#cd9239', endColorstr='#a27528',GradientType=0 );
+}
+
+.info:before { border-color: transparent #00617f #00617f transparent; }
+
+.warning:before { border-color: transparent #6f0d0d #6f0d0d transparent; }
+
+.unreleased:before { border-color: transparent #664719 #664719 transparent; }
+
+.info:after {
+ content: '\24D8';
+ color: #fff;
+ position: absolute;
+ top: 15px;
+ left: 15px;
+ font-size: 28px;
+ font-weight: 700;
+ text-shadow: 0 -1px 0 rgba(0,0,0,.5);
+}
+
+.warning:after {
+ content: '\203C';
+ color: #fc0;
+ position: absolute;
+ top: 15px;
+ left: 15px;
+ font-size: 32px;
+ font-weight: 700;
+ text-shadow: 0 -1px 0 rgba(0,0,0,.5);
+}
+
+.unreleased:after {
+ content: '\2692';
+ color: #2b2a12;
+ position: absolute;
+ top: 8px;
+ left: 15px;
+ font-size: 38px;
+ font-weight: 700;
+ text-shadow: 0 1px 0 rgba(255,255,255,.25);
+}
+
+/* Responsive tables */
+
+@media (max-width: 768px) {
+ .mobile-side-scroller {
+ overflow-x: scroll;
+ margin: 0 -40px;
+ padding: 0 10px;
+ }
+}
+
+
+.show-on-mobiles {
+ display: none;
+}
+
+@media screen and (max-width: 568px) {
+ .show-on-mobiles {
+ display: block !important;
+ }
+ a .show-on-mobiles {
+ display: inline !important;
+ }
+}
diff --git a/archives/index.html b/archives/index.html
deleted file mode 100644
index 9bffa52..0000000
--- a/archives/index.html
+++ /dev/null
@@ -1,379 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Archives - scriptExplorer
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/assets/fonts/bitter-regular-webfont.eot b/assets/fonts/bitter-regular-webfont.eot
deleted file mode 100755
index 8520490..0000000
Binary files a/assets/fonts/bitter-regular-webfont.eot and /dev/null differ
diff --git a/assets/fonts/bitter-regular-webfont.svg b/assets/fonts/bitter-regular-webfont.svg
deleted file mode 100755
index 2a271a9..0000000
--- a/assets/fonts/bitter-regular-webfont.svg
+++ /dev/null
@@ -1,677 +0,0 @@
-
-
-
diff --git a/assets/fonts/bitter-regular-webfont.ttf b/assets/fonts/bitter-regular-webfont.ttf
deleted file mode 100755
index 20105af..0000000
Binary files a/assets/fonts/bitter-regular-webfont.ttf and /dev/null differ
diff --git a/assets/fonts/bitter-regular-webfont.woff b/assets/fonts/bitter-regular-webfont.woff
deleted file mode 100755
index 73f7c90..0000000
Binary files a/assets/fonts/bitter-regular-webfont.woff and /dev/null differ
diff --git a/assets/fonts/junge-regular-webfont.eot b/assets/fonts/junge-regular-webfont.eot
deleted file mode 100755
index e429e28..0000000
Binary files a/assets/fonts/junge-regular-webfont.eot and /dev/null differ
diff --git a/assets/fonts/junge-regular-webfont.svg b/assets/fonts/junge-regular-webfont.svg
deleted file mode 100755
index 7e0fd31..0000000
--- a/assets/fonts/junge-regular-webfont.svg
+++ /dev/null
@@ -1,238 +0,0 @@
-
-
-
diff --git a/assets/fonts/junge-regular-webfont.ttf b/assets/fonts/junge-regular-webfont.ttf
deleted file mode 100755
index 3bf086c..0000000
Binary files a/assets/fonts/junge-regular-webfont.ttf and /dev/null differ
diff --git a/assets/fonts/junge-regular-webfont.woff b/assets/fonts/junge-regular-webfont.woff
deleted file mode 100755
index 8eea41f..0000000
Binary files a/assets/fonts/junge-regular-webfont.woff and /dev/null differ
diff --git a/assets/fonts/texgyrepagella-regular-webfont.eot b/assets/fonts/texgyrepagella-regular-webfont.eot
deleted file mode 100755
index 0467601..0000000
Binary files a/assets/fonts/texgyrepagella-regular-webfont.eot and /dev/null differ
diff --git a/assets/fonts/texgyrepagella-regular-webfont.svg b/assets/fonts/texgyrepagella-regular-webfont.svg
deleted file mode 100755
index 4b2af14..0000000
--- a/assets/fonts/texgyrepagella-regular-webfont.svg
+++ /dev/null
@@ -1,1505 +0,0 @@
-
-
-
diff --git a/assets/fonts/texgyrepagella-regular-webfont.ttf b/assets/fonts/texgyrepagella-regular-webfont.ttf
deleted file mode 100755
index 015a71b..0000000
Binary files a/assets/fonts/texgyrepagella-regular-webfont.ttf and /dev/null differ
diff --git a/assets/fonts/texgyrepagella-regular-webfont.woff b/assets/fonts/texgyrepagella-regular-webfont.woff
deleted file mode 100755
index 1d26c4e..0000000
Binary files a/assets/fonts/texgyrepagella-regular-webfont.woff and /dev/null differ
diff --git a/assets/fonts/texgyrepagella-regular.otf b/assets/fonts/texgyrepagella-regular.otf
deleted file mode 100755
index e455590..0000000
Binary files a/assets/fonts/texgyrepagella-regular.otf and /dev/null differ
diff --git a/assets/fonts/ubuntu-c-webfont.eot b/assets/fonts/ubuntu-c-webfont.eot
deleted file mode 100755
index 1a64676..0000000
Binary files a/assets/fonts/ubuntu-c-webfont.eot and /dev/null differ
diff --git a/assets/fonts/ubuntu-c-webfont.svg b/assets/fonts/ubuntu-c-webfont.svg
deleted file mode 100755
index aec752f..0000000
--- a/assets/fonts/ubuntu-c-webfont.svg
+++ /dev/null
@@ -1,1560 +0,0 @@
-
-
-
diff --git a/assets/fonts/ubuntu-c-webfont.ttf b/assets/fonts/ubuntu-c-webfont.ttf
deleted file mode 100755
index c75600d..0000000
Binary files a/assets/fonts/ubuntu-c-webfont.ttf and /dev/null differ
diff --git a/assets/fonts/ubuntu-c-webfont.woff b/assets/fonts/ubuntu-c-webfont.woff
deleted file mode 100755
index 8b05786..0000000
Binary files a/assets/fonts/ubuntu-c-webfont.woff and /dev/null differ
diff --git a/assets/images/btn-menu.png b/assets/images/btn-menu.png
deleted file mode 100755
index 59d9d5f..0000000
Binary files a/assets/images/btn-menu.png and /dev/null differ
diff --git a/assets/images/btn-more-small.png b/assets/images/btn-more-small.png
deleted file mode 100755
index 7170810..0000000
Binary files a/assets/images/btn-more-small.png and /dev/null differ
diff --git a/assets/images/btn-more.png b/assets/images/btn-more.png
deleted file mode 100755
index c3eb811..0000000
Binary files a/assets/images/btn-more.png and /dev/null differ
diff --git a/assets/images/btn-search.png b/assets/images/btn-search.png
deleted file mode 100755
index 811b5e6..0000000
Binary files a/assets/images/btn-search.png and /dev/null differ
diff --git a/assets/images/cc-by-sa.png b/assets/images/cc-by-sa.png
deleted file mode 100755
index c67509f..0000000
Binary files a/assets/images/cc-by-sa.png and /dev/null differ
diff --git a/assets/images/favicon-alt.ico b/assets/images/favicon-alt.ico
deleted file mode 100755
index c277d38..0000000
Binary files a/assets/images/favicon-alt.ico and /dev/null differ
diff --git a/assets/images/posts/2013-05-11-ruby-installer.png b/assets/images/posts/2013-05-11-ruby-installer.png
deleted file mode 100755
index 037259e..0000000
Binary files a/assets/images/posts/2013-05-11-ruby-installer.png and /dev/null differ
diff --git a/assets/images/posts/2013-06-09-enable-hook-on-travis-ci.gif b/assets/images/posts/2013-06-09-enable-hook-on-travis-ci.gif
deleted file mode 100755
index d58d40b..0000000
Binary files a/assets/images/posts/2013-06-09-enable-hook-on-travis-ci.gif and /dev/null differ
diff --git a/assets/images/posts/2013-06-15-results-page-on-travis-ci.gif b/assets/images/posts/2013-06-15-results-page-on-travis-ci.gif
deleted file mode 100755
index fefcedf..0000000
Binary files a/assets/images/posts/2013-06-15-results-page-on-travis-ci.gif and /dev/null differ
diff --git a/assets/images/posts/2013-07-05-travis-ci-status-image-options.gif b/assets/images/posts/2013-07-05-travis-ci-status-image-options.gif
deleted file mode 100755
index 620bcd2..0000000
Binary files a/assets/images/posts/2013-07-05-travis-ci-status-image-options.gif and /dev/null differ
diff --git a/assets/images/posts/2013-07-14-dconf-editor-periperals-touchpad.png b/assets/images/posts/2013-07-14-dconf-editor-periperals-touchpad.png
deleted file mode 100755
index f415e9a..0000000
Binary files a/assets/images/posts/2013-07-14-dconf-editor-periperals-touchpad.png and /dev/null differ
diff --git a/assets/images/posts/2014-03-23-evaluate-using-console-panel.gif b/assets/images/posts/2014-03-23-evaluate-using-console-panel.gif
deleted file mode 100755
index ac2799c..0000000
Binary files a/assets/images/posts/2014-03-23-evaluate-using-console-panel.gif and /dev/null differ
diff --git a/assets/images/posts/2014-03-23-evaluate-using-elements-panel.gif b/assets/images/posts/2014-03-23-evaluate-using-elements-panel.gif
deleted file mode 100755
index a91c17a..0000000
Binary files a/assets/images/posts/2014-03-23-evaluate-using-elements-panel.gif and /dev/null differ
diff --git a/assets/images/posts/2014-03-24-heroku-scheduler-dashboard.png b/assets/images/posts/2014-03-24-heroku-scheduler-dashboard.png
deleted file mode 100755
index 20b63f1..0000000
Binary files a/assets/images/posts/2014-03-24-heroku-scheduler-dashboard.png and /dev/null differ
diff --git a/assets/images/posts/2014-03-24-heroku-stringer-settings-page.png b/assets/images/posts/2014-03-24-heroku-stringer-settings-page.png
deleted file mode 100755
index 7e26595..0000000
Binary files a/assets/images/posts/2014-03-24-heroku-stringer-settings-page.png and /dev/null differ
diff --git a/assets/images/posts/2014-04-25-anatomy-of-selenium-project.png b/assets/images/posts/2014-04-25-anatomy-of-selenium-project.png
deleted file mode 100755
index fe8bb23..0000000
Binary files a/assets/images/posts/2014-04-25-anatomy-of-selenium-project.png and /dev/null differ
diff --git a/assets/images/posts/2014-04-25-history-of-selenium-project.png b/assets/images/posts/2014-04-25-history-of-selenium-project.png
deleted file mode 100755
index cbb9a51..0000000
Binary files a/assets/images/posts/2014-04-25-history-of-selenium-project.png and /dev/null differ
diff --git a/assets/images/posts/2014-05-23-firefox-save-file-dialog.png b/assets/images/posts/2014-05-23-firefox-save-file-dialog.png
deleted file mode 100755
index 7ab2d16..0000000
Binary files a/assets/images/posts/2014-05-23-firefox-save-file-dialog.png and /dev/null differ
diff --git a/assets/images/skin/noisy_texture_F9F9F9.png b/assets/images/skin/noisy_texture_F9F9F9.png
deleted file mode 100755
index 9f73d3c..0000000
Binary files a/assets/images/skin/noisy_texture_F9F9F9.png and /dev/null differ
diff --git a/assets/images/skin/noisy_texture_section0-200x200.png b/assets/images/skin/noisy_texture_section0-200x200.png
deleted file mode 100755
index 4c3f62d..0000000
Binary files a/assets/images/skin/noisy_texture_section0-200x200.png and /dev/null differ
diff --git a/assets/images/skin/noisy_texture_section1-200x200.png b/assets/images/skin/noisy_texture_section1-200x200.png
deleted file mode 100755
index 02c696d..0000000
Binary files a/assets/images/skin/noisy_texture_section1-200x200.png and /dev/null differ
diff --git a/assets/images/social/simple-icons-master/facebook-48.png b/assets/images/social/simple-icons-master/facebook-48.png
deleted file mode 100755
index bb213a1..0000000
Binary files a/assets/images/social/simple-icons-master/facebook-48.png and /dev/null differ
diff --git a/assets/images/social/simple-icons-master/github-48.png b/assets/images/social/simple-icons-master/github-48.png
deleted file mode 100755
index be6e3e7..0000000
Binary files a/assets/images/social/simple-icons-master/github-48.png and /dev/null differ
diff --git a/assets/images/social/simple-icons-master/gmail-48.png b/assets/images/social/simple-icons-master/gmail-48.png
deleted file mode 100755
index 7f7f0e7..0000000
Binary files a/assets/images/social/simple-icons-master/gmail-48.png and /dev/null differ
diff --git a/assets/images/social/simple-icons-master/lastfm-48.png b/assets/images/social/simple-icons-master/lastfm-48.png
deleted file mode 100755
index 604acf8..0000000
Binary files a/assets/images/social/simple-icons-master/lastfm-48.png and /dev/null differ
diff --git a/assets/images/social/simple-icons-master/linkedin-48.png b/assets/images/social/simple-icons-master/linkedin-48.png
deleted file mode 100755
index ccfcc16..0000000
Binary files a/assets/images/social/simple-icons-master/linkedin-48.png and /dev/null differ
diff --git a/assets/images/social/simple-icons-master/rss-48.png b/assets/images/social/simple-icons-master/rss-48.png
deleted file mode 100755
index d5d4f55..0000000
Binary files a/assets/images/social/simple-icons-master/rss-48.png and /dev/null differ
diff --git a/assets/images/social/simple-icons-master/stackoverflow-48.png b/assets/images/social/simple-icons-master/stackoverflow-48.png
deleted file mode 100755
index 4808a51..0000000
Binary files a/assets/images/social/simple-icons-master/stackoverflow-48.png and /dev/null differ
diff --git a/assets/images/social/simple-icons-master/steam-48.png b/assets/images/social/simple-icons-master/steam-48.png
deleted file mode 100755
index a88eaa2..0000000
Binary files a/assets/images/social/simple-icons-master/steam-48.png and /dev/null differ
diff --git a/assets/js/ckeditor/LICENSE.md b/assets/js/ckeditor/LICENSE.md
deleted file mode 100755
index 0a239d2..0000000
--- a/assets/js/ckeditor/LICENSE.md
+++ /dev/null
@@ -1,1264 +0,0 @@
-Software License Agreement
-==========================
-
-CKEditor - The text editor for Internet - http://ckeditor.com
-Copyright (c) 2003-2014, CKSource - Frederico Knabben. All rights reserved.
-
-Licensed under the terms of any of the following licenses at your
-choice:
-
- - GNU General Public License Version 2 or later (the "GPL")
- http://www.gnu.org/licenses/gpl.html
- (See Appendix A)
-
- - GNU Lesser General Public License Version 2.1 or later (the "LGPL")
- http://www.gnu.org/licenses/lgpl.html
- (See Appendix B)
-
- - Mozilla Public License Version 1.1 or later (the "MPL")
- http://www.mozilla.org/MPL/MPL-1.1.html
- (See Appendix C)
-
-You are not required to, but if you want to explicitly declare the
-license you have chosen to be bound to when using, reproducing,
-modifying and distributing this software, just include a text file
-titled "legal.txt" in your version of this software, indicating your
-license choice. In any case, your choice will not restrict any
-recipient of your version of this software to use, reproduce, modify
-and distribute this software under any of the above licenses.
-
-Sources of Intellectual Property Included in CKEditor
------------------------------------------------------
-
-Where not otherwise indicated, all CKEditor content is authored by
-CKSource engineers and consists of CKSource-owned intellectual
-property. In some specific instances, CKEditor will incorporate work
-done by developers outside of CKSource with their express permission.
-
-Trademarks
-----------
-
-CKEditor is a trademark of CKSource - Frederico Knabben. All other brand
-and product names are trademarks, registered trademarks or service
-marks of their respective holders.
-
----
-
-Appendix A: The GPL License
----------------------------
-
-GNU GENERAL PUBLIC LICENSE
-Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software-to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Lesser General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
-GNU GENERAL PUBLIC LICENSE
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-END OF TERMS AND CONDITIONS
-
-
-Appendix B: The LGPL License
-----------------------------
-
-GNU LESSER GENERAL PUBLIC LICENSE
-Version 2.1, February 1999
-
- Copyright (C) 1991, 1999 Free Software Foundation, Inc.
- 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-[This is the first released version of the Lesser GPL. It also counts
- as the successor of the GNU Library Public License, version 2, hence
- the version number 2.1.]
-
-Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-Licenses are intended to guarantee your freedom to share and change
-free software-to make sure the software is free for all its users.
-
- This license, the Lesser General Public License, applies to some
-specially designated software packages-typically libraries-of the
-Free Software Foundation and other authors who decide to use it. You
-can use it too, but we suggest you first think carefully about whether
-this license or the ordinary General Public License is the better
-strategy to use in any particular case, based on the explanations below.
-
- When we speak of free software, we are referring to freedom of use,
-not price. Our General Public Licenses are designed to make sure that
-you have the freedom to distribute copies of free software (and charge
-for this service if you wish); that you receive source code or can get
-it if you want it; that you can change the software and use pieces of
-it in new free programs; and that you are informed that you can do
-these things.
-
- To protect your rights, we need to make restrictions that forbid
-distributors to deny you these rights or to ask you to surrender these
-rights. These restrictions translate to certain responsibilities for
-you if you distribute copies of the library or if you modify it.
-
- For example, if you distribute copies of the library, whether gratis
-or for a fee, you must give the recipients all the rights that we gave
-you. You must make sure that they, too, receive or can get the source
-code. If you link other code with the library, you must provide
-complete object files to the recipients, so that they can relink them
-with the library after making changes to the library and recompiling
-it. And you must show them these terms so they know their rights.
-
- We protect your rights with a two-step method: (1) we copyright the
-library, and (2) we offer you this license, which gives you legal
-permission to copy, distribute and/or modify the library.
-
- To protect each distributor, we want to make it very clear that
-there is no warranty for the free library. Also, if the library is
-modified by someone else and passed on, the recipients should know
-that what they have is not the original version, so that the original
-author's reputation will not be affected by problems that might be
-introduced by others.
-
- Finally, software patents pose a constant threat to the existence of
-any free program. We wish to make sure that a company cannot
-effectively restrict the users of a free program by obtaining a
-restrictive license from a patent holder. Therefore, we insist that
-any patent license obtained for a version of the library must be
-consistent with the full freedom of use specified in this license.
-
- Most GNU software, including some libraries, is covered by the
-ordinary GNU General Public License. This license, the GNU Lesser
-General Public License, applies to certain designated libraries, and
-is quite different from the ordinary General Public License. We use
-this license for certain libraries in order to permit linking those
-libraries into non-free programs.
-
- When a program is linked with a library, whether statically or using
-a shared library, the combination of the two is legally speaking a
-combined work, a derivative of the original library. The ordinary
-General Public License therefore permits such linking only if the
-entire combination fits its criteria of freedom. The Lesser General
-Public License permits more lax criteria for linking other code with
-the library.
-
- We call this license the "Lesser" General Public License because it
-does Less to protect the user's freedom than the ordinary General
-Public License. It also provides other free software developers Less
-of an advantage over competing non-free programs. These disadvantages
-are the reason we use the ordinary General Public License for many
-libraries. However, the Lesser license provides advantages in certain
-special circumstances.
-
- For example, on rare occasions, there may be a special need to
-encourage the widest possible use of a certain library, so that it becomes
-a de-facto standard. To achieve this, non-free programs must be
-allowed to use the library. A more frequent case is that a free
-library does the same job as widely used non-free libraries. In this
-case, there is little to gain by limiting the free library to free
-software only, so we use the Lesser General Public License.
-
- In other cases, permission to use a particular library in non-free
-programs enables a greater number of people to use a large body of
-free software. For example, permission to use the GNU C Library in
-non-free programs enables many more people to use the whole GNU
-operating system, as well as its variant, the GNU/Linux operating
-system.
-
- Although the Lesser General Public License is Less protective of the
-users' freedom, it does ensure that the user of a program that is
-linked with the Library has the freedom and the wherewithal to run
-that program using a modified version of the Library.
-
- The precise terms and conditions for copying, distribution and
-modification follow. Pay close attention to the difference between a
-"work based on the library" and a "work that uses the library". The
-former contains code derived from the library, whereas the latter must
-be combined with the library in order to run.
-
-GNU LESSER GENERAL PUBLIC LICENSE
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License Agreement applies to any software library or other
-program which contains a notice placed by the copyright holder or
-other authorized party saying it may be distributed under the terms of
-this Lesser General Public License (also called "this License").
-Each licensee is addressed as "you".
-
- A "library" means a collection of software functions and/or data
-prepared so as to be conveniently linked with application programs
-(which use some of those functions and data) to form executables.
-
- The "Library", below, refers to any such software library or work
-which has been distributed under these terms. A "work based on the
-Library" means either the Library or any derivative work under
-copyright law: that is to say, a work containing the Library or a
-portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is
-included without limitation in the term "modification".)
-
- "Source code" for a work means the preferred form of the work for
-making modifications to it. For a library, complete source code means
-all the source code for all modules it contains, plus any associated
-interface definition files, plus the scripts used to control compilation
-and installation of the library.
-
- Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running a program using the Library is not restricted, and output from
-such a program is covered only if its contents constitute a work based
-on the Library (independent of the use of the Library in a tool for
-writing it). Whether that is true depends on what the Library does
-and what the program that uses the Library does.
-
- 1. You may copy and distribute verbatim copies of the Library's
-complete source code as you receive it, in any medium, provided that
-you conspicuously and appropriately publish on each copy an
-appropriate copyright notice and disclaimer of warranty; keep intact
-all the notices that refer to this License and to the absence of any
-warranty; and distribute a copy of this License along with the
-Library.
-
- You may charge a fee for the physical act of transferring a copy,
-and you may at your option offer warranty protection in exchange for a
-fee.
-
- 2. You may modify your copy or copies of the Library or any portion
-of it, thus forming a work based on the Library, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) The modified work must itself be a software library.
-
- b) You must cause the files modified to carry prominent notices
- stating that you changed the files and the date of any change.
-
- c) You must cause the whole of the work to be licensed at no
- charge to all third parties under the terms of this License.
-
- d) If a facility in the modified Library refers to a function or a
- table of data to be supplied by an application program that uses
- the facility, other than as an argument passed when the facility
- is invoked, then you must make a good faith effort to ensure that,
- in the event an application does not supply such function or
- table, the facility still operates, and performs whatever part of
- its purpose remains meaningful.
-
- (For example, a function in a library to compute square roots has
- a purpose that is entirely well-defined independent of the
- application. Therefore, Subsection 2d requires that any
- application-supplied function or table used by this function must
- be optional: if the application does not supply it, the square
- root function must still compute square roots.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Library,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Library, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote
-it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Library.
-
-In addition, mere aggregation of another work not based on the Library
-with the Library (or with a work based on the Library) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may opt to apply the terms of the ordinary GNU General Public
-License instead of this License to a given copy of the Library. To do
-this, you must alter all the notices that refer to this License, so
-that they refer to the ordinary GNU General Public License, version 2,
-instead of to this License. (If a newer version than version 2 of the
-ordinary GNU General Public License has appeared, then you can specify
-that version instead if you wish.) Do not make any other change in
-these notices.
-
- Once this change is made in a given copy, it is irreversible for
-that copy, so the ordinary GNU General Public License applies to all
-subsequent copies and derivative works made from that copy.
-
- This option is useful when you wish to copy part of the code of
-the Library into a program that is not a library.
-
- 4. You may copy and distribute the Library (or a portion or
-derivative of it, under Section 2) in object code or executable form
-under the terms of Sections 1 and 2 above provided that you accompany
-it with the complete corresponding machine-readable source code, which
-must be distributed under the terms of Sections 1 and 2 above on a
-medium customarily used for software interchange.
-
- If distribution of object code is made by offering access to copy
-from a designated place, then offering equivalent access to copy the
-source code from the same place satisfies the requirement to
-distribute the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 5. A program that contains no derivative of any portion of the
-Library, but is designed to work with the Library by being compiled or
-linked with it, is called a "work that uses the Library". Such a
-work, in isolation, is not a derivative work of the Library, and
-therefore falls outside the scope of this License.
-
- However, linking a "work that uses the Library" with the Library
-creates an executable that is a derivative of the Library (because it
-contains portions of the Library), rather than a "work that uses the
-library". The executable is therefore covered by this License.
-Section 6 states terms for distribution of such executables.
-
- When a "work that uses the Library" uses material from a header file
-that is part of the Library, the object code for the work may be a
-derivative work of the Library even though the source code is not.
-Whether this is true is especially significant if the work can be
-linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
- If such an object file uses only numerical parameters, data
-structure layouts and accessors, and small macros and small inline
-functions (ten lines or less in length), then the use of the object
-file is unrestricted, regardless of whether it is legally a derivative
-work. (Executables containing this object code plus portions of the
-Library will still fall under Section 6.)
-
- Otherwise, if the work is a derivative of the Library, you may
-distribute the object code for the work under the terms of Section 6.
-Any executables containing that work also fall under Section 6,
-whether or not they are linked directly with the Library itself.
-
- 6. As an exception to the Sections above, you may also combine or
-link a "work that uses the Library" with the Library to produce a
-work containing portions of the Library, and distribute that work
-under terms of your choice, provided that the terms permit
-modification of the work for the customer's own use and reverse
-engineering for debugging such modifications.
-
- You must give prominent notice with each copy of the work that the
-Library is used in it and that the Library and its use are covered by
-this License. You must supply a copy of this License. If the work
-during execution displays copyright notices, you must include the
-copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one
-of these things:
-
- a) Accompany the work with the complete corresponding
- machine-readable source code for the Library including whatever
- changes were used in the work (which must be distributed under
- Sections 1 and 2 above); and, if the work is an executable linked
- with the Library, with the complete machine-readable "work that
- uses the Library", as object code and/or source code, so that the
- user can modify the Library and then relink to produce a modified
- executable containing the modified Library. (It is understood
- that the user who changes the contents of definitions files in the
- Library will not necessarily be able to recompile the application
- to use the modified definitions.)
-
- b) Use a suitable shared library mechanism for linking with the
- Library. A suitable mechanism is one that (1) uses at run time a
- copy of the library already present on the user's computer system,
- rather than copying library functions into the executable, and (2)
- will operate properly with a modified version of the library, if
- the user installs one, as long as the modified version is
- interface-compatible with the version that the work was made with.
-
- c) Accompany the work with a written offer, valid for at
- least three years, to give the same user the materials
- specified in Subsection 6a, above, for a charge no more
- than the cost of performing this distribution.
-
- d) If distribution of the work is made by offering access to copy
- from a designated place, offer equivalent access to copy the above
- specified materials from the same place.
-
- e) Verify that the user has already received a copy of these
- materials or that you have already sent this user a copy.
-
- For an executable, the required form of the "work that uses the
-Library" must include any data and utility programs needed for
-reproducing the executable from it. However, as a special exception,
-the materials to be distributed need not include anything that is
-normally distributed (in either source or binary form) with the major
-components (compiler, kernel, and so on) of the operating system on
-which the executable runs, unless that component itself accompanies
-the executable.
-
- It may happen that this requirement contradicts the license
-restrictions of other proprietary libraries that do not normally
-accompany the operating system. Such a contradiction means you cannot
-use both them and the Library together in an executable that you
-distribute.
-
- 7. You may place library facilities that are a work based on the
-Library side-by-side in a single library together with other library
-facilities not covered by this License, and distribute such a combined
-library, provided that the separate distribution of the work based on
-the Library and of the other library facilities is otherwise
-permitted, and provided that you do these two things:
-
- a) Accompany the combined library with a copy of the same work
- based on the Library, uncombined with any other library
- facilities. This must be distributed under the terms of the
- Sections above.
-
- b) Give prominent notice with the combined library of the fact
- that part of it is a work based on the Library, and explaining
- where to find the accompanying uncombined form of the same work.
-
- 8. You may not copy, modify, sublicense, link with, or distribute
-the Library except as expressly provided under this License. Any
-attempt otherwise to copy, modify, sublicense, link with, or
-distribute the Library is void, and will automatically terminate your
-rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses
-terminated so long as such parties remain in full compliance.
-
- 9. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Library or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Library or works based on it.
-
- 10. Each time you redistribute the Library (or any work based on the
-Library), the recipient automatically receives a license from the
-original licensor to copy, distribute, link with or modify the Library
-subject to these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties with
-this License.
-
- 11. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Library at all. For example, if a patent
-license would not permit royalty-free redistribution of the Library by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-If any portion of this section is held invalid or unenforceable under any
-particular circumstance, the balance of the section is intended to apply,
-and the section as a whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 12. If the distribution and/or use of the Library is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Library under this License may add
-an explicit geographical distribution limitation excluding those countries,
-so that distribution is permitted only in or among countries not thus
-excluded. In such case, this License incorporates the limitation as if
-written in the body of this License.
-
- 13. The Free Software Foundation may publish revised and/or new
-versions of the Lesser General Public License from time to time.
-Such new versions will be similar in spirit to the present version,
-but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library
-specifies a version number of this License which applies to it and
-"any later version", you have the option of following the terms and
-conditions either of that version or of any later version published by
-the Free Software Foundation. If the Library does not specify a
-license version number, you may choose any version ever published by
-the Free Software Foundation.
-
- 14. If you wish to incorporate parts of the Library into other free
-programs whose distribution conditions are incompatible with these,
-write to the author to ask for permission. For software which is
-copyrighted by the Free Software Foundation, write to the Free
-Software Foundation; we sometimes make exceptions for this. Our
-decision will be guided by the two goals of preserving the free status
-of all derivatives of our free software and of promoting the sharing
-and reuse of software generally.
-
-NO WARRANTY
-
- 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
-WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
-OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
-KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
-LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
-THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
- 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
-WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
-AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
-FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
-RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
-FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
-SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGES.
-
-END OF TERMS AND CONDITIONS
-
-
-Appendix C: The MPL License
----------------------------
-
-MOZILLA PUBLIC LICENSE
-Version 1.1
-
-1. Definitions.
-
- 1.0.1. "Commercial Use" means distribution or otherwise making the
- Covered Code available to a third party.
-
- 1.1. "Contributor" means each entity that creates or contributes to
- the creation of Modifications.
-
- 1.2. "Contributor Version" means the combination of the Original
- Code, prior Modifications used by a Contributor, and the Modifications
- made by that particular Contributor.
-
- 1.3. "Covered Code" means the Original Code or Modifications or the
- combination of the Original Code and Modifications, in each case
- including portions thereof.
-
- 1.4. "Electronic Distribution Mechanism" means a mechanism generally
- accepted in the software development community for the electronic
- transfer of data.
-
- 1.5. "Executable" means Covered Code in any form other than Source
- Code.
-
- 1.6. "Initial Developer" means the individual or entity identified
- as the Initial Developer in the Source Code notice required by Exhibit
- A.
-
- 1.7. "Larger Work" means a work which combines Covered Code or
- portions thereof with code not governed by the terms of this License.
-
- 1.8. "License" means this document.
-
- 1.8.1. "Licensable" means having the right to grant, to the maximum
- extent possible, whether at the time of the initial grant or
- subsequently acquired, any and all of the rights conveyed herein.
-
- 1.9. "Modifications" means any addition to or deletion from the
- substance or structure of either the Original Code or any previous
- Modifications. When Covered Code is released as a series of files, a
- Modification is:
- A. Any addition to or deletion from the contents of a file
- containing Original Code or previous Modifications.
-
- B. Any new file that contains any part of the Original Code or
- previous Modifications.
-
- 1.10. "Original Code" means Source Code of computer software code
- which is described in the Source Code notice required by Exhibit A as
- Original Code, and which, at the time of its release under this
- License is not already Covered Code governed by this License.
-
- 1.10.1. "Patent Claims" means any patent claim(s), now owned or
- hereafter acquired, including without limitation, method, process,
- and apparatus claims, in any patent Licensable by grantor.
-
- 1.11. "Source Code" means the preferred form of the Covered Code for
- making modifications to it, including all modules it contains, plus
- any associated interface definition files, scripts used to control
- compilation and installation of an Executable, or source code
- differential comparisons against either the Original Code or another
- well known, available Covered Code of the Contributor's choice. The
- Source Code can be in a compressed or archival form, provided the
- appropriate decompression or de-archiving software is widely available
- for no charge.
-
- 1.12. "You" (or "Your") means an individual or a legal entity
- exercising rights under, and complying with all of the terms of, this
- License or a future version of this License issued under Section 6.1.
- For legal entities, "You" includes any entity which controls, is
- controlled by, or is under common control with You. For purposes of
- this definition, "control" means (a) the power, direct or indirect,
- to cause the direction or management of such entity, whether by
- contract or otherwise, or (b) ownership of more than fifty percent
- (50%) of the outstanding shares or beneficial ownership of such
- entity.
-
-2. Source Code License.
-
- 2.1. The Initial Developer Grant.
- The Initial Developer hereby grants You a world-wide, royalty-free,
- non-exclusive license, subject to third party intellectual property
- claims:
- (a) under intellectual property rights (other than patent or
- trademark) Licensable by Initial Developer to use, reproduce,
- modify, display, perform, sublicense and distribute the Original
- Code (or portions thereof) with or without Modifications, and/or
- as part of a Larger Work; and
-
- (b) under Patents Claims infringed by the making, using or
- selling of Original Code, to make, have made, use, practice,
- sell, and offer for sale, and/or otherwise dispose of the
- Original Code (or portions thereof).
-
- (c) the licenses granted in this Section 2.1(a) and (b) are
- effective on the date Initial Developer first distributes
- Original Code under the terms of this License.
-
- (d) Notwithstanding Section 2.1(b) above, no patent license is
- granted: 1) for code that You delete from the Original Code; 2)
- separate from the Original Code; or 3) for infringements caused
- by: i) the modification of the Original Code or ii) the
- combination of the Original Code with other software or devices.
-
- 2.2. Contributor Grant.
- Subject to third party intellectual property claims, each Contributor
- hereby grants You a world-wide, royalty-free, non-exclusive license
-
- (a) under intellectual property rights (other than patent or
- trademark) Licensable by Contributor, to use, reproduce, modify,
- display, perform, sublicense and distribute the Modifications
- created by such Contributor (or portions thereof) either on an
- unmodified basis, with other Modifications, as Covered Code
- and/or as part of a Larger Work; and
-
- (b) under Patent Claims infringed by the making, using, or
- selling of Modifications made by that Contributor either alone
- and/or in combination with its Contributor Version (or portions
- of such combination), to make, use, sell, offer for sale, have
- made, and/or otherwise dispose of: 1) Modifications made by that
- Contributor (or portions thereof); and 2) the combination of
- Modifications made by that Contributor with its Contributor
- Version (or portions of such combination).
-
- (c) the licenses granted in Sections 2.2(a) and 2.2(b) are
- effective on the date Contributor first makes Commercial Use of
- the Covered Code.
-
- (d) Notwithstanding Section 2.2(b) above, no patent license is
- granted: 1) for any code that Contributor has deleted from the
- Contributor Version; 2) separate from the Contributor Version;
- 3) for infringements caused by: i) third party modifications of
- Contributor Version or ii) the combination of Modifications made
- by that Contributor with other software (except as part of the
- Contributor Version) or other devices; or 4) under Patent Claims
- infringed by Covered Code in the absence of Modifications made by
- that Contributor.
-
-3. Distribution Obligations.
-
- 3.1. Application of License.
- The Modifications which You create or to which You contribute are
- governed by the terms of this License, including without limitation
- Section 2.2. The Source Code version of Covered Code may be
- distributed only under the terms of this License or a future version
- of this License released under Section 6.1, and You must include a
- copy of this License with every copy of the Source Code You
- distribute. You may not offer or impose any terms on any Source Code
- version that alters or restricts the applicable version of this
- License or the recipients' rights hereunder. However, You may include
- an additional document offering the additional rights described in
- Section 3.5.
-
- 3.2. Availability of Source Code.
- Any Modification which You create or to which You contribute must be
- made available in Source Code form under the terms of this License
- either on the same media as an Executable version or via an accepted
- Electronic Distribution Mechanism to anyone to whom you made an
- Executable version available; and if made available via Electronic
- Distribution Mechanism, must remain available for at least twelve (12)
- months after the date it initially became available, or at least six
- (6) months after a subsequent version of that particular Modification
- has been made available to such recipients. You are responsible for
- ensuring that the Source Code version remains available even if the
- Electronic Distribution Mechanism is maintained by a third party.
-
- 3.3. Description of Modifications.
- You must cause all Covered Code to which You contribute to contain a
- file documenting the changes You made to create that Covered Code and
- the date of any change. You must include a prominent statement that
- the Modification is derived, directly or indirectly, from Original
- Code provided by the Initial Developer and including the name of the
- Initial Developer in (a) the Source Code, and (b) in any notice in an
- Executable version or related documentation in which You describe the
- origin or ownership of the Covered Code.
-
- 3.4. Intellectual Property Matters
- (a) Third Party Claims.
- If Contributor has knowledge that a license under a third party's
- intellectual property rights is required to exercise the rights
- granted by such Contributor under Sections 2.1 or 2.2,
- Contributor must include a text file with the Source Code
- distribution titled "LEGAL" which describes the claim and the
- party making the claim in sufficient detail that a recipient will
- know whom to contact. If Contributor obtains such knowledge after
- the Modification is made available as described in Section 3.2,
- Contributor shall promptly modify the LEGAL file in all copies
- Contributor makes available thereafter and shall take other steps
- (such as notifying appropriate mailing lists or newsgroups)
- reasonably calculated to inform those who received the Covered
- Code that new knowledge has been obtained.
-
- (b) Contributor APIs.
- If Contributor's Modifications include an application programming
- interface and Contributor has knowledge of patent licenses which
- are reasonably necessary to implement that API, Contributor must
- also include this information in the LEGAL file.
-
- (c) Representations.
- Contributor represents that, except as disclosed pursuant to
- Section 3.4(a) above, Contributor believes that Contributor's
- Modifications are Contributor's original creation(s) and/or
- Contributor has sufficient rights to grant the rights conveyed by
- this License.
-
- 3.5. Required Notices.
- You must duplicate the notice in Exhibit A in each file of the Source
- Code. If it is not possible to put such notice in a particular Source
- Code file due to its structure, then You must include such notice in a
- location (such as a relevant directory) where a user would be likely
- to look for such a notice. If You created one or more Modification(s)
- You may add your name as a Contributor to the notice described in
- Exhibit A. You must also duplicate this License in any documentation
- for the Source Code where You describe recipients' rights or ownership
- rights relating to Covered Code. You may choose to offer, and to
- charge a fee for, warranty, support, indemnity or liability
- obligations to one or more recipients of Covered Code. However, You
- may do so only on Your own behalf, and not on behalf of the Initial
- Developer or any Contributor. You must make it absolutely clear than
- any such warranty, support, indemnity or liability obligation is
- offered by You alone, and You hereby agree to indemnify the Initial
- Developer and every Contributor for any liability incurred by the
- Initial Developer or such Contributor as a result of warranty,
- support, indemnity or liability terms You offer.
-
- 3.6. Distribution of Executable Versions.
- You may distribute Covered Code in Executable form only if the
- requirements of Section 3.1-3.5 have been met for that Covered Code,
- and if You include a notice stating that the Source Code version of
- the Covered Code is available under the terms of this License,
- including a description of how and where You have fulfilled the
- obligations of Section 3.2. The notice must be conspicuously included
- in any notice in an Executable version, related documentation or
- collateral in which You describe recipients' rights relating to the
- Covered Code. You may distribute the Executable version of Covered
- Code or ownership rights under a license of Your choice, which may
- contain terms different from this License, provided that You are in
- compliance with the terms of this License and that the license for the
- Executable version does not attempt to limit or alter the recipient's
- rights in the Source Code version from the rights set forth in this
- License. If You distribute the Executable version under a different
- license You must make it absolutely clear that any terms which differ
- from this License are offered by You alone, not by the Initial
- Developer or any Contributor. You hereby agree to indemnify the
- Initial Developer and every Contributor for any liability incurred by
- the Initial Developer or such Contributor as a result of any such
- terms You offer.
-
- 3.7. Larger Works.
- You may create a Larger Work by combining Covered Code with other code
- not governed by the terms of this License and distribute the Larger
- Work as a single product. In such a case, You must make sure the
- requirements of this License are fulfilled for the Covered Code.
-
-4. Inability to Comply Due to Statute or Regulation.
-
- If it is impossible for You to comply with any of the terms of this
- License with respect to some or all of the Covered Code due to
- statute, judicial order, or regulation then You must: (a) comply with
- the terms of this License to the maximum extent possible; and (b)
- describe the limitations and the code they affect. Such description
- must be included in the LEGAL file described in Section 3.4 and must
- be included with all distributions of the Source Code. Except to the
- extent prohibited by statute or regulation, such description must be
- sufficiently detailed for a recipient of ordinary skill to be able to
- understand it.
-
-5. Application of this License.
-
- This License applies to code to which the Initial Developer has
- attached the notice in Exhibit A and to related Covered Code.
-
-6. Versions of the License.
-
- 6.1. New Versions.
- Netscape Communications Corporation ("Netscape") may publish revised
- and/or new versions of the License from time to time. Each version
- will be given a distinguishing version number.
-
- 6.2. Effect of New Versions.
- Once Covered Code has been published under a particular version of the
- License, You may always continue to use it under the terms of that
- version. You may also choose to use such Covered Code under the terms
- of any subsequent version of the License published by Netscape. No one
- other than Netscape has the right to modify the terms applicable to
- Covered Code created under this License.
-
- 6.3. Derivative Works.
- If You create or use a modified version of this License (which you may
- only do in order to apply it to code which is not already Covered Code
- governed by this License), You must (a) rename Your license so that
- the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape",
- "MPL", "NPL" or any confusingly similar phrase do not appear in your
- license (except to note that your license differs from this License)
- and (b) otherwise make it clear that Your version of the license
- contains terms which differ from the Mozilla Public License and
- Netscape Public License. (Filling in the name of the Initial
- Developer, Original Code or Contributor in the notice described in
- Exhibit A shall not of themselves be deemed to be modifications of
- this License.)
-
-7. DISCLAIMER OF WARRANTY.
-
- COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
- WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
- WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
- DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING.
- THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
- IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT,
- YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE
- COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
- OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF
- ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
-
-8. TERMINATION.
-
- 8.1. This License and the rights granted hereunder will terminate
- automatically if You fail to comply with terms herein and fail to cure
- such breach within 30 days of becoming aware of the breach. All
- sublicenses to the Covered Code which are properly granted shall
- survive any termination of this License. Provisions which, by their
- nature, must remain in effect beyond the termination of this License
- shall survive.
-
- 8.2. If You initiate litigation by asserting a patent infringement
- claim (excluding declatory judgment actions) against Initial Developer
- or a Contributor (the Initial Developer or Contributor against whom
- You file such action is referred to as "Participant") alleging that:
-
- (a) such Participant's Contributor Version directly or indirectly
- infringes any patent, then any and all rights granted by such
- Participant to You under Sections 2.1 and/or 2.2 of this License
- shall, upon 60 days notice from Participant terminate prospectively,
- unless if within 60 days after receipt of notice You either: (i)
- agree in writing to pay Participant a mutually agreeable reasonable
- royalty for Your past and future use of Modifications made by such
- Participant, or (ii) withdraw Your litigation claim with respect to
- the Contributor Version against such Participant. If within 60 days
- of notice, a reasonable royalty and payment arrangement are not
- mutually agreed upon in writing by the parties or the litigation claim
- is not withdrawn, the rights granted by Participant to You under
- Sections 2.1 and/or 2.2 automatically terminate at the expiration of
- the 60 day notice period specified above.
-
- (b) any software, hardware, or device, other than such Participant's
- Contributor Version, directly or indirectly infringes any patent, then
- any rights granted to You by such Participant under Sections 2.1(b)
- and 2.2(b) are revoked effective as of the date You first made, used,
- sold, distributed, or had made, Modifications made by that
- Participant.
-
- 8.3. If You assert a patent infringement claim against Participant
- alleging that such Participant's Contributor Version directly or
- indirectly infringes any patent where such claim is resolved (such as
- by license or settlement) prior to the initiation of patent
- infringement litigation, then the reasonable value of the licenses
- granted by such Participant under Sections 2.1 or 2.2 shall be taken
- into account in determining the amount or value of any payment or
- license.
-
- 8.4. In the event of termination under Sections 8.1 or 8.2 above,
- all end user license agreements (excluding distributors and resellers)
- which have been validly granted by You or any distributor hereunder
- prior to termination shall survive termination.
-
-9. LIMITATION OF LIABILITY.
-
- UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
- (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
- DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
- OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR
- ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
- CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
- WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
- COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
- INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
- LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
- RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
- PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
- EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
- THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
-
-10. U.S. GOVERNMENT END USERS.
-
- The Covered Code is a "commercial item," as that term is defined in
- 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
- software" and "commercial computer software documentation," as such
- terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
- C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
- all U.S. Government End Users acquire Covered Code with only those
- rights set forth herein.
-
-11. MISCELLANEOUS.
-
- This License represents the complete agreement concerning subject
- matter hereof. If any provision of this License is held to be
- unenforceable, such provision shall be reformed only to the extent
- necessary to make it enforceable. This License shall be governed by
- California law provisions (except to the extent applicable law, if
- any, provides otherwise), excluding its conflict-of-law provisions.
- With respect to disputes in which at least one party is a citizen of,
- or an entity chartered or registered to do business in the United
- States of America, any litigation relating to this License shall be
- subject to the jurisdiction of the Federal Courts of the Northern
- District of California, with venue lying in Santa Clara County,
- California, with the losing party responsible for costs, including
- without limitation, court costs and reasonable attorneys' fees and
- expenses. The application of the United Nations Convention on
- Contracts for the International Sale of Goods is expressly excluded.
- Any law or regulation which provides that the language of a contract
- shall be construed against the drafter shall not apply to this
- License.
-
-12. RESPONSIBILITY FOR CLAIMS.
-
- As between Initial Developer and the Contributors, each party is
- responsible for claims and damages arising, directly or indirectly,
- out of its utilization of rights under this License and You agree to
- work with Initial Developer and Contributors to distribute such
- responsibility on an equitable basis. Nothing herein is intended or
- shall be deemed to constitute any admission of liability.
-
-13. MULTIPLE-LICENSED CODE.
-
- Initial Developer may designate portions of the Covered Code as
- "Multiple-Licensed". "Multiple-Licensed" means that the Initial
- Developer permits you to utilize portions of the Covered Code under
- Your choice of the NPL or the alternative licenses, if any, specified
- by the Initial Developer in the file described in Exhibit A.
-
-EXHIBIT A -Mozilla Public License.
-
- ``The contents of this file are subject to the Mozilla Public License
- Version 1.1 (the "License"); you may not use this file except in
- compliance with the License. You may obtain a copy of the License at
- http://www.mozilla.org/MPL/
-
- Software distributed under the License is distributed on an "AS IS"
- basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
- License for the specific language governing rights and limitations
- under the License.
-
- The Original Code is ______________________________________.
-
- The Initial Developer of the Original Code is ________________________.
- Portions created by ______________________ are Copyright (C) ______
- _______________________. All Rights Reserved.
-
- Contributor(s): ______________________________________.
-
- Alternatively, the contents of this file may be used under the terms
- of the _____ license (the "[___] License"), in which case the
- provisions of [______] License are applicable instead of those
- above. If you wish to allow use of your version of this file only
- under the terms of the [____] License and not to allow others to use
- your version of this file under the MPL, indicate your decision by
- deleting the provisions above and replace them with the notice and
- other provisions required by the [___] License. If you do not delete
- the provisions above, a recipient may use your version of this file
- under either the MPL or the [___] License."
-
- [NOTE: The text of this Exhibit A may differ slightly from the text of
- the notices in the Source Code files of the Original Code. You should
- use the text of this Exhibit A rather than the text found in the
- Original Code Source Code for Your Modifications.]
diff --git a/assets/js/ckeditor/README.md b/assets/js/ckeditor/README.md
deleted file mode 100755
index c5a55cd..0000000
--- a/assets/js/ckeditor/README.md
+++ /dev/null
@@ -1,39 +0,0 @@
-CKEditor 4
-==========
-
-Copyright (c) 2003-2014, CKSource - Frederico Knabben. All rights reserved.
-http://ckeditor.com - See LICENSE.md for license information.
-
-CKEditor is a text editor to be used inside web pages. It's not a replacement
-for desktop text editors like Word or OpenOffice, but a component to be used as
-part of web applications and websites.
-
-## Documentation
-
-The full editor documentation is available online at the following address:
-http://docs.ckeditor.com
-
-## Installation
-
-Installing CKEditor is an easy task. Just follow these simple steps:
-
- 1. **Download** the latest version from the CKEditor website:
- http://ckeditor.com. You should have already completed this step, but be
- sure you have the very latest version.
- 2. **Extract** (decompress) the downloaded file into the root of your website.
-
-**Note:** CKEditor is by default installed in the `ckeditor` folder. You can
-place the files in whichever you want though.
-
-## Checking Your Installation
-
-The editor comes with a few sample pages that can be used to verify that
-installation proceeded properly. Take a look at the `samples` directory.
-
-To test your installation, just call the following page at your website:
-
- http:////samples/index.html
-
-For example:
-
- http://www.example.com/ckeditor/samples/index.html
diff --git a/assets/js/ckeditor/adapters/jquery.js b/assets/js/ckeditor/adapters/jquery.js
deleted file mode 100755
index 2a192b8..0000000
--- a/assets/js/ckeditor/adapters/jquery.js
+++ /dev/null
@@ -1,10 +0,0 @@
-/*
- Copyright (c) 2003-2014, CKSource - Frederico Knabben. All rights reserved.
- For licensing, see LICENSE.md or http://ckeditor.com/license
-*/
-(function(a){CKEDITOR.config.jqueryOverrideVal="undefined"==typeof CKEDITOR.config.jqueryOverrideVal?!0:CKEDITOR.config.jqueryOverrideVal;"undefined"!=typeof a&&(a.extend(a.fn,{ckeditorGet:function(){var a=this.eq(0).data("ckeditorInstance");if(!a)throw"CKEditor is not initialized yet, use ckeditor() with a callback.";return a},ckeditor:function(g,d){if(!CKEDITOR.env.isCompatible)throw Error("The environment is incompatible.");if(!a.isFunction(g))var k=d,d=g,g=k;var i=[],d=d||{};this.each(function(){var b=
-a(this),c=b.data("ckeditorInstance"),f=b.data("_ckeditorInstanceLock"),h=this,j=new a.Deferred;i.push(j.promise());if(c&&!f)g&&g.apply(c,[this]),j.resolve();else if(f)c.once("instanceReady",function(){setTimeout(function(){c.element?(c.element.$==h&&g&&g.apply(c,[h]),j.resolve()):setTimeout(arguments.callee,100)},0)},null,null,9999);else{if(d.autoUpdateElement||"undefined"==typeof d.autoUpdateElement&&CKEDITOR.config.autoUpdateElement)d.autoUpdateElementJquery=!0;d.autoUpdateElement=!1;b.data("_ckeditorInstanceLock",
-!0);c=a(this).is("textarea")?CKEDITOR.replace(h,d):CKEDITOR.inline(h,d);b.data("ckeditorInstance",c);c.on("instanceReady",function(d){var e=d.editor;setTimeout(function(){if(e.element){d.removeListener();e.on("dataReady",function(){b.trigger("dataReady.ckeditor",[e])});e.on("setData",function(a){b.trigger("setData.ckeditor",[e,a.data])});e.on("getData",function(a){b.trigger("getData.ckeditor",[e,a.data])},999);e.on("destroy",function(){b.trigger("destroy.ckeditor",[e])});e.on("save",function(){a(h.form).submit();
-return!1},null,null,20);if(e.config.autoUpdateElementJquery&&b.is("textarea")&&a(h.form).length){var c=function(){b.ckeditor(function(){e.updateElement()})};a(h.form).submit(c);a(h.form).bind("form-pre-serialize",c);b.bind("destroy.ckeditor",function(){a(h.form).unbind("submit",c);a(h.form).unbind("form-pre-serialize",c)})}e.on("destroy",function(){b.removeData("ckeditorInstance")});b.removeData("_ckeditorInstanceLock");b.trigger("instanceReady.ckeditor",[e]);g&&g.apply(e,[h]);j.resolve()}else setTimeout(arguments.callee,
-100)},0)},null,null,9999)}});var f=new a.Deferred;this.promise=f.promise();a.when.apply(this,i).then(function(){f.resolve()});this.editor=this.eq(0).data("ckeditorInstance");return this}}),CKEDITOR.config.jqueryOverrideVal&&(a.fn.val=CKEDITOR.tools.override(a.fn.val,function(g){return function(d){if(arguments.length){var k=this,i=[],f=this.each(function(){var b=a(this),c=b.data("ckeditorInstance");if(b.is("textarea")&&c){var f=new a.Deferred;c.setData(d,function(){f.resolve()});i.push(f.promise());
-return!0}return g.call(b,d)});if(i.length){var b=new a.Deferred;a.when.apply(this,i).done(function(){b.resolveWith(k)});return b.promise()}return f}var f=a(this).eq(0),c=f.data("ckeditorInstance");return f.is("textarea")&&c?c.getData():g.call(f)}})))})(window.jQuery);
diff --git a/assets/js/ckeditor/build-config.js b/assets/js/ckeditor/build-config.js
deleted file mode 100755
index f587744..0000000
--- a/assets/js/ckeditor/build-config.js
+++ /dev/null
@@ -1,141 +0,0 @@
-/**
- * @license Copyright (c) 2003-2014, CKSource - Frederico Knabben. All rights reserved.
- * For licensing, see LICENSE.md or http://ckeditor.com/license
- */
-
-/**
- * This file was added automatically by CKEditor builder.
- * You may re-use it at any time to build CKEditor again.
- *
- * If you would like to build CKEditor online again
- * (for example to upgrade), visit one the following links:
- *
- * (1) http://ckeditor.com/builder
- * Visit online builder to build CKEditor from scratch.
- *
- * (2) http://ckeditor.com/builder/5346be27bc0918d0fd5cc09a6bae537b
- * Visit online builder to build CKEditor, starting with the same setup as before.
- *
- * (3) http://ckeditor.com/builder/download/5346be27bc0918d0fd5cc09a6bae537b
- * Straight download link to the latest version of CKEditor (Optimized) with the same setup as before.
- *
- * NOTE:
- * This file is not used by CKEditor, you may remove it.
- * Changing this file will not change your CKEditor configuration.
- */
-
-var CKBUILDER_CONFIG = {
- skin: 'moono',
- preset: 'standard',
- ignore: [
- 'dev',
- '.gitignore',
- '.gitattributes',
- 'README.md',
- '.mailmap'
- ],
- plugins : {
- 'a11yhelp' : 1,
- 'about' : 1,
- 'basicstyles' : 1,
- 'blockquote' : 1,
- 'clipboard' : 1,
- 'contextmenu' : 1,
- 'elementspath' : 1,
- 'enterkey' : 1,
- 'entities' : 1,
- 'filebrowser' : 1,
- 'floatingspace' : 1,
- 'format' : 1,
- 'horizontalrule' : 1,
- 'htmlwriter' : 1,
- 'image' : 1,
- 'indentlist' : 1,
- 'link' : 1,
- 'list' : 1,
- 'magicline' : 1,
- 'maximize' : 1,
- 'pastefromword' : 1,
- 'pastetext' : 1,
- 'removeformat' : 1,
- 'resize' : 1,
- 'scayt' : 1,
- 'sourcearea' : 1,
- 'specialchar' : 1,
- 'stylescombo' : 1,
- 'tab' : 1,
- 'table' : 1,
- 'tabletools' : 1,
- 'toolbar' : 1,
- 'undo' : 1,
- 'wsc' : 1,
- 'wysiwygarea' : 1
- },
- languages : {
- 'af' : 1,
- 'ar' : 1,
- 'bg' : 1,
- 'bn' : 1,
- 'bs' : 1,
- 'ca' : 1,
- 'cs' : 1,
- 'cy' : 1,
- 'da' : 1,
- 'de' : 1,
- 'el' : 1,
- 'en' : 1,
- 'en-au' : 1,
- 'en-ca' : 1,
- 'en-gb' : 1,
- 'eo' : 1,
- 'es' : 1,
- 'et' : 1,
- 'eu' : 1,
- 'fa' : 1,
- 'fi' : 1,
- 'fo' : 1,
- 'fr' : 1,
- 'fr-ca' : 1,
- 'gl' : 1,
- 'gu' : 1,
- 'he' : 1,
- 'hi' : 1,
- 'hr' : 1,
- 'hu' : 1,
- 'id' : 1,
- 'is' : 1,
- 'it' : 1,
- 'ja' : 1,
- 'ka' : 1,
- 'km' : 1,
- 'ko' : 1,
- 'ku' : 1,
- 'lt' : 1,
- 'lv' : 1,
- 'mk' : 1,
- 'mn' : 1,
- 'ms' : 1,
- 'nb' : 1,
- 'nl' : 1,
- 'no' : 1,
- 'pl' : 1,
- 'pt' : 1,
- 'pt-br' : 1,
- 'ro' : 1,
- 'ru' : 1,
- 'si' : 1,
- 'sk' : 1,
- 'sl' : 1,
- 'sq' : 1,
- 'sr' : 1,
- 'sr-latn' : 1,
- 'sv' : 1,
- 'th' : 1,
- 'tr' : 1,
- 'ug' : 1,
- 'uk' : 1,
- 'vi' : 1,
- 'zh' : 1,
- 'zh-cn' : 1
- }
-};
diff --git a/assets/js/ckeditor/ckeditor.js b/assets/js/ckeditor/ckeditor.js
deleted file mode 100755
index 14fc474..0000000
--- a/assets/js/ckeditor/ckeditor.js
+++ /dev/null
@@ -1,902 +0,0 @@
-/*
-Copyright (c) 2003-2014, CKSource - Frederico Knabben. All rights reserved.
-For licensing, see LICENSE.html or http://ckeditor.com/license
-*/
-(function(){if(window.CKEDITOR&&window.CKEDITOR.dom)return;window.CKEDITOR||(window.CKEDITOR=function(){var a={timestamp:"E0LB",version:"4.3.2",revision:"ba625e6",rnd:Math.floor(900*Math.random())+100,_:{pending:[]},status:"unloaded",basePath:function(){var b=window.CKEDITOR_BASEPATH||"";if(!b)for(var d=document.getElementsByTagName("script"),a=0;a=0;o--)if(n[o].priority<=m){n.splice(o+1,0,j);return{removeListener:i}}n.unshift(j)}return{removeListener:i}},
-once:function(){var b=arguments[1];arguments[1]=function(d){d.removeListener();return b.apply(this,arguments)};return this.on.apply(this,arguments)},capture:function(){CKEDITOR.event.useCapture=1;var b=this.on.apply(this,arguments);CKEDITOR.event.useCapture=0;return b},fire:function(){var b=0,d=function(){b=1},a=0,h=function(){a=1};return function(m,j,i){var n=e(this)[m],m=b,r=a;b=a=0;if(n){var o=n.listeners;if(o.length)for(var o=o.slice(0),u,f=0;f=0&&a.listeners.splice(h,1)}},removeAllListeners:function(){var b=e(this),d;for(d in b)delete b[d]},hasListeners:function(b){return(b=e(this)[b])&&b.listeners.length>0}}}());
-CKEDITOR.editor||(CKEDITOR.editor=function(){CKEDITOR._.pending.push([this,arguments]);CKEDITOR.event.call(this)},CKEDITOR.editor.prototype.fire=function(a,e){a in{instanceReady:1,loaded:1}&&(this[a]=true);return CKEDITOR.event.prototype.fire.call(this,a,e,this)},CKEDITOR.editor.prototype.fireOnce=function(a,e){a in{instanceReady:1,loaded:1}&&(this[a]=true);return CKEDITOR.event.prototype.fireOnce.call(this,a,e,this)},CKEDITOR.event.implementOn(CKEDITOR.editor.prototype));
-CKEDITOR.env||(CKEDITOR.env=function(){var a=navigator.userAgent.toLowerCase(),e=window.opera,b={ie:a.indexOf("trident/")>-1,opera:!!e&&e.version,webkit:a.indexOf(" applewebkit/")>-1,air:a.indexOf(" adobeair/")>-1,mac:a.indexOf("macintosh")>-1,quirks:document.compatMode=="BackCompat"&&(!document.documentMode||document.documentMode<10),mobile:a.indexOf("mobile")>-1,iOS:/(ipad|iphone|ipod)/.test(a),isCustomDomain:function(){if(!this.ie)return false;var d=document.domain,b=window.location.hostname;return d!=
-b&&d!="["+b+"]"},secure:location.protocol=="https:"};b.gecko=navigator.product=="Gecko"&&!b.webkit&&!b.opera&&!b.ie;if(b.webkit)a.indexOf("chrome")>-1?b.chrome=true:b.safari=true;var c=0;if(b.ie){c=b.quirks||!document.documentMode?parseFloat(a.match(/msie (\d+)/)[1]):document.documentMode;b.ie9Compat=c==9;b.ie8Compat=c==8;b.ie7Compat=c==7;b.ie6Compat=c<7||b.quirks}if(b.gecko){var d=a.match(/rv:([\d\.]+)/);if(d){d=d[1].split(".");c=d[0]*1E4+(d[1]||0)*100+(d[2]||0)*1}}b.opera&&(c=parseFloat(e.version()));
-b.air&&(c=parseFloat(a.match(/ adobeair\/(\d+)/)[1]));b.webkit&&(c=parseFloat(a.match(/ applewebkit\/(\d+)/)[1]));b.version=c;b.isCompatible=b.iOS&&c>=534||!b.mobile&&(b.ie&&c>6||b.gecko&&c>=10801||b.opera&&c>=9.5||b.air&&c>=1||b.webkit&&c>=522||false);b.hidpi=window.devicePixelRatio>=2;b.needsBrFiller=b.gecko||b.webkit||b.ie&&c>10;b.needsNbspFiller=b.ie&&c<11;b.cssClass="cke_browser_"+(b.ie?"ie":b.gecko?"gecko":b.opera?"opera":b.webkit?"webkit":"unknown");if(b.quirks)b.cssClass=b.cssClass+" cke_browser_quirks";
-if(b.ie){b.cssClass=b.cssClass+(" cke_browser_ie"+(b.quirks||b.version<7?"6":b.version));if(b.quirks)b.cssClass=b.cssClass+" cke_browser_iequirks"}if(b.gecko)if(c<10900)b.cssClass=b.cssClass+" cke_browser_gecko18";else if(c<=11E3)b.cssClass=b.cssClass+" cke_browser_gecko19";if(b.air)b.cssClass=b.cssClass+" cke_browser_air";if(b.iOS)b.cssClass=b.cssClass+" cke_browser_ios";if(b.hidpi)b.cssClass=b.cssClass+" cke_hidpi";return b}());
-"unloaded"==CKEDITOR.status&&function(){CKEDITOR.event.implementOn(CKEDITOR);CKEDITOR.loadFullCore=function(){if(CKEDITOR.status!="basic_ready")CKEDITOR.loadFullCore._load=1;else{delete CKEDITOR.loadFullCore;var a=document.createElement("script");a.type="text/javascript";a.src=CKEDITOR.basePath+"ckeditor.js";document.getElementsByTagName("head")[0].appendChild(a)}};CKEDITOR.loadFullCoreTimeout=0;CKEDITOR.add=function(a){(this._.pending||(this._.pending=[])).push(a)};(function(){CKEDITOR.domReady(function(){var a=
-CKEDITOR.loadFullCore,e=CKEDITOR.loadFullCoreTimeout;if(a){CKEDITOR.status="basic_ready";a&&a._load?a():e&&setTimeout(function(){CKEDITOR.loadFullCore&&CKEDITOR.loadFullCore()},e*1E3)}})})();CKEDITOR.status="basic_loaded"}();CKEDITOR.dom={};
-(function(){var a=[],e=CKEDITOR.env.gecko?"-moz-":CKEDITOR.env.webkit?"-webkit-":CKEDITOR.env.opera?"-o-":CKEDITOR.env.ie?"-ms-":"";CKEDITOR.on("reset",function(){a=[]});CKEDITOR.tools={arrayCompare:function(b,a){if(!b&&!a)return true;if(!b||!a||b.length!=a.length)return false;for(var d=0;d"+a+""):d.push('');return d.join("")},htmlEncode:function(b){return(""+b).replace(/&/g,"&").replace(/>/g,">").replace(//g,">")},htmlDecodeAttr:function(b){return b.replace(/"/g,'"').replace(/</g,"<").replace(/>/g,">")},getNextNumber:function(){var b=0;return function(){return++b}}(),getNextId:function(){return"cke_"+this.getNextNumber()},override:function(b,a){var d=a(b);d.prototype=b.prototype;return d},setTimeout:function(b,a,d,g,e){e||(e=window);d||(d=e);return e.setTimeout(function(){g?b.apply(d,[].concat(g)):
-b.apply(d)},a||0)},trim:function(){var b=/(?:^[ \t\n\r]+)|(?:[ \t\n\r]+$)/g;return function(a){return a.replace(b,"")}}(),ltrim:function(){var b=/^[ \t\n\r]+/g;return function(a){return a.replace(b,"")}}(),rtrim:function(){var b=/[ \t\n\r]+$/g;return function(a){return a.replace(b,"")}}(),indexOf:function(b,a){if(typeof a=="function")for(var d=0,g=b.length;d=0?b[d]:null},bind:function(b,a){return function(){return b.apply(a,arguments)}},createClass:function(b){var a=b.$,d=b.base,g=b.privates||b._,e=b.proto,b=b.statics;!a&&(a=function(){d&&this.base.apply(this,arguments)});if(g)var m=a,a=function(){var d=this._||(this._={}),a;for(a in g){var b=g[a];d[a]=typeof b=="function"?CKEDITOR.tools.bind(b,this):b}m.apply(this,arguments)};if(d){a.prototype=this.prototypedCopy(d.prototype);a.prototype.constructor=a;a.base=
-d;a.baseProto=d.prototype;a.prototype.base=function(){this.base=d.prototype.base;d.apply(this,arguments);this.base=arguments.callee}}e&&this.extend(a.prototype,e,true);b&&this.extend(a,b,true);return a},addFunction:function(b,c){return a.push(function(){return b.apply(c||this,arguments)})-1},removeFunction:function(b){a[b]=null},callFunction:function(b){var c=a[b];return c&&c.apply(window,Array.prototype.slice.call(arguments,1))},cssLength:function(){var a=/^-?\d+\.?\d*px$/,c;return function(d){c=
-CKEDITOR.tools.trim(d+"")+"px";return a.test(c)?c:d||""}}(),convertToPx:function(){var a;return function(c){if(!a){a=CKEDITOR.dom.element.createFromHtml('',CKEDITOR.document);CKEDITOR.document.getBody().append(a)}if(!/%$/.test(c)){a.setStyle("width",c);return a.$.clientWidth}return c}}(),repeat:function(a,c){return Array(c+1).join(a)},tryThese:function(){for(var a,c=0,d=arguments.length;c8)&&e)a=e+":"+a;return new CKEDITOR.dom.nodeList(this.$.getElementsByTagName(a))},getHead:function(){var a=this.$.getElementsByTagName("head")[0];return a=
-a?new CKEDITOR.dom.element(a):this.getDocumentElement().append(new CKEDITOR.dom.element("head"),true)},getBody:function(){return new CKEDITOR.dom.element(this.$.body)},getDocumentElement:function(){return new CKEDITOR.dom.element(this.$.documentElement)},getWindow:function(){return new CKEDITOR.dom.window(this.$.parentWindow||this.$.defaultView)},write:function(a){this.$.open("text/html","replace");CKEDITOR.env.ie&&(a=a.replace(/(?:^\s*]*?>)|^/i,'$&\n
-
-
-
diff --git a/assets/js/ckeditor/plugins/wsc/dialogs/tmp.html b/assets/js/ckeditor/plugins/wsc/dialogs/tmp.html
deleted file mode 100755
index 6764295..0000000
--- a/assets/js/ckeditor/plugins/wsc/dialogs/tmp.html
+++ /dev/null
@@ -1,118 +0,0 @@
-
-
-
-
- iframe
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/assets/js/ckeditor/plugins/wsc/dialogs/tmpFrameset.html b/assets/js/ckeditor/plugins/wsc/dialogs/tmpFrameset.html
deleted file mode 100755
index 0d675f4..0000000
--- a/assets/js/ckeditor/plugins/wsc/dialogs/tmpFrameset.html
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
diff --git a/assets/js/ckeditor/plugins/wsc/dialogs/wsc.css b/assets/js/ckeditor/plugins/wsc/dialogs/wsc.css
deleted file mode 100755
index 9e834f1..0000000
--- a/assets/js/ckeditor/plugins/wsc/dialogs/wsc.css
+++ /dev/null
@@ -1,82 +0,0 @@
-/*
-Copyright (c) 2003-2012, CKSource - Frederico Knabben. All rights reserved.
-For licensing, see LICENSE.html or http://ckeditor.com/license
-*/
-
-html, body
-{
- background-color: transparent;
- margin: 0px;
- padding: 0px;
-}
-
-body
-{
- padding: 10px;
-}
-
-body, td, input, select, textarea
-{
- font-size: 11px;
- font-family: 'Microsoft Sans Serif' , Arial, Helvetica, Verdana;
-}
-
-.midtext
-{
- padding:0px;
- margin:10px;
-}
-
-.midtext p
-{
- padding:0px;
- margin:10px;
-}
-
-.Button
-{
- border: #737357 1px solid;
- color: #3b3b1f;
- background-color: #c7c78f;
-}
-
-.PopupTabArea
-{
- color: #737357;
- background-color: #e3e3c7;
-}
-
-.PopupTitleBorder
-{
- border-bottom: #d5d59d 1px solid;
-}
-.PopupTabEmptyArea
-{
- padding-left: 10px;
- border-bottom: #d5d59d 1px solid;
-}
-
-.PopupTab, .PopupTabSelected
-{
- border-right: #d5d59d 1px solid;
- border-top: #d5d59d 1px solid;
- border-left: #d5d59d 1px solid;
- padding: 3px 5px 3px 5px;
- color: #737357;
-}
-
-.PopupTab
-{
- margin-top: 1px;
- border-bottom: #d5d59d 1px solid;
- cursor: pointer;
-}
-
-.PopupTabSelected
-{
- font-weight: bold;
- cursor: default;
- padding-top: 4px;
- border-bottom: #f1f1e3 1px solid;
- background-color: #f1f1e3;
-}
diff --git a/assets/js/ckeditor/plugins/wsc/dialogs/wsc.js b/assets/js/ckeditor/plugins/wsc/dialogs/wsc.js
deleted file mode 100755
index bcbb7fa..0000000
--- a/assets/js/ckeditor/plugins/wsc/dialogs/wsc.js
+++ /dev/null
@@ -1,67 +0,0 @@
-/*
- Copyright (c) 2003-2012, CKSource - Frederico Knabben. All rights reserved.
- For licensing, see LICENSE.html or http://ckeditor.com/license
-*/
-(function(){function w(a){if(!a)throw"Languages-by-groups list are required for construct selectbox";var c=[],d="",f;for(f in a)for(var g in a[f]){var h=a[f][g];"en_US"==h?d=h:c.push(h)}c.sort();d&&c.unshift(d);return{getCurrentLangGroup:function(c){a:{for(var d in a)for(var f in a[d])if(f.toUpperCase()===c.toUpperCase()){c=d;break a}c=""}return c},setLangList:function(){var c={},d;for(d in a)for(var f in a[d])c[a[d][f]]=f;return c}()}}var e=function(){var a=function(a,b,f){var f=f||{},g=f.expires;
-if("number"==typeof g&&g){var h=new Date;h.setTime(h.getTime()+1E3*g);g=f.expires=h}g&&g.toUTCString&&(f.expires=g.toUTCString());var b=encodeURIComponent(b),a=a+"="+b,e;for(e in f)b=f[e],a+="; "+e,!0!==b&&(a+="="+b);document.cookie=a};return{postMessage:{init:function(a){document.addEventListener?window.addEventListener("message",a,!1):window.attachEvent("onmessage",a)},send:function(a){var b=a.fn||null,f=a.id||"",g=a.target||window,h=a.message||{id:f};"[object Object]"==Object.prototype.toString.call(a.message)&&
-(a.message.id||(a.message.id=f),h=a.message);a=window.JSON.stringify(h,b);g.postMessage(a,"*")}},hash:{create:function(){},parse:function(){}},cookie:{set:a,get:function(a){return(a=document.cookie.match(RegExp("(?:^|; )"+a.replace(/([\.$?*|{}\(\)\[\]\\\/\+^])/g,"\\$1")+"=([^;]*)")))?decodeURIComponent(a[1]):void 0},remove:function(c){a(c,"",{expires:-1})}}}}(),a=a||{};a.TextAreaNumber=null;a.load=!0;a.cmd={SpellTab:"spell",Thesaurus:"thes",GrammTab:"grammar"};a.dialog=null;a.optionNode=null;a.selectNode=
-null;a.grammerSuggest=null;a.textNode={};a.iframeMain=null;a.dataTemp="";a.div_overlay=null;a.textNodeInfo={};a.selectNode={};a.selectNodeResponce={};a.langList=null;a.langSelectbox=null;a.banner="";a.show_grammar=null;a.div_overlay_no_check=null;a.targetFromFrame={};a.onLoadOverlay=null;a.LocalizationComing={};a.OverlayPlace=null;a.LocalizationButton={ChangeTo:{instance:null,text:"Change to"},ChangeAll:{instance:null,text:"Change All"},IgnoreWord:{instance:null,text:"Ignore word"},IgnoreAllWords:{instance:null,
-text:"Ignore all words"},Options:{instance:null,text:"Options",optionsDialog:{instance:null}},AddWord:{instance:null,text:"Add word"},FinishChecking:{instance:null,text:"Finish Checking"}};a.LocalizationLabel={ChangeTo:{instance:null,text:"Change to"},Suggestions:{instance:null,text:"Suggestions"}};var x=function(b){for(var c in b)b[c].instance.getElement().setText(a.LocalizationComing[c])},y=function(b){for(var c in b){if(!b[c].instance.setLabel)break;b[c].instance.setLabel(a.LocalizationComing[c])}},
-j,p;a.framesetHtml=function(b){return''};a.setIframe=function(b,c){var d=a.framesetHtml(c);return b.getElement().setHtml(d)};a.setCurrentIframe=function(b){a.setIframe(a.dialog._.contents[b].Content,b)};a.setHeightBannerFrame=function(){var b=a.dialog.getContentElement("SpellTab","banner").getElement(),
-c=a.dialog.getContentElement("GrammTab","banner").getElement(),d=a.dialog.getContentElement("Thesaurus","banner").getElement();b.setStyle("height","90px");c.setStyle("height","90px");d.setStyle("height","90px")};a.setHeightFrame=function(){document.getElementById(a.iframeNumber+"_"+a.dialog._.currentTabId).style.height="240px"};a.sendData=function(b){var c=b._.currentTabId,d=b._.contents[c].Content,f,g;a.setIframe(d,c);b.parts.tabs.removeAllListeners();b.parts.tabs.on("click",function(h){h=h||window.event;
-h.data.getTarget().is("a")&&c!=b._.currentTabId&&(c=b._.currentTabId,d=b._.contents[c].Content,f=a.iframeNumber+"_"+c,a.div_overlay.setEnable(),d.getElement().getChildCount()?t(a.targetFromFrame[f],a.cmd[c]):(a.setIframe(d,c),g=document.getElementById(f),a.targetFromFrame[f]=g.contentWindow))})};a.buildSelectLang=function(a){var c=new CKEDITOR.dom.element("div"),d=new CKEDITOR.dom.element("select"),a="wscLang"+a;c.addClass("cke_dialog_ui_input_select");c.setAttribute("role","presentation");c.setStyles({height:"auto",
-position:"absolute",right:"0",top:"-1px",width:"160px","white-space":"normal"});d.setAttribute("id",a);d.addClass("cke_dialog_ui_input_select");d.setStyles({width:"160px"});c.append(d);return c};a.buildOptionLang=function(b,c){var d=document.getElementById("wscLang"+c),f=document.createDocumentFragment(),g,h,e=[];if(0===d.options.length){for(g in b)e.push([g,b[g]]);e.sort();for(var k=0;k"},{type:"html",id:"Content",label:"spellContent",html:"",setup:function(b){var b=a.iframeNumber+"_"+b._.currentTabId,
-c=document.getElementById(b);a.targetFromFrame[b]=c.contentWindow}},{type:"hbox",id:"bottomGroup",style:"width:560px; margin: 0 auto;",widths:["50%","50%"],children:[{type:"hbox",id:"leftCol",align:"left",width:"50%",children:[{type:"vbox",id:"rightCol1",widths:["50%","50%"],children:[{type:"text",id:"text",label:a.LocalizationLabel.ChangeTo.text+":",labelLayout:"horizontal",labelStyle:"font: 12px/25px arial, sans-serif;",width:"140px","default":"",onShow:function(){a.textNode.SpellTab=this;a.LocalizationLabel.ChangeTo.instance=
-this},onHide:function(){this.reset()}},{type:"hbox",id:"rightCol",align:"right",width:"30%",children:[{type:"vbox",id:"rightCol_col__left",children:[{type:"text",id:"labelSuggestions",label:a.LocalizationLabel.Suggestions.text+":",onShow:function(){a.LocalizationLabel.Suggestions.instance=this;this.getInputElement().hide()}},{type:"html",id:"logo",html:'',setup:function(){this.getElement().$.src=
-a.logotype;this.getElement().getParent().setStyles({"text-align":"left"})}}]},{type:"select",id:"list_of_suggestions",labelStyle:"font: 12px/25px arial, sans-serif;",size:"6",inputStyle:"width: 140px; height: auto;",items:[["loading..."]],onShow:function(){p=this},onHide:function(){this.clear()},onChange:function(){a.textNode.SpellTab.setValue(this.getValue())}}]}]}]},{type:"hbox",id:"rightCol",align:"right",width:"50%",children:[{type:"vbox",id:"rightCol_col__left",widths:["50%","50%","50%","50%"],
-children:[{type:"button",id:"ChangeTo",label:a.LocalizationButton.ChangeTo.text,title:"Change to",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id);a.LocalizationButton.ChangeTo.instance=this},onClick:c},{type:"button",id:"ChangeAll",label:a.LocalizationButton.ChangeAll.text,title:"Change All",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id);a.LocalizationButton.ChangeAll.instance=this},onClick:c},{type:"button",id:"AddWord",
-label:a.LocalizationButton.AddWord.text,title:"Add word",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id);a.LocalizationButton.AddWord.instance=this},onClick:c},{type:"button",id:"FinishChecking",label:a.LocalizationButton.FinishChecking.text,title:"Finish Checking",style:"width: 100%;margin-top: 9px;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id);a.LocalizationButton.FinishChecking.instance=this},onClick:c}]},{type:"vbox",id:"rightCol_col__right",
-widths:["50%","50%","50%"],children:[{type:"button",id:"IgnoreWord",label:a.LocalizationButton.IgnoreWord.text,title:"Ignore word",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id);a.LocalizationButton.IgnoreWord.instance=this},onClick:c},{type:"button",id:"IgnoreAllWords",label:a.LocalizationButton.IgnoreAllWords.text,title:"Ignore all words",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id);a.LocalizationButton.IgnoreAllWords.instance=
-this},onClick:c},{type:"button",id:"option",label:a.LocalizationButton.Options.text,title:"Option",style:"width: 100%;",onLoad:function(){a.LocalizationButton.Options.instance=this;"file:"==document.location.protocol&&this.disable()},onClick:function(){"file:"==document.location.protocol?alert("WSC: Options functionality is disabled when runing from file system"):b.openDialog("options")}}]}]}]},{type:"hbox",id:"BlockFinishChecking",style:"width:560px; margin: 0 auto;",widths:["70%","30%"],onShow:function(){this.getElement().hide()},
-onHide:l,children:[{type:"hbox",id:"leftCol",align:"left",width:"70%",children:[{type:"vbox",id:"rightCol1",setup:function(){this.getChild()[0].getElement().$.src=a.logotype;this.getChild()[0].getElement().getParent().setStyles({"text-align":"center"})},children:[{type:"html",id:"logo",html:''}]}]},{type:"hbox",id:"rightCol",align:"right",width:"30%",children:[{type:"vbox",
-id:"rightCol_col__left",children:[{type:"button",id:"Option_button",label:a.LocalizationButton.Options.text,title:"Option",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id);"file:"==document.location.protocol&&this.disable()},onClick:function(){"file:"==document.location.protocol?alert("WSC: Options functionality is disabled when runing from file system"):b.openDialog("options")}},{type:"button",id:"FinishChecking",label:a.LocalizationButton.FinishChecking.text,
-title:"Finish Checking",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onClick:c}]}]}]}]},{id:"GrammTab",label:"Grammar",accessKey:"G",elements:[{type:"html",id:"banner",label:"banner",style:"",html:""},{type:"html",id:"Content",label:"GrammarContent",html:"",setup:function(){var b=a.iframeNumber+"_"+a.dialog._.currentTabId,c=document.getElementById(b);a.targetFromFrame[b]=c.contentWindow}},{type:"vbox",id:"bottomGroup",style:"width:560px; margin: 0 auto;",
-children:[{type:"hbox",id:"leftCol",widths:["66%","34%"],children:[{type:"vbox",children:[{type:"text",id:"text",label:"Change to:",labelLayout:"horizontal",labelStyle:"font: 12px/25px arial, sans-serif;",inputStyle:"float: right; width: 200px;","default":"",onShow:function(){a.textNode.GrammTab=this},onHide:function(){this.reset()}},{type:"html",id:"html_text",html:"",
-onShow:function(){a.textNodeInfo.GrammTab=this}},{type:"html",id:"radio",html:"",onShow:function(){a.grammerSuggest=this}}]},{type:"vbox",children:[{type:"button",id:"ChangeTo",label:"Change to",title:"Change to",style:"width: 133px; float: right;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onClick:c},{type:"button",id:"IgnoreWord",label:"Ignore word",title:"Ignore word",style:"width: 133px; float: right;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},
-onClick:c},{type:"button",id:"IgnoreAllWords",label:"Ignore Problem",title:"Ignore Problem",style:"width: 133px; float: right;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onClick:c},{type:"button",id:"FinishChecking",label:"Finish Checking",title:"Finish Checking",style:"width: 133px; float: right; margin-top: 9px;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onClick:c}]}]}]},{type:"hbox",id:"BlockFinishChecking",style:"width:560px; margin: 0 auto;",
-widths:["70%","30%"],onShow:function(){this.getElement().hide()},onHide:l,children:[{type:"hbox",id:"leftCol",align:"left",width:"70%",children:[{type:"vbox",id:"rightCol1",children:[{type:"html",id:"logo",html:'',setup:function(){this.getElement().$.src=a.logotype;this.getElement().getParent().setStyles({"text-align":"center"})}}]}]},{type:"hbox",id:"rightCol",align:"right",
-width:"30%",children:[{type:"vbox",id:"rightCol_col__left",children:[{type:"button",id:"FinishChecking",label:"Finish Checking",title:"Finish Checking",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onClick:c}]}]}]}]},{id:"Thesaurus",label:"Thesaurus",accessKey:"T",elements:[{type:"html",id:"banner",label:"banner",style:"",html:""},{type:"html",id:"Content",label:"spellContent",html:"",setup:function(){var b=a.iframeNumber+"_"+a.dialog._.currentTabId,
-c=document.getElementById(b);a.targetFromFrame[b]=c.contentWindow}},{type:"vbox",id:"bottomGroup",style:"width:560px; margin: -10px auto; overflow: hidden;",children:[{type:"hbox",widths:["75%","25%"],children:[{type:"vbox",children:[{type:"hbox",widths:["65%","35%"],children:[{type:"text",id:"ChangeTo",label:"Change to:",labelLayout:"horizontal",inputStyle:"width: 160px;",labelStyle:"font: 12px/25px arial, sans-serif;","default":"",onShow:function(){a.textNode.Thesaurus=this},onHide:function(){this.reset()}},
-{type:"button",id:"ChangeTo",label:"Change to",title:"Change to",style:"width: 121px; margin-top: 1px;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onClick:c}]},{type:"hbox",children:[{type:"select",id:"categories",label:"Categories:",labelStyle:"font: 12px/25px arial, sans-serif;",size:"5",inputStyle:"width: 180px; height: auto;",items:[],onShow:function(){a.selectNode.categories=this},onHide:function(){this.clear()},onChange:function(){a.buildOptionSynonyms(this.getValue())}},
-{type:"select",id:"synonyms",label:"Synonyms:",labelStyle:"font: 12px/25px arial, sans-serif;",size:"5",inputStyle:"width: 180px; height: auto;",items:[],onShow:function(){a.selectNode.synonyms=this;a.textNode.Thesaurus.setValue(this.getValue())},onHide:function(){this.clear()},onChange:function(){a.textNode.Thesaurus.setValue(this.getValue())}}]}]},{type:"vbox",width:"120px",style:"margin-top:46px;",children:[{type:"html",id:"logotype",label:"WebSpellChecker.net",html:'',
-setup:function(){this.getElement().$.src=a.logotype;this.getElement().getParent().setStyles({"text-align":"center"})}},{type:"button",id:"FinishChecking",label:"Finish Checking",title:"Finish Checking",style:"width: 121px; float: right; margin-top: 9px;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onClick:c}]}]}]},{type:"hbox",id:"BlockFinishChecking",style:"width:560px; margin: 0 auto;",widths:["70%","30%"],onShow:function(){this.getElement().hide()},children:[{type:"hbox",
-id:"leftCol",align:"left",width:"70%",children:[{type:"vbox",id:"rightCol1",children:[{type:"html",id:"logo",html:'',setup:function(){this.getElement().$.src=a.logotype;this.getElement().getParent().setStyles({"text-align":"center"})}}]}]},{type:"hbox",id:"rightCol",align:"right",width:"30%",children:[{type:"vbox",id:"rightCol_col__left",children:[{type:"button",id:"FinishChecking",
-label:"Finish Checking",title:"Finish Checking",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onClick:c}]}]}]}]}]}});CKEDITOR.dialog.add("options",function(){var b=null,c={},d={},f=null,g=null;e.cookie.get("udn");e.cookie.get("osp");var h=function(){g=this.getElement().getAttribute("title-cmd");var a=[];a[0]=d.IgnoreAllCapsWords;a[1]=d.IgnoreWordsNumbers;a[2]=d.IgnoreMixedCaseWords;a[3]=d.IgnoreDomainNames;a=a.toString().replace(/,/g,"");e.cookie.set("osp",
-a);e.cookie.set("udnCmd",g?g:"ignore");"delete"!=g&&(a="",""!==j.getValue()&&(a=j.getValue()),e.cookie.set("udn",a));e.postMessage.send({id:"options_dic_send"})},i=function(){f.getElement().setHtml(a.LocalizationComing.error);f.getElement().show()};return{title:a.LocalizationComing.Options,minWidth:430,minHeight:130,resizable:CKEDITOR.DIALOG_RESIZE_NONE,contents:[{id:"OptionsTab",label:"Options",accessKey:"O",elements:[{type:"hbox",id:"options_error",children:[{type:"html",style:"display: block;text-align: center;white-space: normal!important; font-size: 12px;color:red",
-html:"",onShow:function(){f=this}}]},{type:"vbox",id:"Options_content",children:[{type:"hbox",id:"Options_manager",widths:["52%","48%"],children:[{type:"fieldset",label:"Spell Checking Options",style:"border: none;margin-top: 13px;padding: 10px 0 10px 10px",onShow:function(){this.getInputElement().$.children[0].innerHTML=a.LocalizationComing.SpellCheckingOptions},children:[{type:"vbox",id:"Options_checkbox",children:[{type:"checkbox",id:"IgnoreAllCapsWords",label:"Ignore All-Caps Words",
-labelStyle:"margin-left: 5px; font: 12px/16px arial, sans-serif;display: inline-block;white-space: normal;",style:"float:left; min-height: 16px;","default":"",onClick:function(){d[this.id]=!this.getValue()?0:1}},{type:"checkbox",id:"IgnoreWordsNumbers",label:"Ignore Words with Numbers",labelStyle:"margin-left: 5px; font: 12px/16px arial, sans-serif;display: inline-block;white-space: normal;",style:"float:left; min-height: 16px;","default":"",onClick:function(){d[this.id]=!this.getValue()?0:1}},{type:"checkbox",
-id:"IgnoreMixedCaseWords",label:"Ignore Mixed-Case Words",labelStyle:"margin-left: 5px; font: 12px/16px arial, sans-serif;display: inline-block;white-space: normal;",style:"float:left; min-height: 16px;","default":"",onClick:function(){d[this.id]=!this.getValue()?0:1}},{type:"checkbox",id:"IgnoreDomainNames",label:"Ignore Domain Names",labelStyle:"margin-left: 5px; font: 12px/16px arial, sans-serif;display: inline-block;white-space: normal;",style:"float:left; min-height: 16px;","default":"",onClick:function(){d[this.id]=
-!this.getValue()?0:1}}]}]},{type:"vbox",id:"Options_DictionaryName",children:[{type:"text",id:"DictionaryName",style:"margin-bottom: 10px",label:"Dictionary Name:",labelLayout:"vertical",labelStyle:"font: 12px/25px arial, sans-serif;","default":"",onLoad:function(){j=this;this.setValue(a.userDictionaryName?a.userDictionaryName:(e.cookie.get("udn"),this.getValue()))},onShow:function(){j=this;this.setValue(!e.cookie.get("udn")?this.getValue():e.cookie.get("udn"));this.setLabel(a.LocalizationComing.DictionaryName)},
-onHide:function(){this.reset()}},{type:"hbox",id:"Options_buttons",children:[{type:"vbox",id:"Options_leftCol_col",widths:["50%","50%"],children:[{type:"button",id:"create",label:"Create",title:"Create",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onShow:function(){this.getElement().setText(a.LocalizationComing.Create)},onClick:h},{type:"button",id:"restore",label:"Restore",title:"Restore",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",
-this.id)},onShow:function(){this.getElement().setText(a.LocalizationComing.Restore)},onClick:h}]},{type:"vbox",id:"Options_rightCol_col",widths:["50%","50%"],children:[{type:"button",id:"rename",label:"Rename",title:"Rename",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",this.id)},onShow:function(){this.getElement().setText(a.LocalizationComing.Rename)},onClick:h},{type:"button",id:"delete",label:"Remove",title:"Remove",style:"width: 100%;",onLoad:function(){this.getElement().setAttribute("title-cmd",
-this.id)},onShow:function(){this.getElement().setText(a.LocalizationComing.Remove)},onClick:h}]}]}]}]},{type:"hbox",id:"Options_text",children:[{type:"html",style:"text-align: justify;margin-top: 15px;white-space: normal!important; font-size: 12px;color:#777;",html:"