Reverted my upgrading.md to fix merge conflict.

This commit is contained in:
zachgersh 2013-05-10 20:01:34 -07:00
commit 81bbafefea
29 changed files with 42 additions and 25 deletions

View File

@ -1,10 +1,16 @@
## HEAD
### Major Enhancements
### Minor Enhancements
* Update pygments.rb version to 0.5.0 (#1061)
* Update Kramdown version to 1.0.2 (#1067)
### Bug Fixes
* Catching that Redcarpet gem isn't installed (#1059)
### Site Enhancements
* Move pages to be Pages for realz (#985)
* Updated links to Liquid documentation (#1073)
### Development Fixes
## 1.0.1 / 2013-05-08

View File

@ -27,8 +27,8 @@ Gem::Specification.new do |s|
s.add_runtime_dependency('classifier', "~> 1.3")
s.add_runtime_dependency('directory_watcher', "~> 1.4.1")
s.add_runtime_dependency('maruku', "~> 0.5")
s.add_runtime_dependency('kramdown', "~> 0.14")
s.add_runtime_dependency('pygments.rb', "~> 0.4.2")
s.add_runtime_dependency('kramdown', "~> 1.0.2")
s.add_runtime_dependency('pygments.rb', "~> 0.5.0")
s.add_runtime_dependency('commander', "~> 4.1.3")
s.add_runtime_dependency('safe_yaml', "~> 0.7.0")
s.add_runtime_dependency('colorator', "~> 0.1")

View File

@ -1,3 +1,2 @@
permalink: /docs/:categories/:title
pygments: true
gauges_id: 503c5af6613f5d0f19000027

View File

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

View File

@ -3,6 +3,7 @@ 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 its

View File

@ -3,6 +3,7 @@ layout: docs
title: Contributing
prev_section: deployment-methods
next_section: troubleshooting
permalink: /docs/contributing/
---
So you've got an awesome idea to throw into Jekyll. Great! Please keep the

View File

@ -3,6 +3,7 @@ layout: docs
title: Deployment methods
prev_section: github-pages
next_section: contributing
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.

View File

@ -3,6 +3,7 @@ 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

View File

@ -3,6 +3,7 @@ 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

View File

@ -3,6 +3,7 @@ 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,

View File

@ -3,6 +3,7 @@ layout: docs
title: Heroku
prev_section: github-pages
next_section: manual-deployment
permalink: /docs/heroku/
---
Move along, people. Nothing to see here.

View File

@ -1,11 +0,0 @@
<!DOCTYPE HTML>
<html lang="en-US">
<head>
<meta charset="UTF-8">
<meta http-equiv="refresh" content="0;url=home">
<title>Jekyll</title>
</head>
<body style="background: #333;">
</body>
</html>

View File

@ -2,6 +2,7 @@
layout: docs
title: Welcome
next_section: installation
permalink: /docs/home/
---
This site aims to be a comprehensive guide to Jekyll. Well cover topics such
@ -15,7 +16,8 @@ development of Jekyll itself.
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://textile.sitemonks.com/)) and [Liquid](http://liquidmarkup.org/)
[Textile](http://textile.sitemonks.com/)) and
[Liquid](http://wiki.shopify.com/Liquid)
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

View File

@ -3,6 +3,7 @@ layout: docs
title: Installation
prev_section: home
next_section: usage
permalink: /docs/installation/
---
Getting Jekyll installed and ready-to-go should only take a few minutes. If it

View File

@ -3,6 +3,7 @@ layout: docs
title: Blog migrations
prev_section: variables
next_section: templates
permalink: /docs/migrations/
---
If youre switching to Jekyll from another blogging system, Jekylls importers

View File

@ -3,6 +3,7 @@ layout: docs
title: Creating pages
prev_section: posts
next_section: variables
permalink: /docs/pages/
---
In addition to [writing posts](../posts), another thing you may want to do with

View File

@ -3,6 +3,7 @@ layout: docs
title: Pagination
prev_section: permalinks
next_section: plugins
permalink: /docs/pagination/
---
With many websites—especially blogs—its very common to break the main listing

View File

@ -3,6 +3,7 @@ layout: docs
title: Permalinks
prev_section: templates
next_section: pagination
permalink: /docs/permalinks/
---
Jekyll supports a flexible way to build your sites URLs. You can specify the

View File

@ -3,6 +3,7 @@ layout: docs
title: Plugins
prev_section: assets
next_section: extras
permalink: /docs/plugins/
---
Jekyll has a plugin system with hooks that allow you to create custom generated

View File

@ -3,6 +3,7 @@ layout: docs
title: Writing posts
prev_section: frontmatter
next_section: pages
permalink: /docs/posts/
---
One of Jekylls best aspects is that it is “blog aware”. What does this mean,
@ -95,7 +96,7 @@ Linking to a PDF for readers to download:
Its 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://liquidmarkup.org/) and its tags. Heres a basic example of how
language](http://wiki.shopify.com/Liquid) and its tags. Heres a basic example of how
to create a list of links to your blog posts:
{% highlight html %}

View File

@ -3,6 +3,7 @@ layout: docs
title: Resources
prev_section: sites
next_section: upgrading
permalink: /docs/resources/
---
Jekylls 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.

View File

@ -3,6 +3,7 @@ layout: docs
title: Sites using Jekyll
prev_section: troubleshooting
next_section: resources
permalink: /docs/sites/
---
Its interesting to see what designs and features others have come up

View File

@ -3,6 +3,7 @@ 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

View File

@ -3,9 +3,10 @@ layout: docs
title: Templates
prev_section: migrations
next_section: permalinks
permalink: /docs/templates/
---
Jekyll uses the [Liquid](http://www.liquidmarkup.org/) templating language to
Jekyll uses the [Liquid](http://wiki.shopify.com/Liquid) templating language to
process templates. All of the [standard Liquid tags and
filters](http://wiki.github.com/shopify/liquid/liquid-for-designers) are
supported, Jekyll even adds a few handy filters and tags of its own to make

View File

@ -3,6 +3,7 @@ layout: docs
title: Troubleshooting
prev_section: contributing
next_section: sites
permalink: /docs/troubleshooting/
---
If you ever run into problems installing or using Jekyll, heres a few tips that might be of help. If the problem youre experiencing isnt covered below, please [report an issue](https://github.com/mojombo/jekyll/issues/new) so the Jekyll community can make everyones experience better.

View File

@ -2,10 +2,10 @@
layout: docs
title: Upgrading
prev_section: resources
next_section: changelist
permalink: /docs/upgrading/
---
Upgrading from an older version of Jekyll? A few things have changed in 1.0.0
Upgrading from an older version of Jekyll? A few things have changed in 1.0
that you'll want to know about.

View File

@ -3,6 +3,7 @@ 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

View File

@ -3,6 +3,7 @@ layout: docs
title: Variables
prev_section: pages
next_section: migrations
permalink: /docs/variables/
---
Jekyll traverses your site looking for files to process. Any files with [YAML

View File

@ -18,19 +18,19 @@ overview: true
<p>
No more databases, comment moderation, or pesky updates to install—just <em>your content</em>.
</p>
<a href="{% post_url 2012-07-01-usage %}" class="">How Jekyll works &rarr;</a>
<a href="/docs/usage" class="">How Jekyll works &rarr;</a>
</div>
<div class="unit one-third">
<h2>Static</h2>
<p><a href="http://daringfireball.net/projects/markdown/">Markdown</a> (or <a href="http://textile.sitemonks.com/">Textile</a>), <a href="http://liquidmarkup.org/">Liquid</a>, HTML <span class="amp">&amp;</span> CSS go in. Static sites come out ready for deployment.</p>
<a href="{% post_url 2012-07-01-templates %}" class="">Jekyll template guide &rarr;</a>
<p><a href="http://daringfireball.net/projects/markdown/">Markdown</a> (or <a href="http://textile.sitemonks.com/">Textile</a>), <a href="http://wiki.shopify.com/Liquid">Liquid</a>, HTML <span class="amp">&amp;</span> CSS go in. Static sites come out ready for deployment.</p>
<a href="/docs/templates" class="">Jekyll template guide &rarr;</a>
</div>
<div class="unit one-third">
<h2>Blog-aware</h2>
<p>
Permalinks, categories, pages, posts, and custom layouts are all first-class citizens here.
</p>
<a href="{% post_url 2012-07-01-migrations %}" class="">Migrate your blog &rarr;</a>
<a href="/docs/migrations" class="">Migrate your blog &rarr;</a>
</div>
<div class="clear"></div>
</div>