jekyll-docs 3.6.2.0 → 3.7.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +5 -5
- data/lib/jekyll-docs.rb +7 -5
- data/site/404.html +5 -6
- data/site/community/index.html +9 -297
- data/site/conduct/index.html +3 -2
- data/site/css/screen.css +1 -1
- data/site/docs/assets/index.html +46 -30
- data/site/docs/code_of_conduct/index.html +44 -28
- data/site/docs/collections/index.html +85 -48
- data/site/docs/conduct/index.html +44 -28
- data/site/docs/configuration/index.html +66 -35
- data/site/docs/continuous-integration/buddyworks/index.html +55 -39
- data/site/docs/continuous-integration/circleci/index.html +65 -49
- data/site/docs/continuous-integration/index.html +44 -28
- data/site/docs/continuous-integration/travis-ci/index.html +45 -29
- data/site/docs/contributing/index.html +53 -33
- data/site/docs/datafiles/index.html +71 -62
- data/site/docs/deployment-methods/index.html +49 -33
- data/site/docs/drafts/index.html +44 -28
- data/site/docs/extras/index.html +44 -28
- data/site/docs/frontmatter/index.html +55 -39
- data/site/docs/github-pages/index.html +107 -111
- data/site/docs/history/index.html +299 -115
- data/site/docs/home/index.html +45 -29
- data/site/docs/includes/index.html +51 -34
- data/site/docs/index.html +3 -2
- data/site/docs/installation/index.html +65 -49
- data/site/docs/maintaining/affinity-team-captain/index.html +46 -30
- data/site/docs/maintaining/avoiding-burnout/index.html +44 -28
- data/site/docs/maintaining/becoming-a-maintainer/index.html +45 -29
- data/site/docs/maintaining/index.html +44 -28
- data/site/docs/maintaining/merging-a-pull-request/index.html +45 -29
- data/site/docs/maintaining/reviewing-a-pull-request/index.html +45 -29
- data/site/docs/maintaining/special-labels/index.html +44 -28
- data/site/docs/maintaining/triaging-an-issue/index.html +45 -29
- data/site/docs/migrations/index.html +44 -28
- data/site/docs/pages/index.html +48 -32
- data/site/docs/pagination/index.html +105 -84
- data/site/docs/permalinks/index.html +48 -32
- data/site/docs/plugins/index.html +97 -58
- data/site/docs/posts/index.html +126 -71
- data/site/docs/quickstart/index.html +48 -32
- data/site/docs/resources/index.html +46 -29
- data/site/docs/sites/index.html +44 -28
- data/site/docs/static-files/index.html +44 -28
- data/site/docs/structure/index.html +44 -28
- data/site/docs/support/index.html +725 -0
- data/site/docs/templates/index.html +77 -54
- data/site/docs/themes/index.html +63 -37
- data/site/docs/troubleshooting/index.html +56 -40
- data/site/docs/upgrading/0-to-2/index.html +45 -29
- data/site/docs/upgrading/2-to-3/index.html +50 -34
- data/site/docs/upgrading/index.html +63 -31
- data/site/docs/usage/index.html +68 -44
- data/site/docs/variables/index.html +44 -28
- data/site/docs/windows/index.html +66 -54
- data/site/feed.xml +81 -108
- data/site/github.html +3 -2
- data/site/help/index.html +66 -46
- data/site/img/jekyll-sticker.jpg +0 -0
- data/site/img/jekylllayoutconcept.png +0 -0
- data/site/img/twitter-card.png +0 -0
- data/site/index.html +43 -27
- data/site/issues.html +3 -2
- data/site/jekyllconf/index.html +315 -0
- data/site/latest_version.txt +1 -1
- data/site/news/2013/05/05/jekyll-1-0-0-released/index.html +69 -33
- data/site/news/2013/05/08/jekyll-1-0-1-released/index.html +69 -33
- data/site/news/2013/05/12/jekyll-1-0-2-released/index.html +69 -33
- data/site/news/2013/06/07/jekyll-1-0-3-released/index.html +69 -33
- data/site/news/2013/07/14/jekyll-1-1-0-released/index.html +69 -33
- data/site/news/2013/07/24/jekyll-1-1-1-released/index.html +81 -45
- data/site/news/2013/07/25/jekyll-1-0-4-released/index.html +69 -33
- data/site/news/2013/07/25/jekyll-1-1-2-released/index.html +69 -33
- data/site/news/2013/09/06/jekyll-1-2-0-released/index.html +69 -33
- data/site/news/2013/09/14/jekyll-1-2-1-released/index.html +69 -33
- data/site/news/2013/10/28/jekyll-1-3-0-rc1-released/index.html +69 -33
- data/site/news/2013/11/04/jekyll-1-3-0-released/index.html +69 -33
- data/site/news/2013/11/26/jekyll-1-3-1-released/index.html +69 -33
- data/site/news/2013/12/07/jekyll-1-4-0-released/index.html +69 -33
- data/site/news/2013/12/09/jekyll-1-4-1-released/index.html +69 -33
- data/site/news/2013/12/16/jekyll-1-4-2-released/index.html +69 -33
- data/site/news/2014/01/13/jekyll-1-4-3-released/index.html +69 -33
- data/site/news/2014/03/24/jekyll-1-5-0-released/index.html +69 -33
- data/site/news/2014/03/27/jekyll-1-5-1-released/index.html +69 -33
- data/site/news/2014/05/06/jekyll-turns-2-0-0/index.html +69 -33
- data/site/news/2014/05/08/jekyll-2-0-3-released/index.html +69 -33
- data/site/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/index.html +69 -33
- data/site/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/index.html +69 -33
- data/site/news/2014/07/01/jekyll-2-1-1-released/index.html +69 -33
- data/site/news/2014/07/29/jekyll-2-2-0-released/index.html +69 -33
- data/site/news/2014/08/10/jekyll-2-3-0-released/index.html +69 -33
- data/site/news/2014/09/09/jekyll-2-4-0-released/index.html +69 -33
- data/site/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/index.html +70 -34
- data/site/news/2014/11/09/jekyll-2-5-1-released/index.html +69 -33
- data/site/news/2014/11/12/jekyll-2-5-2-released/index.html +69 -33
- data/site/news/2014/12/17/alfredxing-welcome-to-jekyll-core/index.html +69 -33
- data/site/news/2014/12/22/jekyll-2-5-3-released/index.html +70 -34
- data/site/news/2015/01/20/jekyll-meet-and-greet/index.html +69 -33
- data/site/news/2015/01/24/jekyll-3-0-0-beta1-released/index.html +70 -34
- data/site/news/2015/02/26/introducing-jekyll-talk/index.html +69 -33
- data/site/news/2015/10/26/jekyll-3-0-released/index.html +69 -33
- data/site/news/2015/11/17/jekyll-3-0-1-released/index.html +69 -33
- data/site/news/2016/01/20/jekyll-3-0-2-released/index.html +69 -33
- data/site/news/2016/01/24/jekyll-3-1-0-released/index.html +69 -33
- data/site/news/2016/01/28/jekyll-3-1-1-released/index.html +71 -35
- data/site/news/2016/02/08/jekyll-3-0-3-released/index.html +69 -33
- data/site/news/2016/02/19/jekyll-3-1-2-released/index.html +69 -33
- data/site/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/index.html +69 -33
- data/site/news/2016/04/19/jekyll-3-0-4-released/index.html +69 -33
- data/site/news/2016/04/19/jekyll-3-1-3-released/index.html +69 -33
- data/site/news/2016/04/26/jekyll-3-0-5-released/index.html +69 -33
- data/site/news/2016/05/18/jekyll-3-1-4-released/index.html +69 -33
- data/site/news/2016/05/18/jekyll-3-1-5-released/index.html +69 -33
- data/site/news/2016/05/19/jekyll-3-1-6-released/index.html +69 -33
- data/site/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/index.html +69 -33
- data/site/news/2016/07/26/jekyll-3-2-0-released/index.html +69 -33
- data/site/news/2016/08/02/jekyll-3-2-1-released/index.html +70 -34
- data/site/news/2016/08/24/jekyll-admin-initial-release/index.html +69 -33
- data/site/news/2016/10/06/jekyll-3-3-is-here/index.html +69 -33
- data/site/news/2016/11/14/jekyll-3-3-1-released/index.html +69 -33
- data/site/news/2017/01/02/jekyll-3-7-0-released/index.html +626 -0
- data/site/news/2017/01/18/jekyll-3-4-0-released/index.html +69 -33
- data/site/news/2017/03/02/jekyll-3-4-1-released/index.html +69 -33
- data/site/news/2017/03/09/jekyll-3-4-2-released/index.html +69 -33
- data/site/news/2017/03/21/jekyll-3-4-3-released/index.html +69 -33
- data/site/news/2017/06/15/jekyll-3-5-0-released/index.html +71 -35
- data/site/news/2017/07/17/jekyll-3-5-1-released/index.html +69 -33
- data/site/news/2017/08/12/jekyll-3-5-2-released/index.html +69 -33
- data/site/news/2017/09/21/jekyll-3-6-0-released/index.html +69 -33
- data/site/news/2017/10/19/diversity-open-source/index.html +631 -0
- data/site/news/2017/10/21/jekyll-3-6-2-released/index.html +627 -0
- data/site/news/index.html +270 -49
- data/site/news/releases/index.html +204 -49
- data/site/redirects.json +1 -0
- data/site/sitemap.xml +77 -57
- data/site/tutorials/convert-site-to-jekyll/index.html +58 -31
- data/site/tutorials/custom-404-page/index.html +70 -42
- data/site/tutorials/home/index.html +53 -29
- data/site/tutorials/index.html +3 -2
- data/site/tutorials/navigation/index.html +70 -38
- data/site/tutorials/orderofinterpretation/index.html +61 -34
- data/site/tutorials/video-walkthroughs/index.html +352 -0
- metadata +17 -12
- data/site/CNAME +0 -1
- data/site/icomoon-selection.json +0 -96
- data/site/readme.md +0 -23
|
@@ -4,14 +4,16 @@
|
|
|
4
4
|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
|
5
5
|
<meta charset="UTF-8">
|
|
6
6
|
<meta name="viewport" content="width=device-width,initial-scale=1">
|
|
7
|
-
<meta name="generator" content="Jekyll v3.
|
|
7
|
+
<meta name="generator" content="Jekyll v3.7.0">
|
|
8
8
|
<link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites">
|
|
9
9
|
<link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
|
|
10
10
|
<link rel="stylesheet" href="//fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
|
|
11
|
+
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css">
|
|
11
12
|
<link rel="stylesheet" href="/css/screen.css">
|
|
12
13
|
<link rel="icon" type="image/x-icon" href="/favicon.ico">
|
|
13
|
-
<!-- Begin Jekyll SEO tag v2.
|
|
14
|
+
<!-- Begin Jekyll SEO tag v2.4.0 -->
|
|
14
15
|
<title>Jekyll on Windows | Jekyll • Simple, blog-aware, static sites</title>
|
|
16
|
+
<meta name="generator" content="Jekyll v3.7.0">
|
|
15
17
|
<meta property="og:title" content="Jekyll on Windows">
|
|
16
18
|
<meta property="og:locale" content="en_US">
|
|
17
19
|
<meta name="description" content="While Windows is not an officially-supported platform, it can be used to run Jekyll with the proper tweaks. This page aims to collect some of the general knowledge and lessons that have been unearthed by Windows users.">
|
|
@@ -20,12 +22,12 @@
|
|
|
20
22
|
<meta property="og:url" content="https://jekyllrb.com/docs/windows/">
|
|
21
23
|
<meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites">
|
|
22
24
|
<meta property="og:type" content="article">
|
|
23
|
-
<meta property="article:published_time" content="
|
|
25
|
+
<meta property="article:published_time" content="2018-01-03T02:41:17-08:00">
|
|
24
26
|
<meta name="twitter:card" content="summary">
|
|
25
27
|
<meta name="twitter:site" content="@jekyllrb">
|
|
26
28
|
<meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY">
|
|
27
29
|
<script type="application/ld+json">
|
|
28
|
-
{"
|
|
30
|
+
{"headline":"Jekyll on Windows","dateModified":"2018-01-03T02:41:17-08:00","datePublished":"2018-01-03T02:41:17-08:00","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/windows/"},"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"url":"https://jekyllrb.com/docs/windows/","description":"While Windows is not an officially-supported platform, it can be used to run Jekyll with the proper tweaks. This page aims to collect some of the general knowledge and lessons that have been unearthed by Windows users.","@type":"BlogPosting","@context":"http://schema.org"}</script>
|
|
29
31
|
<!-- End Jekyll SEO tag -->
|
|
30
32
|
|
|
31
33
|
<!--[if lt IE 9]>
|
|
@@ -37,8 +39,17 @@
|
|
|
37
39
|
|
|
38
40
|
<body class="wrap">
|
|
39
41
|
<header>
|
|
40
|
-
<
|
|
41
|
-
<
|
|
42
|
+
<div class="flexbox">
|
|
43
|
+
<div class="center-on-mobiles">
|
|
44
|
+
<h1>
|
|
45
|
+
<a href="/" class="logo">
|
|
46
|
+
<span class="sr-only">Jekyll</span>
|
|
47
|
+
<img src="/img/logo-2x.png" width="140" height="65" alt="Jekyll Logo">
|
|
48
|
+
</a>
|
|
49
|
+
</h1>
|
|
50
|
+
</div>
|
|
51
|
+
<nav class="main-nav hide-on-mobiles">
|
|
52
|
+
<ul>
|
|
42
53
|
<li class="">
|
|
43
54
|
<a href="/">Home</a>
|
|
44
55
|
</li>
|
|
@@ -48,29 +59,29 @@
|
|
|
48
59
|
<li class="">
|
|
49
60
|
<a href="/news/">News</a>
|
|
50
61
|
</li>
|
|
51
|
-
<li class="">
|
|
52
|
-
<a href="/community/">Community</a>
|
|
53
|
-
</li>
|
|
54
62
|
<li class="">
|
|
55
63
|
<a href="/help/">Help</a>
|
|
56
64
|
</li>
|
|
57
|
-
<li>
|
|
58
|
-
<a href="https://github.com/jekyll/jekyll">GitHub</a>
|
|
59
|
-
</li>
|
|
60
65
|
</ul>
|
|
61
66
|
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
<a href="/">
|
|
67
|
-
<span class="sr-only">Jekyll</span>
|
|
68
|
-
<img src="/img/logo-2x.png" width="249" height="115" alt="Jekyll Logo">
|
|
69
|
-
</a>
|
|
70
|
-
</h1>
|
|
67
|
+
</nav>
|
|
68
|
+
<div class="search hide-on-mobiles">
|
|
69
|
+
<input type="text" id="docsearch-input" placeholder="Search the docs…">
|
|
70
|
+
|
|
71
71
|
</div>
|
|
72
|
-
<
|
|
72
|
+
<div class="meta hide-on-mobiles">
|
|
73
73
|
<ul>
|
|
74
|
+
<li>
|
|
75
|
+
<a href="https://github.com/jekyll/jekyll/releases/tag/v3.7.0">v3.7.0</a>
|
|
76
|
+
</li>
|
|
77
|
+
<li>
|
|
78
|
+
<a href="https://github.com/jekyll/jekyll">GitHub</a>
|
|
79
|
+
</li>
|
|
80
|
+
</ul>
|
|
81
|
+
</div>
|
|
82
|
+
</div>
|
|
83
|
+
<nav class="mobile-nav show-on-mobiles">
|
|
84
|
+
<ul>
|
|
74
85
|
<li class="">
|
|
75
86
|
<a href="/">Home</a>
|
|
76
87
|
</li>
|
|
@@ -80,9 +91,6 @@
|
|
|
80
91
|
<li class="">
|
|
81
92
|
<a href="/news/">News</a>
|
|
82
93
|
</li>
|
|
83
|
-
<li class="">
|
|
84
|
-
<a href="/community/">Community</a>
|
|
85
|
-
</li>
|
|
86
94
|
<li class="">
|
|
87
95
|
<a href="/help/">Help</a>
|
|
88
96
|
</li>
|
|
@@ -91,8 +99,7 @@
|
|
|
91
99
|
</li>
|
|
92
100
|
</ul>
|
|
93
101
|
|
|
94
|
-
|
|
95
|
-
</div>
|
|
102
|
+
</nav>
|
|
96
103
|
</header>
|
|
97
104
|
|
|
98
105
|
|
|
@@ -299,39 +306,39 @@
|
|
|
299
306
|
|
|
300
307
|
<p>First let’s make sure all our packages / repositories are up to date. Open a new Command Prompt instance, and type the following:</p>
|
|
301
308
|
|
|
302
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>bash
|
|
309
|
+
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>bash
|
|
303
310
|
</code></pre></div></div>
|
|
304
311
|
<p>Your Command Prompt instance should now be a Bash instance. Now we must update our repo lists and packages.</p>
|
|
305
312
|
|
|
306
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>sudo apt-get update
|
|
313
|
+
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">sudo </span>apt-get update <span class="nt">-y</span> <span class="o">&&</span> <span class="nb">sudo </span>apt-get upgrade <span class="nt">-y</span>
|
|
307
314
|
</code></pre></div></div>
|
|
308
315
|
<p>Now we can install Ruby. To do this we will use a repository from <a href="https://www.brightbox.com/docs/ruby/ubuntu/">BrightBox</a>, which hosts optimized versions of Ruby for Ubuntu.</p>
|
|
309
316
|
|
|
310
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>sudo apt-add-repository ppa:brightbox/ruby-ng
|
|
311
|
-
sudo apt-get update
|
|
312
|
-
sudo apt-get install ruby2.3 ruby2.3-dev build-essential
|
|
317
|
+
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">sudo </span>apt-add-repository ppa:brightbox/ruby-ng
|
|
318
|
+
<span class="nb">sudo </span>apt-get update
|
|
319
|
+
<span class="nb">sudo </span>apt-get <span class="nb">install </span>ruby2.3 ruby2.3-dev build-essential
|
|
313
320
|
</code></pre></div></div>
|
|
314
321
|
|
|
315
322
|
<p>Next let’s update our Ruby gems:</p>
|
|
316
323
|
|
|
317
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>sudo gem update
|
|
324
|
+
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">sudo </span>gem update
|
|
318
325
|
</code></pre></div></div>
|
|
319
326
|
|
|
320
327
|
<p>Now all that is left to do is install Jekyll.</p>
|
|
321
328
|
|
|
322
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>sudo gem install jekyll bundler
|
|
329
|
+
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">sudo </span>gem <span class="nb">install </span>jekyll bundler
|
|
323
330
|
</code></pre></div></div>
|
|
324
331
|
|
|
325
332
|
<p>Check if Jekyll installed properly by running:</p>
|
|
326
333
|
|
|
327
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>jekyll
|
|
334
|
+
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>jekyll <span class="nt">-v</span>
|
|
328
335
|
</code></pre></div></div>
|
|
329
336
|
|
|
330
337
|
<p><strong>And that’s it!</strong></p>
|
|
331
338
|
|
|
332
339
|
<p>To start a new project named <code class="highlighter-rouge">my_blog</code>, just run:</p>
|
|
333
340
|
|
|
334
|
-
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>jekyll new my_blog
|
|
341
|
+
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>jekyll new my_blog
|
|
335
342
|
</code></pre></div></div>
|
|
336
343
|
|
|
337
344
|
<p>You can make sure time management is working properly by inspecting your <code class="highlighter-rouge">_posts</code> folder. You should see a markdown file with the current date in the filename.</p>
|
|
@@ -401,20 +408,20 @@ sudo apt-get install ruby2.3 ruby2.3-dev build-essential
|
|
|
401
408
|
|
|
402
409
|
<p><strong>Note:</strong> In the current <a href="https://github.com/sparklemotion/nokogiri/issues/1456#issuecomment-206481794" title="Nokogiri fails to install on Ruby 2.3 for Windows">pre release</a> it works out of the box with Windows x64 but this version is not referenced in the github-pages.</p>
|
|
403
410
|
|
|
404
|
-
<
|
|
411
|
+
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>choco <span class="nb">install </span>libxml2 <span class="nt">-Source</span> <span class="s2">"https://www.nuget.org/api/v2/"</span>
|
|
405
412
|
|
|
406
|
-
|
|
413
|
+
choco <span class="nb">install </span>libxslt <span class="nt">-Source</span> <span class="s2">"https://www.nuget.org/api/v2/"</span>
|
|
407
414
|
|
|
408
|
-
|
|
415
|
+
choco <span class="nb">install </span>libiconv <span class="nt">-Source</span> <span class="s2">"https://www.nuget.org/api/v2/
|
|
409
416
|
|
|
410
|
-
|
|
411
|
-
|
|
412
|
-
|
|
413
|
-
|
|
414
|
-
|
|
415
|
-
|
|
416
|
-
|
|
417
|
-
</code></pre></div></div>
|
|
417
|
+
gem install nokogiri --^
|
|
418
|
+
--with-xml2-include=C:</span><span class="se">\C</span><span class="s2">hocolatey</span><span class="se">\l</span><span class="s2">ib</span><span class="se">\l</span><span class="s2">ibxml2.2.7.8.7</span><span class="se">\b</span><span class="s2">uild</span><span class="se">\n</span><span class="s2">ative</span><span class="se">\i</span><span class="s2">nclude^
|
|
419
|
+
--with-xml2-lib=C:</span><span class="se">\C</span><span class="s2">hocolatey</span><span class="se">\l</span><span class="s2">ib</span><span class="se">\l</span><span class="s2">ibxml2.redist.2.7.8.7</span><span class="se">\b</span><span class="s2">uild</span><span class="se">\n</span><span class="s2">ative</span><span class="se">\b</span><span class="s2">in</span><span class="se">\v</span><span class="s2">110</span><span class="se">\x</span><span class="s2">64</span><span class="se">\R</span><span class="s2">elease</span><span class="se">\d</span><span class="s2">ynamic</span><span class="se">\c</span><span class="s2">decl^
|
|
420
|
+
--with-iconv-include=C:</span><span class="se">\C</span><span class="s2">hocolatey</span><span class="se">\l</span><span class="s2">ib</span><span class="se">\l</span><span class="s2">ibiconv.1.14.0.11</span><span class="se">\b</span><span class="s2">uild</span><span class="se">\n</span><span class="s2">ative</span><span class="se">\i</span><span class="s2">nclude^
|
|
421
|
+
--with-iconv-lib=C:</span><span class="se">\C</span><span class="s2">hocolatey</span><span class="se">\l</span><span class="s2">ib</span><span class="se">\l</span><span class="s2">ibiconv.redist.1.14.0.11</span><span class="se">\b</span><span class="s2">uild</span><span class="se">\n</span><span class="s2">ative</span><span class="se">\b</span><span class="s2">in</span><span class="se">\v</span><span class="s2">110</span><span class="se">\x</span><span class="s2">64</span><span class="se">\R</span><span class="s2">elease</span><span class="se">\d</span><span class="s2">ynamic</span><span class="se">\c</span><span class="s2">decl^
|
|
422
|
+
--with-xslt-include=C:</span><span class="se">\C</span><span class="s2">hocolatey</span><span class="se">\l</span><span class="s2">ib</span><span class="se">\l</span><span class="s2">ibxslt.1.1.28.0</span><span class="se">\b</span><span class="s2">uild</span><span class="se">\n</span><span class="s2">ative</span><span class="se">\i</span><span class="s2">nclude^
|
|
423
|
+
--with-xslt-lib=C:</span><span class="se">\C</span><span class="s2">hocolatey</span><span class="se">\l</span><span class="s2">ib</span><span class="se">\l</span><span class="s2">ibxslt.redist.1.1.28.0</span><span class="se">\b</span><span class="s2">uild</span><span class="se">\n</span><span class="s2">ative</span><span class="se">\b</span><span class="s2">in</span><span class="se">\v</span><span class="s2">110</span><span class="se">\x</span><span class="s2">64</span><span class="se">\R</span><span class="s2">elease</span><span class="se">\d</span><span class="s2">ynamic
|
|
424
|
+
</span></code></pre></div></div>
|
|
418
425
|
|
|
419
426
|
<h4 id="install-github-pages">Install github-pages</h4>
|
|
420
427
|
|
|
@@ -441,14 +448,10 @@ There will be a warning on startup that you should include <code class="highligh
|
|
|
441
448
|
|
|
442
449
|
<p>In the future the installation process of the github-pages should be as simple as the setup of the blog. But as long as the new version of the Nokogiri (<a href="https://github.com/sparklemotion/nokogiri/releases" title="Nokogiri Releases">v1.6.8</a>) is not stable and referenced, it is work to get it up and running on Windows.</p>
|
|
443
450
|
|
|
444
|
-
<hr>
|
|
445
|
-
|
|
446
451
|
<p>For a more conventional way of installing Jekyll you can follow this <a href="https://labs.sverrirs.com/jekyll/">complete guide to install Jekyll 3 on Windows by Sverrir Sigmundarson</a>.</p>
|
|
447
452
|
|
|
448
453
|
<p>Optionally you can use <a href="https://github.com/KeJunMao/fastjekyll#autoinstall-jekyll-for-windows">Autoinstall Jekyll for Windows</a>.</p>
|
|
449
454
|
|
|
450
|
-
<hr>
|
|
451
|
-
|
|
452
455
|
<h2 id="encoding">Encoding</h2>
|
|
453
456
|
|
|
454
457
|
<p>If you use UTF-8 encoding, make sure that no <code class="highlighter-rouge">BOM</code> header characters exist in your files or very, very bad things will happen to
|
|
@@ -456,7 +459,7 @@ Jekyll. This is especially relevant when you’re running Jekyll on Windows.</p>
|
|
|
456
459
|
|
|
457
460
|
<p>Additionally, you might need to change the code page of the console window to UTF-8 in case you get a “Liquid Exception: Incompatible character encoding” error during the site generation process. It can be done with the following command:</p>
|
|
458
461
|
|
|
459
|
-
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code
|
|
462
|
+
<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>chcp 65001
|
|
460
463
|
</code></pre></div></div>
|
|
461
464
|
|
|
462
465
|
<h2 id="time-zone-management">Time-Zone Management</h2>
|
|
@@ -473,7 +476,7 @@ While ‘new’ blogs created with Jekyll v3.4 and greater, will have the follow
|
|
|
473
476
|
|
|
474
477
|
<h2 id="auto-regeneration">Auto Regeneration</h2>
|
|
475
478
|
|
|
476
|
-
<p>
|
|
479
|
+
<p>Jekyll uses the <code class="highlighter-rouge">listen</code> gem to watch for changes when the <code class="highlighter-rouge">--watch</code> switch is specified during a build or serve. While <code class="highlighter-rouge">listen</code> has built-in support for UNIX systems, it may require an extra gem for compatibility with Windows.</p>
|
|
477
480
|
|
|
478
481
|
<p>Add the following to the Gemfile for your site if you have issues with auto-regeneration on Windows alone:</p>
|
|
479
482
|
|
|
@@ -716,7 +719,7 @@ While ‘new’ blogs created with Jekyll v3.4 and greater, will have the follow
|
|
|
716
719
|
<footer>
|
|
717
720
|
<div class="grid">
|
|
718
721
|
<div class="unit one-third center-on-mobiles">
|
|
719
|
-
<p>The contents of this website are <br>©
|
|
722
|
+
<p>The contents of this website are <br>© 2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
|
|
720
723
|
</div>
|
|
721
724
|
<div class="unit two-thirds align-right center-on-mobiles">
|
|
722
725
|
<p>
|
|
@@ -794,6 +797,15 @@ While ‘new’ blogs created with Jekyll v3.4 and greater, will have the follow
|
|
|
794
797
|
</script>
|
|
795
798
|
|
|
796
799
|
|
|
800
|
+
<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.js"></script>
|
|
801
|
+
<script type="text/javascript"> docsearch({
|
|
802
|
+
apiKey: '50fe39c839958dfad797000f33e2ec17',
|
|
803
|
+
indexName: 'jekyllrb',
|
|
804
|
+
inputSelector: '#docsearch-input',
|
|
805
|
+
enhancedSearchInput: true,
|
|
806
|
+
debug: false // Set debug to true if you want to inspect the dropdown
|
|
807
|
+
});
|
|
808
|
+
</script>
|
|
797
809
|
|
|
798
810
|
</body>
|
|
799
811
|
</html>
|
data/site/feed.xml
CHANGED
|
@@ -1,4 +1,76 @@
|
|
|
1
|
-
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.
|
|
1
|
+
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.7.0">Jekyll</generator><link href="https://jekyllrb.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://jekyllrb.com/" rel="alternate" type="text/html" /><updated>2018-01-03T02:41:17-08:00</updated><id>https://jekyllrb.com/</id><title type="html">Jekyll • Simple, blog-aware, static sites</title><subtitle>Transform your plain text into static websites and blogs</subtitle><entry><title type="html">Jekyll 3.6.2 Released</title><link href="https://jekyllrb.com/news/2017/10/21/jekyll-3-6-2-released/" rel="alternate" type="text/html" title="Jekyll 3.6.2 Released" /><published>2017-10-21T12:31:40-07:00</published><updated>2017-10-21T12:31:40-07:00</updated><id>https://jekyllrb.com/news/2017/10/21/jekyll-3-6-2-released</id><content type="html" xml:base="https://jekyllrb.com/news/2017/10/21/jekyll-3-6-2-released/"><p>3.6.2 is out, it’s a tiny patch release and we invite you to run <code class="highlighter-rouge">bundle update</code>
|
|
2
|
+
if you want to avoid possible build problems with:</p>
|
|
3
|
+
|
|
4
|
+
<ul>
|
|
5
|
+
<li>some UTF-8 and UTF-16 encoded files,</li>
|
|
6
|
+
<li>fully numeric layout names (we convert those to string for you now).</li>
|
|
7
|
+
</ul>
|
|
8
|
+
|
|
9
|
+
<p>Other changes include updates to our documentation, like this <a href="../tutorials/video-walkthroughs/">complete
|
|
10
|
+
video series by Giraffe Academy</a> aimed at
|
|
11
|
+
complete beginners. A big thanks to Mike for this.</p>
|
|
12
|
+
|
|
13
|
+
<p>And if you’re wondering what happened to version 3.6.1, it was just our new
|
|
14
|
+
release maintainer getting familiar with the release process. 😄</p>
|
|
15
|
+
|
|
16
|
+
<p>We try to release patch releases as quickly as possible and we’re already
|
|
17
|
+
working on the next minor version 3.7.0 that will allow you to store all your
|
|
18
|
+
collections in a single directory. Stay tuned.</p>
|
|
19
|
+
|
|
20
|
+
<p>Theme developers are invited to test the brand new
|
|
21
|
+
<a href="https://github.com/benbalter/jekyll-remote-theme"><code class="highlighter-rouge">jekyll-remote-theme</code></a> plugin
|
|
22
|
+
and give their feedback to @benbalter. This plugin allows you to use any
|
|
23
|
+
GitHub hosted theme as a remote theme!</p>
|
|
24
|
+
|
|
25
|
+
<p>Once again, many thanks to our contributors who helped make this release possible:
|
|
26
|
+
ashmaroli, bellvat, Frank Taillandier, i-give-up, Jan Piotrowski, Maximiliano
|
|
27
|
+
Kotvinsky, Oliver Steele and Pat Hawks. For some it was their <a href="/news/2017/10/19/diversity-open-source/">first
|
|
28
|
+
contribution to open-source</a> 👏</p>
|
|
29
|
+
|
|
30
|
+
<p>As it’s been nine years this week that Tom Preston-Werner started this project,
|
|
31
|
+
I also wanna seize this opportunity to thank <a href="https://github.com/jekyll/jekyll/graphs/contributors">all of the 732 contributors</a> who
|
|
32
|
+
helped make it possible for Jekyll to power millions of websites around the world
|
|
33
|
+
today.</p>
|
|
34
|
+
|
|
35
|
+
<p>Happy Birthday Jekyll! 🎂</p></content><author><name>dirtyf</name></author><summary type="html">3.6.2 is out, it’s a tiny patch release and we invite you to run bundle update if you want to avoid possible build problems with:</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry><entry><title type="html">Diversity in Open Source, and Jekyll’s role in it</title><link href="https://jekyllrb.com/news/2017/10/19/diversity-open-source/" rel="alternate" type="text/html" title="Diversity in Open Source, and Jekyll's role in it" /><published>2017-10-19T12:33:00-07:00</published><updated>2017-10-19T12:33:00-07:00</updated><id>https://jekyllrb.com/news/2017/10/19/diversity-open-source</id><content type="html" xml:base="https://jekyllrb.com/news/2017/10/19/diversity-open-source/"><p>Open Source has a problem with diversity. GitHub recently conducted a <a href="http://opensourcesurvey.org/2017">survey</a> which revealed that 95% of the respondents were identifying as male. This is even worse than in the tech industry overall, where the percentage is only about 76%. Every other week, there seems to be another case of a maintainer engaging in targeted harassment against minorities. People somehow deem it completely okay to let these things slide, though.</p>
|
|
36
|
+
|
|
37
|
+
<p>Fortunately, there’s a couple of things we can do to make it easier and more comfortable for people that have never contributed to any open source project before, to contribute to our projects.</p>
|
|
38
|
+
|
|
39
|
+
<h2 id="add-a-code-of-conduct-and-enforce-it">Add a Code of Conduct, and enforce it</h2>
|
|
40
|
+
|
|
41
|
+
<p>This might seem like one of the easiest steps to do, but it actually requires a lot of dedication to pull through with. Basically, a Code of Conduct is a document detailing what is and what isn’t acceptable behavior in your project. A good Code of Conduct also details enforcement procedures, that means how the person violating the Code of Conduct gets dealt with. This is the point at which I’ve seen a looooot of projects fail. It’s easy enough to copy-paste a Code of Conduct into your project, but it’s more important to be clear on how to enforce it. Inconsistent —or worse, nonexistent— enforcement is just going to scare off newcomers even more!</p>
|
|
42
|
+
|
|
43
|
+
<p>The most widely adopted Code of Conduct is the <a href="https://www.contributor-covenant.org/">Contributor Covenant</a>. It’s a very good catch-all document, but it is a bit light in the enforcement section, so I’d recommend to flesh it out by yourself, be it by means of adding contact information or expanding the enforcement rules.</p>
|
|
44
|
+
|
|
45
|
+
<p>No matter which Code of Conduct you pick, the most important thing is to actually <em>read it for yourself</em>. The worst thing in open source is a maintainer that doesn’t know when they’ve violated their own Code of Conduct.</p>
|
|
46
|
+
|
|
47
|
+
<h2 id="document-your-contributing-workflow">Document your contributing workflow</h2>
|
|
48
|
+
|
|
49
|
+
<p>The problem that puts people off the most is incomplete or missing documentation, as revealed through GitHub’s <a href="http://opensourcesurvey.org/2017">open source survey</a>. A very popular myth in programming is that good code explains itself, which might be true, but only for the person writing it. It’s important, especially once you put your project out there for the world to see, to document not only your code, but also the process by which you maintain it. Otherwise, it’s going to be extremely hard for newcomers to even figure out where to begin contributing to your project.</p>
|
|
50
|
+
|
|
51
|
+
<p>Jekyll has <a href="/docs/contributing">an entire section of its docs</a> dedicated to information on how to contribute for this very reason. Every documentation page has a link to directly edit and improve it on GitHub. It’s also important to realize that not all contributions are code. It can be documentation, it can be reviewing pull requests, but it can also just be weighing into issues, and all of this should be recognized in the same way. At Jekyll, out of 397 total merged pull requests in the last year, <strong>204</strong> were documentation pull requests!</p>
|
|
52
|
+
|
|
53
|
+
<h2 id="create-newcomer-friendly-issues">Create newcomer-friendly issues</h2>
|
|
54
|
+
|
|
55
|
+
<p>For most people new to open source, the biggest hurdle is creating their first pull request. That’s why initiatives such as <a href="https://twitter.com/yourfirstpr">YourFirstPR</a> and <a href="http://www.firsttimersonly.com/">First Timers Only</a> were started. Recently, <a href="https://github.com/hoodiehq/first-timers-bot">a GitHub bot that automatically creates first-timer friendly issues</a> was launched, which makes it very easy for maintainers to convert otherwise small or trivial changes into viable pull requests that can be taken on by newcomers! So we decided to give it a shot, and we’ve created a couple of very easy <code class="highlighter-rouge">first timers only</code> issues:</p>
|
|
56
|
+
|
|
57
|
+
<ul>
|
|
58
|
+
<li><a href="https://github.com/jekyll/jekyll/issues/6437">Issue #6437</a></li>
|
|
59
|
+
<li><a href="https://github.com/jekyll/jekyll/issues/6438">Issue #6438</a></li>
|
|
60
|
+
<li><a href="https://github.com/jekyll/jekyll/issues/6439">Issue #6439</a></li>
|
|
61
|
+
</ul>
|
|
62
|
+
|
|
63
|
+
<p>(There’s also an up-to-date listing of all of our <code class="highlighter-rouge">first timers only</code> issues <a href="https://github.com/jekyll/jekyll/issues?q=is%3Aissue+is%3Aopen+label%3Afirst-time-only">here</a>)</p>
|
|
64
|
+
|
|
65
|
+
<p>These issues are designed to be taken on only by someone who has had little to no exposure to contributing to open source before, and additionally, project maintainers offer support in case a question arises.</p>
|
|
66
|
+
|
|
67
|
+
<p>Jekyll is a very big and popular open source project, and we hope that with these special issues, we can help people who haven’t contributed to open source before to catch a footing in these unsteady waters.</p>
|
|
68
|
+
|
|
69
|
+
<h2 id="be-nice">Be nice</h2>
|
|
70
|
+
|
|
71
|
+
<p>I know this is a cliche and a overused phrase, but really, it works if you pull through with it. Come to terms with the fact that some people aren’t as fast or reliable as you might want to think. Don’t get angry when a contributor takes a day longer than you might like them to. Treat new contributors to your project with respect, but also with hospitality. Think twice before you send that comment with slurs in it.</p>
|
|
72
|
+
|
|
73
|
+
<p>I’ve been contributing to open source for about 4 years now, and I’ve had my fair share of horrible, horrible experiences. But Jekyll has historically been a project that has always valued the people contributing to it over the code itself, and I hope we can keep it that way. I also hope that other project maintainers read this and take inspiration from this post. Every project should be more diverse.</p></content><author><name>pup</name></author><summary type="html">Open Source has a problem with diversity. GitHub recently conducted a survey which revealed that 95% of the respondents were identifying as male. This is even worse than in the tech industry overall, where the percentage is only about 76%. Every other week, there seems to be another case of a maintainer engaging in targeted harassment against minorities. People somehow deem it completely okay to let these things slide, though.</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry><entry><title type="html">Jekyll turns 3.6!</title><link href="https://jekyllrb.com/news/2017/09/21/jekyll-3-6-0-released/" rel="alternate" type="text/html" title="Jekyll turns 3.6!" /><published>2017-09-21T13:38:20-07:00</published><updated>2017-09-21T13:38:20-07:00</updated><id>https://jekyllrb.com/news/2017/09/21/jekyll-3-6-0-released</id><content type="html" xml:base="https://jekyllrb.com/news/2017/09/21/jekyll-3-6-0-released/"><p>Another much-anticipated release of Jekyll. This release comes with it Rouge 2 support, but note you can continue to use Rouge 1 if you’d prefer. We also now require Ruby 2.1.0 as 2.0.x is no longer supported by the Ruby team.</p>
|
|
2
74
|
|
|
3
75
|
<p>Otherwise, it’s a massive bug-fix release! A few bugs were found and squashed with our <code class="highlighter-rouge">Drop</code> implementation. We’re using the Schwartzian transform to speed up our custom sorting (thanks, Perl community!). We now protect against images that are named like posts and we generally worked on guarding our code to enforce requirements, instead of assuming the input was as expected.</p>
|
|
4
76
|
|
|
@@ -6,7 +78,7 @@
|
|
|
6
78
|
|
|
7
79
|
<p>Many thanks to our contributors who helped make this release possible: Aleksander Kuś, André Jaenisch, Antonio Argote, ashmaroli, Ben Balter, Bogdan, Bradley Meck, David Zhang, Florian Thomas, Frank Taillandier, Jordon Bedwell, Joshua Byrd, Kyle Zhao, lymaconsulting, Maciej Bembenista, Matt Sturgeon, Natanael Arndt, Ohad Schneider, Pat Hawks, Pedro Lamas, and Sid Verma.</p>
|
|
8
80
|
|
|
9
|
-
<p>As always, Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">Another much-anticipated release of Jekyll. This release comes with it Rouge 2 support, but note you can continue to use Rouge 1 if you’d prefer. We also now require Ruby 2.1.0 as 2.0.x is no longer supported by the Ruby team.</summary
|
|
81
|
+
<p>As always, Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">Another much-anticipated release of Jekyll. This release comes with it Rouge 2 support, but note you can continue to use Rouge 1 if you’d prefer. We also now require Ruby 2.1.0 as 2.0.x is no longer supported by the Ruby team.</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry><entry><title type="html">Jekyll 3.5.2 Released</title><link href="https://jekyllrb.com/news/2017/08/12/jekyll-3-5-2-released/" rel="alternate" type="text/html" title="Jekyll 3.5.2 Released" /><published>2017-08-12T13:31:40-07:00</published><updated>2017-08-12T13:31:40-07:00</updated><id>https://jekyllrb.com/news/2017/08/12/jekyll-3-5-2-released</id><content type="html" xml:base="https://jekyllrb.com/news/2017/08/12/jekyll-3-5-2-released/"><p>3.5.2 is out with 6 great bug fixes, most notably one which should dramatically speed up generation of your site! In testing #6266, jekyllrb.com generation when from 18 seconds down to 8! Here is the full line-up of fixes:</p>
|
|
10
82
|
|
|
11
83
|
<ul>
|
|
12
84
|
<li>Backport #6266 for v3.5.x: Memoize the return value of <code class="highlighter-rouge">Document#url</code> (#6301)</li>
|
|
@@ -22,7 +94,7 @@
|
|
|
22
94
|
<p>Many thanks to our contributors without whom this release could not be
|
|
23
95
|
possible: Ben Balter &amp; Kyle Zhao.</p>
|
|
24
96
|
|
|
25
|
-
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">3.5.2 is out with 6 great bug fixes, most notably one which should dramatically speed up generation of your site! In testing #6266, jekyllrb.com generation when from 18 seconds down to 8! Here is the full line-up of fixes:</summary
|
|
97
|
+
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">3.5.2 is out with 6 great bug fixes, most notably one which should dramatically speed up generation of your site! In testing #6266, jekyllrb.com generation when from 18 seconds down to 8! Here is the full line-up of fixes:</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry><entry><title type="html">Jekyll 3.5.1 Released</title><link href="https://jekyllrb.com/news/2017/07/17/jekyll-3-5-1-released/" rel="alternate" type="text/html" title="Jekyll 3.5.1 Released" /><published>2017-07-17T09:40:37-07:00</published><updated>2017-07-17T09:40:37-07:00</updated><id>https://jekyllrb.com/news/2017/07/17/jekyll-3-5-1-released</id><content type="html" xml:base="https://jekyllrb.com/news/2017/07/17/jekyll-3-5-1-released/"><p>We’ve released a few bugfixes in the form of v3.5.1 today:</p>
|
|
26
98
|
|
|
27
99
|
<ul>
|
|
28
100
|
<li>Some plugins stopped functioning properly due to a NoMethodError for <code class="highlighter-rouge">registers</code> on NilClass. That’s been fixed.</li>
|
|
@@ -34,7 +106,7 @@ possible: Ben Balter &amp; Kyle Zhao.</p>
|
|
|
34
106
|
|
|
35
107
|
<p>More details in <a href="/docs/history/#v3-5-1">the history</a>. Many thanks to all the contributors to Jekyll v3.5.1: Adam Voss, ashmaroli, Ben Balter, Coby Chapple, Doug Beney, Fadhil, Florian Thomas, Frank Taillandier, James, jaybe, Joshua Byrd, Kevin Plattret, &amp; Robert Jäschke.</p>
|
|
36
108
|
|
|
37
|
-
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">We’ve released a few bugfixes in the form of v3.5.1 today:</summary
|
|
109
|
+
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">We’ve released a few bugfixes in the form of v3.5.1 today:</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry><entry><title type="html">Jekyll turns 3.5, oh my!</title><link href="https://jekyllrb.com/news/2017/06/15/jekyll-3-5-0-released/" rel="alternate" type="text/html" title="Jekyll turns 3.5, oh my!" /><published>2017-06-15T14:32:32-07:00</published><updated>2017-06-15T14:32:32-07:00</updated><id>https://jekyllrb.com/news/2017/06/15/jekyll-3-5-0-released</id><content type="html" xml:base="https://jekyllrb.com/news/2017/06/15/jekyll-3-5-0-released/"><p>Good news! Nearly 400 commits later, Jekyll 3.5.0 has been released into
|
|
38
110
|
the wild. Some new shiny things you might want to test out:</p>
|
|
39
111
|
|
|
40
112
|
<ul>
|
|
@@ -65,7 +137,7 @@ Thank you, all!</p>
|
|
|
65
137
|
bugs. Better yet, submit a patch if you find the bug in the code and know
|
|
66
138
|
how to fix it! :heart:</p>
|
|
67
139
|
|
|
68
|
-
<p>Happy Jekylling! :tada:</p></content><author><name>parkr</name></author><summary type="html">Good news! Nearly 400 commits later, Jekyll 3.5.0 has been released into the wild. Some new shiny things you might want to test out:</summary
|
|
140
|
+
<p>Happy Jekylling! :tada:</p></content><author><name>parkr</name></author><summary type="html">Good news! Nearly 400 commits later, Jekyll 3.5.0 has been released into the wild. Some new shiny things you might want to test out:</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry><entry><title type="html">Jekyll 3.4.3 Released</title><link href="https://jekyllrb.com/news/2017/03/21/jekyll-3-4-3-released/" rel="alternate" type="text/html" title="Jekyll 3.4.3 Released" /><published>2017-03-21T06:52:53-07:00</published><updated>2017-03-21T06:52:53-07:00</updated><id>https://jekyllrb.com/news/2017/03/21/jekyll-3-4-3-released</id><content type="html" xml:base="https://jekyllrb.com/news/2017/03/21/jekyll-3-4-3-released/"><p>Another one-PR patch update as we continue our quest to destroy all bugs. A
|
|
69
141
|
fairly technical debriefing follows, but the TLDR is that we have updated the
|
|
70
142
|
<code class="highlighter-rouge">uri_escape</code> filter to more closely follow the pre-v3.4.0 behavior.</p>
|
|
71
143
|
|
|
@@ -102,7 +174,7 @@ which will simply escape the characters in a string, much like <code class=&q
|
|
|
102
174
|
<p>Thanks to @cameronmcefee and @FriesFlorian for reporting
|
|
103
175
|
<a href="https://github.com/jekyll/jekyll/issues/5954">this issue</a>.</p>
|
|
104
176
|
|
|
105
|
-
<p>Happy Jekylling!</p></content><author><name>pathawks</name></author><summary type="html">Another one-PR patch update as we continue our quest to destroy all bugs. A fairly technical debriefing follows, but the TLDR is that we have updated the uri_escape filter to more closely follow the pre-v3.4.0 behavior.</summary
|
|
177
|
+
<p>Happy Jekylling!</p></content><author><name>pathawks</name></author><summary type="html">Another one-PR patch update as we continue our quest to destroy all bugs. A fairly technical debriefing follows, but the TLDR is that we have updated the uri_escape filter to more closely follow the pre-v3.4.0 behavior.</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry><entry><title type="html">Jekyll 3.4.2 Released</title><link href="https://jekyllrb.com/news/2017/03/09/jekyll-3-4-2-released/" rel="alternate" type="text/html" title="Jekyll 3.4.2 Released" /><published>2017-03-09T12:41:57-08:00</published><updated>2017-03-09T12:41:57-08:00</updated><id>https://jekyllrb.com/news/2017/03/09/jekyll-3-4-2-released</id><content type="html" xml:base="https://jekyllrb.com/news/2017/03/09/jekyll-3-4-2-released/"><p>Another one-PR patch update, though without the same <a href="/news/2017/03/02/jekyll-3-4-1-released/">lessons as for the
|
|
106
178
|
previous release</a>.</p>
|
|
107
179
|
|
|
108
180
|
<p>This release includes a beneficial change for a number of plugins:
|
|
@@ -143,7 +215,7 @@ sitemaps everywhere are filled with just the right content.</p>
|
|
|
143
215
|
<p>As always, if you notice any bugs, please search the issues and file one if
|
|
144
216
|
you can’t find another related to your issue.</p>
|
|
145
217
|
|
|
146
|
-
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">Another one-PR patch update, though without the same lessons as for the previous release.</summary
|
|
218
|
+
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">Another one-PR patch update, though without the same lessons as for the previous release.</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry><entry><title type="html">Jekyll 3.4.1, or “Unintended Consequences”</title><link href="https://jekyllrb.com/news/2017/03/02/jekyll-3-4-1-released/" rel="alternate" type="text/html" title="Jekyll 3.4.1, or "Unintended Consequences"" /><published>2017-03-02T11:20:26-08:00</published><updated>2017-03-02T11:20:26-08:00</updated><id>https://jekyllrb.com/news/2017/03/02/jekyll-3-4-1-released</id><content type="html" xml:base="https://jekyllrb.com/news/2017/03/02/jekyll-3-4-1-released/"><p>Conformity is a confounding thing.</p>
|
|
147
219
|
|
|
148
220
|
<p>We write tests to ensure that a piece of functionality that works today
|
|
149
221
|
will work tomorrow, as further modifications are made to the codebase. This
|
|
@@ -235,7 +307,7 @@ effort.</p>
|
|
|
235
307
|
previous glory. We certainly won’t let that unintended functionality be
|
|
236
308
|
unintended any longer.</p>
|
|
237
309
|
|
|
238
|
-
<p>As always, Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">Conformity is a confounding thing.</summary
|
|
310
|
+
<p>As always, Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">Conformity is a confounding thing.</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry><entry><title type="html">Jekyll turns 3.4.0</title><link href="https://jekyllrb.com/news/2017/01/18/jekyll-3-4-0-released/" rel="alternate" type="text/html" title="Jekyll turns 3.4.0" /><published>2017-01-18T11:19:13-08:00</published><updated>2017-01-18T11:19:13-08:00</updated><id>https://jekyllrb.com/news/2017/01/18/jekyll-3-4-0-released</id><content type="html" xml:base="https://jekyllrb.com/news/2017/01/18/jekyll-3-4-0-released/"><p>Hey there! We have a quick update of Jekyll for you to enjoy this January.
|
|
239
311
|
Packed full of bug fixes as usual, thanks to the tireless efforts of our
|
|
240
312
|
exceptional Jekyll community. Three changes to call out:</p>
|
|
241
313
|
|
|
@@ -270,103 +342,4 @@ about how to accomplish certain tasks with Jekyll.</p>
|
|
|
270
342
|
<p>We have some exciting updates in store for v3.5, and we’re hard at work on
|
|
271
343
|
those already.</p>
|
|
272
344
|
|
|
273
|
-
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">Hey there! We have a quick update of Jekyll for you to enjoy this January. Packed full of bug fixes as usual, thanks to the tireless efforts of our exceptional Jekyll community. Three changes to call out:</summary
|
|
274
|
-
fixes to call out:</p>
|
|
275
|
-
|
|
276
|
-
<ol>
|
|
277
|
-
<li>Only warn about auto-regeneration issues on Windows instead of disabling</li>
|
|
278
|
-
<li>Exclude very specific <code class="highlighter-rouge">vendor/</code> subdirectories instead of all of <code class="highlighter-rouge">vendor/</code></li>
|
|
279
|
-
<li>Allow permalink templates to have plaintext underscores</li>
|
|
280
|
-
</ol>
|
|
281
|
-
|
|
282
|
-
<p>..and lots more! Check out the <a href="/docs/history/#v3-3-1">full history for more</a>.</p>
|
|
283
|
-
|
|
284
|
-
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">Hello! We have a bugfix release of Jekyll hot off the presses for you. Key fixes to call out:</summary></entry><entry><title type="html">Jekyll 3.3 is here with better theme support, new URL filters, and tons more</title><link href="https://jekyllrb.com/news/2016/10/06/jekyll-3-3-is-here/" rel="alternate" type="text/html" title="Jekyll 3.3 is here with better theme support, new URL filters, and tons more" /><published>2016-10-06T11:10:38-07:00</published><updated>2016-10-06T11:10:38-07:00</updated><id>https://jekyllrb.com/news/2016/10/06/jekyll-3-3-is-here</id><content type="html" xml:base="https://jekyllrb.com/news/2016/10/06/jekyll-3-3-is-here/"><p>There are tons of great new quality-of-life features you can use in 3.3.
|
|
285
|
-
Three key things you might want to try:</p>
|
|
286
|
-
|
|
287
|
-
<h3 id="1-themes-can-now-ship-static--dynamic-assets-in-an-assets-directory">1. Themes can now ship static &amp; dynamic assets in an <code class="highlighter-rouge">/assets</code> directory</h3>
|
|
288
|
-
|
|
289
|
-
<p>In Jekyll 3.2, we shipped the ability to use a theme that was packaged as a
|
|
290
|
-
<a href="http://guides.rubygems.org/">gem</a>. 3.2 included support for includes,
|
|
291
|
-
layouts, and sass partials. In 3.3, we’re adding assets to that list.</p>
|
|
292
|
-
|
|
293
|
-
<p>In an effort to make theme management a bit easier, any files you put into
|
|
294
|
-
<code class="highlighter-rouge">/assets</code> in your theme will be read in as though they were part of the
|
|
295
|
-
user’s site. This means you can ship SCSS and CoffeeScript, images and
|
|
296
|
-
webfonts, and so on – anything you’d consider a part of the
|
|
297
|
-
<em>presentation</em>. Same rules apply here as in a Jekyll site: if it has YAML
|
|
298
|
-
front matter, it will be converted and rendered. No YAML front matter, and
|
|
299
|
-
it will simply be copied over like a static asset.</p>
|
|
300
|
-
|
|
301
|
-
<p>Note that if a user has a file of the same path, the theme content will not
|
|
302
|
-
be included in the site, i.e. a user’s <code class="highlighter-rouge">/assets/main.scss</code> will be read and
|
|
303
|
-
processed if present instead of a theme’s <code class="highlighter-rouge">/assets/main.scss</code>.</p>
|
|
304
|
-
|
|
305
|
-
<p>See our <a href="/docs/themes/#assets">documentation on the subject</a>
|
|
306
|
-
for more info.</p>
|
|
307
|
-
|
|
308
|
-
<h3 id="2-relative_url-and-absolute_url-filters">2. <code class="highlighter-rouge">relative_url</code> and <code class="highlighter-rouge">absolute_url</code> filters</h3>
|
|
309
|
-
|
|
310
|
-
<p>Want a clean way to prepend the <code class="highlighter-rouge">baseurl</code> or <code class="highlighter-rouge">url</code> in your config? These
|
|
311
|
-
new filters have you covered. When working locally, if you set your
|
|
312
|
-
<code class="highlighter-rouge">baseurl</code> to match your deployment environment, say <code class="highlighter-rouge">baseurl: "/myproject"</code>,
|
|
313
|
-
then <code class="highlighter-rouge">relative_url</code> will ensure that this baseurl is prepended to anything
|
|
314
|
-
you pass it:</p>
|
|
315
|
-
|
|
316
|
-
<figure class="highlight"><pre><code class="language-liquid" data-lang="liquid"><span class="p">{{</span><span class="w"> </span><span class="s2">"/docs/assets/"</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">relative_url</span><span class="w"> </span><span class="p">}}</span> =&gt; /myproject/docs/assets</code></pre></figure>
|
|
317
|
-
|
|
318
|
-
<p>By default, <code class="highlighter-rouge">baseurl</code> is set to <code class="highlighter-rouge">""</code> and therefore yields (never set to
|
|
319
|
-
<code class="highlighter-rouge">"/"</code>):</p>
|
|
320
|
-
|
|
321
|
-
<figure class="highlight"><pre><code class="language-liquid" data-lang="liquid"><span class="p">{{</span><span class="w"> </span><span class="s2">"/docs/assets/"</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">relative_url</span><span class="w"> </span><span class="p">}}</span> =&gt; /docs/assets</code></pre></figure>
|
|
322
|
-
|
|
323
|
-
<p>A result of <code class="highlighter-rouge">relative_url</code> will safely always produce a URL which is
|
|
324
|
-
relative to the domain root. A similar principle applies to <code class="highlighter-rouge">absolute_url</code>.
|
|
325
|
-
It prepends your <code class="highlighter-rouge">baseurl</code> and <code class="highlighter-rouge">url</code> values, making absolute URLs all the
|
|
326
|
-
easier to make:</p>
|
|
327
|
-
|
|
328
|
-
<figure class="highlight"><pre><code class="language-liquid" data-lang="liquid"><span class="p">{{</span><span class="w"> </span><span class="s2">"/docs/assets/"</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> =&gt; https://jekyllrb.com/myproject/docs/assets</code></pre></figure>
|
|
329
|
-
|
|
330
|
-
<h3 id="3-siteurl-is-set-by-the-development-server">3. <code class="highlighter-rouge">site.url</code> is set by the development server</h3>
|
|
331
|
-
|
|
332
|
-
<p>When you run <code class="highlighter-rouge">jekyll serve</code> locally, it starts a web server, usually at
|
|
333
|
-
<code class="highlighter-rouge">http://localhost:4000</code>, that you use to preview your site during
|
|
334
|
-
development. If you are using the new <code class="highlighter-rouge">absolute_url</code> filter, or using
|
|
335
|
-
<code class="highlighter-rouge">site.url</code> anywhere, you have probably had to create a development config
|
|
336
|
-
which resets the <code class="highlighter-rouge">url</code> value to point to <code class="highlighter-rouge">http://localhost:4000</code>.</p>
|
|
337
|
-
|
|
338
|
-
<p>No longer! When you run <code class="highlighter-rouge">jekyll serve</code>, Jekyll will build your site with
|
|
339
|
-
the value of the <code class="highlighter-rouge">host</code>, <code class="highlighter-rouge">port</code>, and SSL-related options. This defaults to
|
|
340
|
-
<code class="highlighter-rouge">url: http://localhost:4000</code>. When you are developing locally, <code class="highlighter-rouge">site.url</code>
|
|
341
|
-
will yield <code class="highlighter-rouge">http://localhost:4000</code>.</p>
|
|
342
|
-
|
|
343
|
-
<p>This happens by default when running Jekyll locally. It will not be set if
|
|
344
|
-
you set <code class="highlighter-rouge">JEKYLL_ENV=production</code> and run <code class="highlighter-rouge">jekyll serve</code>. If <code class="highlighter-rouge">JEKYLL_ENV</code> is
|
|
345
|
-
any value except <code class="highlighter-rouge">development</code> (its default value), Jekyll will not
|
|
346
|
-
overwrite the value of <code class="highlighter-rouge">url</code> in your config. And again, this only applies
|
|
347
|
-
to serving, not to building.</p>
|
|
348
|
-
|
|
349
|
-
<h2 id="a-lot-more">A <em>lot</em> more!</h2>
|
|
350
|
-
|
|
351
|
-
<p>There are dozens of bug fixes and minor improvements to make your Jekyll
|
|
352
|
-
experience better than ever. With every Jekyll release, we strive to bring
|
|
353
|
-
greater stability and reliability to your everyday development workflow.</p>
|
|
354
|
-
|
|
355
|
-
<p>As always, thanks to our many contributors who contributed countless hours
|
|
356
|
-
of their free time to making this release happen:</p>
|
|
357
|
-
|
|
358
|
-
<p>Anatoliy Yastreb, Anthony Gaudino, Antonio, Ashwin Maroli, Ben Balter,
|
|
359
|
-
Charles Horn, Chris Finazzo, Daniel Chapman, David Zhang, Eduardo
|
|
360
|
-
Bouças, Edward Thomson, Eloy Espinaco, Florian Thomas, Frank Taillandier,
|
|
361
|
-
Gerardo, Heng Kwokfu, Heng, K. (Stephen), Jeff Kolesky, Jonathan Thornton,
|
|
362
|
-
Jordon Bedwell, Jussi Kinnula, Júnior Messias, Kyle O’Brien, Manmeet Gill,
|
|
363
|
-
Mark H. Wilkinson, Marko Locher, Mertcan GÖKGÖZ, Michal Švácha, Mike
|
|
364
|
-
Kasberg, Nadjib Amar, Nicolas Hoizey, Nicolas Porcel, Parker Moore, Pat
|
|
365
|
-
Hawks, Patrick Marsceill, Stephen Checkoway, Stuart Kent, XhmikosR, Zlatan
|
|
366
|
-
Vasović, mertkahyaoglu, shingo-nakanishi, and vohedge.</p>
|
|
367
|
-
|
|
368
|
-
<p><a href="/docs/history/#v3-3-0">Full release notes</a> are available
|
|
369
|
-
for your perusal. If you notice any issues, please don’t hesitate to file a
|
|
370
|
-
bug report.</p>
|
|
371
|
-
|
|
372
|
-
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">There are tons of great new quality-of-life features you can use in 3.3. Three key things you might want to try:</summary></entry></feed>
|
|
345
|
+
<p>Happy Jekylling!</p></content><author><name>parkr</name></author><summary type="html">Hey there! We have a quick update of Jekyll for you to enjoy this January. Packed full of bug fixes as usual, thanks to the tireless efforts of our exceptional Jekyll community. Three changes to call out:</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://jekyllrb.com/img/twitter-card.png" /></entry></feed>
|