jekyll-docs 3.1.6 → 3.2.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/jekyll-docs.rb +7 -13
- data/site/community/index.html +305 -0
- data/site/conduct/index.html +10 -0
- data/site/css/screen.css +1445 -0
- data/site/docs/assets/index.html +701 -0
- data/site/docs/collections/index.html +973 -0
- data/site/docs/conduct/index.html +718 -0
- data/site/docs/configuration/index.html +1337 -0
- data/site/docs/continuous-integration/index.html +846 -0
- data/site/docs/contributing/index.html +815 -0
- data/site/docs/datafiles/index.html +742 -0
- data/site/docs/deployment-methods/index.html +866 -0
- data/site/docs/drafts/index.html +615 -0
- data/site/docs/extras/index.html +656 -0
- data/site/docs/frontmatter/index.html +776 -0
- data/site/docs/github-pages/index.html +778 -0
- data/site/docs/history/index.html +3293 -0
- data/site/docs/home/index.html +627 -0
- data/site/docs/index.html +10 -0
- data/site/docs/installation/index.html +682 -0
- data/site/docs/migrations/index.html +627 -0
- data/site/docs/pages/index.html +698 -0
- data/site/docs/pagination/index.html +840 -0
- data/site/docs/permalinks/index.html +924 -0
- data/site/docs/plugins/index.html +1726 -0
- data/site/docs/posts/index.html +811 -0
- data/site/docs/quickstart/index.html +599 -0
- data/site/docs/resources/index.html +717 -0
- data/site/docs/sites/index.html +676 -0
- data/site/docs/static-files/index.html +655 -0
- data/site/docs/structure/index.html +794 -0
- data/site/docs/templates/index.html +1105 -0
- data/site/docs/themes/index.html +751 -0
- data/site/docs/troubleshooting/index.html +826 -0
- data/site/docs/upgrading/0-to-2/index.html +802 -0
- data/site/docs/upgrading/2-to-3/index.html +785 -0
- data/site/docs/upgrading/index.html +664 -0
- data/site/docs/usage/index.html +673 -0
- data/site/docs/variables/index.html +1013 -0
- data/site/docs/windows/index.html +775 -0
- data/site/feed.xml +222 -0
- data/site/github.html +10 -0
- data/site/help/index.html +246 -0
- data/site/img/article-footer.png +0 -0
- data/site/img/footer-logo.png +0 -0
- data/site/img/logo-2x.png +0 -0
- data/site/index.html +200 -16
- data/site/issues.html +10 -0
- data/site/news/2013/05/05/jekyll-1-0-0-released/index.html +524 -0
- data/site/news/2013/05/08/jekyll-1-0-1-released/index.html +524 -0
- data/site/news/2013/05/12/jekyll-1-0-2-released/index.html +525 -0
- data/site/news/2013/06/07/jekyll-1-0-3-released/index.html +522 -0
- data/site/news/2013/07/14/jekyll-1-1-0-released/index.html +524 -0
- data/site/news/2013/07/24/jekyll-1-1-1-released/index.html +523 -0
- data/site/news/2013/07/25/jekyll-1-0-4-released/index.html +519 -0
- data/site/news/2013/07/25/jekyll-1-1-2-released/index.html +519 -0
- data/site/news/2013/09/06/jekyll-1-2-0-released/index.html +526 -0
- data/site/news/2013/09/14/jekyll-1-2-1-released/index.html +520 -0
- data/site/news/2013/10/28/jekyll-1-3-0-rc1-released/index.html +518 -0
- data/site/news/2013/11/04/jekyll-1-3-0-released/index.html +553 -0
- data/site/news/2013/11/26/jekyll-1-3-1-released/index.html +522 -0
- data/site/news/2013/12/07/jekyll-1-4-0-released/index.html +537 -0
- data/site/news/2013/12/09/jekyll-1-4-1-released/index.html +519 -0
- data/site/news/2013/12/16/jekyll-1-4-2-released/index.html +518 -0
- data/site/news/2014/01/13/jekyll-1-4-3-released/index.html +527 -0
- data/site/news/2014/03/24/jekyll-1-5-0-released/index.html +518 -0
- data/site/news/2014/03/27/jekyll-1-5-1-released/index.html +523 -0
- data/site/news/2014/05/06/jekyll-turns-2-0-0/index.html +539 -0
- data/site/news/2014/05/08/jekyll-2-0-3-released/index.html +519 -0
- data/site/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/index.html +521 -0
- data/site/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/index.html +536 -0
- data/site/news/2014/07/01/jekyll-2-1-1-released/index.html +533 -0
- data/site/news/2014/07/29/jekyll-2-2-0-released/index.html +522 -0
- data/site/news/2014/08/10/jekyll-2-3-0-released/index.html +542 -0
- data/site/news/2014/09/09/jekyll-2-4-0-released/index.html +528 -0
- data/site/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/index.html +551 -0
- data/site/news/2014/11/09/jekyll-2-5-1-released/index.html +529 -0
- data/site/news/2014/11/12/jekyll-2-5-2-released/index.html +519 -0
- data/site/news/2014/12/17/alfredxing-welcome-to-jekyll-core/index.html +526 -0
- data/site/news/2014/12/22/jekyll-2-5-3-released/index.html +521 -0
- data/site/news/2015/01/20/jekyll-meet-and-greet/index.html +522 -0
- data/site/news/2015/01/24/jekyll-3-0-0-beta1-released/index.html +542 -0
- data/site/news/2015/02/26/introducing-jekyll-talk/index.html +517 -0
- data/site/news/2015/10/26/jekyll-3-0-released/index.html +546 -0
- data/site/news/2015/11/17/jekyll-3-0-1-released/index.html +530 -0
- data/site/news/2016/01/20/jekyll-3-0-2-released/index.html +520 -0
- data/site/news/2016/01/24/jekyll-3-1-0-released/index.html +553 -0
- data/site/news/2016/01/28/jekyll-3-1-1-released/index.html +537 -0
- data/site/news/2016/02/08/jekyll-3-0-3-released/index.html +532 -0
- data/site/news/2016/02/19/jekyll-3-1-2-released/index.html +523 -0
- data/site/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/index.html +519 -0
- data/site/news/2016/04/19/jekyll-3-0-4-released/index.html +525 -0
- data/site/news/2016/04/19/jekyll-3-1-3-released/index.html +521 -0
- data/site/news/2016/04/26/jekyll-3-0-5-released/index.html +526 -0
- data/site/news/2016/05/18/jekyll-3-1-4-released/index.html +530 -0
- data/site/news/2016/05/18/jekyll-3-1-5-released/index.html +518 -0
- data/site/news/2016/05/19/jekyll-3-1-6-released/index.html +520 -0
- data/site/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/index.html +521 -0
- data/site/news/2016/07/26/jekyll-3-2-0-released/index.html +630 -0
- data/site/news/index.html +2831 -10
- data/site/news/releases/index.html +2603 -10
- data/site/sitemap.xml +327 -0
- metadata +99 -111
- data/site/_config.yml +0 -25
- data/site/_data/docs.yml +0 -49
- data/site/_docs/assets.md +0 -94
- data/site/_docs/collections.md +0 -380
- data/site/_docs/conduct.md +0 -55
- data/site/_docs/configuration.md +0 -747
- data/site/_docs/continuous-integration.md +0 -221
- data/site/_docs/contributing.md +0 -124
- data/site/_docs/datafiles.md +0 -151
- data/site/_docs/deployment-methods.md +0 -213
- data/site/_docs/drafts.md +0 -20
- data/site/_docs/extras.md +0 -22
- data/site/_docs/frontmatter.md +0 -191
- data/site/_docs/github-pages.md +0 -133
- data/site/_docs/history.md +0 -2323
- data/site/_docs/index.md +0 -57
- data/site/_docs/installation.md +0 -106
- data/site/_docs/migrations.md +0 -9
- data/site/_docs/pages.md +0 -100
- data/site/_docs/pagination.md +0 -224
- data/site/_docs/permalinks.md +0 -308
- data/site/_docs/plugins.md +0 -903
- data/site/_docs/posts.md +0 -237
- data/site/_docs/quickstart.md +0 -26
- data/site/_docs/resources.md +0 -38
- data/site/_docs/sites.md +0 -23
- data/site/_docs/static_files.md +0 -52
- data/site/_docs/structure.md +0 -211
- data/site/_docs/templates.md +0 -451
- data/site/_docs/troubleshooting.md +0 -207
- data/site/_docs/upgrading.md +0 -10
- data/site/_docs/upgrading/0-to-2.md +0 -140
- data/site/_docs/upgrading/2-to-3.md +0 -126
- data/site/_docs/usage.md +0 -101
- data/site/_docs/variables.md +0 -390
- data/site/_docs/windows.md +0 -46
- data/site/_includes/analytics.html +0 -30
- data/site/_includes/anchor_links.html +0 -33
- data/site/_includes/docs_contents.html +0 -8
- data/site/_includes/docs_contents_mobile.html +0 -10
- data/site/_includes/docs_option.html +0 -11
- data/site/_includes/docs_ul.html +0 -17
- data/site/_includes/footer.html +0 -15
- data/site/_includes/header.html +0 -18
- data/site/_includes/news_contents.html +0 -33
- data/site/_includes/news_contents_mobile.html +0 -11
- data/site/_includes/news_item.html +0 -24
- data/site/_includes/primary-nav-items.html +0 -17
- data/site/_includes/section_nav.html +0 -39
- data/site/_includes/top.html +0 -17
- data/site/_layouts/default.html +0 -13
- data/site/_layouts/docs.html +0 -26
- data/site/_layouts/news.html +0 -19
- data/site/_layouts/news_item.html +0 -27
- data/site/_layouts/page.html +0 -18
- data/site/_posts/2013-05-06-jekyll-1-0-0-released.markdown +0 -23
- data/site/_posts/2013-05-08-jekyll-1-0-1-released.markdown +0 -27
- data/site/_posts/2013-05-12-jekyll-1-0-2-released.markdown +0 -28
- data/site/_posts/2013-06-07-jekyll-1-0-3-released.markdown +0 -25
- data/site/_posts/2013-07-14-jekyll-1-1-0-released.markdown +0 -27
- data/site/_posts/2013-07-24-jekyll-1-1-1-released.markdown +0 -31
- data/site/_posts/2013-07-25-jekyll-1-0-4-released.markdown +0 -20
- data/site/_posts/2013-07-25-jekyll-1-1-2-released.markdown +0 -20
- data/site/_posts/2013-09-06-jekyll-1-2-0-released.markdown +0 -23
- data/site/_posts/2013-09-14-jekyll-1-2-1-released.markdown +0 -19
- data/site/_posts/2013-10-28-jekyll-1-3-0-rc1-released.markdown +0 -17
- data/site/_posts/2013-11-04-jekyll-1-3-0-released.markdown +0 -43
- data/site/_posts/2013-11-26-jekyll-1-3-1-released.markdown +0 -21
- data/site/_posts/2013-12-07-jekyll-1-4-0-released.markdown +0 -30
- data/site/_posts/2013-12-09-jekyll-1-4-1-released.markdown +0 -18
- data/site/_posts/2013-12-16-jekyll-1-4-2-released.markdown +0 -18
- data/site/_posts/2014-01-13-jekyll-1-4-3-released.markdown +0 -26
- data/site/_posts/2014-03-24-jekyll-1-5-0-released.markdown +0 -19
- data/site/_posts/2014-03-27-jekyll-1-5-1-released.markdown +0 -26
- data/site/_posts/2014-05-06-jekyll-turns-2-0-0.markdown +0 -31
- data/site/_posts/2014-05-08-jekyll-2-0-3-released.markdown +0 -18
- data/site/_posts/2014-06-04-jekyll-stickers-1-dollar-stickermule.markdown +0 -19
- data/site/_posts/2014-06-28-jekyll-turns-21-i-mean-2-1-0.markdown +0 -31
- data/site/_posts/2014-07-01-jekyll-2-1-1-released.markdown +0 -30
- data/site/_posts/2014-07-29-jekyll-2-2-0-released.markdown +0 -19
- data/site/_posts/2014-08-10-jekyll-2-3-0-released.markdown +0 -41
- data/site/_posts/2014-09-09-jekyll-2-4-0-released.markdown +0 -25
- data/site/_posts/2014-11-06-jekylls-midlife-crisis-jekyll-turns-2-5-0.markdown +0 -47
- data/site/_posts/2014-11-08-jekyll-2-5-1-released.markdown +0 -29
- data/site/_posts/2014-11-12-jekyll-2-5-2-released.markdown +0 -18
- data/site/_posts/2014-12-17-alfredxing-welcome-to-jekyll-core.md +0 -27
- data/site/_posts/2014-12-22-jekyll-2-5-3-released.markdown +0 -20
- data/site/_posts/2015-01-20-jekyll-meet-and-greet.markdown +0 -20
- data/site/_posts/2015-01-24-jekyll-3-0-0-beta1-released.markdown +0 -40
- data/site/_posts/2015-02-26-introducing-jekyll-talk.markdown +0 -15
- data/site/_posts/2015-10-26-jekyll-3-0-released.markdown +0 -35
- data/site/_posts/2015-11-17-jekyll-3-0-1-released.markdown +0 -25
- data/site/_posts/2016-01-20-jekyll-3-0-2-released.markdown +0 -19
- data/site/_posts/2016-01-24-jekyll-3-1-0-released.markdown +0 -50
- data/site/_posts/2016-01-28-jekyll-3-1-1-released.markdown +0 -33
- data/site/_posts/2016-02-08-jekyll-3-0-3-released.markdown +0 -32
- data/site/_posts/2016-02-19-jekyll-3-1-2-released.markdown +0 -20
- data/site/_sass/_font-awesome.scss +0 -25
- data/site/_sass/_gridism.scss +0 -124
- data/site/_sass/_mixins.scss +0 -38
- data/site/_sass/_normalize.scss +0 -1
- data/site/_sass/_pygments.scss +0 -78
- data/site/_sass/_style.scss +0 -1002
- data/site/css/screen.scss +0 -9
- data/site/help/index.md +0 -41
- data/site/redirects/github.html +0 -4
- data/site/redirects/issues.html +0 -4
data/site/_docs/conduct.md
DELETED
@@ -1,55 +0,0 @@
|
|
1
|
-
---
|
2
|
-
layout: docs
|
3
|
-
title: Code of Conduct
|
4
|
-
permalink: "/docs/conduct/"
|
5
|
-
redirect_from: "/conduct/index.html"
|
6
|
-
editable: false
|
7
|
-
---
|
8
|
-
|
9
|
-
As contributors and maintainers of this project, and in the interest of
|
10
|
-
fostering an open and welcoming community, we pledge to respect all people who
|
11
|
-
contribute through reporting issues, posting feature requests, updating
|
12
|
-
documentation, submitting pull requests or patches, and other activities.
|
13
|
-
|
14
|
-
We are committed to making participation in this project a harassment-free
|
15
|
-
experience for everyone, regardless of level of experience, gender, gender
|
16
|
-
identity and expression, sexual orientation, disability, personal appearance,
|
17
|
-
body size, race, ethnicity, age, religion, or nationality.
|
18
|
-
|
19
|
-
Examples of unacceptable behavior by participants include:
|
20
|
-
|
21
|
-
* The use of sexualized language or imagery
|
22
|
-
* Personal attacks
|
23
|
-
* Trolling or insulting/derogatory comments
|
24
|
-
* Public or private harassment
|
25
|
-
* Publishing other's private information, such as physical or electronic
|
26
|
-
addresses, without explicit permission
|
27
|
-
* Other unethical or unprofessional conduct
|
28
|
-
|
29
|
-
Project maintainers have the right and responsibility to remove, edit, or
|
30
|
-
reject comments, commits, code, wiki edits, issues, and other contributions
|
31
|
-
that are not aligned to this Code of Conduct, or to ban temporarily or
|
32
|
-
permanently any contributor for other behaviors that they deem inappropriate,
|
33
|
-
threatening, offensive, or harmful.
|
34
|
-
|
35
|
-
By adopting this Code of Conduct, project maintainers commit themselves to
|
36
|
-
fairly and consistently applying these principles to every aspect of managing
|
37
|
-
this project. Project maintainers who do not follow or enforce the Code of
|
38
|
-
Conduct may be permanently removed from the project team.
|
39
|
-
|
40
|
-
This Code of Conduct applies both within project spaces and in public spaces
|
41
|
-
when an individual is representing the project or its community.
|
42
|
-
|
43
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
44
|
-
reported by opening an issue or contacting a project maintainer. All complaints
|
45
|
-
will be reviewed and investigated and will result in a response that is deemed
|
46
|
-
necessary and appropriate to the circumstances. Maintainers are obligated to
|
47
|
-
maintain confidentiality with regard to the reporter of an incident.
|
48
|
-
|
49
|
-
|
50
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
51
|
-
version 1.3.0, available at
|
52
|
-
[http://contributor-covenant.org/version/1/3/0/][version]
|
53
|
-
|
54
|
-
[homepage]: http://contributor-covenant.org
|
55
|
-
[version]: http://contributor-covenant.org/version/1/3/0/
|
data/site/_docs/configuration.md
DELETED
@@ -1,747 +0,0 @@
|
|
1
|
-
---
|
2
|
-
layout: docs
|
3
|
-
title: Configuration
|
4
|
-
permalink: /docs/configuration/
|
5
|
-
---
|
6
|
-
|
7
|
-
Jekyll allows you to concoct your sites in any way you can dream up, and it’s
|
8
|
-
thanks to the powerful and flexible configuration options that this is possible.
|
9
|
-
These options can either be specified in a `_config.yml` file placed in your
|
10
|
-
site’s root directory, or can be specified as flags for the `jekyll` executable
|
11
|
-
in the terminal.
|
12
|
-
|
13
|
-
## Configuration Settings
|
14
|
-
|
15
|
-
### Global Configuration
|
16
|
-
|
17
|
-
The table below lists the available settings for Jekyll, and the various <code
|
18
|
-
class="option">options</code> (specified in the configuration file) and <code
|
19
|
-
class="flag">flags</code> (specified on the command-line) that control them.
|
20
|
-
|
21
|
-
<div class="mobile-side-scroller">
|
22
|
-
<table>
|
23
|
-
<thead>
|
24
|
-
<tr>
|
25
|
-
<th>Setting</th>
|
26
|
-
<th>
|
27
|
-
<span class="option">Options</span> and <span class="flag">Flags</span>
|
28
|
-
</th>
|
29
|
-
</tr>
|
30
|
-
</thead>
|
31
|
-
<tbody>
|
32
|
-
<tr class="setting">
|
33
|
-
<td>
|
34
|
-
<p class="name"><strong>Site Source</strong></p>
|
35
|
-
<p class="description">Change the directory where Jekyll will read files</p>
|
36
|
-
</td>
|
37
|
-
<td class="align-center">
|
38
|
-
<p><code class="option">source: DIR</code></p>
|
39
|
-
<p><code class="flag">-s, --source DIR</code></p>
|
40
|
-
</td>
|
41
|
-
</tr>
|
42
|
-
<tr class="setting">
|
43
|
-
<td>
|
44
|
-
<p class="name"><strong>Site Destination</strong></p>
|
45
|
-
<p class="description">Change the directory where Jekyll will write files</p>
|
46
|
-
</td>
|
47
|
-
<td class="align-center">
|
48
|
-
<p><code class="option">destination: DIR</code></p>
|
49
|
-
<p><code class="flag">-d, --destination DIR</code></p>
|
50
|
-
</td>
|
51
|
-
</tr>
|
52
|
-
<tr class="setting">
|
53
|
-
<td>
|
54
|
-
<p class="name"><strong>Safe</strong></p>
|
55
|
-
<p class="description">Disable <a href="../plugins/">custom plugins, and ignore symbolic links</a>.</p>
|
56
|
-
</td>
|
57
|
-
<td class="align-center">
|
58
|
-
<p><code class="option">safe: BOOL</code></p>
|
59
|
-
<p><code class="flag">--safe</code></p>
|
60
|
-
</td>
|
61
|
-
</tr>
|
62
|
-
<tr class="setting">
|
63
|
-
<td>
|
64
|
-
<p class="name"><strong>Exclude</strong></p>
|
65
|
-
<p class="description">
|
66
|
-
Exclude directories and/or files from the
|
67
|
-
conversion. These exclusions are relative to the site's
|
68
|
-
source directory and cannot be outside the source directory.
|
69
|
-
</p>
|
70
|
-
</td>
|
71
|
-
<td class="align-center">
|
72
|
-
<p><code class="option">exclude: [DIR, FILE, ...]</code></p>
|
73
|
-
</td>
|
74
|
-
</tr>
|
75
|
-
<tr class="setting">
|
76
|
-
<td>
|
77
|
-
<p class="name"><strong>Include</strong></p>
|
78
|
-
<p class="description">
|
79
|
-
Force inclusion of directories and/or files in the conversion.
|
80
|
-
<code>.htaccess</code> is a good example since dotfiles are excluded
|
81
|
-
by default.
|
82
|
-
</p>
|
83
|
-
</td>
|
84
|
-
<td class="align-center">
|
85
|
-
<p><code class="option">include: [DIR, FILE, ...]</code></p>
|
86
|
-
</td>
|
87
|
-
</tr>
|
88
|
-
<tr class="setting">
|
89
|
-
<td>
|
90
|
-
<p class="name"><strong>Keep files</strong></p>
|
91
|
-
<p class="description">
|
92
|
-
When clobbering the site destination, keep the selected files.
|
93
|
-
Useful for files that are not generated by jekyll; e.g. files or
|
94
|
-
assets that are generated by your build tool.
|
95
|
-
The paths are relative to the <code>destination</code>.
|
96
|
-
</p>
|
97
|
-
</td>
|
98
|
-
<td class="align-center">
|
99
|
-
<p><code class="option">keep_files: [DIR, FILE, ...]</code></p>
|
100
|
-
</td>
|
101
|
-
</tr>
|
102
|
-
<tr class="setting">
|
103
|
-
<td>
|
104
|
-
<p class="name"><strong>Time Zone</strong></p>
|
105
|
-
<p class="description">
|
106
|
-
Set the time zone for site generation. This sets the <code>TZ</code>
|
107
|
-
environment variable, which Ruby uses to handle time and date
|
108
|
-
creation and manipulation. Any entry from the
|
109
|
-
<a href="http://en.wikipedia.org/wiki/Tz_database">IANA Time Zone
|
110
|
-
Database</a> is valid, e.g. <code>America/New_York</code>. A list of all
|
111
|
-
available values can be found <a href="http://en.wikipedia.org/wiki/List_of_tz_database_time_zones">
|
112
|
-
here</a>. The default is the local time zone, as set by your operating system.
|
113
|
-
</p>
|
114
|
-
</td>
|
115
|
-
<td class="align-center">
|
116
|
-
<p><code class="option">timezone: TIMEZONE</code></p>
|
117
|
-
</td>
|
118
|
-
</tr>
|
119
|
-
<tr class="setting">
|
120
|
-
<td>
|
121
|
-
<p class="name"><strong>Encoding</strong></p>
|
122
|
-
<p class="description">
|
123
|
-
Set the encoding of files by name (only available for Ruby
|
124
|
-
1.9 or later).
|
125
|
-
The default value is <code>utf-8</code> starting in 2.0.0,
|
126
|
-
and <code>nil</code> before 2.0.0, which will yield the Ruby
|
127
|
-
default of <code>ASCII-8BIT</code>.
|
128
|
-
Available encodings can be shown by the
|
129
|
-
command <code>ruby -e 'puts Encoding::list.join("\n")'</code>.
|
130
|
-
</p>
|
131
|
-
</td>
|
132
|
-
<td class="align-center">
|
133
|
-
<p><code class="option">encoding: ENCODING</code></p>
|
134
|
-
</td>
|
135
|
-
</tr>
|
136
|
-
<tr>
|
137
|
-
<td>
|
138
|
-
<p class='name'><strong>Defaults</strong></p>
|
139
|
-
<p class='description'>
|
140
|
-
Set defaults for <a href="../frontmatter/" title="YAML Front Matter">YAML Front Matter</a>
|
141
|
-
variables.
|
142
|
-
</p>
|
143
|
-
</td>
|
144
|
-
<td class='align-center'>
|
145
|
-
<p>see <a href="#front-matter-defaults" title="details">below</a></p>
|
146
|
-
</td>
|
147
|
-
</tr>
|
148
|
-
</tbody>
|
149
|
-
</table>
|
150
|
-
</div>
|
151
|
-
|
152
|
-
<div class="note warning">
|
153
|
-
<h5>Destination folders are cleaned on site builds</h5>
|
154
|
-
<p>
|
155
|
-
The contents of <code><destination></code> are automatically
|
156
|
-
cleaned, by default, when the site is built. Files or folders that are not
|
157
|
-
created by your site will be removed. Some files could be retained
|
158
|
-
by specifying them within the <code><keep_files></code> configuration directive.
|
159
|
-
</p>
|
160
|
-
<p>
|
161
|
-
Do not use an important location for <code><destination></code>; instead, use it as
|
162
|
-
a staging area and copy files from there to your web server.
|
163
|
-
</p>
|
164
|
-
</div>
|
165
|
-
|
166
|
-
### Build Command Options
|
167
|
-
|
168
|
-
<div class="mobile-side-scroller">
|
169
|
-
<table>
|
170
|
-
<thead>
|
171
|
-
<tr>
|
172
|
-
<th>Setting</th>
|
173
|
-
<th><span class="option">Options</span> and <span class="flag">Flags</span></th>
|
174
|
-
</tr>
|
175
|
-
</thead>
|
176
|
-
<tbody>
|
177
|
-
<tr class="setting">
|
178
|
-
<td>
|
179
|
-
<p class="name"><strong>Regeneration</strong></p>
|
180
|
-
<p class="description">Enable auto-regeneration of the site when files are modified.</p>
|
181
|
-
</td>
|
182
|
-
<td class="align-center">
|
183
|
-
<p><code class="flag">-w, --[no-]watch</code></p>
|
184
|
-
</td>
|
185
|
-
</tr>
|
186
|
-
<tr class="setting">
|
187
|
-
<td>
|
188
|
-
<p class="name"><strong>Configuration</strong></p>
|
189
|
-
<p class="description">Specify config files instead of using <code>_config.yml</code> automatically. Settings in later files override settings in earlier files.</p>
|
190
|
-
</td>
|
191
|
-
<td class="align-center">
|
192
|
-
<p><code class="flag">--config FILE1[,FILE2,...]</code></p>
|
193
|
-
</td>
|
194
|
-
</tr>
|
195
|
-
<tr class="setting">
|
196
|
-
<td>
|
197
|
-
<p class="name"><strong>Drafts</strong></p>
|
198
|
-
<p class="description">Process and render draft posts.</p>
|
199
|
-
</td>
|
200
|
-
<td class="align-center">
|
201
|
-
<p><code class="option">show_drafts: BOOL</code></p>
|
202
|
-
<p><code class="flag">--drafts</code></p>
|
203
|
-
</td>
|
204
|
-
</tr>
|
205
|
-
<tr class="setting">
|
206
|
-
<td>
|
207
|
-
<p class="name"><strong>Environment</strong></p>
|
208
|
-
<p class="description">Use a specific environment value in the build.</p>
|
209
|
-
</td>
|
210
|
-
<td class="align-center">
|
211
|
-
<p><code class="flag">JEKYLL_ENV=production</code></p>
|
212
|
-
</td>
|
213
|
-
</tr>
|
214
|
-
<tr class="setting">
|
215
|
-
<td>
|
216
|
-
<p class="name"><strong>Future</strong></p>
|
217
|
-
<p class="description">Publish posts with a future date.</p>
|
218
|
-
</td>
|
219
|
-
<td class="align-center">
|
220
|
-
<p><code class="option">future: BOOL</code></p>
|
221
|
-
<p><code class="flag">--future</code></p>
|
222
|
-
</td>
|
223
|
-
</tr>
|
224
|
-
<tr class="setting">
|
225
|
-
<td>
|
226
|
-
<p class="name"><strong>LSI</strong></p>
|
227
|
-
<p class="description">Produce an index for related posts.</p>
|
228
|
-
</td>
|
229
|
-
<td class="align-center">
|
230
|
-
<p><code class="option">lsi: BOOL</code></p>
|
231
|
-
<p><code class="flag">--lsi</code></p>
|
232
|
-
</td>
|
233
|
-
</tr>
|
234
|
-
<tr class="setting">
|
235
|
-
<td>
|
236
|
-
<p class="name"><strong>Limit Posts</strong></p>
|
237
|
-
<p class="description">Limit the number of posts to parse and publish.</p>
|
238
|
-
</td>
|
239
|
-
<td class="align-center">
|
240
|
-
<p><code class="option">limit_posts: NUM</code></p>
|
241
|
-
<p><code class="flag">--limit_posts NUM</code></p>
|
242
|
-
</td>
|
243
|
-
</tr>
|
244
|
-
<tr class="setting">
|
245
|
-
<td>
|
246
|
-
<p class="name"><strong>Force polling</strong></p>
|
247
|
-
<p class="description">Force watch to use polling.</p>
|
248
|
-
</td>
|
249
|
-
<td class="align-center">
|
250
|
-
<p><code class="flag">--force_polling</code></p>
|
251
|
-
</td>
|
252
|
-
</tr>
|
253
|
-
<tr class="setting">
|
254
|
-
<td>
|
255
|
-
<p class="name"><strong>Verbose output</strong></p>
|
256
|
-
<p class="description">Print verbose output.</p>
|
257
|
-
</td>
|
258
|
-
<td class="align-center">
|
259
|
-
<p><code class="flag">-V, --verbose</code></p>
|
260
|
-
</td>
|
261
|
-
</tr>
|
262
|
-
<tr class="setting">
|
263
|
-
<td>
|
264
|
-
<p class="name"><strong>Silence Output</strong></p>
|
265
|
-
<p class="description">Silence the normal output from Jekyll
|
266
|
-
during a build</p>
|
267
|
-
</td>
|
268
|
-
<td class="align-center">
|
269
|
-
<p><code class="flag">-q, --quiet</code></p>
|
270
|
-
</td>
|
271
|
-
</tr>
|
272
|
-
<tr class="setting">
|
273
|
-
<td>
|
274
|
-
<p class="name"><strong>Incremental build</strong></p>
|
275
|
-
<p class="description">
|
276
|
-
Enable the experimental incremental build feature. Incremental build only
|
277
|
-
re-builds posts and pages that have changed, resulting in significant performance
|
278
|
-
improvements for large sites, but may also break site generation in certain
|
279
|
-
cases.
|
280
|
-
</p>
|
281
|
-
</td>
|
282
|
-
<td class="align-center">
|
283
|
-
<p><code class="option">incremental: BOOL</code></p>
|
284
|
-
<p><code class="flag">-I, --incremental</code></p>
|
285
|
-
</td>
|
286
|
-
</tr>
|
287
|
-
</tbody>
|
288
|
-
</table>
|
289
|
-
</div>
|
290
|
-
|
291
|
-
|
292
|
-
### Serve Command Options
|
293
|
-
|
294
|
-
In addition to the options below, the `serve` sub-command can accept any of the options
|
295
|
-
for the `build` sub-command, which are then applied to the site build which occurs right
|
296
|
-
before your site is served.
|
297
|
-
|
298
|
-
<div class="mobile-side-scroller">
|
299
|
-
<table>
|
300
|
-
<thead>
|
301
|
-
<tr>
|
302
|
-
<th>Setting</th>
|
303
|
-
<th><span class="option">Options</span> and <span class="flag">Flags</span></th>
|
304
|
-
</tr>
|
305
|
-
</thead>
|
306
|
-
<tbody>
|
307
|
-
<tr class="setting">
|
308
|
-
<td>
|
309
|
-
<p class="name"><strong>Local Server Port</strong></p>
|
310
|
-
<p class="description">Listen on the given port.</p>
|
311
|
-
</td>
|
312
|
-
<td class="align-center">
|
313
|
-
<p><code class="option">port: PORT</code></p>
|
314
|
-
<p><code class="flag">--port PORT</code></p>
|
315
|
-
</td>
|
316
|
-
</tr>
|
317
|
-
<tr class="setting">
|
318
|
-
<td>
|
319
|
-
<p class="name"><strong>Local Server Hostname</strong></p>
|
320
|
-
<p class="description">Listen at the given hostname.</p>
|
321
|
-
</td>
|
322
|
-
<td class="align-center">
|
323
|
-
<p><code class="option">host: HOSTNAME</code></p>
|
324
|
-
<p><code class="flag">--host HOSTNAME</code></p>
|
325
|
-
</td>
|
326
|
-
</tr>
|
327
|
-
<tr class="setting">
|
328
|
-
<td>
|
329
|
-
<p class="name"><strong>Base URL</strong></p>
|
330
|
-
<p class="description">Serve the website from the given base URL</p>
|
331
|
-
</td>
|
332
|
-
<td class="align-center">
|
333
|
-
<p><code class="option">baseurl: URL</code></p>
|
334
|
-
<p><code class="flag">--baseurl URL</code></p>
|
335
|
-
</td>
|
336
|
-
</tr>
|
337
|
-
<tr class="setting">
|
338
|
-
<td>
|
339
|
-
<p class="name"><strong>Detach</strong></p>
|
340
|
-
<p class="description">Detach the server from the terminal</p>
|
341
|
-
</td>
|
342
|
-
<td class="align-center">
|
343
|
-
<p><code class="option">detach: BOOL</code></p>
|
344
|
-
<p><code class="flag">-B, --detach</code></p>
|
345
|
-
</td>
|
346
|
-
</tr>
|
347
|
-
<tr class="setting">
|
348
|
-
<td>
|
349
|
-
<p class="name"><strong>Skips the initial site build.</strong></p>
|
350
|
-
<p class="description">Skips the initial site build which occurs before the server is started.</p>
|
351
|
-
</td>
|
352
|
-
<td class="align-center">
|
353
|
-
<p><code class="flag">--skip-initial-build</code></p>
|
354
|
-
</td>
|
355
|
-
</tr>
|
356
|
-
<tr class="setting">
|
357
|
-
<td>
|
358
|
-
<p class="name"><strong>X.509 (SSL) Private Key</strong></p>
|
359
|
-
<p class="description">SSL Private Key.</p>
|
360
|
-
</td>
|
361
|
-
<td class="align-center">
|
362
|
-
<p><code class="flag">--ssl-key</code></p>
|
363
|
-
</td>
|
364
|
-
</tr>
|
365
|
-
<tr class="setting">
|
366
|
-
<td>
|
367
|
-
<p class="name"><strong>X.509 (SSL) Certificate</strong></p>
|
368
|
-
<p class="description">SSL Public certificate.</p>
|
369
|
-
</td>
|
370
|
-
<td class="align-center">
|
371
|
-
<p><code class="flag">--ssl-cert</code></p>
|
372
|
-
</td>
|
373
|
-
</tr>
|
374
|
-
</tbody>
|
375
|
-
</table>
|
376
|
-
</div>
|
377
|
-
|
378
|
-
<div class="note warning">
|
379
|
-
<h5>Do not use tabs in configuration files</h5>
|
380
|
-
<p>
|
381
|
-
This will either lead to parsing errors, or Jekyll will revert to the
|
382
|
-
default settings. Use spaces instead.
|
383
|
-
</p>
|
384
|
-
</div>
|
385
|
-
|
386
|
-
## Custom WEBRick Headers
|
387
|
-
|
388
|
-
You can provide custom headers for your site by adding them to `_config.yml`
|
389
|
-
|
390
|
-
{% highlight yaml %}
|
391
|
-
# File: _config.yml
|
392
|
-
webrick:
|
393
|
-
headers:
|
394
|
-
My-Header: My-Value
|
395
|
-
My-Other-Header: My-Other-Value
|
396
|
-
{% endhighlight %}
|
397
|
-
|
398
|
-
### Defaults
|
399
|
-
|
400
|
-
We only provide one default and that's a Content-Type header that disables
|
401
|
-
caching in development so that you don't have to fight with Chrome's aggressive
|
402
|
-
caching when you are in development mode.
|
403
|
-
|
404
|
-
## Specifying a Jekyll environment at build time
|
405
|
-
|
406
|
-
In the build (or serve) arguments, you can specify a Jekyll environment and value. The build will then apply this value in any conditional statements in your content.
|
407
|
-
|
408
|
-
For example, suppose you set this conditional statement in your code:
|
409
|
-
|
410
|
-
{% highlight liquid %}
|
411
|
-
{% raw %}
|
412
|
-
{% if jekyll.environment == "production" %}
|
413
|
-
{% include disqus.html %}
|
414
|
-
{% endif %}
|
415
|
-
{% endraw %}
|
416
|
-
{% endhighlight %}
|
417
|
-
|
418
|
-
When you build your Jekyll site, the content inside the `if` statement won't be run unless you also specify a `production` environment in the build command, like this:
|
419
|
-
|
420
|
-
{% highlight sh %}
|
421
|
-
JEKYLL_ENV=production jekyll build
|
422
|
-
{% endhighlight %}
|
423
|
-
|
424
|
-
Specifying an environment value allows you to make certain content available only within specific environments.
|
425
|
-
|
426
|
-
The default value for `JEKYLL_ENV` is `development`. Therefore if you omit `JEKYLL_ENV` from the build arguments, the default value will be `JEKYLL_ENV=development`. Any content inside `{% raw %}{% if jekyll.environment == "development" %}{% endraw %}` tags will automatically appear in the build.
|
427
|
-
|
428
|
-
Your environment values can be anything you want (not just `development` or `production`). Some elements you might want to hide in development environments include Disqus comment forms or Google Analytics. Conversely, you might want to expose an "Edit me in GitHub" button in a development environment but not include it in production environments.
|
429
|
-
|
430
|
-
By specifying the option in the build command, you avoid having to change values in your configuration files when moving from one environment to another.
|
431
|
-
|
432
|
-
## Front Matter defaults
|
433
|
-
|
434
|
-
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.
|
435
|
-
|
436
|
-
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.
|
437
|
-
|
438
|
-
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.
|
439
|
-
|
440
|
-
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.
|
441
|
-
|
442
|
-
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:
|
443
|
-
|
444
|
-
{% highlight yaml %}
|
445
|
-
defaults:
|
446
|
-
-
|
447
|
-
scope:
|
448
|
-
path: "" # an empty string here means all files in the project
|
449
|
-
values:
|
450
|
-
layout: "default"
|
451
|
-
{% endhighlight %}
|
452
|
-
|
453
|
-
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.
|
454
|
-
|
455
|
-
{% highlight yaml %}
|
456
|
-
defaults:
|
457
|
-
-
|
458
|
-
scope:
|
459
|
-
path: "" # an empty string here means all files in the project
|
460
|
-
type: "posts" # previously `post` in Jekyll 2.2.
|
461
|
-
values:
|
462
|
-
layout: "default"
|
463
|
-
{% endhighlight %}
|
464
|
-
|
465
|
-
Now, this will only set the layout for files where the type is `posts`.
|
466
|
-
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.
|
467
|
-
|
468
|
-
As mentioned earlier, you can set multiple scope/values pairs for `defaults`.
|
469
|
-
|
470
|
-
{% highlight yaml %}
|
471
|
-
defaults:
|
472
|
-
-
|
473
|
-
scope:
|
474
|
-
path: ""
|
475
|
-
type: "posts"
|
476
|
-
values:
|
477
|
-
layout: "my-site"
|
478
|
-
-
|
479
|
-
scope:
|
480
|
-
path: "projects"
|
481
|
-
type: "pages" # previously `page` in Jekyll 2.2.
|
482
|
-
values:
|
483
|
-
layout: "project" # overrides previous default layout
|
484
|
-
author: "Mr. Hyde"
|
485
|
-
{% endhighlight %}
|
486
|
-
|
487
|
-
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`.
|
488
|
-
|
489
|
-
{% highlight yaml %}
|
490
|
-
collections:
|
491
|
-
- my_collection:
|
492
|
-
output: true
|
493
|
-
|
494
|
-
defaults:
|
495
|
-
-
|
496
|
-
scope:
|
497
|
-
path: ""
|
498
|
-
type: "my_collection" # a collection in your site, in plural form
|
499
|
-
values:
|
500
|
-
layout: "default"
|
501
|
-
{% endhighlight %}
|
502
|
-
|
503
|
-
In this example, the `layout` is set to `default` inside the
|
504
|
-
[collection](../collections/) with the name `my_collection`.
|
505
|
-
|
506
|
-
### Precedence
|
507
|
-
|
508
|
-
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.
|
509
|
-
|
510
|
-
You can see that in the second to 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.
|
511
|
-
|
512
|
-
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:
|
513
|
-
|
514
|
-
{% highlight yaml %}
|
515
|
-
# In _config.yml
|
516
|
-
...
|
517
|
-
defaults:
|
518
|
-
-
|
519
|
-
scope:
|
520
|
-
path: "projects"
|
521
|
-
type: "pages"
|
522
|
-
values:
|
523
|
-
layout: "project"
|
524
|
-
author: "Mr. Hyde"
|
525
|
-
category: "project"
|
526
|
-
...
|
527
|
-
{% endhighlight %}
|
528
|
-
|
529
|
-
{% highlight yaml %}
|
530
|
-
# In projects/foo_project.md
|
531
|
-
---
|
532
|
-
author: "John Smith"
|
533
|
-
layout: "foobar"
|
534
|
-
---
|
535
|
-
The post text goes here...
|
536
|
-
{% endhighlight %}
|
537
|
-
|
538
|
-
The `projects/foo_project.md` would have the `layout` set to `foobar` instead
|
539
|
-
of `project` and the `author` set to `John Smith` instead of `Mr. Hyde` when
|
540
|
-
the site is built.
|
541
|
-
|
542
|
-
## Default Configuration
|
543
|
-
|
544
|
-
Jekyll runs with the following configuration options by default. Alternative
|
545
|
-
settings for these options can be explicitly specified in the configuration
|
546
|
-
file or on the command-line.
|
547
|
-
|
548
|
-
<div class="note warning">
|
549
|
-
<h5>There are two unsupported kramdown options</h5>
|
550
|
-
<p>
|
551
|
-
Please note that both <code>remove_block_html_tags</code> and
|
552
|
-
<code>remove_span_html_tags</code> are currently unsupported in Jekyll due
|
553
|
-
to the fact that they are not included within the kramdown HTML converter.
|
554
|
-
</p>
|
555
|
-
</div>
|
556
|
-
|
557
|
-
{% highlight yaml %}
|
558
|
-
# Where things are
|
559
|
-
source: .
|
560
|
-
destination: ./_site
|
561
|
-
plugins_dir: ./_plugins
|
562
|
-
layouts_dir: ./_layouts
|
563
|
-
data_dir: ./_data
|
564
|
-
includes_dir: ./_includes
|
565
|
-
collections: null
|
566
|
-
|
567
|
-
# Handling Reading
|
568
|
-
safe: false
|
569
|
-
include: [".htaccess"]
|
570
|
-
exclude: []
|
571
|
-
keep_files: [".git", ".svn"]
|
572
|
-
encoding: "utf-8"
|
573
|
-
markdown_ext: "markdown,mkdown,mkdn,mkd,md"
|
574
|
-
|
575
|
-
# Filtering Content
|
576
|
-
show_drafts: null
|
577
|
-
limit_posts: 0
|
578
|
-
future: false
|
579
|
-
unpublished: false
|
580
|
-
|
581
|
-
# Plugins
|
582
|
-
whitelist: []
|
583
|
-
gems: []
|
584
|
-
|
585
|
-
# Conversion
|
586
|
-
markdown: kramdown
|
587
|
-
highlighter: rouge
|
588
|
-
lsi: false
|
589
|
-
excerpt_separator: "\n\n"
|
590
|
-
incremental: false
|
591
|
-
|
592
|
-
# Serving
|
593
|
-
detach: false
|
594
|
-
port: 4000
|
595
|
-
host: 127.0.0.1
|
596
|
-
baseurl: "" # does not include hostname
|
597
|
-
|
598
|
-
# Outputting
|
599
|
-
permalink: date
|
600
|
-
paginate_path: /page:num
|
601
|
-
timezone: null
|
602
|
-
|
603
|
-
quiet: false
|
604
|
-
defaults: []
|
605
|
-
|
606
|
-
# Markdown Processors
|
607
|
-
rdiscount:
|
608
|
-
extensions: []
|
609
|
-
|
610
|
-
redcarpet:
|
611
|
-
extensions: []
|
612
|
-
|
613
|
-
kramdown:
|
614
|
-
auto_ids: true
|
615
|
-
footnote_nr: 1
|
616
|
-
entity_output: as_char
|
617
|
-
toc_levels: 1..6
|
618
|
-
smart_quotes: lsquo,rsquo,ldquo,rdquo
|
619
|
-
enable_coderay: false
|
620
|
-
|
621
|
-
coderay:
|
622
|
-
coderay_wrap: div
|
623
|
-
coderay_line_numbers: inline
|
624
|
-
coderay_line_number_start: 1
|
625
|
-
coderay_tab_width: 4
|
626
|
-
coderay_bold_every: 10
|
627
|
-
coderay_css: style
|
628
|
-
{% endhighlight %}
|
629
|
-
|
630
|
-
## Markdown Options
|
631
|
-
|
632
|
-
The various Markdown renderers supported by Jekyll sometimes have extra options
|
633
|
-
available.
|
634
|
-
|
635
|
-
### Redcarpet
|
636
|
-
|
637
|
-
Redcarpet can be configured by providing an `extensions` sub-setting, whose
|
638
|
-
value should be an array of strings. Each string should be the name of one of
|
639
|
-
the `Redcarpet::Markdown` class's extensions; if present in the array, it will
|
640
|
-
set the corresponding extension to `true`.
|
641
|
-
|
642
|
-
Jekyll handles two special Redcarpet extensions:
|
643
|
-
|
644
|
-
- `no_fenced_code_blocks` --- By default, Jekyll sets the `fenced_code_blocks`
|
645
|
-
extension (for delimiting code blocks with triple tildes or triple backticks)
|
646
|
-
to `true`, probably because GitHub's eager adoption of them is starting to make
|
647
|
-
them inescapable. Redcarpet's normal `fenced_code_blocks` extension is inert
|
648
|
-
when used with Jekyll; instead, you can use this inverted version of the
|
649
|
-
extension for disabling fenced code.
|
650
|
-
|
651
|
-
Note that you can also specify a language for highlighting after the first
|
652
|
-
delimiter:
|
653
|
-
|
654
|
-
```ruby
|
655
|
-
# ...ruby code
|
656
|
-
```
|
657
|
-
|
658
|
-
With both fenced code blocks and highlighter enabled, this will statically
|
659
|
-
highlight the code; without any syntax highlighter, it will add a
|
660
|
-
`class="LANGUAGE"` attribute to the `<code>` element, which can be used as a
|
661
|
-
hint by various JavaScript code highlighting libraries.
|
662
|
-
|
663
|
-
- `smart` --- This pseudo-extension turns on SmartyPants, which converts
|
664
|
-
straight quotes to curly quotes and runs of hyphens to em (`---`) and en (`--`) dashes.
|
665
|
-
|
666
|
-
All other extensions retain their usual names from Redcarpet, and no renderer
|
667
|
-
options aside from `smart` can be specified in Jekyll. [A list of available
|
668
|
-
extensions can be found in the Redcarpet README file.][redcarpet_extensions]
|
669
|
-
Make sure you're looking at the README for the right version of
|
670
|
-
Redcarpet: Jekyll currently uses v3.2.x. The most commonly used
|
671
|
-
extensions are:
|
672
|
-
|
673
|
-
- `tables`
|
674
|
-
- `no_intra_emphasis`
|
675
|
-
- `autolink`
|
676
|
-
|
677
|
-
[redcarpet_extensions]: https://github.com/vmg/redcarpet/blob/v3.2.2/README.markdown#and-its-like-really-simple-to-use
|
678
|
-
|
679
|
-
### Kramdown
|
680
|
-
|
681
|
-
In addition to the defaults mentioned above, you can also turn on recognition
|
682
|
-
of GitHub Flavored Markdown by passing an `input` option with a value of "GFM".
|
683
|
-
|
684
|
-
For example, in your `_config.yml`:
|
685
|
-
|
686
|
-
kramdown:
|
687
|
-
input: GFM
|
688
|
-
|
689
|
-
### Custom Markdown Processors
|
690
|
-
|
691
|
-
If you're interested in creating a custom markdown processor, you're in luck! Create a new class in the `Jekyll::Converters::Markdown` namespace:
|
692
|
-
|
693
|
-
{% highlight ruby %}
|
694
|
-
class Jekyll::Converters::Markdown::MyCustomProcessor
|
695
|
-
def initialize(config)
|
696
|
-
require 'funky_markdown'
|
697
|
-
@config = config
|
698
|
-
rescue LoadError
|
699
|
-
STDERR.puts 'You are missing a library required for Markdown. Please run:'
|
700
|
-
STDERR.puts ' $ [sudo] gem install funky_markdown'
|
701
|
-
raise FatalException.new("Missing dependency: funky_markdown")
|
702
|
-
end
|
703
|
-
|
704
|
-
def convert(content)
|
705
|
-
::FunkyMarkdown.new(content).convert
|
706
|
-
end
|
707
|
-
end
|
708
|
-
{% endhighlight %}
|
709
|
-
|
710
|
-
Once you've created your class and have it properly set up either as a plugin
|
711
|
-
in the `_plugins` folder or as a gem, specify it in your `_config.yml`:
|
712
|
-
|
713
|
-
{% highlight yaml %}
|
714
|
-
markdown: MyCustomProcessor
|
715
|
-
{% endhighlight %}
|
716
|
-
|
717
|
-
## Incremental Regeneration
|
718
|
-
<div class="note warning">
|
719
|
-
<h5>Incremental regeneration is still an experimental feature</h5>
|
720
|
-
<p>
|
721
|
-
While incremental regeneration will work for the most common cases, it will
|
722
|
-
not work correctly in every scenario. Please be extremely cautious when
|
723
|
-
using the feature, and report any problems not listed below by
|
724
|
-
<a href="https://github.com/jekyll/jekyll/issues/new">opening an issue on GitHub</a>.
|
725
|
-
</p>
|
726
|
-
</div>
|
727
|
-
|
728
|
-
Incremental regeneration helps shorten build times by only generating documents
|
729
|
-
and pages that were updated since the previous build. It does this by keeping
|
730
|
-
track of both file modification times and inter-document dependencies in the
|
731
|
-
`.jekyll-metadata` file.
|
732
|
-
|
733
|
-
Under the current implementation, incremental regeneration will only generate a
|
734
|
-
document or page if either it, or one of its dependencies, is modified. Currently,
|
735
|
-
the only types of dependencies tracked are includes (using the
|
736
|
-
{% raw %}`{% include %}`{% endraw %} tag) and layouts. This means that plain
|
737
|
-
references to other documents (for example, the common case of iterating over
|
738
|
-
`site.posts` in a post listings page) will not be detected as a dependency.
|
739
|
-
|
740
|
-
To remedy some of these shortfalls, putting `regenerate: true` in the front-matter
|
741
|
-
of a document will force Jekyll to regenerate it regardless of whether it has been
|
742
|
-
modified. Note that this will generate the specified document only; references
|
743
|
-
to other documents' contents will not work since they won't be re-rendered.
|
744
|
-
|
745
|
-
Incremental regeneration can be enabled via the `--incremental` flag (`-I` for
|
746
|
-
short) from the command-line or by setting `incremental: true` in your
|
747
|
-
configuration file.
|