diff --git a/site/_includes/docs_contents.html b/site/_includes/docs_contents.html index 35904fbf..57b6b32c 100644 --- a/site/_includes/docs_contents.html +++ b/site/_includes/docs_contents.html @@ -3,94 +3,94 @@
Safe
-Disable custom plugins.
+Disable custom plugins.
safe: BOOL
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.
+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.
- If you want to use Liquid tags and variables but + 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!) diff --git a/site/docs/installation.md b/site/docs/installation.md index b2d1fa96..1bf1b8cb 100644 --- a/site/docs/installation.md +++ b/site/docs/installation.md @@ -42,7 +42,7 @@ $ gem install jekyll 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 +installing Jekyll, check out the [troubleshooting](../troubleshooting/) page or [report an issue](https://github.com/mojombo/jekyll/issues/new) so the Jekyll community can improve the experience for everyone. @@ -51,7 +51,7 @@ community can improve the experience for everyone. 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. +Check out [the extras page](../extras/) for more information.
- GitHub Pages is powered by Jekyll,
+ 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.
@@ -458,7 +458,7 @@ You can find a few useful plugins at the following locations:
If you have a Jekyll plugin that you would like to see added to this list, - you should read the contributing page to find + you should read the contributing page to find out how to make that happen.
- Stores configuration data. Many of + 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. @@ -67,7 +67,7 @@ An overview of what each of these does:
- Drafts are unpublished posts. The format of these files is without a date: title.MARKUP
. Learn how to work with drafts.
+ Drafts are unpublished posts. The format of these files is without a date: title.MARKUP
. Learn how to work with drafts.
These are the templates that wrap posts. Layouts are chosen on a post-
- by-post basis in the YAML front matter,
+ 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.
@@ -114,7 +114,7 @@ An overview of what each of these does:
Your dynamic content, so to speak. The format of these files is
important, and must follow the format:
YEAR-MONTH-DAY-title.MARKUP
.
- The permalinks can be customized for each
+ The permalinks can be customized for each
post, but the date and markup language are determined solely by the
file name.
@@ -142,7 +142,7 @@ An overview of what each of these does:
- Provided that the file has a YAML Front
+ 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
@@ -161,7 +161,7 @@ An overview of what each of these does:
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
+ 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/site/docs/troubleshooting.md b/site/docs/troubleshooting.md
index 6ea19bd9..6bd14da0 100644
--- a/site/docs/troubleshooting.md
+++ b/site/docs/troubleshooting.md
@@ -84,7 +84,7 @@ http://localhost:4000/blog
## Configuration problems
-The order of precedence for conflicting [configuration settings](../configuration)
+The order of precedence for conflicting [configuration settings](../configuration/)
is as follows:
1. Command-line flags
diff --git a/site/docs/usage.md b/site/docs/usage.md
index b62144d1..ac09c40a 100644
--- a/site/docs/usage.md
+++ b/site/docs/usage.md
@@ -35,7 +35,7 @@ $ jekyll serve --watch
# => As above, but watch for changes and regenerate automatically.
{% endhighlight %}
-This is just a few of the available [configuration options](../configuration).
+This is 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
@@ -55,4 +55,4 @@ $ jekyll build --source _source --destination _deploy
{% endhighlight %}
For more about the possible configuration options, see the
-[configuration](../configuration) page.
+[configuration](../configuration/) page.
diff --git a/site/docs/variables.md b/site/docs/variables.md
index 410a4c83..763ad387 100644
--- a/site/docs/variables.md
+++ b/site/docs/variables.md
@@ -7,7 +7,7 @@ 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
+Front Matter](../frontmatter/) are subject to processing. For each of these
files, Jekyll makes a variety of data available via the [Liquid templating
system](http://wiki.github.com/shopify/liquid/liquid-for-designers). The
following is a reference of the available data.
@@ -36,7 +36,7 @@ following is a reference of the available data.
page
- Page specific information + the YAML Front
+ Page specific information + the YAML Front
Matter. Custom variables set via the YAML front matter will be
available here. See below for details.
@@ -57,7 +57,7 @@ following is a reference of the available data.
When the paginate
configuration option is set, this
variable becomes available for use. See Pagination for details.
+ href="../pagination/">Pagination for details.
/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.
+ in the YAML Front Matter.
@@ -230,7 +230,7 @@ following is a reference of the available data.
The list of tags to which this post belongs. These can be specified in - the YAML Front Matter. + the YAML Front Matter.
No more databases, comment moderation, or pesky updates to install—just your content.
- How Jekyll works → + How Jekyll works →Markdown (or Textile), Liquid, HTML & CSS go in. Static sites come out ready for deployment.
- Jekyll template guide → + Jekyll template guide →Permalinks, categories, pages, posts, and custom layouts are all first-class citizens here.
- Migrate your blog → + Migrate your blog →