jekyll-docs 3.8.5 → 3.9.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/site/404.html +5 -4
- data/site/docs/assets/index.html +22 -21
- data/site/docs/code_of_conduct/index.html +8 -7
- data/site/docs/collections/index.html +44 -43
- data/site/docs/conduct/index.html +8 -7
- data/site/docs/configuration/index.html +68 -67
- data/site/docs/continuous-integration/buddyworks/index.html +10 -9
- data/site/docs/continuous-integration/circleci/index.html +13 -12
- data/site/docs/continuous-integration/index.html +8 -7
- data/site/docs/continuous-integration/travis-ci/index.html +32 -31
- data/site/docs/contributing/index.html +34 -33
- data/site/docs/datafiles/index.html +24 -23
- data/site/docs/deployment-methods/index.html +30 -29
- data/site/docs/drafts/index.html +11 -10
- data/site/docs/extras/index.html +9 -8
- data/site/docs/frontmatter/index.html +8 -7
- data/site/docs/github-pages/index.html +19 -18
- data/site/docs/history/index.html +674 -645
- data/site/docs/home/index.html +8 -7
- data/site/docs/includes/index.html +44 -43
- data/site/docs/installation/index.html +16 -15
- data/site/docs/maintaining/affinity-team-captain/index.html +11 -10
- data/site/docs/maintaining/avoiding-burnout/index.html +8 -7
- data/site/docs/maintaining/becoming-a-maintainer/index.html +9 -8
- data/site/docs/maintaining/index.html +8 -7
- data/site/docs/maintaining/merging-a-pull-request/index.html +23 -22
- data/site/docs/maintaining/releasing-a-new-version/index.html +19 -18
- data/site/docs/maintaining/reviewing-a-pull-request/index.html +10 -9
- data/site/docs/maintaining/special-labels/index.html +14 -13
- data/site/docs/maintaining/triaging-an-issue/index.html +12 -11
- data/site/docs/migrations/index.html +9 -8
- data/site/docs/pages/index.html +12 -11
- data/site/docs/pagination/index.html +25 -24
- data/site/docs/permalinks/index.html +33 -32
- data/site/docs/plugins/index.html +57 -56
- data/site/docs/posts/index.html +37 -36
- data/site/docs/quickstart/index.html +18 -17
- data/site/docs/resources/index.html +9 -8
- data/site/docs/sites/index.html +8 -7
- data/site/docs/static-files/index.html +14 -13
- data/site/docs/structure/index.html +8 -7
- data/site/docs/support/index.html +9 -8
- data/site/docs/templates/index.html +44 -43
- data/site/docs/themes/index.html +63 -62
- data/site/docs/troubleshooting/index.html +48 -47
- data/site/docs/upgrading/0-to-2/index.html +51 -50
- data/site/docs/upgrading/2-to-3/index.html +35 -34
- data/site/docs/upgrading/index.html +11 -10
- data/site/docs/usage/index.html +15 -14
- data/site/docs/variables/index.html +8 -7
- data/site/docs/windows/index.html +29 -28
- data/site/feed.xml +45 -41
- data/site/help/index.html +7 -6
- data/site/index.html +7 -6
- data/site/jekyllconf/index.html +9 -8
- data/site/latest_version.txt +1 -1
- data/site/news/2013/05/05/jekyll-1-0-0-released/index.html +16 -10
- data/site/news/2013/05/08/jekyll-1-0-1-released/index.html +18 -12
- data/site/news/2013/05/12/jekyll-1-0-2-released/index.html +19 -13
- data/site/news/2013/06/07/jekyll-1-0-3-released/index.html +20 -14
- data/site/news/2013/07/14/jekyll-1-1-0-released/index.html +19 -13
- data/site/news/2013/07/24/jekyll-1-1-1-released/index.html +16 -10
- data/site/news/2013/07/25/jekyll-1-0-4-released/index.html +18 -12
- data/site/news/2013/07/25/jekyll-1-1-2-released/index.html +18 -12
- data/site/news/2013/09/06/jekyll-1-2-0-released/index.html +21 -15
- data/site/news/2013/09/14/jekyll-1-2-1-released/index.html +19 -13
- data/site/news/2013/10/28/jekyll-1-3-0-rc1-released/index.html +16 -10
- data/site/news/2013/11/04/jekyll-1-3-0-released/index.html +25 -19
- data/site/news/2013/11/26/jekyll-1-3-1-released/index.html +17 -11
- data/site/news/2013/12/07/jekyll-1-4-0-released/index.html +17 -11
- data/site/news/2013/12/09/jekyll-1-4-1-released/index.html +16 -10
- data/site/news/2013/12/16/jekyll-1-4-2-released/index.html +18 -12
- data/site/news/2014/01/13/jekyll-1-4-3-released/index.html +17 -11
- data/site/news/2014/03/24/jekyll-1-5-0-released/index.html +17 -11
- data/site/news/2014/03/27/jekyll-1-5-1-released/index.html +17 -11
- data/site/news/2014/05/06/jekyll-turns-2-0-0/index.html +20 -14
- data/site/news/2014/05/08/jekyll-2-0-3-released/index.html +16 -10
- data/site/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/index.html +16 -10
- data/site/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/index.html +21 -15
- data/site/news/2014/07/01/jekyll-2-1-1-released/index.html +18 -12
- data/site/news/2014/07/29/jekyll-2-2-0-released/index.html +17 -11
- data/site/news/2014/08/10/jekyll-2-3-0-released/index.html +24 -18
- data/site/news/2014/09/09/jekyll-2-4-0-released/index.html +23 -17
- data/site/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/index.html +22 -16
- data/site/news/2014/11/09/jekyll-2-5-1-released/index.html +16 -10
- data/site/news/2014/11/12/jekyll-2-5-2-released/index.html +18 -12
- data/site/news/2014/12/17/alfredxing-welcome-to-jekyll-core/index.html +16 -10
- data/site/news/2014/12/22/jekyll-2-5-3-released/index.html +16 -10
- data/site/news/2015/01/20/jekyll-meet-and-greet/index.html +16 -10
- data/site/news/2015/01/24/jekyll-3-0-0-beta1-released/index.html +16 -10
- data/site/news/2015/02/26/introducing-jekyll-talk/index.html +16 -10
- data/site/news/2015/10/26/jekyll-3-0-released/index.html +21 -15
- data/site/news/2015/11/17/jekyll-3-0-1-released/index.html +20 -14
- data/site/news/2016/01/20/jekyll-3-0-2-released/index.html +18 -12
- data/site/news/2016/01/24/jekyll-3-1-0-released/index.html +21 -15
- data/site/news/2016/01/28/jekyll-3-1-1-released/index.html +21 -15
- data/site/news/2016/02/08/jekyll-3-0-3-released/index.html +17 -11
- data/site/news/2016/02/19/jekyll-3-1-2-released/index.html +18 -12
- data/site/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/index.html +16 -10
- data/site/news/2016/04/19/jekyll-3-0-4-released/index.html +17 -11
- data/site/news/2016/04/19/jekyll-3-1-3-released/index.html +17 -11
- data/site/news/2016/04/26/jekyll-3-0-5-released/index.html +16 -10
- data/site/news/2016/05/18/jekyll-3-1-4-released/index.html +22 -16
- data/site/news/2016/05/18/jekyll-3-1-5-released/index.html +17 -11
- data/site/news/2016/05/19/jekyll-3-1-6-released/index.html +17 -11
- data/site/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/index.html +16 -10
- data/site/news/2016/07/26/jekyll-3-2-0-released/index.html +20 -14
- data/site/news/2016/08/02/jekyll-3-2-1-released/index.html +17 -11
- data/site/news/2016/08/24/jekyll-admin-initial-release/index.html +16 -10
- data/site/news/2016/10/06/jekyll-3-3-is-here/index.html +42 -36
- data/site/news/2016/11/14/jekyll-3-3-1-released/index.html +17 -11
- data/site/news/2017/01/18/jekyll-3-4-0-released/index.html +18 -12
- data/site/news/2017/03/02/jekyll-3-4-1-released/index.html +17 -11
- data/site/news/2017/03/09/jekyll-3-4-2-released/index.html +21 -15
- data/site/news/2017/03/21/jekyll-3-4-3-released/index.html +26 -20
- data/site/news/2017/06/15/jekyll-3-5-0-released/index.html +25 -19
- data/site/news/2017/07/17/jekyll-3-5-1-released/index.html +18 -12
- data/site/news/2017/08/12/jekyll-3-5-2-released/index.html +21 -15
- data/site/news/2017/09/21/jekyll-3-6-0-released/index.html +17 -11
- data/site/news/2017/10/19/diversity-open-source/index.html +18 -12
- data/site/news/2017/10/21/jekyll-3-6-2-released/index.html +18 -12
- data/site/news/2018/01/02/jekyll-3-7-0-released/index.html +21 -15
- data/site/news/2018/01/25/jekyll-3-7-2-released/index.html +26 -20
- data/site/news/2018/02/19/meet-jekyll-s-new-lead-developer/index.html +16 -10
- data/site/news/2018/02/24/jekyll-3-7-3-released/index.html +22 -16
- data/site/news/2018/05/01/jekyll-3-8-1-released/index.html +19 -13
- data/site/news/2018/05/19/jekyll-3-8-2-released/index.html +17 -11
- data/site/news/2018/06/05/jekyll-3-8-3-released/index.html +19 -13
- data/site/news/2019/07/02/jekyll-3-8-6-released/index.html +623 -0
- data/site/news/index.html +263 -218
- data/site/news/releases/index.html +261 -216
- data/site/philosophy.html +1 -1
- data/site/sitemap.xml +61 -57
- data/site/team/index.html +7 -6
- data/site/tutorials/convert-site-to-jekyll/index.html +97 -96
- data/site/tutorials/custom-404-page/index.html +16 -15
- data/site/tutorials/home/index.html +10 -9
- data/site/tutorials/navigation/index.html +102 -101
- data/site/tutorials/orderofinterpretation/index.html +32 -31
- data/site/tutorials/using-jekyll-with-bundler/index.html +19 -18
- data/site/tutorials/video-walkthroughs/index.html +8 -7
- metadata +10 -24
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
<head>
|
|
4
4
|
<meta charset="UTF-8">
|
|
5
5
|
<meta name="viewport" content="width=device-width,initial-scale=1">
|
|
6
|
-
<meta name="generator" content="Jekyll v3.
|
|
6
|
+
<meta name="generator" content="Jekyll v3.9.0">
|
|
7
7
|
<link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
|
|
8
8
|
<link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
|
|
9
9
|
<link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
|
|
@@ -11,9 +11,9 @@
|
|
|
11
11
|
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
|
|
12
12
|
<link rel="stylesheet" href="/css/screen.css">
|
|
13
13
|
<link rel="icon" type="image/x-icon" href="/favicon.ico">
|
|
14
|
-
<!-- Begin Jekyll SEO tag v2.
|
|
14
|
+
<!-- Begin Jekyll SEO tag v2.6.1 -->
|
|
15
15
|
<title>Data Files | Jekyll • Simple, blog-aware, static sites</title>
|
|
16
|
-
<meta name="generator" content="Jekyll v3.
|
|
16
|
+
<meta name="generator" content="Jekyll v3.9.0" />
|
|
17
17
|
<meta property="og:title" content="Data Files" />
|
|
18
18
|
<meta property="og:locale" content="en_US" />
|
|
19
19
|
<meta name="description" content="In addition to the built-in variables available from Jekyll, you can specify your own custom data that can be accessed via the Liquid templating system." />
|
|
@@ -22,12 +22,13 @@
|
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/datafiles/" />
|
|
23
23
|
<meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
|
|
24
24
|
<meta property="og:type" content="article" />
|
|
25
|
-
<meta property="article:published_time" content="
|
|
25
|
+
<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
|
|
26
26
|
<meta name="twitter:card" content="summary" />
|
|
27
|
+
<meta property="twitter:title" content="Data Files" />
|
|
27
28
|
<meta name="twitter:site" content="@jekyllrb" />
|
|
28
29
|
<meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
|
|
29
30
|
<script type="application/ld+json">
|
|
30
|
-
{"headline":"Data Files","dateModified":"
|
|
31
|
+
{"url":"https://jekyllrb.com/docs/datafiles/","headline":"Data Files","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"In addition to the built-in variables available from Jekyll, you can specify your own custom data that can be accessed via the Liquid templating system.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/datafiles/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
|
|
31
32
|
<!-- End Jekyll SEO tag -->
|
|
32
33
|
|
|
33
34
|
<!--[if lt IE 9]>
|
|
@@ -72,7 +73,7 @@
|
|
|
72
73
|
<div class="meta hide-on-mobiles">
|
|
73
74
|
<ul>
|
|
74
75
|
<li>
|
|
75
|
-
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.
|
|
76
|
+
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
|
|
76
77
|
</li>
|
|
77
78
|
<li>
|
|
78
79
|
<a href="https://github.com/jekyll/jekyll">GitHub</a>
|
|
@@ -299,28 +300,28 @@ you can specify your own custom data that can be accessed via the <a href="https
|
|
|
299
300
|
templating system</a>.</p>
|
|
300
301
|
|
|
301
302
|
<p>Jekyll supports loading data from <a href="http://yaml.org/">YAML</a>, <a href="http://www.json.org/">JSON</a>,
|
|
302
|
-
and <a href="https://en.wikipedia.org/wiki/Comma-separated_values">CSV</a> files located in the <code class="highlighter-rouge">_data</code> directory.
|
|
303
|
+
and <a href="https://en.wikipedia.org/wiki/Comma-separated_values">CSV</a> files located in the <code class="language-plaintext highlighter-rouge">_data</code> directory.
|
|
303
304
|
Note that CSV files <em>must</em> contain a header row.</p>
|
|
304
305
|
|
|
305
306
|
<p>This powerful feature allows you to avoid repetition in your templates and to
|
|
306
|
-
set site specific options without changing <code class="highlighter-rouge">_config.yml</code>.</p>
|
|
307
|
+
set site specific options without changing <code class="language-plaintext highlighter-rouge">_config.yml</code>.</p>
|
|
307
308
|
|
|
308
309
|
<p>Plugins/themes can also leverage Data Files to set configuration variables.</p>
|
|
309
310
|
|
|
310
311
|
<h2 id="the-data-folder">The Data Folder</h2>
|
|
311
312
|
|
|
312
|
-
<p>As explained on the <a href="../structure/">directory structure</a> page, the <code class="highlighter-rouge">_data</code>
|
|
313
|
+
<p>As explained on the <a href="../structure/">directory structure</a> page, the <code class="language-plaintext highlighter-rouge">_data</code>
|
|
313
314
|
folder is where you can store additional data for Jekyll to use when generating
|
|
314
315
|
your site. These files must be YAML, JSON, or CSV files (using either
|
|
315
|
-
the <code class="highlighter-rouge">.yml</code>, <code class="highlighter-rouge">.yaml</code>, <code class="highlighter-rouge">.json</code> or <code class="highlighter-rouge">.csv</code> extension), and they will be
|
|
316
|
-
accessible via <code class="highlighter-rouge">site.data</code>.</p>
|
|
316
|
+
the <code class="language-plaintext highlighter-rouge">.yml</code>, <code class="language-plaintext highlighter-rouge">.yaml</code>, <code class="language-plaintext highlighter-rouge">.json</code> or <code class="language-plaintext highlighter-rouge">.csv</code> extension), and they will be
|
|
317
|
+
accessible via <code class="language-plaintext highlighter-rouge">site.data</code>.</p>
|
|
317
318
|
|
|
318
319
|
<h2 id="example-list-of-members">Example: List of members</h2>
|
|
319
320
|
|
|
320
321
|
<p>Here is a basic example of using Data Files to avoid copy-pasting large chunks
|
|
321
322
|
of code in your Jekyll templates:</p>
|
|
322
323
|
|
|
323
|
-
<p>In <code class="highlighter-rouge">_data/members.yml</code>:</p>
|
|
324
|
+
<p>In <code class="language-plaintext highlighter-rouge">_data/members.yml</code>:</p>
|
|
324
325
|
|
|
325
326
|
<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">Eric Mill</span>
|
|
326
327
|
<span class="na">github</span><span class="pi">:</span> <span class="s">konklone</span>
|
|
@@ -332,7 +333,7 @@ of code in your Jekyll templates:</p>
|
|
|
332
333
|
<span class="na">github</span><span class="pi">:</span> <span class="s">liufengyun</span>
|
|
333
334
|
</code></pre></div></div>
|
|
334
335
|
|
|
335
|
-
<p>Or <code class="highlighter-rouge">_data/members.csv</code>:</p>
|
|
336
|
+
<p>Or <code class="language-plaintext highlighter-rouge">_data/members.csv</code>:</p>
|
|
336
337
|
|
|
337
338
|
<div class="language-text highlighter-rouge"><div class="highlight"><pre class="highlight"><code>name,github
|
|
338
339
|
Eric Mill,konklone
|
|
@@ -340,13 +341,13 @@ Parker Moore,parkr
|
|
|
340
341
|
Liu Fengyun,liufengyun
|
|
341
342
|
</code></pre></div></div>
|
|
342
343
|
|
|
343
|
-
<p>This data can be accessed via <code class="highlighter-rouge">site.data.members</code> (notice that the filename
|
|
344
|
+
<p>This data can be accessed via <code class="language-plaintext highlighter-rouge">site.data.members</code> (notice that the filename
|
|
344
345
|
determines the variable name).</p>
|
|
345
346
|
|
|
346
347
|
<p>You can now render the list of members in a template:</p>
|
|
347
348
|
|
|
348
349
|
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><ul>
|
|
349
|
-
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span>member
|
|
350
|
+
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span><span class="nv">member</span><span class="w"> </span><span class="nt">in</span><span class="w"> </span><span class="nv">site.data.members</span><span class="w"> </span><span class="p">%}</span>
|
|
350
351
|
<li>
|
|
351
352
|
<a href="https://github.com/<span class="p">{{</span><span class="w"> </span><span class="nv">member</span><span class="p">.</span><span class="nv">github</span><span class="w"> </span><span class="p">}}</span>">
|
|
352
353
|
<span class="p">{{</span><span class="w"> </span><span class="nv">member</span><span class="p">.</span><span class="nv">name</span><span class="w"> </span><span class="p">}}</span>
|
|
@@ -360,12 +361,12 @@ determines the variable name).</p>
|
|
|
360
361
|
|
|
361
362
|
<h2 id="example-organizations">Example: Organizations</h2>
|
|
362
363
|
|
|
363
|
-
<p>Data files can also be placed in sub-folders of the <code class="highlighter-rouge">_data</code> folder. Each folder
|
|
364
|
+
<p>Data files can also be placed in sub-folders of the <code class="language-plaintext highlighter-rouge">_data</code> folder. Each folder
|
|
364
365
|
level will be added to a variable’s namespace. The example below shows how
|
|
365
|
-
GitHub organizations could be defined separately in a file under the <code class="highlighter-rouge">orgs</code>
|
|
366
|
+
GitHub organizations could be defined separately in a file under the <code class="language-plaintext highlighter-rouge">orgs</code>
|
|
366
367
|
folder:</p>
|
|
367
368
|
|
|
368
|
-
<p>In <code class="highlighter-rouge">_data/orgs/jekyll.yml</code>:</p>
|
|
369
|
+
<p>In <code class="language-plaintext highlighter-rouge">_data/orgs/jekyll.yml</code>:</p>
|
|
369
370
|
|
|
370
371
|
<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">username</span><span class="pi">:</span> <span class="s">jekyll</span>
|
|
371
372
|
<span class="na">name</span><span class="pi">:</span> <span class="s">Jekyll</span>
|
|
@@ -377,7 +378,7 @@ folder:</p>
|
|
|
377
378
|
<span class="na">github</span><span class="pi">:</span> <span class="s">parkr</span>
|
|
378
379
|
</code></pre></div></div>
|
|
379
380
|
|
|
380
|
-
<p>In <code class="highlighter-rouge">_data/orgs/doeorg.yml</code>:</p>
|
|
381
|
+
<p>In <code class="language-plaintext highlighter-rouge">_data/orgs/doeorg.yml</code>:</p>
|
|
381
382
|
|
|
382
383
|
<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">username</span><span class="pi">:</span> <span class="s">doeorg</span>
|
|
383
384
|
<span class="na">name</span><span class="pi">:</span> <span class="s">Doe Org</span>
|
|
@@ -386,11 +387,11 @@ folder:</p>
|
|
|
386
387
|
<span class="na">github</span><span class="pi">:</span> <span class="s">jdoe</span>
|
|
387
388
|
</code></pre></div></div>
|
|
388
389
|
|
|
389
|
-
<p>The organizations can then be accessed via <code class="highlighter-rouge">site.data.orgs</code>, followed by the
|
|
390
|
+
<p>The organizations can then be accessed via <code class="language-plaintext highlighter-rouge">site.data.orgs</code>, followed by the
|
|
390
391
|
file name:</p>
|
|
391
392
|
|
|
392
393
|
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><ul>
|
|
393
|
-
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span>org_hash
|
|
394
|
+
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span><span class="nv">org_hash</span><span class="w"> </span><span class="nt">in</span><span class="w"> </span><span class="nv">site.data.orgs</span><span class="w"> </span><span class="p">%}</span>
|
|
394
395
|
<span class="p">{%</span><span class="w"> </span><span class="nt">assign</span><span class="w"> </span><span class="nv">org</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">org_hash</span><span class="p">[</span><span class="mi">1</span><span class="p">]</span><span class="w"> </span><span class="p">%}</span>
|
|
395
396
|
<li>
|
|
396
397
|
<a href="https://github.com/<span class="p">{{</span><span class="w"> </span><span class="nv">org</span><span class="p">.</span><span class="nv">username</span><span class="w"> </span><span class="p">}}</span>">
|
|
@@ -406,7 +407,7 @@ file name:</p>
|
|
|
406
407
|
|
|
407
408
|
<p>Pages and posts can also access a specific data item. The example below shows how to access a specific item:</p>
|
|
408
409
|
|
|
409
|
-
<p><code class="highlighter-rouge">_data/people.yml</code>:</p>
|
|
410
|
+
<p><code class="language-plaintext highlighter-rouge">_data/people.yml</code>:</p>
|
|
410
411
|
|
|
411
412
|
<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">dave</span><span class="pi">:</span>
|
|
412
413
|
<span class="na">name</span><span class="pi">:</span> <span class="s">David Smith</span>
|
|
@@ -697,7 +698,7 @@ author: dave
|
|
|
697
698
|
<footer>
|
|
698
699
|
<div class="grid">
|
|
699
700
|
<div class="unit one-third center-on-mobiles">
|
|
700
|
-
<p>The contents of this website are <br />©
|
|
701
|
+
<p>The contents of this website are <br />© 2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
|
|
701
702
|
</div>
|
|
702
703
|
<div class="unit two-thirds align-right center-on-mobiles">
|
|
703
704
|
<p>
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
<head>
|
|
4
4
|
<meta charset="UTF-8">
|
|
5
5
|
<meta name="viewport" content="width=device-width,initial-scale=1">
|
|
6
|
-
<meta name="generator" content="Jekyll v3.
|
|
6
|
+
<meta name="generator" content="Jekyll v3.9.0">
|
|
7
7
|
<link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
|
|
8
8
|
<link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
|
|
9
9
|
<link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
|
|
@@ -11,9 +11,9 @@
|
|
|
11
11
|
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
|
|
12
12
|
<link rel="stylesheet" href="/css/screen.css">
|
|
13
13
|
<link rel="icon" type="image/x-icon" href="/favicon.ico">
|
|
14
|
-
<!-- Begin Jekyll SEO tag v2.
|
|
14
|
+
<!-- Begin Jekyll SEO tag v2.6.1 -->
|
|
15
15
|
<title>Deployment methods | Jekyll • Simple, blog-aware, static sites</title>
|
|
16
|
-
<meta name="generator" content="Jekyll v3.
|
|
16
|
+
<meta name="generator" content="Jekyll v3.9.0" />
|
|
17
17
|
<meta property="og:title" content="Deployment methods" />
|
|
18
18
|
<meta property="og:locale" content="en_US" />
|
|
19
19
|
<meta name="description" content="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." />
|
|
@@ -22,12 +22,13 @@
|
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/deployment-methods/" />
|
|
23
23
|
<meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
|
|
24
24
|
<meta property="og:type" content="article" />
|
|
25
|
-
<meta property="article:published_time" content="
|
|
25
|
+
<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
|
|
26
26
|
<meta name="twitter:card" content="summary" />
|
|
27
|
+
<meta property="twitter:title" content="Deployment methods" />
|
|
27
28
|
<meta name="twitter:site" content="@jekyllrb" />
|
|
28
29
|
<meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
|
|
29
30
|
<script type="application/ld+json">
|
|
30
|
-
{"headline":"Deployment methods","dateModified":"
|
|
31
|
+
{"url":"https://jekyllrb.com/docs/deployment-methods/","headline":"Deployment methods","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"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.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/deployment-methods/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
|
|
31
32
|
<!-- End Jekyll SEO tag -->
|
|
32
33
|
|
|
33
34
|
<!--[if lt IE 9]>
|
|
@@ -72,7 +73,7 @@
|
|
|
72
73
|
<div class="meta hide-on-mobiles">
|
|
73
74
|
<ul>
|
|
74
75
|
<li>
|
|
75
|
-
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.
|
|
76
|
+
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
|
|
76
77
|
</li>
|
|
77
78
|
<li>
|
|
78
79
|
<a href="https://github.com/jekyll/jekyll">GitHub</a>
|
|
@@ -311,7 +312,7 @@
|
|
|
311
312
|
|
|
312
313
|
<p><a href="https://www.aerobatic.com">Aerobatic</a> has custom domains, global CDN distribution, basic auth, CORS proxying, and a growing list of plugins all included.</p>
|
|
313
314
|
|
|
314
|
-
<p>Automating the deployment of a Jekyll site is simple. See their <a href="https://www.aerobatic.com/docs/static-site-generators/#jekyll">Jekyll docs</a> for more details. Your built <code class="highlighter-rouge">_site</code> folder is deployed to their highly-available, globally distributed hosting service.</p>
|
|
315
|
+
<p>Automating the deployment of a Jekyll site is simple. See their <a href="https://www.aerobatic.com/docs/static-site-generators/#jekyll">Jekyll docs</a> for more details. Your built <code class="language-plaintext highlighter-rouge">_site</code> folder is deployed to their highly-available, globally distributed hosting service.</p>
|
|
315
316
|
|
|
316
317
|
<h2 id="kickster">Kickster</h2>
|
|
317
318
|
|
|
@@ -323,11 +324,11 @@
|
|
|
323
324
|
|
|
324
325
|
<h2 id="web-hosting-providers-ftp">Web hosting providers (FTP)</h2>
|
|
325
326
|
|
|
326
|
-
<p>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 <code class="highlighter-rouge">jekyll build</code> command and copy the contents of the generated <code class="highlighter-rouge">_site</code> folder to the root folder of your hosting account. This is most likely to be the <code class="highlighter-rouge">httpdocs</code> or <code class="highlighter-rouge">public_html</code> folder on most hosting providers.</p>
|
|
327
|
+
<p>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 <code class="language-plaintext highlighter-rouge">jekyll build</code> command and copy the contents of the generated <code class="language-plaintext highlighter-rouge">_site</code> folder to the root folder of your hosting account. This is most likely to be the <code class="language-plaintext highlighter-rouge">httpdocs</code> or <code class="language-plaintext highlighter-rouge">public_html</code> folder on most hosting providers.</p>
|
|
327
328
|
|
|
328
329
|
<h2 id="self-managed-web-server">Self-managed web server</h2>
|
|
329
330
|
|
|
330
|
-
<p>If you have direct access to the deployment web server, the process is essentially the same, except you might have other methods available to you (such as <code class="highlighter-rouge">scp</code>, or even direct filesystem access) for transferring the files. Just remember to make sure the contents of the generated <code class="highlighter-rouge">_site</code> folder get placed in the appropriate web root directory for your web server.</p>
|
|
331
|
+
<p>If you have direct access to the deployment web server, the process is essentially the same, except you might have other methods available to you (such as <code class="language-plaintext highlighter-rouge">scp</code>, or even direct filesystem access) for transferring the files. Just remember to make sure the contents of the generated <code class="language-plaintext highlighter-rouge">_site</code> folder get placed in the appropriate web root directory for your web server.</p>
|
|
331
332
|
|
|
332
333
|
<h2 id="automated-methods">Automated methods</h2>
|
|
333
334
|
|
|
@@ -343,7 +344,7 @@ this</a>.</p>
|
|
|
343
344
|
|
|
344
345
|
<h3 id="git-post-receive-hook">Git post-receive hook</h3>
|
|
345
346
|
|
|
346
|
-
<p>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 <code class="highlighter-rouge">authorized_keys</code> file. With that in place, setting up the post-receive hook is done as follows:</p>
|
|
347
|
+
<p>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 <code class="language-plaintext highlighter-rouge">authorized_keys</code> file. With that in place, setting up the post-receive hook is done as follows:</p>
|
|
347
348
|
|
|
348
349
|
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>laptop<span class="nv">$ </span>ssh deployer@example.com
|
|
349
350
|
server<span class="nv">$ </span><span class="nb">mkdir </span>myrepo.git
|
|
@@ -375,7 +376,7 @@ deploy using this hook:</p>
|
|
|
375
376
|
</code></pre></div></div>
|
|
376
377
|
|
|
377
378
|
<p>Deploying is now as easy as telling nginx or Apache to look at
|
|
378
|
-
<code class="highlighter-rouge">/var/www/myrepo</code> and running the following:</p>
|
|
379
|
+
<code class="language-plaintext highlighter-rouge">/var/www/myrepo</code> and running the following:</p>
|
|
379
380
|
|
|
380
381
|
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>laptops<span class="nv">$ </span>git push deploy master
|
|
381
382
|
</code></pre></div></div>
|
|
@@ -391,14 +392,14 @@ deploy using this hook:</p>
|
|
|
391
392
|
|
|
392
393
|
<h3 id="scp">scp</h3>
|
|
393
394
|
|
|
394
|
-
<p>Once you’ve generated the <code class="highlighter-rouge">_site</code> directory, you can easily scp its content using a
|
|
395
|
-
<code class="highlighter-rouge">tasks/deploy</code> shell script similar to <a href="https://github.com/henrik/henrik.nyh.se/blob/master/script/deploy">this deploy script</a>. You’d obviously
|
|
395
|
+
<p>Once you’ve generated the <code class="language-plaintext highlighter-rouge">_site</code> directory, you can easily scp its content using a
|
|
396
|
+
<code class="language-plaintext highlighter-rouge">tasks/deploy</code> shell script similar to <a href="https://github.com/henrik/henrik.nyh.se/blob/master/script/deploy">this deploy script</a>. You’d obviously
|
|
396
397
|
need to change the values to reflect your site’s details. There is even <a href="https://gist.github.com/henrik/214959">a
|
|
397
398
|
matching TextMate command</a> that will help you run this script.</p>
|
|
398
399
|
|
|
399
400
|
<h3 id="rsync">rsync</h3>
|
|
400
401
|
|
|
401
|
-
<p>Once you’ve generated the <code class="highlighter-rouge">_site</code> directory, you can easily rsync its content using a <code class="highlighter-rouge">tasks/deploy</code> shell script similar to <a href="https://github.com/vitalyrepin/vrepinblog/blob/master/transfer.sh">this deploy script here</a>. You’d obviously need to change the values to reflect your site’s details.</p>
|
|
402
|
+
<p>Once you’ve generated the <code class="language-plaintext highlighter-rouge">_site</code> directory, you can easily rsync its content using a <code class="language-plaintext highlighter-rouge">tasks/deploy</code> shell script similar to <a href="https://github.com/vitalyrepin/vrepinblog/blob/master/transfer.sh">this deploy script here</a>. You’d obviously need to change the values to reflect your site’s details.</p>
|
|
402
403
|
|
|
403
404
|
<p>Certificate-based authorization is another way to simplify the publishing
|
|
404
405
|
process. It makes sense to restrict rsync access only to the directory which it is supposed to sync. This can be done using rrsync.</p>
|
|
@@ -409,8 +410,8 @@ process. It makes sense to restrict rsync access only to the directory which it
|
|
|
409
410
|
|
|
410
411
|
<ul>
|
|
411
412
|
<li><a href="https://ftp.samba.org/pub/unpacked/rsync/support/rrsync">Download rrsync</a></li>
|
|
412
|
-
<li>Place it in the <code class="highlighter-rouge">bin</code> subdirectory of your home folder (<code class="highlighter-rouge">~/bin</code>)</li>
|
|
413
|
-
<li>Make it executable (<code class="highlighter-rouge">chmod +x</code>)</li>
|
|
413
|
+
<li>Place it in the <code class="language-plaintext highlighter-rouge">bin</code> subdirectory of your home folder (<code class="language-plaintext highlighter-rouge">~/bin</code>)</li>
|
|
414
|
+
<li>Make it executable (<code class="language-plaintext highlighter-rouge">chmod +x</code>)</li>
|
|
414
415
|
</ul>
|
|
415
416
|
|
|
416
417
|
<h4 id="step-2-set-up-certificate-based-ssh-access-server-side">Step 2: Set up certificate-based SSH access (server side)</h4>
|
|
@@ -418,17 +419,17 @@ process. It makes sense to restrict rsync access only to the directory which it
|
|
|
418
419
|
<p>This <a href="https://wiki.gentoo.org/wiki/SSH#Passwordless_Authentication">process</a> is
|
|
419
420
|
described in several places online. What is different from the typical approach
|
|
420
421
|
is to put the restriction to certificate-based authorization in
|
|
421
|
-
<code class="highlighter-rouge">~/.ssh/authorized_keys</code>. Then, launch <code class="highlighter-rouge">rrsync</code> and supply
|
|
422
|
+
<code class="language-plaintext highlighter-rouge">~/.ssh/authorized_keys</code>. Then, launch <code class="language-plaintext highlighter-rouge">rrsync</code> and supply
|
|
422
423
|
it with the folder it shall have read-write access to:</p>
|
|
423
424
|
|
|
424
425
|
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">command</span><span class="o">=</span><span class="s2">"</span><span class="nv">$HOME</span><span class="s2">/bin/rrsync <folder>"</span>,no-agent-forwarding,no-port-forwarding,no-pty,no-user-rc,no-X11-forwarding ssh-rsa <cert>
|
|
425
426
|
</code></pre></div></div>
|
|
426
427
|
|
|
427
|
-
<p><code class="highlighter-rouge"><folder></code> is the path to your site. E.g., <code class="highlighter-rouge">~/public_html/you.org/blog-html/</code>.</p>
|
|
428
|
+
<p><code class="language-plaintext highlighter-rouge"><folder></code> is the path to your site. E.g., <code class="language-plaintext highlighter-rouge">~/public_html/you.org/blog-html/</code>.</p>
|
|
428
429
|
|
|
429
430
|
<h4 id="step-3-rsync-client-side">Step 3: Rsync (client-side)</h4>
|
|
430
431
|
|
|
431
|
-
<p>Add the <code class="highlighter-rouge">deploy</code> script to the site source folder:</p>
|
|
432
|
+
<p>Add the <code class="language-plaintext highlighter-rouge">deploy</code> script to the site source folder:</p>
|
|
432
433
|
|
|
433
434
|
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c">#!/bin/sh</span>
|
|
434
435
|
|
|
@@ -438,11 +439,11 @@ rsync <span class="nt">-crvz</span> <span class="nt">--rsh</span><span class="o"
|
|
|
438
439
|
<p>Command line parameters are:</p>
|
|
439
440
|
|
|
440
441
|
<ul>
|
|
441
|
-
<li><code class="highlighter-rouge">--rsh=ssh -p2222</code> — The port for SSH access. It is required if
|
|
442
|
+
<li><code class="language-plaintext highlighter-rouge">--rsh=ssh -p2222</code> — The port for SSH access. It is required if
|
|
442
443
|
your host uses a different port than the default (e.g, HostGator)</li>
|
|
443
|
-
<li><code class="highlighter-rouge"><folder></code> — The name of the local output folder (defaults to <code class="highlighter-rouge">_site</code>)</li>
|
|
444
|
-
<li><code class="highlighter-rouge"><user></code> — The username for your hosting account</li>
|
|
445
|
-
<li><code class="highlighter-rouge"><site></code> — Your hosting server</li>
|
|
444
|
+
<li><code class="language-plaintext highlighter-rouge"><folder></code> — The name of the local output folder (defaults to <code class="language-plaintext highlighter-rouge">_site</code>)</li>
|
|
445
|
+
<li><code class="language-plaintext highlighter-rouge"><user></code> — The username for your hosting account</li>
|
|
446
|
+
<li><code class="language-plaintext highlighter-rouge"><site></code> — Your hosting server</li>
|
|
446
447
|
</ul>
|
|
447
448
|
|
|
448
449
|
<p>Using this setup, you might run the following command:</p>
|
|
@@ -450,13 +451,13 @@ your host uses a different port than the default (e.g, HostGator)</li>
|
|
|
450
451
|
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>rsync <span class="nt">-crvz</span> <span class="nt">--rsh</span><span class="o">=</span><span class="s1">'ssh -p2222'</span> <span class="nt">--delete-after</span> <span class="nt">--delete-excluded</span> _site/ hostuser@example.org:
|
|
451
452
|
</code></pre></div></div>
|
|
452
453
|
|
|
453
|
-
<p>Don’t forget the column <code class="highlighter-rouge">:</code> after server name!</p>
|
|
454
|
+
<p>Don’t forget the column <code class="language-plaintext highlighter-rouge">:</code> after server name!</p>
|
|
454
455
|
|
|
455
456
|
<h4 id="step-4-optional-exclude-the-transfer-script-from-being-copied-to-the-output-folder">Step 4 (Optional): Exclude the transfer script from being copied to the output folder.</h4>
|
|
456
457
|
|
|
457
458
|
<p>This step is recommended if you use these instructions to deploy your site. If
|
|
458
|
-
you put the <code class="highlighter-rouge">deploy</code> script in the root folder of your project, Jekyll will
|
|
459
|
-
copy it to the output folder. This behavior can be changed in <code class="highlighter-rouge">_config.yml</code>.</p>
|
|
459
|
+
you put the <code class="language-plaintext highlighter-rouge">deploy</code> script in the root folder of your project, Jekyll will
|
|
460
|
+
copy it to the output folder. This behavior can be changed in <code class="language-plaintext highlighter-rouge">_config.yml</code>.</p>
|
|
460
461
|
|
|
461
462
|
<p>Just add the following line:</p>
|
|
462
463
|
|
|
@@ -464,11 +465,11 @@ copy it to the output folder. This behavior can be changed in <code class="highl
|
|
|
464
465
|
<span class="na">exclude</span><span class="pi">:</span> <span class="pi">[</span><span class="s2">"</span><span class="s">deploy"</span><span class="pi">]</span>
|
|
465
466
|
</code></pre></div></div>
|
|
466
467
|
|
|
467
|
-
<p>Alternatively, you can use an <code class="highlighter-rouge">rsync-exclude.txt</code> file to control which files will be transferred to your server.</p>
|
|
468
|
+
<p>Alternatively, you can use an <code class="language-plaintext highlighter-rouge">rsync-exclude.txt</code> file to control which files will be transferred to your server.</p>
|
|
468
469
|
|
|
469
470
|
<h4 id="done">Done!</h4>
|
|
470
471
|
|
|
471
|
-
<p>Now it’s possible to publish your website simply by running the <code class="highlighter-rouge">deploy</code>
|
|
472
|
+
<p>Now it’s possible to publish your website simply by running the <code class="language-plaintext highlighter-rouge">deploy</code>
|
|
472
473
|
script. If your SSH certificate is <a href="https://martin.kleppmann.com/2013/05/24/improving-security-of-ssh-private-keys.html">passphrase-protected</a>, you will be asked to enter it when the
|
|
473
474
|
script executes.</p>
|
|
474
475
|
|
|
@@ -797,7 +798,7 @@ for that</a>.</p>
|
|
|
797
798
|
<footer>
|
|
798
799
|
<div class="grid">
|
|
799
800
|
<div class="unit one-third center-on-mobiles">
|
|
800
|
-
<p>The contents of this website are <br />©
|
|
801
|
+
<p>The contents of this website are <br />© 2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
|
|
801
802
|
</div>
|
|
802
803
|
<div class="unit two-thirds align-right center-on-mobiles">
|
|
803
804
|
<p>
|
data/site/docs/drafts/index.html
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
<head>
|
|
4
4
|
<meta charset="UTF-8">
|
|
5
5
|
<meta name="viewport" content="width=device-width,initial-scale=1">
|
|
6
|
-
<meta name="generator" content="Jekyll v3.
|
|
6
|
+
<meta name="generator" content="Jekyll v3.9.0">
|
|
7
7
|
<link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
|
|
8
8
|
<link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
|
|
9
9
|
<link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
|
|
@@ -11,9 +11,9 @@
|
|
|
11
11
|
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
|
|
12
12
|
<link rel="stylesheet" href="/css/screen.css">
|
|
13
13
|
<link rel="icon" type="image/x-icon" href="/favicon.ico">
|
|
14
|
-
<!-- Begin Jekyll SEO tag v2.
|
|
14
|
+
<!-- Begin Jekyll SEO tag v2.6.1 -->
|
|
15
15
|
<title>Working with drafts | Jekyll • Simple, blog-aware, static sites</title>
|
|
16
|
-
<meta name="generator" content="Jekyll v3.
|
|
16
|
+
<meta name="generator" content="Jekyll v3.9.0" />
|
|
17
17
|
<meta property="og:title" content="Working with drafts" />
|
|
18
18
|
<meta property="og:locale" content="en_US" />
|
|
19
19
|
<meta name="description" content="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 section) and create your first draft:" />
|
|
@@ -22,12 +22,13 @@
|
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/drafts/" />
|
|
23
23
|
<meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
|
|
24
24
|
<meta property="og:type" content="article" />
|
|
25
|
-
<meta property="article:published_time" content="
|
|
25
|
+
<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
|
|
26
26
|
<meta name="twitter:card" content="summary" />
|
|
27
|
+
<meta property="twitter:title" content="Working with drafts" />
|
|
27
28
|
<meta name="twitter:site" content="@jekyllrb" />
|
|
28
29
|
<meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
|
|
29
30
|
<script type="application/ld+json">
|
|
30
|
-
{"headline":"Working with drafts","dateModified":"
|
|
31
|
+
{"url":"https://jekyllrb.com/docs/drafts/","headline":"Working with drafts","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"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 section) and create your first draft:","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/drafts/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
|
|
31
32
|
<!-- End Jekyll SEO tag -->
|
|
32
33
|
|
|
33
34
|
<!--[if lt IE 9]>
|
|
@@ -72,7 +73,7 @@
|
|
|
72
73
|
<div class="meta hide-on-mobiles">
|
|
73
74
|
<ul>
|
|
74
75
|
<li>
|
|
75
|
-
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.
|
|
76
|
+
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
|
|
76
77
|
</li>
|
|
77
78
|
<li>
|
|
78
79
|
<a href="https://github.com/jekyll/jekyll">GitHub</a>
|
|
@@ -296,15 +297,15 @@
|
|
|
296
297
|
<h1>Working with drafts</h1>
|
|
297
298
|
<p>Drafts are posts without a date. They’re posts you’re still working on and
|
|
298
299
|
don’t want to publish yet. To get up and running with drafts, create a
|
|
299
|
-
<code class="highlighter-rouge">_drafts</code> folder in your site’s root (as described in the <a href="/docs/structure/">site structure</a> section) and create your
|
|
300
|
+
<code class="language-plaintext highlighter-rouge">_drafts</code> folder in your site’s root (as described in the <a href="/docs/structure/">site structure</a> section) and create your
|
|
300
301
|
first draft:</p>
|
|
301
302
|
|
|
302
303
|
<div class="language-text highlighter-rouge"><div class="highlight"><pre class="highlight"><code>|-- _drafts/
|
|
303
304
|
| |-- a-draft-post.md
|
|
304
305
|
</code></pre></div></div>
|
|
305
306
|
|
|
306
|
-
<p>To preview your site with drafts, simply run <code class="highlighter-rouge">jekyll serve</code> or <code class="highlighter-rouge">jekyll build</code>
|
|
307
|
-
with the <code class="highlighter-rouge">--drafts</code> switch. Each will be assigned the value modification time
|
|
307
|
+
<p>To preview your site with drafts, simply run <code class="language-plaintext highlighter-rouge">jekyll serve</code> or <code class="language-plaintext highlighter-rouge">jekyll build</code>
|
|
308
|
+
with the <code class="language-plaintext highlighter-rouge">--drafts</code> switch. Each will be assigned the value modification time
|
|
308
309
|
of the draft file for its date, and thus you will see currently edited drafts
|
|
309
310
|
as the latest posts.</p>
|
|
310
311
|
|
|
@@ -560,7 +561,7 @@ as the latest posts.</p>
|
|
|
560
561
|
<footer>
|
|
561
562
|
<div class="grid">
|
|
562
563
|
<div class="unit one-third center-on-mobiles">
|
|
563
|
-
<p>The contents of this website are <br />©
|
|
564
|
+
<p>The contents of this website are <br />© 2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
|
|
564
565
|
</div>
|
|
565
566
|
<div class="unit two-thirds align-right center-on-mobiles">
|
|
566
567
|
<p>
|
data/site/docs/extras/index.html
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
<head>
|
|
4
4
|
<meta charset="UTF-8">
|
|
5
5
|
<meta name="viewport" content="width=device-width,initial-scale=1">
|
|
6
|
-
<meta name="generator" content="Jekyll v3.
|
|
6
|
+
<meta name="generator" content="Jekyll v3.9.0">
|
|
7
7
|
<link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
|
|
8
8
|
<link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
|
|
9
9
|
<link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
|
|
@@ -11,9 +11,9 @@
|
|
|
11
11
|
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
|
|
12
12
|
<link rel="stylesheet" href="/css/screen.css">
|
|
13
13
|
<link rel="icon" type="image/x-icon" href="/favicon.ico">
|
|
14
|
-
<!-- Begin Jekyll SEO tag v2.
|
|
14
|
+
<!-- Begin Jekyll SEO tag v2.6.1 -->
|
|
15
15
|
<title>Extras | Jekyll • Simple, blog-aware, static sites</title>
|
|
16
|
-
<meta name="generator" content="Jekyll v3.
|
|
16
|
+
<meta name="generator" content="Jekyll v3.9.0" />
|
|
17
17
|
<meta property="og:title" content="Extras" />
|
|
18
18
|
<meta property="og:locale" content="en_US" />
|
|
19
19
|
<meta name="description" content="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." />
|
|
@@ -22,12 +22,13 @@
|
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/extras/" />
|
|
23
23
|
<meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
|
|
24
24
|
<meta property="og:type" content="article" />
|
|
25
|
-
<meta property="article:published_time" content="
|
|
25
|
+
<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
|
|
26
26
|
<meta name="twitter:card" content="summary" />
|
|
27
|
+
<meta property="twitter:title" content="Extras" />
|
|
27
28
|
<meta name="twitter:site" content="@jekyllrb" />
|
|
28
29
|
<meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
|
|
29
30
|
<script type="application/ld+json">
|
|
30
|
-
{"headline":"Extras","dateModified":"
|
|
31
|
+
{"url":"https://jekyllrb.com/docs/extras/","headline":"Extras","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"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.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/extras/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
|
|
31
32
|
<!-- End Jekyll SEO tag -->
|
|
32
33
|
|
|
33
34
|
<!--[if lt IE 9]>
|
|
@@ -72,7 +73,7 @@
|
|
|
72
73
|
<div class="meta hide-on-mobiles">
|
|
73
74
|
<ul>
|
|
74
75
|
<li>
|
|
75
|
-
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.
|
|
76
|
+
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
|
|
76
77
|
</li>
|
|
77
78
|
<li>
|
|
78
79
|
<a href="https://github.com/jekyll/jekyll">GitHub</a>
|
|
@@ -304,7 +305,7 @@ may want to install, depending on how you plan to use Jekyll.</p>
|
|
|
304
305
|
<div class="language-html highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt"><script </span><span class="na">src=</span><span class="s">"https://txtpen.com/embed.js?site=<your site name>"</span><span class="nt">></script></span>
|
|
305
306
|
</code></pre></div></div>
|
|
306
307
|
|
|
307
|
-
<p>to your template files in <code class="highlighter-rouge">/_layout</code> folder.</p>
|
|
308
|
+
<p>to your template files in <code class="language-plaintext highlighter-rouge">/_layout</code> folder.</p>
|
|
308
309
|
|
|
309
310
|
<h2 id="math-support">Math Support</h2>
|
|
310
311
|
|
|
@@ -613,7 +614,7 @@ may want to install, depending on how you plan to use Jekyll.</p>
|
|
|
613
614
|
<footer>
|
|
614
615
|
<div class="grid">
|
|
615
616
|
<div class="unit one-third center-on-mobiles">
|
|
616
|
-
<p>The contents of this website are <br />©
|
|
617
|
+
<p>The contents of this website are <br />© 2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
|
|
617
618
|
</div>
|
|
618
619
|
<div class="unit two-thirds align-right center-on-mobiles">
|
|
619
620
|
<p>
|