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
data/site/docs/posts/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>Writing posts | 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="Writing posts" />
|
18
18
|
<meta property="og:locale" content="en_US" />
|
19
19
|
<meta name="description" content="One of Jekyll’s best aspects is that it is “blog aware”. What does this mean, exactly? Well, simply put, it means that blogging is baked into Jekyll’s functionality. If you write articles and publish them online, you can publish and maintain a blog simply by managing a folder of text-files on your computer. Compared to the hassle of configuring and maintaining databases and web-based CMS systems, this will be a welcome change!" />
|
@@ -22,12 +22,13 @@
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/posts/" />
|
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="Writing posts" />
|
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":"Writing posts","dateModified":"
|
31
|
+
{"url":"https://jekyllrb.com/docs/posts/","headline":"Writing posts","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":"One of Jekyll’s best aspects is that it is “blog aware”. What does this mean, exactly? Well, simply put, it means that blogging is baked into Jekyll’s functionality. If you write articles and publish them online, you can publish and maintain a blog simply by managing a folder of text-files on your computer. Compared to the hassle of configuring and maintaining databases and web-based CMS systems, this will be a welcome change!","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/posts/"},"@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>
|
@@ -303,7 +304,7 @@ CMS systems, this will be a welcome change!</p>
|
|
303
304
|
|
304
305
|
<h2 id="the-posts-folder">The Posts Folder</h2>
|
305
306
|
|
306
|
-
<p>As explained on the <a href="../structure/">directory structure</a> page, the <code class="highlighter-rouge">_posts</code>
|
307
|
+
<p>As explained on the <a href="../structure/">directory structure</a> page, the <code class="language-plaintext highlighter-rouge">_posts</code>
|
307
308
|
folder is where your blog posts will live. These files are generally
|
308
309
|
<a href="https://daringfireball.net/projects/markdown/">Markdown</a> or HTML, but can
|
309
310
|
be other formats with the proper converter installed.
|
@@ -313,18 +314,18 @@ static site.</p>
|
|
313
314
|
|
314
315
|
<h3 id="creating-post-files">Creating Post Files</h3>
|
315
316
|
|
316
|
-
<p>To create a new post, all you need to do is create a file in the <code class="highlighter-rouge">_posts</code>
|
317
|
+
<p>To create a new post, all you need to do is create a file in the <code class="language-plaintext highlighter-rouge">_posts</code>
|
317
318
|
directory. How you name files in this folder is important. Jekyll requires blog
|
318
319
|
post files to be named according to the following format:</p>
|
319
320
|
|
320
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>YEAR-MONTH-DAY-title.MARKUP
|
321
|
+
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>YEAR-MONTH-DAY-title.MARKUP
|
321
322
|
</code></pre></div></div>
|
322
323
|
|
323
|
-
<p>Where <code class="highlighter-rouge">YEAR</code> is a four-digit number, <code class="highlighter-rouge">MONTH</code> and <code class="highlighter-rouge">DAY</code> are both two-digit
|
324
|
-
numbers, and <code class="highlighter-rouge">MARKUP</code> is the file extension representing the format used in the
|
324
|
+
<p>Where <code class="language-plaintext highlighter-rouge">YEAR</code> is a four-digit number, <code class="language-plaintext highlighter-rouge">MONTH</code> and <code class="language-plaintext highlighter-rouge">DAY</code> are both two-digit
|
325
|
+
numbers, and <code class="language-plaintext highlighter-rouge">MARKUP</code> is the file extension representing the format used in the
|
325
326
|
file. For example, the following are examples of valid post filenames:</p>
|
326
327
|
|
327
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>2011-12-31-new-years-eve-is-awesome.md
|
328
|
+
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>2011-12-31-new-years-eve-is-awesome.md
|
328
329
|
2012-09-12-how-to-write-a-blog.md
|
329
330
|
</code></pre></div></div>
|
330
331
|
|
@@ -369,11 +370,11 @@ out where to store these files in your site is something everyone will face.</p>
|
|
369
370
|
|
370
371
|
<p>There are a number of ways to include digital assets in Jekyll.
|
371
372
|
One common solution is to create a folder in the root of the project directory
|
372
|
-
called something like <code class="highlighter-rouge">assets</code>, into which any images, files
|
373
|
+
called something like <code class="language-plaintext highlighter-rouge">assets</code>, into which any images, files
|
373
374
|
or other resources are placed. Then, from within any post, they can be linked
|
374
375
|
to using the site’s root as the path for the asset to include. Again, this will
|
375
376
|
depend on the way your site’s (sub)domain and path are configured, but here are
|
376
|
-
some examples in Markdown of how you could do this using the <code class="highlighter-rouge">absolute_url</code>
|
377
|
+
some examples in Markdown of how you could do this using the <code class="language-plaintext highlighter-rouge">absolute_url</code>
|
377
378
|
filter in a post.</p>
|
378
379
|
|
379
380
|
<p>Including an image asset in a post:</p>
|
@@ -407,7 +408,7 @@ You’ll find this post in your <span class="sb">`_posts`</span> directory. Go a
|
|
407
408
|
To add new posts, simply add a file in the <span class="sb">`_posts`</span> directory that follows the convention <span class="sb">`YYYY-MM-DD-name-of-post.ext`</span> and includes the necessary front matter. Take a look at the source for this post to get an idea about how it works.
|
408
409
|
</code></pre></div></div>
|
409
410
|
|
410
|
-
<p>Everything in between the first and second <code class="highlighter-rouge">---</code> are part of the YAML Front Matter, and everything after the second <code class="highlighter-rouge">---</code> will be rendered with Markdown and show up as “Content”.</p>
|
411
|
+
<p>Everything in between the first and second <code class="language-plaintext highlighter-rouge">---</code> are part of the YAML Front Matter, and everything after the second <code class="language-plaintext highlighter-rouge">---</code> will be rendered with Markdown and show up as “Content”.</p>
|
411
412
|
|
412
413
|
<h2 id="displaying-an-index-of-posts">Displaying an index of posts</h2>
|
413
414
|
|
@@ -430,9 +431,9 @@ basic example of how to create a list of links to your blog posts:</p>
|
|
430
431
|
and how you structure your site. You should read more about <a href="../templates/">how templates
|
431
432
|
work</a> with Jekyll if you want to know more.</p>
|
432
433
|
|
433
|
-
<p>Note that the <code class="highlighter-rouge">post</code> variable only exists inside the <code class="highlighter-rouge">for</code> loop above. If
|
434
|
+
<p>Note that the <code class="language-plaintext highlighter-rouge">post</code> variable only exists inside the <code class="language-plaintext highlighter-rouge">for</code> loop above. If
|
434
435
|
you wish to access the currently-rendering page/posts’s variables (the
|
435
|
-
variables of the post/page that has the <code class="highlighter-rouge">for</code> loop in it), use the <code class="highlighter-rouge">page</code>
|
436
|
+
variables of the post/page that has the <code class="language-plaintext highlighter-rouge">for</code> loop in it), use the <code class="language-plaintext highlighter-rouge">page</code>
|
436
437
|
variable instead.</p>
|
437
438
|
|
438
439
|
<h2 id="displaying-post-categories-or-tags">Displaying post categories or tags</h2>
|
@@ -448,14 +449,14 @@ list</a>.</p>
|
|
448
449
|
or a template displaying just the posts in those categories you specify. Here’s
|
449
450
|
a basic example of how to create a list of posts from a specific category.</p>
|
450
451
|
|
451
|
-
<p>First, in the <code class="highlighter-rouge">_layouts</code> directory create a new file called <code class="highlighter-rouge">category.html</code> - in
|
452
|
+
<p>First, in the <code class="language-plaintext highlighter-rouge">_layouts</code> directory create a new file called <code class="language-plaintext highlighter-rouge">category.html</code> - in
|
452
453
|
that file put (at least) the following:</p>
|
453
454
|
|
454
455
|
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code>---
|
455
456
|
layout: page
|
456
457
|
---
|
457
458
|
|
458
|
-
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span>post
|
459
|
+
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span><span class="nv">post</span><span class="w"> </span><span class="nt">in</span><span class="w"> </span><span class="nv">site.categories[page.category]</span><span class="w"> </span><span class="p">%}</span>
|
459
460
|
<a href="<span class="p">{{</span><span class="w"> </span><span class="nv">post</span><span class="p">.</span><span class="nv">url</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">absolute_url</span><span class="w"> </span><span class="p">}}</span>">
|
460
461
|
<span class="p">{{</span><span class="w"> </span><span class="nv">post</span><span class="p">.</span><span class="nv">title</span><span class="w"> </span><span class="p">}}</span>
|
461
462
|
</a>
|
@@ -463,9 +464,9 @@ layout: page
|
|
463
464
|
</code></pre></div></div>
|
464
465
|
|
465
466
|
<p>Next, in the root directory of your Jekyll install, create a new directory
|
466
|
-
called <code class="highlighter-rouge">category</code> and then create a file for each category you want to list. For
|
467
|
-
example, if you have a category <code class="highlighter-rouge">blog</code> then create a file in the new directory
|
468
|
-
called <code class="highlighter-rouge">blog.html</code> with at least</p>
|
467
|
+
called <code class="language-plaintext highlighter-rouge">category</code> and then create a file for each category you want to list. For
|
468
|
+
example, if you have a category <code class="language-plaintext highlighter-rouge">blog</code> then create a file in the new directory
|
469
|
+
called <code class="language-plaintext highlighter-rouge">blog.html</code> with at least</p>
|
469
470
|
|
470
471
|
<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nn">---</span>
|
471
472
|
<span class="na">layout</span><span class="pi">:</span> <span class="s">category</span>
|
@@ -474,7 +475,7 @@ called <code class="highlighter-rouge">blog.html</code> with at least</p>
|
|
474
475
|
<span class="nn">---</span>
|
475
476
|
</code></pre></div></div>
|
476
477
|
|
477
|
-
<p>In this case, the listing pages will be accessible at <code class="highlighter-rouge">{baseurl}/category/blog.html</code></p>
|
478
|
+
<p>In this case, the listing pages will be accessible at <code class="language-plaintext highlighter-rouge">{baseurl}/category/blog.html</code></p>
|
478
479
|
|
479
480
|
<p>Although categories and tags are very similar, they are used to group posts,
|
480
481
|
there are a few differences between them. Categories and sub-categories create
|
@@ -486,7 +487,7 @@ site. A post with the following header</p>
|
|
486
487
|
<span class="na">category</span><span class="pi">:</span> <span class="pi">[</span> <span class="nv">blog</span><span class="pi">,</span> <span class="nv">travel</span> <span class="pi">]</span>
|
487
488
|
<span class="nn">---</span>
|
488
489
|
</code></pre></div></div>
|
489
|
-
<p>will be accessible at <code class="highlighter-rouge">{baseurl}/blog/travel/year/month/day/A-Trip.html</code>. On
|
490
|
+
<p>will be accessible at <code class="language-plaintext highlighter-rouge">{baseurl}/blog/travel/year/month/day/A-Trip.html</code>. On
|
490
491
|
the other hand, a tagged post</p>
|
491
492
|
<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nn">---</span>
|
492
493
|
<span class="na">layout</span><span class="pi">:</span> <span class="s">post</span>
|
@@ -494,8 +495,8 @@ the other hand, a tagged post</p>
|
|
494
495
|
<span class="na">tags</span><span class="pi">:</span> <span class="pi">[</span> <span class="nv">blog</span><span class="pi">,</span> <span class="nv">travel</span> <span class="pi">]</span>
|
495
496
|
<span class="nn">---</span>
|
496
497
|
</code></pre></div></div>
|
497
|
-
<p>will be saved as <code class="highlighter-rouge">{baseurl}/year/month/day/A-Trip.html</code>. It is up to you to
|
498
|
-
create <code class="highlighter-rouge">{baseurl}/tag/blog.html</code> and <code class="highlighter-rouge">{baseurl}/tag/travel.html</code> the same way as
|
498
|
+
<p>will be saved as <code class="language-plaintext highlighter-rouge">{baseurl}/year/month/day/A-Trip.html</code>. It is up to you to
|
499
|
+
create <code class="language-plaintext highlighter-rouge">{baseurl}/tag/blog.html</code> and <code class="language-plaintext highlighter-rouge">{baseurl}/tag/travel.html</code> the same way as
|
499
500
|
described above for categories.</p>
|
500
501
|
|
501
502
|
<p>While this example is done with tags and categories, you can easily extend your
|
@@ -504,14 +505,14 @@ lists to filter by any other variable created with extensions.</p>
|
|
504
505
|
<h2 id="post-excerpts">Post excerpts</h2>
|
505
506
|
|
506
507
|
<p>Each post automatically takes the first block of text, from the beginning of
|
507
|
-
the content to the first occurrence of <code class="highlighter-rouge">excerpt_separator</code>, and sets it in the
|
508
|
+
the content to the first occurrence of <code class="language-plaintext highlighter-rouge">excerpt_separator</code>, and sets it in the
|
508
509
|
post’s data hash.
|
509
510
|
Take the above example of an index of posts. Perhaps you want to include
|
510
511
|
a little hint about the post’s content by adding the first paragraph of each of
|
511
512
|
your posts:</p>
|
512
513
|
|
513
514
|
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><ul>
|
514
|
-
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span>post
|
515
|
+
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span><span class="nv">post</span><span class="w"> </span><span class="nt">in</span><span class="w"> </span><span class="nv">site.posts</span><span class="w"> </span><span class="p">%}</span>
|
515
516
|
<li>
|
516
517
|
<a href="<span class="p">{{</span><span class="w"> </span><span class="nv">post</span><span class="p">.</span><span class="nv">url</span><span class="w"> </span><span class="p">}}</span>"><span class="p">{{</span><span class="w"> </span><span class="nv">post</span><span class="p">.</span><span class="nv">title</span><span class="w"> </span><span class="p">}}</span></a>
|
517
518
|
<span class="p">{{</span><span class="w"> </span><span class="nv">post</span><span class="p">.</span><span class="nv">excerpt</span><span class="w"> </span><span class="p">}}</span>
|
@@ -521,16 +522,16 @@ your posts:</p>
|
|
521
522
|
</code></pre></div></div>
|
522
523
|
|
523
524
|
<p>Because Jekyll grabs the first paragraph you will not need to wrap the excerpt
|
524
|
-
in <code class="highlighter-rouge">p</code> tags, which is already done for you. These tags can be removed with the
|
525
|
+
in <code class="language-plaintext highlighter-rouge">p</code> tags, which is already done for you. These tags can be removed with the
|
525
526
|
following if you’d prefer:</p>
|
526
527
|
|
527
528
|
<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{{</span><span class="w"> </span><span class="nv">post</span><span class="p">.</span><span class="nv">excerpt</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">remove</span><span class="p">:</span><span class="w"> </span><span class="s1">'<p>'</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">remove</span><span class="p">:</span><span class="w"> </span><span class="s1">'</p>'</span><span class="w"> </span><span class="p">}}</span>
|
528
529
|
</code></pre></div></div>
|
529
530
|
|
530
531
|
<p>If you don’t like the automatically-generated post excerpt, it can be
|
531
|
-
explicitly overridden by adding an <code class="highlighter-rouge">excerpt</code> value to your post’s YAML
|
532
|
+
explicitly overridden by adding an <code class="language-plaintext highlighter-rouge">excerpt</code> value to your post’s YAML
|
532
533
|
Front Matter. Alternatively, you can choose to define a custom
|
533
|
-
<code class="highlighter-rouge">excerpt_separator</code> in the post’s YAML front matter:</p>
|
534
|
+
<code class="language-plaintext highlighter-rouge">excerpt_separator</code> in the post’s YAML front matter:</p>
|
534
535
|
|
535
536
|
<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nn">---</span>
|
536
537
|
<span class="na">excerpt_separator</span><span class="pi">:</span> <span class="s"><!--more--></span>
|
@@ -541,15 +542,15 @@ Front Matter. Alternatively, you can choose to define a custom
|
|
541
542
|
<span class="s">Out-of-excerpt</span>
|
542
543
|
</code></pre></div></div>
|
543
544
|
|
544
|
-
<p>You can also set the <code class="highlighter-rouge">excerpt_separator</code> globally in your <code class="highlighter-rouge">_config.yml</code>
|
545
|
+
<p>You can also set the <code class="language-plaintext highlighter-rouge">excerpt_separator</code> globally in your <code class="language-plaintext highlighter-rouge">_config.yml</code>
|
545
546
|
configuration file.</p>
|
546
547
|
|
547
|
-
<p>Completely disable excerpts by setting your <code class="highlighter-rouge">excerpt_separator</code> to <code class="highlighter-rouge">""</code>.</p>
|
548
|
+
<p>Completely disable excerpts by setting your <code class="language-plaintext highlighter-rouge">excerpt_separator</code> to <code class="language-plaintext highlighter-rouge">""</code>.</p>
|
548
549
|
|
549
550
|
<p>Also, as with any output generated by Liquid tags, you can pass the
|
550
|
-
<code class="highlighter-rouge">| strip_html</code> filter to remove any html tags in the output. This is
|
551
|
+
<code class="language-plaintext highlighter-rouge">| strip_html</code> filter to remove any html tags in the output. This is
|
551
552
|
particularly helpful if you wish to output a post excerpt as a
|
552
|
-
<code class="highlighter-rouge">meta="description"</code> tag within the post <code class="highlighter-rouge">head</code>, or anywhere else having
|
553
|
+
<code class="language-plaintext highlighter-rouge">meta="description"</code> tag within the post <code class="language-plaintext highlighter-rouge">head</code>, or anywhere else having
|
553
554
|
html tags along with the content is not desirable.</p>
|
554
555
|
|
555
556
|
<h2 id="highlighting-code-snippets">Highlighting code snippets</h2>
|
@@ -844,7 +845,7 @@ site.</p>
|
|
844
845
|
<footer>
|
845
846
|
<div class="grid">
|
846
847
|
<div class="unit one-third center-on-mobiles">
|
847
|
-
<p>The contents of this website are <br>©
|
848
|
+
<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>
|
848
849
|
</div>
|
849
850
|
<div class="unit two-thirds align-right center-on-mobiles">
|
850
851
|
<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>Quick-start guide | 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="Quick-start guide" />
|
18
18
|
<meta property="og:locale" content="en_US" />
|
19
19
|
<meta name="description" content="If you already have a full Ruby development environment with all headers and RubyGems installed (see Jekyll’s requirements), you can create a new Jekyll site by doing the following:" />
|
@@ -22,12 +22,13 @@
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/quickstart/" />
|
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="Quick-start guide" />
|
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":"Quick-start guide","dateModified":"
|
31
|
+
{"url":"https://jekyllrb.com/docs/quickstart/","headline":"Quick-start guide","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":"If you already have a full Ruby development environment with all headers and RubyGems installed (see Jekyll’s requirements), you can create a new Jekyll site by doing the following:","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/quickstart/"},"@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>
|
@@ -315,26 +316,26 @@ bundle <span class="nb">exec </span>jekyll serve
|
|
315
316
|
|
316
317
|
<h2 id="about-bundler">About Bundler</h2>
|
317
318
|
|
318
|
-
<p><code class="highlighter-rouge">gem install jekyll bundler</code> installs the <a href="https://rubygems.org/gems/jekyll/">jekyll</a> and <a href="https://rubygems.org/gems/bundler">bundler</a> gems through <a href="https://rubygems.org/">RubyGems</a>. You need only to install the gems one time — not every time you create a new Jekyll project. Here are some additional details:</p>
|
319
|
+
<p><code class="language-plaintext highlighter-rouge">gem install jekyll bundler</code> installs the <a href="https://rubygems.org/gems/jekyll/">jekyll</a> and <a href="https://rubygems.org/gems/bundler">bundler</a> gems through <a href="https://rubygems.org/">RubyGems</a>. You need only to install the gems one time — not every time you create a new Jekyll project. Here are some additional details:</p>
|
319
320
|
|
320
321
|
<ul>
|
321
|
-
<li><code class="highlighter-rouge">bundler</code> is a gem that manages other Ruby gems. It makes sure your gems and gem versions are compatible, and that you have all necessary dependencies each gem requires.</li>
|
322
|
+
<li><code class="language-plaintext highlighter-rouge">bundler</code> is a gem that manages other Ruby gems. It makes sure your gems and gem versions are compatible, and that you have all necessary dependencies each gem requires.</li>
|
322
323
|
<li>
|
323
|
-
<p>The <code class="highlighter-rouge">Gemfile</code> and <code class="highlighter-rouge">Gemfile.lock</code> files inform Bundler about the gem requirements in your site. If your site doesn’t have these Gemfiles, you can omit <code class="highlighter-rouge">bundle exec</code> and just run <code class="highlighter-rouge">jekyll serve</code>.</p>
|
324
|
+
<p>The <code class="language-plaintext highlighter-rouge">Gemfile</code> and <code class="language-plaintext highlighter-rouge">Gemfile.lock</code> files inform Bundler about the gem requirements in your site. If your site doesn’t have these Gemfiles, you can omit <code class="language-plaintext highlighter-rouge">bundle exec</code> and just run <code class="language-plaintext highlighter-rouge">jekyll serve</code>.</p>
|
324
325
|
</li>
|
325
|
-
<li>When you run <code class="highlighter-rouge">bundle exec jekyll serve</code>, Bundler uses the gems and versions as specified in <code class="highlighter-rouge">Gemfile.lock</code> to ensure your Jekyll site builds with no compatibility or dependency conflicts.</li>
|
326
|
+
<li>When you run <code class="language-plaintext highlighter-rouge">bundle exec jekyll serve</code>, Bundler uses the gems and versions as specified in <code class="language-plaintext highlighter-rouge">Gemfile.lock</code> to ensure your Jekyll site builds with no compatibility or dependency conflicts.</li>
|
326
327
|
</ul>
|
327
328
|
|
328
329
|
<h2 id="options-for-creating-a-new-site-with-jekyll">Options for creating a new site with Jekyll</h2>
|
329
330
|
|
330
|
-
<p><code class="highlighter-rouge">jekyll new <PATH></code> installs a new Jekyll site at the path specified (relative to current directory). In this case, Jekyll will be installed in a directory called <code class="highlighter-rouge">myblog</code>. Here are some additional details:</p>
|
331
|
+
<p><code class="language-plaintext highlighter-rouge">jekyll new <PATH></code> installs a new Jekyll site at the path specified (relative to current directory). In this case, Jekyll will be installed in a directory called <code class="language-plaintext highlighter-rouge">myblog</code>. Here are some additional details:</p>
|
331
332
|
|
332
333
|
<ul>
|
333
|
-
<li>To install the Jekyll site into the directory you’re currently in, run <code class="highlighter-rouge">jekyll new .</code> If the existing directory isn’t empty, you can pass the <code class="highlighter-rouge">--force</code> option with <code class="highlighter-rouge">jekyll new . --force</code>.</li>
|
334
|
-
<li><code class="highlighter-rouge">jekyll new</code> automatically initiates <code class="highlighter-rouge">bundle install</code> to install the dependencies required. (If you don’t want Bundler to install the gems, use <code class="highlighter-rouge">jekyll new myblog --skip-bundle</code>.)</li>
|
335
|
-
<li>By default, the Jekyll site installed by <code class="highlighter-rouge">jekyll new</code> uses a gem-based theme called <a href="https://github.com/jekyll/minima">Minima</a>. With <a href="../themes">gem-based themes</a>, some of the directories and files are stored in the theme-gem, hidden from your immediate view.</li>
|
336
|
-
<li>We recommend setting up Jekyll with a gem-based theme but if you want to start with a blank slate, use <code class="highlighter-rouge">jekyll new myblog --blank</code></li>
|
337
|
-
<li>To learn about other parameters you can include with <code class="highlighter-rouge">jekyll new</code>, type <code class="highlighter-rouge">jekyll new --help</code>.</li>
|
334
|
+
<li>To install the Jekyll site into the directory you’re currently in, run <code class="language-plaintext highlighter-rouge">jekyll new .</code> If the existing directory isn’t empty, you can pass the <code class="language-plaintext highlighter-rouge">--force</code> option with <code class="language-plaintext highlighter-rouge">jekyll new . --force</code>.</li>
|
335
|
+
<li><code class="language-plaintext highlighter-rouge">jekyll new</code> automatically initiates <code class="language-plaintext highlighter-rouge">bundle install</code> to install the dependencies required. (If you don’t want Bundler to install the gems, use <code class="language-plaintext highlighter-rouge">jekyll new myblog --skip-bundle</code>.)</li>
|
336
|
+
<li>By default, the Jekyll site installed by <code class="language-plaintext highlighter-rouge">jekyll new</code> uses a gem-based theme called <a href="https://github.com/jekyll/minima">Minima</a>. With <a href="../themes">gem-based themes</a>, some of the directories and files are stored in the theme-gem, hidden from your immediate view.</li>
|
337
|
+
<li>We recommend setting up Jekyll with a gem-based theme but if you want to start with a blank slate, use <code class="language-plaintext highlighter-rouge">jekyll new myblog --blank</code></li>
|
338
|
+
<li>To learn about other parameters you can include with <code class="language-plaintext highlighter-rouge">jekyll new</code>, type <code class="language-plaintext highlighter-rouge">jekyll new --help</code>.</li>
|
338
339
|
</ul>
|
339
340
|
|
340
341
|
<p class="note info">When in doubt, use the <code>help</code> command to remind you of all available options and usage, it also works with the <code>new</code>, <code>build</code> and <code>serve</code> subcommands, e.g. <code>jekyll help new</code> or <code>jekyll help build</code>.</p>
|
@@ -571,7 +572,7 @@ bundle <span class="nb">exec </span>jekyll serve
|
|
571
572
|
<footer>
|
572
573
|
<div class="grid">
|
573
574
|
<div class="unit one-third center-on-mobiles">
|
574
|
-
<p>The contents of this website are <br />©
|
575
|
+
<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>
|
575
576
|
</div>
|
576
577
|
<div class="unit two-thirds align-right center-on-mobiles">
|
577
578
|
<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>Resources | 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="Resources" />
|
18
18
|
<meta property="og:locale" content="en_US" />
|
19
19
|
<meta name="description" content="Jekyll’s growing use is producing a wide variety of tutorials, frameworks, extensions, examples, and other resources that can be very helpful. Below is a collection of links to some of the most popular Jekyll resources." />
|
@@ -22,12 +22,13 @@
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/resources/" />
|
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="Resources" />
|
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":"Resources","dateModified":"
|
31
|
+
{"url":"https://jekyllrb.com/docs/resources/","headline":"Resources","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 growing use is producing a wide variety of tutorials, frameworks, extensions, examples, and other resources that can be very helpful. Below is a collection of links to some of the most popular Jekyll resources.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/resources/"},"@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>
|
@@ -302,7 +303,7 @@
|
|
302
303
|
<li><a href="https://atom.io/packages/jekyll">jekyll-atom</a>: A collection of snippets and tools for Jekyll in Atom</li>
|
303
304
|
<li><a href="https://atom.io/packages/markdown-writer">markdown-writer</a>: An Atom package for Jekyll. It can create new posts/drafts, manage tags/categories, insert link/images and add many useful key mappings.</li>
|
304
305
|
<li><a href="https://github.com/23maverick23/sublime-jekyll">sublime-jekyll</a>: A Sublime Text package for Jekyll static sites. This package should help creating Jekyll sites and posts easier by providing access to key template tags and filters, as well as common completions and a current date/datetime command (for dating posts). You can install this package manually via GitHub, or via <a href="https://packagecontrol.io/packages/Jekyll">Package Control</a>.</li>
|
305
|
-
<li><a href="https://github.com/parkr/vim-jekyll">vim-jekyll</a>: A vim plugin to generate new posts and run <code class="highlighter-rouge">jekyll build</code> all without leaving vim.</li>
|
306
|
+
<li><a href="https://github.com/parkr/vim-jekyll">vim-jekyll</a>: A vim plugin to generate new posts and run <code class="language-plaintext highlighter-rouge">jekyll build</code> all without leaving vim.</li>
|
306
307
|
<li><a href="https://wordpress.org/plugins/wp2jekyll/">WordPress2Jekyll</a>: A WordPress plugin that allows you to use WordPress as your editor and (automatically) export content in to Jekyll. WordPress2Jekyll attempts to marry these two systems together in order to make a site that can be easily managed from all devices.</li>
|
307
308
|
</ul>
|
308
309
|
|
@@ -687,7 +688,7 @@
|
|
687
688
|
<footer>
|
688
689
|
<div class="grid">
|
689
690
|
<div class="unit one-third center-on-mobiles">
|
690
|
-
<p>The contents of this website are <br />©
|
691
|
+
<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>
|
691
692
|
</div>
|
692
693
|
<div class="unit two-thirds align-right center-on-mobiles">
|
693
694
|
<p>
|
data/site/docs/sites/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>Sites using Jekyll | 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="Sites using Jekyll" />
|
18
18
|
<meta property="og:locale" content="en_US" />
|
19
19
|
<meta name="description" content="It’s interesting to see what designs and features others have come up with. Below are some Jekyll-powered blogs which were hand-picked for learning purposes." />
|
@@ -22,12 +22,13 @@
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/sites/" />
|
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="Sites using Jekyll" />
|
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":"Sites using Jekyll","dateModified":"
|
31
|
+
{"url":"https://jekyllrb.com/docs/sites/","headline":"Sites using Jekyll","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":"It’s interesting to see what designs and features others have come up with. Below are some Jekyll-powered blogs which were hand-picked for learning purposes.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/sites/"},"@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>
|
@@ -622,7 +623,7 @@ and their sources on the <a href="https://github.com/jekyll/jekyll/wiki/Sites">
|
|
622
623
|
<footer>
|
623
624
|
<div class="grid">
|
624
625
|
<div class="unit one-third center-on-mobiles">
|
625
|
-
<p>The contents of this website are <br />©
|
626
|
+
<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>
|
626
627
|
</div>
|
627
628
|
<div class="unit two-thirds align-right center-on-mobiles">
|
628
629
|
<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>Static 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="Static Files" />
|
18
18
|
<meta property="og:locale" content="en_US" />
|
19
19
|
<meta name="description" content="In addition to renderable and convertible content, we also have static files." />
|
@@ -22,12 +22,13 @@
|
|
22
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/static-files/" />
|
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="Static 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":"Static Files","dateModified":"
|
31
|
+
{"url":"https://jekyllrb.com/docs/static-files/","headline":"Static 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 renderable and convertible content, we also have static files.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/static-files/"},"@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>
|
@@ -300,7 +301,7 @@ files</strong>.</p>
|
|
300
301
|
<p>A static file is a file that does not contain any YAML front matter. These
|
301
302
|
include images, PDFs, and other un-rendered content.</p>
|
302
303
|
|
303
|
-
<p>They’re accessible in Liquid via <code class="highlighter-rouge">site.static_files</code> and contain the
|
304
|
+
<p>They’re accessible in Liquid via <code class="language-plaintext highlighter-rouge">site.static_files</code> and contain the
|
304
305
|
following metadata:</p>
|
305
306
|
|
306
307
|
<div class="mobile-side-scroller">
|
@@ -357,7 +358,7 @@ following metadata:</p>
|
|
357
358
|
</table>
|
358
359
|
</div>
|
359
360
|
|
360
|
-
<p>Note that in the above table, <code class="highlighter-rouge">file</code> can be anything. It’s simply an arbitrarily set variable used in your own logic (such as in a for loop). It isn’t a global site or page variable.</p>
|
361
|
+
<p>Note that in the above table, <code class="language-plaintext highlighter-rouge">file</code> can be anything. It’s simply an arbitrarily set variable used in your own logic (such as in a for loop). It isn’t a global site or page variable.</p>
|
361
362
|
|
362
363
|
<h2 id="add-front-matter-to-static-files">Add front matter to static files</h2>
|
363
364
|
|
@@ -365,7 +366,7 @@ following metadata:</p>
|
|
365
366
|
|
366
367
|
<p>Here’s an example:</p>
|
367
368
|
|
368
|
-
<p>In your <code class="highlighter-rouge">_config.yml</code> file, add the following values to the <code class="highlighter-rouge">defaults</code> property:</p>
|
369
|
+
<p>In your <code class="language-plaintext highlighter-rouge">_config.yml</code> file, add the following values to the <code class="language-plaintext highlighter-rouge">defaults</code> property:</p>
|
369
370
|
|
370
371
|
<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span>
|
371
372
|
<span class="pi">-</span> <span class="na">scope</span><span class="pi">:</span>
|
@@ -374,12 +375,12 @@ following metadata:</p>
|
|
374
375
|
<span class="na">image</span><span class="pi">:</span> <span class="no">true</span>
|
375
376
|
</code></pre></div></div>
|
376
377
|
|
377
|
-
<p>This assumes that your Jekyll site has a folder path of <code class="highlighter-rouge">assets/img</code> where you have images (static files) stored. When Jekyll builds the site, it will treat each image as if it had the front matter value of <code class="highlighter-rouge">image: true</code>.</p>
|
378
|
+
<p>This assumes that your Jekyll site has a folder path of <code class="language-plaintext highlighter-rouge">assets/img</code> where you have images (static files) stored. When Jekyll builds the site, it will treat each image as if it had the front matter value of <code class="language-plaintext highlighter-rouge">image: true</code>.</p>
|
378
379
|
|
379
|
-
<p>Suppose you want to list all your image assets as contained in <code class="highlighter-rouge">assets/img</code>. You could use this for loop to look in the <code class="highlighter-rouge">static_files</code> object and get all static files that have this front matter property:</p>
|
380
|
+
<p>Suppose you want to list all your image assets as contained in <code class="language-plaintext highlighter-rouge">assets/img</code>. You could use this for loop to look in the <code class="language-plaintext highlighter-rouge">static_files</code> object and get all static files that have this front matter property:</p>
|
380
381
|
|
381
382
|
<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">image_files</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">static_files</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">where</span><span class="p">:</span><span class="w"> </span><span class="s2">"image"</span><span class="p">,</span><span class="w"> </span><span class="kc">true</span><span class="w"> </span><span class="p">%}</span>
|
382
|
-
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span>myimage
|
383
|
+
<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span><span class="nv">myimage</span><span class="w"> </span><span class="nt">in</span><span class="w"> </span><span class="nv">image_files</span><span class="w"> </span><span class="p">%}</span>
|
383
384
|
<span class="p">{{</span><span class="w"> </span><span class="nv">myimage</span><span class="p">.</span><span class="nv">path</span><span class="w"> </span><span class="p">}}</span>
|
384
385
|
<span class="p">{%</span><span class="w"> </span><span class="nt">endfor</span><span class="w"> </span><span class="p">%}</span>
|
385
386
|
</code></pre></div></div>
|
@@ -644,7 +645,7 @@ following metadata:</p>
|
|
644
645
|
<footer>
|
645
646
|
<div class="grid">
|
646
647
|
<div class="unit one-third center-on-mobiles">
|
647
|
-
<p>The contents of this website are <br />©
|
648
|
+
<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>
|
648
649
|
</div>
|
649
650
|
<div class="unit two-thirds align-right center-on-mobiles">
|
650
651
|
<p>
|