dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixes for @parkr comments.

This commit is contained in:
Tom Preston-Werner 2013-04-06 23:14:03 -07:00
parent 8316e1da4a
commit 565e815354
3 changed files with 19 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
site/_posts/2012-07-01-contributing.md
View File

@ -17,9 +17,9 @@ following in mind:
where appropriate. Also, whipping up some documentation in your fork's wiki
would be appreciated, and once merged it will be transferred over to the main
wiki.
* If your contribution changes any Jekyll behavior, make sure to update the
documentation. It lives in `site/_posts`. If the docs are missing information,
please feel free to add it in. Great docs make a great project!
* If your contribution adds or changes any Jekyll behavior, make sure to update
the documentation. It lives in `site/_posts`. If the docs are missing
information, please feel free to add it in. Great docs make a great project!
* Please follow the [GitHub Ruby Styleguide](https://github.com/styleguide/ruby)
when modifying Ruby code.
@ -35,7 +35,7 @@ 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
dependencies. Jekyll uses Bundler, so a quick run of the `bundle` command and
you're all set!
{% highlight bash %}

19
site/_posts/2012-07-01-structure.md
View File

@ -63,8 +63,9 @@ An overview of what each of these does:
<p>
These are the partials that can be mixed and matched by your layouts
and posts to facilitate reuse. The liquid tag <code>{% raw %}{% include
file.ext %}{% endraw %}</code> can be used to include the partial in
and posts to facilitate reuse. The liquid tag
<code>{% raw %}{% include file.ext %}{% endraw %}</code>
can be used to include the partial in
<code>_includes/file.ext</code>.
</p>
@ -79,8 +80,9 @@ An overview of what each of these does:
These are the templates that wrap posts. Layouts are chosen on a post-
by-post basis in the <a href="../frontmatter">YAML front matter</a>,
which is described in the next section. The liquid tag <code>{% raw %}{{
content }}{% endraw %}</code> is used to inject content into the web page.
which is described in the next section. The liquid tag
<code>{% raw %}{{ content }}{% endraw %}</code>
is used to inject content into the web page.
</p>
</td>
@ -93,10 +95,11 @@ An overview of what each of these does:
<p>
Your dynamic content, so to speak. The format of these files is
important, and must follow the format: <code>YEAR-MONTH-DAY-
title.MARKUP</code>. The <a href="../permalinks">permalinks</a> can be
customized for each post, but the date and markup language are
determined solely by the file name.
important, and must follow the format:
<code>YEAR-MONTH-DAY-title.MARKUP</code>.
The <a href="../permalinks">permalinks</a> can be customized for each
post, but the date and markup language are determined solely by the
file name.
</p>
</td>

8
site/_posts/2012-07-01-variables.md
View File

@ -163,8 +163,8 @@ following is a reference of the available data.
<td><p><code>page.url</code></p></td>
<td><p>
The URL of the Post without the domain. e.g. <code>/2008/12/14/my-
post.html</code>
The URL of the Post without the domain. e.g.
<code>/2008/12/14/my-post.html</code>
</p></td>
</tr>
@ -173,8 +173,8 @@ following is a reference of the available data.
<td><p>
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 <code>YYYY-MM-DD
HH:MM:SS</code>
matter by specifying a new date/time in the format
<code>YYYY-MM-DD HH:MM:SS</code>
</p></td>
</tr>