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>Order of interpretation | 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="Order of interpretation" />
|
|
18
18
|
<meta property="og:locale" content="en_US" />
|
|
19
19
|
<meta name="description" content="Jekyll’s main job is to convert your raw text files into a static website. It does this by rendering Liquid, Markdown, and other transforms as it generates the static HTML output." />
|
|
@@ -22,12 +22,13 @@
|
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/tutorials/orderofinterpretation/" />
|
|
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="Order of interpretation" />
|
|
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":"Order of interpretation","dateModified":"
|
|
31
|
+
{"url":"https://jekyllrb.com/tutorials/orderofinterpretation/","headline":"Order of interpretation","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":"Jekyll’s main job is to convert your raw text files into a static website. It does this by rendering Liquid, Markdown, and other transforms as it generates the static HTML output.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/tutorials/orderofinterpretation/"},"@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>
|
|
@@ -166,22 +167,22 @@
|
|
|
166
167
|
|
|
167
168
|
<ol>
|
|
168
169
|
<li>
|
|
169
|
-
<p><strong>Site variables</strong>. Jekyll looks across your files and populates <a href="/docs/variables/">site variables</a>, such as <code class="highlighter-rouge">site</code>, <code class="highlighter-rouge">page</code>, <code class="highlighter-rouge">post</code>, and collection objects. (From these objects, Jekyll determines the values for permalinks, tags, categories, and other details.)</p>
|
|
170
|
+
<p><strong>Site variables</strong>. Jekyll looks across your files and populates <a href="/docs/variables/">site variables</a>, such as <code class="language-plaintext highlighter-rouge">site</code>, <code class="language-plaintext highlighter-rouge">page</code>, <code class="language-plaintext highlighter-rouge">post</code>, and collection objects. (From these objects, Jekyll determines the values for permalinks, tags, categories, and other details.)</p>
|
|
170
171
|
</li>
|
|
171
172
|
<li><strong>Liquid</strong>. Jekyll processes any <a href="https://github.com/Shopify/liquid">Liquid</a> formatting in pages that contain <a href="/docs/frontmatter/">front matter</a>. You can identify Liquid as follows:
|
|
172
173
|
<ul>
|
|
173
|
-
<li><strong>Liquid tags</strong> start with <code class="highlighter-rouge">{%</code> and end with a <code class="highlighter-rouge">%}</code>. For example: <code class="highlighter-rouge">{% highlight %}</code> or <code class="highlighter-rouge">{% seo %}</code>. Tags can define blocks or be inline. Block-defining tags will also come with a corresponding end tag — for example, <code class="highlighter-rouge">{% endhighlight %}</code>.</li>
|
|
174
|
-
<li><strong>Liquid variables</strong> start and end with double curly braces. For example: <code class="highlighter-rouge">{{ site.myvariable }}</code> or <code class="highlighter-rouge">{{ content }}</code>.</li>
|
|
175
|
-
<li><strong>Liquid filters</strong> start with a pipe character (<code class="highlighter-rouge">|</code>) and can only be used within <strong>Liquid variables</strong> after the variable string. For example: the <code class="highlighter-rouge">relative_url</code> filter in <code class="highlighter-rouge">{{ "css/main.css" | relative_url }}</code>.</li>
|
|
174
|
+
<li><strong>Liquid tags</strong> start with <code class="language-plaintext highlighter-rouge">{%</code> and end with a <code class="language-plaintext highlighter-rouge">%}</code>. For example: <code class="language-plaintext highlighter-rouge">{% highlight %}</code> or <code class="language-plaintext highlighter-rouge">{% seo %}</code>. Tags can define blocks or be inline. Block-defining tags will also come with a corresponding end tag — for example, <code class="language-plaintext highlighter-rouge">{% endhighlight %}</code>.</li>
|
|
175
|
+
<li><strong>Liquid variables</strong> start and end with double curly braces. For example: <code class="language-plaintext highlighter-rouge">{{ site.myvariable }}</code> or <code class="language-plaintext highlighter-rouge">{{ content }}</code>.</li>
|
|
176
|
+
<li><strong>Liquid filters</strong> start with a pipe character (<code class="language-plaintext highlighter-rouge">|</code>) and can only be used within <strong>Liquid variables</strong> after the variable string. For example: the <code class="language-plaintext highlighter-rouge">relative_url</code> filter in <code class="language-plaintext highlighter-rouge">{{ "css/main.css" | relative_url }}</code>.</li>
|
|
176
177
|
</ul>
|
|
177
178
|
</li>
|
|
178
179
|
<li>
|
|
179
180
|
<p><strong>Markdown</strong>. Jekyll converts Markdown to HTML using the Markdown filter specified in your config file. Files must have a Markdown file extension and front matter in order for Jekyll to convert them.</p>
|
|
180
181
|
</li>
|
|
181
182
|
<li>
|
|
182
|
-
<p><strong>Layout</strong>. Jekyll pushes content into the layouts specified by the page’s front matter (or as specified in the config file). The content from each page gets pushed into the <code class="highlighter-rouge">{{ content }}</code> tags within the layouts.</p>
|
|
183
|
+
<p><strong>Layout</strong>. Jekyll pushes content into the layouts specified by the page’s front matter (or as specified in the config file). The content from each page gets pushed into the <code class="language-plaintext highlighter-rouge">{{ content }}</code> tags within the layouts.</p>
|
|
183
184
|
</li>
|
|
184
|
-
<li><strong>Files</strong>. Jekyll writes the generated content into files in the <a href="/docs/structure/">directory structure</a> in <code class="highlighter-rouge">_site</code>. Pages, posts, and collections get structured based on their <a href="/docs/permalinks/">permalink</a> setting. Directories that begin with <code class="highlighter-rouge">_</code> (such as <code class="highlighter-rouge">_includes</code> and <code class="highlighter-rouge">_data</code>) are usually hidden in the output.</li>
|
|
185
|
+
<li><strong>Files</strong>. Jekyll writes the generated content into files in the <a href="/docs/structure/">directory structure</a> in <code class="language-plaintext highlighter-rouge">_site</code>. Pages, posts, and collections get structured based on their <a href="/docs/permalinks/">permalink</a> setting. Directories that begin with <code class="language-plaintext highlighter-rouge">_</code> (such as <code class="language-plaintext highlighter-rouge">_includes</code> and <code class="language-plaintext highlighter-rouge">_data</code>) are usually hidden in the output.</li>
|
|
185
186
|
</ol>
|
|
186
187
|
|
|
187
188
|
<h2 id="scenarios-where-incorrect-configurations-create-problems">Scenarios where incorrect configurations create problems</h2>
|
|
@@ -192,7 +193,7 @@
|
|
|
192
193
|
|
|
193
194
|
<h3 id="variable-on-page-not-rendered-because-variable-is-assigned-in-layout">Variable on page not rendered because variable is assigned in layout</h3>
|
|
194
195
|
|
|
195
|
-
<p>In your layout file (<code class="highlighter-rouge">_layouts/default.html</code>), suppose you have a variable assigned:</p>
|
|
196
|
+
<p>In your layout file (<code class="language-plaintext highlighter-rouge">_layouts/default.html</code>), suppose you have a variable assigned:</p>
|
|
196
197
|
|
|
197
198
|
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{%</span><span class="w"> </span><span class="nt">assign</span><span class="w"> </span><span class="nv">myvar</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s2">"joe"</span><span class="w"> </span><span class="p">%}</span>
|
|
198
199
|
</code></pre></div></div>
|
|
@@ -208,7 +209,7 @@
|
|
|
208
209
|
|
|
209
210
|
<h3 id="markdown-in-include-file-not-processed">Markdown in include file not processed</h3>
|
|
210
211
|
|
|
211
|
-
<p>Suppose you have a Markdown file at <code class="highlighter-rouge">_includes/mycontent.md</code>. In the Markdown file, you have some Markdown formatting:</p>
|
|
212
|
+
<p>Suppose you have a Markdown file at <code class="language-plaintext highlighter-rouge">_includes/mycontent.md</code>. In the Markdown file, you have some Markdown formatting:</p>
|
|
212
213
|
|
|
213
214
|
<div class="language-markdown highlighter-rouge"><div class="highlight"><pre class="highlight"><code>This is a list:
|
|
214
215
|
<span class="p">*</span> first item
|
|
@@ -217,57 +218,57 @@
|
|
|
217
218
|
|
|
218
219
|
<p>You include the file into an HTML file as follows:</p>
|
|
219
220
|
|
|
220
|
-
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{%</span><span class="w"> </span><span class="nt">include</span><span class="w"> </span
|
|
221
|
+
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{%</span><span class="w"> </span><span class="nt">include</span><span class="w"> </span>mycontent.md<span class="w"> </span><span class="p">%}</span>
|
|
221
222
|
</code></pre></div></div>
|
|
222
223
|
|
|
223
|
-
<p>The Markdown is not processed because first the Liquid (<code class="highlighter-rouge">include</code> tag) gets processed, inserting <code class="highlighter-rouge">mycontent.md</code> into the HTML file. <em>Then</em> the Markdown would get processed.</p>
|
|
224
|
+
<p>The Markdown is not processed because first the Liquid (<code class="language-plaintext highlighter-rouge">include</code> tag) gets processed, inserting <code class="language-plaintext highlighter-rouge">mycontent.md</code> into the HTML file. <em>Then</em> the Markdown would get processed.</p>
|
|
224
225
|
|
|
225
226
|
<p>But because the content is included into an <em>HTML</em> page, the Markdown isn’t rendered. The Markdown filter processes content only in Markdown files.</p>
|
|
226
227
|
|
|
227
228
|
<p>To make the code work, use HTML formatting in includes that are inserted into HTML files.</p>
|
|
228
229
|
|
|
229
|
-
<p>Note that <code class="highlighter-rouge">highlight</code> tags don’t require Markdown to process. Suppose your include contains the following:</p>
|
|
230
|
+
<p>Note that <code class="language-plaintext highlighter-rouge">highlight</code> tags don’t require Markdown to process. Suppose your include contains the following:</p>
|
|
230
231
|
|
|
231
232
|
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{%</span><span class="w"> </span><span class="nt">highlight</span><span class="w"> </span>javascript<span class="w"> </span><span class="p">%}</span>
|
|
232
233
|
console.log('alert');
|
|
233
234
|
<span class="p">{%</span><span class="w"> </span><span class="nt">endhighlight</span><span class="w"> </span><span class="p">%}</span>
|
|
234
235
|
</code></pre></div></div>
|
|
235
236
|
|
|
236
|
-
<p>The <code class="highlighter-rouge">highlight</code> tag <em>is</em> Liquid. (Liquid passes the content to Rouge or Pygments for syntax highlighting.) As a result, this code will actually convert to HTML with syntax highlighting. Jekyll does not need the Markdown filter to process <code class="highlighter-rouge">highlight</code> tags.</p>
|
|
237
|
+
<p>The <code class="language-plaintext highlighter-rouge">highlight</code> tag <em>is</em> Liquid. (Liquid passes the content to Rouge or Pygments for syntax highlighting.) As a result, this code will actually convert to HTML with syntax highlighting. Jekyll does not need the Markdown filter to process <code class="language-plaintext highlighter-rouge">highlight</code> tags.</p>
|
|
237
238
|
|
|
238
239
|
<h3 id="liquid-mixed-with-javascript-isnt-rendered">Liquid mixed with JavaScript isn’t rendered</h3>
|
|
239
240
|
|
|
240
|
-
<p>Suppose you try to mix Liquid’s <code class="highlighter-rouge">assign</code> tag with JavaScript, like this:</p>
|
|
241
|
+
<p>Suppose you try to mix Liquid’s <code class="language-plaintext highlighter-rouge">assign</code> tag with JavaScript, like this:</p>
|
|
241
242
|
|
|
242
|
-
<div class="language-javascript highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="o"><</span><span class="nx">button</span> <span class="nx">onclick</span><span class="o">=</span><span class="s2">
|
|
243
|
+
<div class="language-javascript highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="o"><</span><span class="nx">button</span> <span class="nx">onclick</span><span class="o">=</span><span class="dl">"</span><span class="s2">someFunction()</span><span class="dl">"</span><span class="o">></span><span class="nx">Click</span> <span class="nx">me</span><span class="o"><</span><span class="sr">/button</span><span class="err">>
|
|
243
244
|
</span>
|
|
244
|
-
<span class="o"><</span><span class="nx">p</span> <span class="nx">id</span><span class="o">=</span><span class="s2">
|
|
245
|
+
<span class="o"><</span><span class="nx">p</span> <span class="nx">id</span><span class="o">=</span><span class="dl">"</span><span class="s2">intro</span><span class="dl">"</span><span class="o">><</span><span class="sr">/p</span><span class="err">>
|
|
245
246
|
</span>
|
|
246
247
|
<span class="o"><</span><span class="nx">script</span><span class="o">></span>
|
|
247
|
-
<span class="p">{</span><span class="o">%</span> <span class="nx">assign</span> <span class="nx">someContent</span> <span class="o">=</span> <span class="s2">
|
|
248
|
+
<span class="p">{</span><span class="o">%</span> <span class="nx">assign</span> <span class="nx">someContent</span> <span class="o">=</span> <span class="dl">"</span><span class="s2">This is some content</span><span class="dl">"</span> <span class="o">%</span><span class="p">}</span>
|
|
248
249
|
<span class="kd">function</span> <span class="nx">someFunction</span><span class="p">()</span> <span class="p">{</span>
|
|
249
|
-
<span class="nb">document</span><span class="p">.</span><span class="nx">getElementById</span><span class="p">(</span><span class="s2">
|
|
250
|
+
<span class="nb">document</span><span class="p">.</span><span class="nx">getElementById</span><span class="p">(</span><span class="dl">"</span><span class="s2">intro</span><span class="dl">"</span><span class="p">).</span><span class="nx">innerHTML</span> <span class="o">=</span> <span class="nx">someContent</span><span class="p">;</span>
|
|
250
251
|
<span class="p">}</span>
|
|
251
252
|
<span class="o"><</span><span class="sr">/script</span><span class="err">>
|
|
252
253
|
</span></code></pre></div></div>
|
|
253
254
|
|
|
254
|
-
<p>This won’t work because the <code class="highlighter-rouge">assign</code> tag is only available during the Liquid rendering phase of the site. In this JavaScript example, the script executes when a user clicks a button (“Click me”) on the HTML page. At that time, the Liquid logic is no longer available, so the <code class="highlighter-rouge">assign</code> tag wouldn’t return anything.</p>
|
|
255
|
+
<p>This won’t work because the <code class="language-plaintext highlighter-rouge">assign</code> tag is only available during the Liquid rendering phase of the site. In this JavaScript example, the script executes when a user clicks a button (“Click me”) on the HTML page. At that time, the Liquid logic is no longer available, so the <code class="language-plaintext highlighter-rouge">assign</code> tag wouldn’t return anything.</p>
|
|
255
256
|
|
|
256
|
-
<p>However, you can use Jekyll’s site variables or Liquid to <em>populate</em> a script that is executed at a later time. For example, suppose you have the following property in your front matter: <code class="highlighter-rouge">someContent: "This is some content"</code>. You could do this:</p>
|
|
257
|
+
<p>However, you can use Jekyll’s site variables or Liquid to <em>populate</em> a script that is executed at a later time. For example, suppose you have the following property in your front matter: <code class="language-plaintext highlighter-rouge">someContent: "This is some content"</code>. You could do this:</p>
|
|
257
258
|
|
|
258
|
-
<div class="language-js highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="o"><</span><span class="nx">button</span> <span class="nx">onclick</span><span class="o">=</span><span class="s2">
|
|
259
|
+
<div class="language-js highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="o"><</span><span class="nx">button</span> <span class="nx">onclick</span><span class="o">=</span><span class="dl">"</span><span class="s2">someFunction()</span><span class="dl">"</span><span class="o">></span><span class="nx">Click</span> <span class="nx">me</span><span class="o"><</span><span class="sr">/button</span><span class="err">>
|
|
259
260
|
</span>
|
|
260
|
-
<span class="o"><</span><span class="nx">p</span> <span class="nx">id</span><span class="o">=</span><span class="s2">
|
|
261
|
+
<span class="o"><</span><span class="nx">p</span> <span class="nx">id</span><span class="o">=</span><span class="dl">"</span><span class="s2">intro</span><span class="dl">"</span><span class="o">><</span><span class="sr">/p</span><span class="err">>
|
|
261
262
|
</span>
|
|
262
263
|
<span class="o"><</span><span class="nx">script</span><span class="o">></span>
|
|
263
264
|
|
|
264
265
|
<span class="kd">function</span> <span class="nx">someFunction</span><span class="p">()</span> <span class="p">{</span>
|
|
265
|
-
<span class="nb">document</span><span class="p">.</span><span class="nx">getElementById</span><span class="p">(</span><span class="s2">
|
|
266
|
+
<span class="nb">document</span><span class="p">.</span><span class="nx">getElementById</span><span class="p">(</span><span class="dl">"</span><span class="s2">intro</span><span class="dl">"</span><span class="p">).</span><span class="nx">innerHTML</span> <span class="o">=</span> <span class="dl">"</span><span class="s2">{{ page.someContent }}</span><span class="dl">"</span><span class="p">;</span>
|
|
266
267
|
<span class="p">}</span>
|
|
267
268
|
<span class="o"><</span><span class="sr">/script</span><span class="err">>
|
|
268
269
|
</span></code></pre></div></div>
|
|
269
270
|
|
|
270
|
-
<p>When Jekyll builds the site, this <code class="highlighter-rouge">someContent</code> property populates the script’s values, converting <code class="highlighter-rouge">{{ page.someContent }}</code> to <code class="highlighter-rouge">"This is some content"</code>.</p>
|
|
271
|
+
<p>When Jekyll builds the site, this <code class="language-plaintext highlighter-rouge">someContent</code> property populates the script’s values, converting <code class="language-plaintext highlighter-rouge">{{ page.someContent }}</code> to <code class="language-plaintext highlighter-rouge">"This is some content"</code>.</p>
|
|
271
272
|
|
|
272
273
|
<p>The key to remember is that Liquid renders when Jekyll builds your site. Liquid is not available at run-time in the browser when a user executes an event.</p>
|
|
273
274
|
|
|
@@ -275,7 +276,7 @@ console.log('alert');
|
|
|
275
276
|
|
|
276
277
|
<p>There’s one more detail to remember: Liquid does not render when embedded in YAML files or front matter. (This isn’t related to order of interpretation, but it’s worth mentioning because it’s a common question about element rendering.)</p>
|
|
277
278
|
|
|
278
|
-
<p>For example, suppose you have a <code class="highlighter-rouge">highlight</code> tag in your <code class="highlighter-rouge">_data/mydata.yml</code> file:</p>
|
|
279
|
+
<p>For example, suppose you have a <code class="language-plaintext highlighter-rouge">highlight</code> tag in your <code class="language-plaintext highlighter-rouge">_data/mydata.yml</code> file:</p>
|
|
279
280
|
|
|
280
281
|
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code>myvalue: >
|
|
281
282
|
<span class="p">{%</span><span class="w"> </span><span class="nt">highlight</span><span class="w"> </span>javascript<span class="w"> </span><span class="p">%}</span>
|
|
@@ -380,7 +381,7 @@ console.log('alert');
|
|
|
380
381
|
<footer>
|
|
381
382
|
<div class="grid">
|
|
382
383
|
<div class="unit one-third center-on-mobiles">
|
|
383
|
-
<p>The contents of this website are <br />©
|
|
384
|
+
<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>
|
|
384
385
|
</div>
|
|
385
386
|
<div class="unit two-thirds align-right center-on-mobiles">
|
|
386
387
|
<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>Using Jekyll with Bundler | 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="Using Jekyll with Bundler" />
|
|
18
18
|
<meta property="og:locale" content="en_US" />
|
|
19
19
|
<meta name="description" content="Bundler provides a consistent environment for Ruby projects by tracking and installing the exact gems and versions that are needed." />
|
|
@@ -22,12 +22,13 @@
|
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/tutorials/using-jekyll-with-bundler/" />
|
|
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="Using Jekyll with Bundler" />
|
|
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":"Using Jekyll with Bundler","dateModified":"
|
|
31
|
+
{"url":"https://jekyllrb.com/tutorials/using-jekyll-with-bundler/","headline":"Using Jekyll with Bundler","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":"Bundler provides a consistent environment for Ruby projects by tracking and installing the exact gems and versions that are needed.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/tutorials/using-jekyll-with-bundler/"},"@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>
|
|
@@ -175,7 +176,7 @@ installed. You can find the installation instructions on their websites.</p>
|
|
|
175
176
|
<h2 id="initialize-bundler">Initialize Bundler</h2>
|
|
176
177
|
|
|
177
178
|
<p>The first thing to do is create a new directory for your project and run
|
|
178
|
-
<code class="highlighter-rouge">bundle init</code>. This creates a new Bundler project (by creating an empty
|
|
179
|
+
<code class="language-plaintext highlighter-rouge">bundle init</code>. This creates a new Bundler project (by creating an empty
|
|
179
180
|
Gemfile).</p>
|
|
180
181
|
|
|
181
182
|
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">mkdir </span>my-jekyll-website
|
|
@@ -186,7 +187,7 @@ bundle init
|
|
|
186
187
|
<h2 id="configure-bundler">Configure Bundler</h2>
|
|
187
188
|
|
|
188
189
|
<p>This step is optional, but encouraged. We’re going to configure Bundler to install
|
|
189
|
-
gems in the <code class="highlighter-rouge">./vendor/bundle/</code> project subdirectory. This allows us to install
|
|
190
|
+
gems in the <code class="language-plaintext highlighter-rouge">./vendor/bundle/</code> project subdirectory. This allows us to install
|
|
190
191
|
our dependencies in an isolated environment, ensuring they don’t conflict with
|
|
191
192
|
other gems on your system. If you skip this step, Bundler will install your
|
|
192
193
|
dependencies globally on your system.</p>
|
|
@@ -207,7 +208,7 @@ dependencies globally on your system.</p>
|
|
|
207
208
|
|
|
208
209
|
<p>Now, we’re going to use Bundler to add Jekyll as a dependency of our new
|
|
209
210
|
project. This command will add the Jekyll gem to our Gemfile and install it to
|
|
210
|
-
the <code class="highlighter-rouge">./vendor/bundle/</code> folder.</p>
|
|
211
|
+
the <code class="language-plaintext highlighter-rouge">./vendor/bundle/</code> folder.</p>
|
|
211
212
|
|
|
212
213
|
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>bundle add jekyll
|
|
213
214
|
</code></pre></div></div>
|
|
@@ -215,8 +216,8 @@ the <code class="highlighter-rouge">./vendor/bundle/</code> folder.</p>
|
|
|
215
216
|
<h2 id="create-a-jekyll-scaffold">Create A Jekyll Scaffold</h2>
|
|
216
217
|
|
|
217
218
|
<p>Now that Jekyll is installed, we can use it to create the scaffolding for our
|
|
218
|
-
site. We need the <code class="highlighter-rouge">--force</code> parameter because our folder isn’t empty - it
|
|
219
|
-
already has some Bundler files in it. We run the <code class="highlighter-rouge">bundle install</code> separately
|
|
219
|
+
site. We need the <code class="language-plaintext highlighter-rouge">--force</code> parameter because our folder isn’t empty - it
|
|
220
|
+
already has some Bundler files in it. We run the <code class="language-plaintext highlighter-rouge">bundle install</code> separately
|
|
220
221
|
because Jekyll gets confused if the Gemfile already exists.</p>
|
|
221
222
|
|
|
222
223
|
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>bundle <span class="nb">exec </span>jekyll new <span class="nt">--force</span> <span class="nt">--skip-bundle</span> <span class="nb">.</span>
|
|
@@ -226,23 +227,23 @@ bundle <span class="nb">install</span>
|
|
|
226
227
|
<h2 id="serve-the-site">Serve the Site</h2>
|
|
227
228
|
|
|
228
229
|
<p>Your new website is ready! You can serve the website with
|
|
229
|
-
<code class="highlighter-rouge">bundle exec jekyll serve</code> and visit it at
|
|
230
|
+
<code class="language-plaintext highlighter-rouge">bundle exec jekyll serve</code> and visit it at
|
|
230
231
|
<a href="http://127.0.0.1:4000">http://127.0.0.1:4000</a>. From here, you’re ready to
|
|
231
232
|
continue developing the site on your own. All of the normal Jekyll commands are
|
|
232
|
-
available to you, but you should prefix them with <code class="highlighter-rouge">bundle exec</code> so that Bundler
|
|
233
|
+
available to you, but you should prefix them with <code class="language-plaintext highlighter-rouge">bundle exec</code> so that Bundler
|
|
233
234
|
runs the version of Jekyll that is installed in your project folder.</p>
|
|
234
235
|
|
|
235
236
|
<h2 id="commit-to-source-control">Commit to Source Control</h2>
|
|
236
237
|
|
|
237
238
|
<p>If you’re storing your new site in version control, you’ll want to ignore the
|
|
238
|
-
<code class="highlighter-rouge">./vendor/</code> and <code class="highlighter-rouge">./.bundle/</code> folders since they contain user- or
|
|
239
|
+
<code class="language-plaintext highlighter-rouge">./vendor/</code> and <code class="language-plaintext highlighter-rouge">./.bundle/</code> folders since they contain user- or
|
|
239
240
|
platform-specific information. New users will be able to install the correct
|
|
240
|
-
dependencies based on <code class="highlighter-rouge">Gemfile</code> and <code class="highlighter-rouge">Gemfile.lock</code>, which should both be checked
|
|
241
|
-
in. You can use this <code class="highlighter-rouge">.gitigonre</code> to get started, if you want.</p>
|
|
241
|
+
dependencies based on <code class="language-plaintext highlighter-rouge">Gemfile</code> and <code class="language-plaintext highlighter-rouge">Gemfile.lock</code>, which should both be checked
|
|
242
|
+
in. You can use this <code class="language-plaintext highlighter-rouge">.gitigonre</code> to get started, if you want.</p>
|
|
242
243
|
|
|
243
244
|
<p><strong>.gitignore</strong></p>
|
|
244
245
|
|
|
245
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code># Ignore folders generated by Bundler
|
|
246
|
+
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code># Ignore folders generated by Bundler
|
|
246
247
|
vendor
|
|
247
248
|
.bundle
|
|
248
249
|
|
|
@@ -349,7 +350,7 @@ _site
|
|
|
349
350
|
<footer>
|
|
350
351
|
<div class="grid">
|
|
351
352
|
<div class="unit one-third center-on-mobiles">
|
|
352
|
-
<p>The contents of this website are <br />©
|
|
353
|
+
<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>
|
|
353
354
|
</div>
|
|
354
355
|
<div class="unit two-thirds align-right center-on-mobiles">
|
|
355
356
|
<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>Video Walkthroughs | 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="Video Walkthroughs" />
|
|
18
18
|
<meta property="og:locale" content="en_US" />
|
|
19
19
|
<meta name="description" content="Giraffe Academy has a series of videos that will walk you through the basics of using Jekyll. In this series you’ll learn everything from installing Jekyll on your computer and setting up your first site, to using more complex features like variables, layouts and conditionals." />
|
|
@@ -22,12 +22,13 @@
|
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/tutorials/video-walkthroughs/" />
|
|
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="Video Walkthroughs" />
|
|
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":"Video Walkthroughs","dateModified":"
|
|
31
|
+
{"url":"https://jekyllrb.com/tutorials/video-walkthroughs/","headline":"Video Walkthroughs","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":"Giraffe Academy has a series of videos that will walk you through the basics of using Jekyll. In this series you’ll learn everything from installing Jekyll on your computer and setting up your first site, to using more complex features like variables, layouts and conditionals.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/tutorials/video-walkthroughs/"},"@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>
|
|
@@ -269,7 +270,7 @@
|
|
|
269
270
|
<footer>
|
|
270
271
|
<div class="grid">
|
|
271
272
|
<div class="unit one-third center-on-mobiles">
|
|
272
|
-
<p>The contents of this website are <br />©
|
|
273
|
+
<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>
|
|
273
274
|
</div>
|
|
274
275
|
<div class="unit two-thirds align-right center-on-mobiles">
|
|
275
276
|
<p>
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: jekyll-docs
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 3.
|
|
4
|
+
version: 3.9.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Parker Moore
|
|
8
|
-
autorequire:
|
|
8
|
+
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date:
|
|
11
|
+
date: 2020-08-05 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: jekyll
|
|
@@ -16,28 +16,14 @@ dependencies:
|
|
|
16
16
|
requirements:
|
|
17
17
|
- - '='
|
|
18
18
|
- !ruby/object:Gem::Version
|
|
19
|
-
version: 3.
|
|
19
|
+
version: 3.9.0
|
|
20
20
|
type: :runtime
|
|
21
21
|
prerelease: false
|
|
22
22
|
version_requirements: !ruby/object:Gem::Requirement
|
|
23
23
|
requirements:
|
|
24
24
|
- - '='
|
|
25
25
|
- !ruby/object:Gem::Version
|
|
26
|
-
version: 3.
|
|
27
|
-
- !ruby/object:Gem::Dependency
|
|
28
|
-
name: bundler
|
|
29
|
-
requirement: !ruby/object:Gem::Requirement
|
|
30
|
-
requirements:
|
|
31
|
-
- - "~>"
|
|
32
|
-
- !ruby/object:Gem::Version
|
|
33
|
-
version: '1.12'
|
|
34
|
-
type: :development
|
|
35
|
-
prerelease: false
|
|
36
|
-
version_requirements: !ruby/object:Gem::Requirement
|
|
37
|
-
requirements:
|
|
38
|
-
- - "~>"
|
|
39
|
-
- !ruby/object:Gem::Version
|
|
40
|
-
version: '1.12'
|
|
26
|
+
version: 3.9.0
|
|
41
27
|
- !ruby/object:Gem::Dependency
|
|
42
28
|
name: rake
|
|
43
29
|
requirement: !ruby/object:Gem::Requirement
|
|
@@ -52,7 +38,7 @@ dependencies:
|
|
|
52
38
|
- - "~>"
|
|
53
39
|
- !ruby/object:Gem::Version
|
|
54
40
|
version: '12.0'
|
|
55
|
-
description:
|
|
41
|
+
description:
|
|
56
42
|
email:
|
|
57
43
|
- parkrmoore@gmail.com
|
|
58
44
|
executables: []
|
|
@@ -211,6 +197,7 @@ files:
|
|
|
211
197
|
- site/news/2018/05/01/jekyll-3-8-1-released/index.html
|
|
212
198
|
- site/news/2018/05/19/jekyll-3-8-2-released/index.html
|
|
213
199
|
- site/news/2018/06/05/jekyll-3-8-3-released/index.html
|
|
200
|
+
- site/news/2019/07/02/jekyll-3-8-6-released/index.html
|
|
214
201
|
- site/news/index.html
|
|
215
202
|
- site/news/releases/index.html
|
|
216
203
|
- site/philosophy.html
|
|
@@ -230,7 +217,7 @@ homepage: https://jekyllrb.com
|
|
|
230
217
|
licenses:
|
|
231
218
|
- MIT
|
|
232
219
|
metadata: {}
|
|
233
|
-
post_install_message:
|
|
220
|
+
post_install_message:
|
|
234
221
|
rdoc_options: []
|
|
235
222
|
require_paths:
|
|
236
223
|
- lib
|
|
@@ -245,9 +232,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
245
232
|
- !ruby/object:Gem::Version
|
|
246
233
|
version: '0'
|
|
247
234
|
requirements: []
|
|
248
|
-
|
|
249
|
-
|
|
250
|
-
signing_key:
|
|
235
|
+
rubygems_version: 3.0.3
|
|
236
|
+
signing_key:
|
|
251
237
|
specification_version: 4
|
|
252
238
|
summary: Offline usage documentation for Jekyll.
|
|
253
239
|
test_files: []
|