jekyll-docs 3.9.0 → 4.0.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (225) hide show
  1. checksums.yaml +4 -4
  2. data/lib/jekyll-docs.rb +3 -3
  3. data/site/404.html +10 -7
  4. data/site/css/screen.css +3 -1
  5. data/site/css/screen.css.map +28 -0
  6. data/site/docs/assets/index.html +412 -453
  7. data/site/docs/code_of_conduct/index.html +447 -501
  8. data/site/docs/collections/index.html +487 -674
  9. data/site/docs/community/bug/index.html +603 -0
  10. data/site/docs/community/index.html +635 -0
  11. data/site/docs/conduct/index.html +447 -515
  12. data/site/docs/configuration/default/index.html +682 -0
  13. data/site/docs/configuration/environments/index.html +641 -0
  14. data/site/docs/configuration/front-matter-defaults/index.html +738 -0
  15. data/site/docs/configuration/incremental-regeneration/index.html +631 -0
  16. data/site/docs/configuration/index.html +405 -1230
  17. data/site/docs/configuration/liquid/index.html +616 -0
  18. data/site/docs/configuration/markdown/index.html +766 -0
  19. data/site/docs/configuration/options/index.html +1011 -0
  20. data/site/docs/configuration/webrick/index.html +615 -0
  21. data/site/docs/continuous-integration/buddyworks/index.html +393 -479
  22. data/site/docs/continuous-integration/circleci/index.html +465 -481
  23. data/site/docs/continuous-integration/travis-ci/index.html +450 -507
  24. data/site/docs/contributing/index.html +425 -514
  25. data/site/docs/datafiles/index.html +411 -453
  26. data/site/docs/deployment-methods/index.html +9 -871
  27. data/site/docs/deployment/automated/index.html +663 -0
  28. data/site/docs/deployment/index.html +607 -0
  29. data/site/docs/deployment/manual/index.html +631 -0
  30. data/site/docs/deployment/third-party/index.html +639 -0
  31. data/site/docs/drafts/index.html +9 -634
  32. data/site/docs/extras/index.html +9 -687
  33. data/site/docs/front-matter/index.html +799 -0
  34. data/site/docs/frontmatter/index.html +9 -819
  35. data/site/docs/github-pages/index.html +407 -475
  36. data/site/docs/history/index.html +1370 -1154
  37. data/site/docs/home/index.html +9 -627
  38. data/site/docs/includes/index.html +425 -501
  39. data/site/docs/index.html +630 -9
  40. data/site/docs/installation/index.html +403 -540
  41. data/site/docs/installation/macos/index.html +716 -0
  42. data/site/docs/installation/other-linux/index.html +613 -0
  43. data/site/docs/installation/ubuntu/index.html +623 -0
  44. data/site/docs/installation/windows/index.html +733 -0
  45. data/site/docs/layouts/index.html +726 -0
  46. data/site/docs/liquid/filters/index.html +1169 -0
  47. data/site/docs/liquid/index.html +615 -0
  48. data/site/docs/liquid/tags/index.html +728 -0
  49. data/site/docs/maintaining/affinity-team-captain/index.html +395 -479
  50. data/site/docs/maintaining/avoiding-burnout/index.html +391 -475
  51. data/site/docs/maintaining/becoming-a-maintainer/index.html +391 -475
  52. data/site/docs/maintaining/index.html +391 -486
  53. data/site/docs/maintaining/merging-a-pull-request/index.html +406 -490
  54. data/site/docs/maintaining/releasing-a-new-version/index.html +409 -485
  55. data/site/docs/maintaining/reviewing-a-pull-request/index.html +392 -476
  56. data/site/docs/maintaining/special-labels/index.html +397 -481
  57. data/site/docs/maintaining/triaging-an-issue/index.html +394 -478
  58. data/site/docs/markdown-101/index.html +601 -0
  59. data/site/docs/migrations/index.html +396 -440
  60. data/site/docs/pages/index.html +408 -482
  61. data/site/docs/pagination/index.html +450 -509
  62. data/site/docs/permalinks/index.html +552 -587
  63. data/site/docs/plugins/commands/index.html +656 -0
  64. data/site/docs/plugins/converters/index.html +685 -0
  65. data/site/docs/plugins/filters/index.html +624 -0
  66. data/site/docs/plugins/generators/index.html +697 -0
  67. data/site/docs/plugins/hooks/index.html +838 -0
  68. data/site/docs/plugins/index.html +415 -1565
  69. data/site/docs/plugins/installation/index.html +681 -0
  70. data/site/docs/plugins/tags/index.html +699 -0
  71. data/site/docs/plugins/your-first-plugin/index.html +741 -0
  72. data/site/docs/posts/index.html +491 -627
  73. data/site/docs/quickstart/index.html +9 -645
  74. data/site/docs/resources/index.html +9 -761
  75. data/site/docs/ruby-101/index.html +640 -0
  76. data/site/docs/sites/index.html +9 -696
  77. data/site/docs/static-files/index.html +401 -433
  78. data/site/docs/step-by-step/01-setup/index.html +771 -0
  79. data/site/docs/step-by-step/02-liquid/index.html +756 -0
  80. data/site/docs/step-by-step/03-front-matter/index.html +730 -0
  81. data/site/docs/step-by-step/04-layouts/index.html +770 -0
  82. data/site/docs/step-by-step/05-includes/index.html +768 -0
  83. data/site/docs/step-by-step/06-data-files/index.html +738 -0
  84. data/site/docs/step-by-step/07-assets/index.html +773 -0
  85. data/site/docs/step-by-step/08-blogging/index.html +835 -0
  86. data/site/docs/step-by-step/09-collections/index.html +932 -0
  87. data/site/docs/step-by-step/10-deployment/index.html +842 -0
  88. data/site/docs/structure/index.html +411 -430
  89. data/site/docs/support/index.html +392 -476
  90. data/site/docs/templates/index.html +9 -1232
  91. data/site/docs/themes/index.html +487 -521
  92. data/site/docs/troubleshooting/index.html +443 -520
  93. data/site/docs/upgrading/0-to-2/index.html +437 -523
  94. data/site/docs/upgrading/2-to-3/index.html +422 -507
  95. data/site/docs/upgrading/3-to-4/index.html +765 -0
  96. data/site/docs/upgrading/index.html +395 -478
  97. data/site/docs/usage/index.html +409 -506
  98. data/site/docs/variables/index.html +504 -652
  99. data/site/docs/windows/index.html +9 -784
  100. data/site/feed.xml +269 -188
  101. data/site/feed/release.xml +324 -0
  102. data/site/fonts/lato-v14-latin-300.woff +0 -0
  103. data/site/fonts/lato-v14-latin-300.woff2 +0 -0
  104. data/site/fonts/lato-v14-latin-300italic.woff +0 -0
  105. data/site/fonts/lato-v14-latin-300italic.woff2 +0 -0
  106. data/site/fonts/lato-v14-latin-700.woff +0 -0
  107. data/site/fonts/lato-v14-latin-700.woff2 +0 -0
  108. data/site/fonts/lato-v14-latin-700italic.woff +0 -0
  109. data/site/fonts/lato-v14-latin-700italic.woff2 +0 -0
  110. data/site/fonts/lato-v14-latin-900.woff +0 -0
  111. data/site/fonts/lato-v14-latin-900.woff2 +0 -0
  112. data/site/fonts/lato-v14-latin-900italic.woff +0 -0
  113. data/site/fonts/lato-v14-latin-900italic.woff2 +0 -0
  114. data/site/fonts/lato-v14-latin-italic.woff +0 -0
  115. data/site/fonts/lato-v14-latin-italic.woff2 +0 -0
  116. data/site/fonts/lato-v14-latin-regular.woff +0 -0
  117. data/site/fonts/lato-v14-latin-regular.woff2 +0 -0
  118. data/site/help/index.html +9 -247
  119. data/site/img/forestry-logo.svg +19 -0
  120. data/site/img/jekyll-og.png +0 -0
  121. data/site/img/spacer.gif +0 -0
  122. data/site/index.html +56 -29
  123. data/site/jekyllconf/index.html +62 -35
  124. data/site/latest_version.txt +1 -1
  125. data/site/news/2013/05/05/jekyll-1-0-0-released/index.html +180 -115
  126. data/site/news/2013/05/08/jekyll-1-0-1-released/index.html +182 -117
  127. data/site/news/2013/05/12/jekyll-1-0-2-released/index.html +183 -118
  128. data/site/news/2013/06/07/jekyll-1-0-3-released/index.html +184 -119
  129. data/site/news/2013/07/14/jekyll-1-1-0-released/index.html +183 -118
  130. data/site/news/2013/07/24/jekyll-1-1-1-released/index.html +180 -115
  131. data/site/news/2013/07/25/jekyll-1-0-4-released/index.html +182 -117
  132. data/site/news/2013/07/25/jekyll-1-1-2-released/index.html +182 -117
  133. data/site/news/2013/09/06/jekyll-1-2-0-released/index.html +185 -120
  134. data/site/news/2013/09/14/jekyll-1-2-1-released/index.html +183 -118
  135. data/site/news/2013/10/28/jekyll-1-3-0-rc1-released/index.html +180 -115
  136. data/site/news/2013/11/04/jekyll-1-3-0-released/index.html +189 -124
  137. data/site/news/2013/11/26/jekyll-1-3-1-released/index.html +181 -116
  138. data/site/news/2013/12/07/jekyll-1-4-0-released/index.html +181 -116
  139. data/site/news/2013/12/09/jekyll-1-4-1-released/index.html +180 -115
  140. data/site/news/2013/12/16/jekyll-1-4-2-released/index.html +182 -117
  141. data/site/news/2014/01/13/jekyll-1-4-3-released/index.html +181 -116
  142. data/site/news/2014/03/24/jekyll-1-5-0-released/index.html +181 -116
  143. data/site/news/2014/03/27/jekyll-1-5-1-released/index.html +181 -116
  144. data/site/news/2014/05/06/jekyll-turns-2-0-0/index.html +184 -119
  145. data/site/news/2014/05/08/jekyll-2-0-3-released/index.html +180 -115
  146. data/site/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/index.html +181 -116
  147. data/site/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/index.html +185 -120
  148. data/site/news/2014/07/01/jekyll-2-1-1-released/index.html +182 -117
  149. data/site/news/2014/07/29/jekyll-2-2-0-released/index.html +181 -116
  150. data/site/news/2014/08/10/jekyll-2-3-0-released/index.html +189 -124
  151. data/site/news/2014/09/09/jekyll-2-4-0-released/index.html +187 -122
  152. data/site/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/index.html +188 -123
  153. data/site/news/2014/11/09/jekyll-2-5-1-released/index.html +180 -115
  154. data/site/news/2014/11/12/jekyll-2-5-2-released/index.html +182 -117
  155. data/site/news/2014/12/17/alfredxing-welcome-to-jekyll-core/index.html +179 -114
  156. data/site/news/2014/12/22/jekyll-2-5-3-released/index.html +180 -115
  157. data/site/news/2015/01/20/jekyll-meet-and-greet/index.html +179 -114
  158. data/site/news/2015/01/24/jekyll-3-0-0-beta1-released/index.html +180 -115
  159. data/site/news/2015/02/26/introducing-jekyll-talk/index.html +180 -115
  160. data/site/news/2015/10/26/jekyll-3-0-released/index.html +185 -120
  161. data/site/news/2015/11/17/jekyll-3-0-1-released/index.html +184 -119
  162. data/site/news/2016/01/20/jekyll-3-0-2-released/index.html +182 -117
  163. data/site/news/2016/01/24/jekyll-3-1-0-released/index.html +186 -121
  164. data/site/news/2016/01/28/jekyll-3-1-1-released/index.html +183 -118
  165. data/site/news/2016/02/08/jekyll-3-0-3-released/index.html +181 -116
  166. data/site/news/2016/02/19/jekyll-3-1-2-released/index.html +182 -117
  167. data/site/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/index.html +179 -114
  168. data/site/news/2016/04/19/jekyll-3-0-4-released/index.html +181 -116
  169. data/site/news/2016/04/19/jekyll-3-1-3-released/index.html +181 -116
  170. data/site/news/2016/04/26/jekyll-3-0-5-released/index.html +180 -115
  171. data/site/news/2016/05/18/jekyll-3-1-4-released/index.html +186 -121
  172. data/site/news/2016/05/18/jekyll-3-1-5-released/index.html +181 -116
  173. data/site/news/2016/05/19/jekyll-3-1-6-released/index.html +181 -116
  174. data/site/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/index.html +179 -114
  175. data/site/news/2016/07/26/jekyll-3-2-0-released/index.html +184 -119
  176. data/site/news/2016/08/02/jekyll-3-2-1-released/index.html +180 -115
  177. data/site/news/2016/08/24/jekyll-admin-initial-release/index.html +179 -114
  178. data/site/news/2016/10/06/jekyll-3-3-is-here/index.html +207 -142
  179. data/site/news/2016/11/14/jekyll-3-3-1-released/index.html +181 -116
  180. data/site/news/2017/01/18/jekyll-3-4-0-released/index.html +183 -118
  181. data/site/news/2017/03/02/jekyll-3-4-1-released/index.html +181 -116
  182. data/site/news/2017/03/09/jekyll-3-4-2-released/index.html +189 -124
  183. data/site/news/2017/03/21/jekyll-3-4-3-released/index.html +190 -125
  184. data/site/news/2017/06/15/jekyll-3-5-0-released/index.html +187 -122
  185. data/site/news/2017/07/17/jekyll-3-5-1-released/index.html +182 -117
  186. data/site/news/2017/08/12/jekyll-3-5-2-released/index.html +185 -120
  187. data/site/news/2017/09/21/jekyll-3-6-0-released/index.html +181 -116
  188. data/site/news/2017/10/19/diversity-open-source/index.html +181 -116
  189. data/site/news/2017/10/21/jekyll-3-6-2-released/index.html +183 -118
  190. data/site/news/2018/01/02/jekyll-3-7-0-released/index.html +184 -119
  191. data/site/news/2018/01/25/jekyll-3-7-2-released/index.html +189 -124
  192. data/site/news/2018/02/19/meet-jekyll-s-new-lead-developer/index.html +180 -115
  193. data/site/news/2018/02/24/jekyll-3-7-3-released/index.html +185 -120
  194. data/site/news/2018/04/19/development-update/index.html +699 -0
  195. data/site/news/2018/04/19/jekyll-3-8-0-released/index.html +715 -0
  196. data/site/news/2018/05/01/jekyll-3-8-1-released/index.html +182 -117
  197. data/site/news/2018/05/19/jekyll-3-8-2-released/index.html +181 -116
  198. data/site/news/2018/06/05/jekyll-3-8-3-released/index.html +183 -118
  199. data/site/news/2018/08/01/jekyll-sponsoring/index.html +748 -0
  200. data/site/news/2018/09/19/security-fixes-for-3-6-3-7-3-8/index.html +692 -0
  201. data/site/news/2018/11/04/jekyll-3-8-5-released/index.html +682 -0
  202. data/site/news/2019/03/18/jekyll-4-0-0-pre-alpha1-released/index.html +710 -0
  203. data/site/news/2019/07/02/jekyll-3-8-6-released/index.html +180 -115
  204. data/site/news/2019/07/20/jekyll-4-0-0-pre-beta1-released/index.html +11 -0
  205. data/site/news/2019/08/04/jekyll-4-0-0-pre-beta1-released/index.html +708 -0
  206. data/site/news/2019/08/20/jekyll-4-0-0-released/index.html +809 -0
  207. data/site/news/index.html +976 -326
  208. data/site/news/releases/index.html +820 -321
  209. data/site/{philosophy.html → philosophy/index.html} +1 -1
  210. data/site/redirects.json +1 -1
  211. data/site/resources/index.html +332 -0
  212. data/site/showcase/index.html +844 -0
  213. data/site/sitemap.xml +256 -81
  214. data/site/team/index.html +63 -77
  215. data/site/tutorials/cache-api/index.html +418 -0
  216. data/site/tutorials/convert-site-to-jekyll/index.html +155 -124
  217. data/site/tutorials/custom-404-page/index.html +76 -43
  218. data/site/tutorials/home/index.html +64 -37
  219. data/site/tutorials/navigation/index.html +186 -103
  220. data/site/tutorials/orderofinterpretation/index.html +80 -53
  221. data/site/tutorials/using-jekyll-with-bundler/index.html +80 -51
  222. data/site/tutorials/video-walkthroughs/index.html +62 -35
  223. metadata +102 -13
  224. data/site/community/index.html +0 -11
  225. data/site/docs/continuous-integration/index.html +0 -681
@@ -3,17 +3,18 @@
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.9.0">
6
+ <meta name="generator" content="Jekyll v4.0.0">
7
7
  <link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
8
+ <link type="application/atom+xml" rel="alternate" href="/feed/release.xml" title="Jekyll releases posts" />
8
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">
9
- <link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
10
- <link rel="stylesheet" href="https://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" />
10
+ <link rel="preload" href="/fonts/lato-v14-latin-300.woff2" as="font" type="font/woff2" crossorigin />
11
+ <link rel="preload" href="/fonts/lato-v14-latin-700.woff2" as="font" type="font/woff2" crossorigin />
12
+ <link rel="preload" href="/css/screen.css" as="style">
12
13
  <link rel="stylesheet" href="/css/screen.css">
13
14
  <link rel="icon" type="image/x-icon" href="/favicon.ico">
14
15
  <!-- Begin Jekyll SEO tag v2.6.1 -->
15
16
  <title>Themes | Jekyll • Simple, blog-aware, static sites</title>
16
- <meta name="generator" content="Jekyll v3.9.0" />
17
+ <meta name="generator" content="Jekyll v4.0.0" />
17
18
  <meta property="og:title" content="Themes" />
18
19
  <meta property="og:locale" content="en_US" />
19
20
  <meta name="description" content="Jekyll has an extensive theme system that allows you to leverage community-maintained templates and styles to customize your site’s presentation. Jekyll themes specify plugins and package up assets, layouts, includes, and stylesheets in a way that can be overridden by your site’s content." />
@@ -21,14 +22,16 @@
21
22
  <link rel="canonical" href="https://jekyllrb.com/docs/themes/" />
22
23
  <meta property="og:url" content="https://jekyllrb.com/docs/themes/" />
23
24
  <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
25
+ <meta property="og:image" content="https://jekyllrb.com/img/jekyll-og.png" />
24
26
  <meta property="og:type" content="article" />
25
- <meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
26
- <meta name="twitter:card" content="summary" />
27
+ <meta property="article:published_time" content="2019-09-11T07:30:27-07:00" />
28
+ <meta name="twitter:card" content="summary_large_image" />
29
+ <meta property="twitter:image" content="https://jekyllrb.com/img/jekyll-og.png" />
27
30
  <meta property="twitter:title" content="Themes" />
28
31
  <meta name="twitter:site" content="@jekyllrb" />
29
32
  <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
30
33
  <script type="application/ld+json">
31
- {"url":"https://jekyllrb.com/docs/themes/","headline":"Themes","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 has an extensive theme system that allows you to leverage community-maintained templates and styles to customize your site’s presentation. Jekyll themes specify plugins and package up assets, layouts, includes, and stylesheets in a way that can be overridden by your site’s content.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/themes/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
34
+ {"description":"Jekyll has an extensive theme system that allows you to leverage community-maintained templates and styles to customize your site’s presentation. Jekyll themes specify plugins and package up assets, layouts, includes, and stylesheets in a way that can be overridden by your site’s content.","@type":"BlogPosting","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/themes/"},"headline":"Themes","dateModified":"2019-09-11T07:30:27-07:00","url":"https://jekyllrb.com/docs/themes/","datePublished":"2019-09-11T07:30:27-07:00","image":"https://jekyllrb.com/img/jekyll-og.png","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@context":"https://schema.org"}</script>
32
35
  <!-- End Jekyll SEO tag -->
33
36
 
34
37
  <!--[if lt IE 9]>
@@ -51,18 +54,27 @@
51
54
  </div>
52
55
  <nav class="main-nav hide-on-mobiles">
53
56
  <ul>
54
- <li class="">
57
+
58
+ <li>
55
59
  <a href="/">Home</a>
56
60
  </li>
61
+
57
62
  <li class="current">
58
- <a href="/docs/home/">Docs</a>
63
+ <a href="/docs/">Docs</a>
59
64
  </li>
60
- <li class="">
61
- <a href="/news/">News</a>
65
+
66
+ <li>
67
+ <a href="/resources/">Resources</a>
68
+ </li>
69
+
70
+ <li>
71
+ <a href="/showcase/">Showcase</a>
62
72
  </li>
63
- <li class="">
64
- <a href="/help/">Help</a>
73
+
74
+ <li>
75
+ <a href="/news/">News</a>
65
76
  </li>
77
+
66
78
  </ul>
67
79
 
68
80
  </nav>
@@ -73,7 +85,7 @@
73
85
  <div class="meta hide-on-mobiles">
74
86
  <ul>
75
87
  <li>
76
- <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
88
+ <a href="https://github.com/jekyll/jekyll/releases/tag/v4.0.0">v4.0.0</a>
77
89
  </li>
78
90
  <li>
79
91
  <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -83,18 +95,24 @@
83
95
  </div>
84
96
  <nav class="mobile-nav show-on-mobiles">
85
97
  <ul>
86
- <li class="">
87
- <a href="/">Home</a>
88
- </li>
89
- <li class="current">
90
- <a href="/docs/home/">Docs</a>
91
- </li>
92
- <li class="">
93
- <a href="/news/">News</a>
94
- </li>
95
- <li class="">
96
- <a href="/help/">Help</a>
97
- </li>
98
+
99
+ <li>
100
+ <a href="/">Home</a>
101
+ </li>
102
+
103
+ <li class="current">
104
+ <a href="/docs/">Docs</a>
105
+ </li>
106
+
107
+ <li>
108
+ <a href="/resources/">Resources</a>
109
+ </li>
110
+
111
+
112
+ <li>
113
+ <a href="/news/">News</a>
114
+ </li>
115
+
98
116
  <li>
99
117
  <a href="https://github.com/jekyll/jekyll">GitHub</a>
100
118
  </li>
@@ -113,176 +131,152 @@
113
131
 
114
132
  <optgroup label="Getting Started">
115
133
 
116
-
117
-
118
- <option value="/docs/home/">Welcome</option>
119
-
120
-
121
-
122
- <option value="/docs/quickstart/">Quick-start guide</option>
123
-
124
-
125
-
126
- <option value="/docs/installation/">Installation</option>
127
-
128
-
129
-
130
- <option value="/docs/windows/">Jekyll on Windows</option>
131
-
132
-
133
-
134
- <option value="/docs/usage/">Basic Usage</option>
135
-
136
-
137
-
138
- <option value="/docs/structure/">Directory structure</option>
139
-
140
-
141
-
142
- <option value="/docs/configuration/">Configuration</option>
143
-
144
-
145
- </optgroup>
146
-
147
- <optgroup label="Your Content">
134
+
135
+ <option value="/docs/">
136
+ Quickstart
137
+ </option>
138
+
139
+
140
+ <option value="/docs/ruby-101/">
141
+ Ruby 101
142
+ </option>
143
+
144
+
145
+ <option value="/docs/installation/">
146
+ Installation
147
+ </option>
148
+
149
+
150
+ <option value="/docs/community/">
151
+ Community
152
+ </option>
153
+
154
+
155
+ <option value="/docs/step-by-step/01-setup/">
156
+ Step by Step Tutorial
157
+ </option>
148
158
 
149
-
150
-
151
- <option value="/docs/frontmatter/">Front Matter</option>
152
-
153
-
154
-
155
- <option value="/docs/posts/">Writing posts</option>
156
-
157
-
158
-
159
- <option value="/docs/drafts/">Working with drafts</option>
160
-
161
-
162
-
163
- <option value="/docs/pages/">Creating pages</option>
164
-
165
-
166
-
167
- <option value="/docs/static-files/">Static Files</option>
168
-
169
-
170
-
171
- <option value="/docs/variables/">Variables</option>
172
-
173
-
174
-
175
- <option value="/docs/collections/">Collections</option>
176
-
177
-
178
-
179
- <option value="/docs/datafiles/">Data Files</option>
180
-
181
-
182
-
183
- <option value="/docs/assets/">Assets</option>
184
-
185
-
186
-
187
- <option value="/docs/migrations/">Blog migrations</option>
188
-
189
-
190
159
  </optgroup>
191
160
 
192
- <optgroup label="Customization">
161
+ <optgroup label="Build">
162
+
163
+
164
+ <option value="/docs/usage/">
165
+ Command Line Usage
166
+ </option>
167
+
168
+
169
+ <option value="/docs/configuration/">
170
+ Configuration
171
+ </option>
193
172
 
194
-
195
-
196
- <option value="/docs/templates/">Templates</option>
197
-
198
-
199
-
200
- <option value="/docs/includes/">Includes</option>
201
-
202
-
203
-
204
- <option value="/docs/permalinks/">Permalinks</option>
205
-
206
-
207
-
208
- <option value="/docs/pagination/">Pagination</option>
209
-
210
-
211
-
212
- <option value="/docs/plugins/">Plugins</option>
213
-
214
-
215
-
216
- <option value="/docs/themes/">Themes</option>
217
-
218
-
219
-
220
- <option value="/docs/extras/">Extras</option>
221
-
222
-
223
173
  </optgroup>
224
174
 
225
- <optgroup label="Deployment">
175
+ <optgroup label="Content">
176
+
177
+
178
+ <option value="/docs/pages/">
179
+ Pages
180
+ </option>
181
+
182
+
183
+ <option value="/docs/posts/">
184
+ Posts
185
+ </option>
186
+
187
+
188
+ <option value="/docs/front-matter/">
189
+ Front Matter
190
+ </option>
191
+
192
+
193
+ <option value="/docs/collections/">
194
+ Collections
195
+ </option>
196
+
197
+
198
+ <option value="/docs/datafiles/">
199
+ Data Files
200
+ </option>
201
+
202
+
203
+ <option value="/docs/assets/">
204
+ Assets
205
+ </option>
206
+
207
+
208
+ <option value="/docs/static-files/">
209
+ Static Files
210
+ </option>
226
211
 
227
-
228
-
229
- <option value="/docs/github-pages/">GitHub Pages</option>
230
-
231
-
232
-
233
- <option value="/docs/deployment-methods/">Deployment methods</option>
234
-
235
-
236
-
237
- <option value="/docs/continuous-integration/">Continuous Integration</option>
238
-
239
-
240
212
  </optgroup>
241
213
 
242
- <optgroup label="Miscellaneous">
214
+ <optgroup label="Site Structure">
215
+
216
+
217
+ <option value="/docs/structure/">
218
+ Directory Structure
219
+ </option>
220
+
221
+
222
+ <option value="/docs/liquid/">
223
+ Liquid
224
+ </option>
225
+
226
+
227
+ <option value="/docs/variables/">
228
+ Variables
229
+ </option>
230
+
231
+
232
+ <option value="/docs/includes/">
233
+ Includes
234
+ </option>
235
+
236
+
237
+ <option value="/docs/layouts/">
238
+ Layouts
239
+ </option>
240
+
241
+
242
+ <option value="/docs/permalinks/">
243
+ Permalinks
244
+ </option>
245
+
246
+
247
+ <option value="/docs/themes/">
248
+ Themes
249
+ </option>
250
+
251
+
252
+ <option value="/docs/pagination/">
253
+ Pagination
254
+ </option>
243
255
 
244
-
245
-
246
- <option value="/docs/troubleshooting/">Troubleshooting</option>
247
-
248
-
249
-
250
- <option value="/docs/sites/">Sites using Jekyll</option>
251
-
252
-
253
-
254
- <option value="/docs/resources/">Resources</option>
255
-
256
-
257
-
258
- <option value="/docs/upgrading/0-to-2/">Upgrading from 0.x to 2.x</option>
259
-
260
-
261
-
262
- <option value="/docs/upgrading/2-to-3/">Upgrading from 2.x to 3.x</option>
263
-
264
-
265
256
  </optgroup>
266
257
 
267
- <optgroup label="Meta">
258
+ <optgroup label="Guides">
259
+
260
+
261
+ <option value="/docs/plugins/">
262
+ Plugins
263
+ </option>
264
+
265
+
266
+ <option value="/docs/migrations/">
267
+ Blog Migrations
268
+ </option>
269
+
270
+
271
+ <option value="/docs/upgrading/">
272
+ Upgrading
273
+ </option>
274
+
275
+
276
+ <option value="/docs/deployment/">
277
+ Deployment
278
+ </option>
268
279
 
269
-
270
-
271
- <option value="/docs/contributing/">Contributing</option>
272
-
273
-
274
-
275
- <option value="/docs/maintaining/">Maintaining Jekyll</option>
276
-
277
-
278
-
279
- <option value="/docs/conduct/">Code of Conduct</option>
280
-
281
-
282
-
283
- <option value="/docs/history/">History</option>
284
-
285
-
286
280
  </optgroup>
287
281
 
288
282
  </select>
@@ -292,33 +286,33 @@
292
286
  <div class="unit four-fifths">
293
287
  <article>
294
288
  <div class="improve right hide-on-mobiles">
295
- <a href="https://github.com/jekyll/jekyll/edit/master/docs/_docs/themes.md"><i class="fa fa-pencil"></i>  Improve this page</a>
289
+ <a data-proofer-ignore href="https://github.com/jekyll/jekyll/edit/master/docs/_docs/themes.md"><i class="fa fa-pencil"></i>  Improve this page</a>
296
290
  </div>
297
291
  <h1>Themes</h1>
298
292
  <p>Jekyll has an extensive theme system that allows you to leverage community-maintained templates and styles to customize your site’s presentation. Jekyll themes specify plugins and package up assets, layouts, includes, and stylesheets in a way that can be overridden by your site’s content.</p>
299
293
 
300
294
  <h2 id="understanding-gem-based-themes">Understanding gem-based themes</h2>
301
295
 
302
- <p>When you <a href="/docs/quickstart">create a new Jekyll site</a> (by running the <code class="language-plaintext highlighter-rouge">jekyll new &lt;PATH&gt;</code> command), Jekyll installs a site that uses a gem-based theme called <a href="https://github.com/jekyll/minima">Minima</a>.</p>
296
+ <p>When you <a href="/docs/">create a new Jekyll site</a> (by running the <code class="highlighter-rouge">jekyll new &lt;PATH&gt;</code> command), Jekyll installs a site that uses a gem-based theme called <a href="https://github.com/jekyll/minima">Minima</a>.</p>
303
297
 
304
- <p>With gem-based themes, some of the site’s directories (such as the <code class="language-plaintext highlighter-rouge">assets</code>, <code class="language-plaintext highlighter-rouge">_layouts</code>, <code class="language-plaintext highlighter-rouge">_includes</code>, and <code class="language-plaintext highlighter-rouge">_sass</code> directories) are stored in the theme’s gem, hidden from your immediate view. Yet all of the necessary directories will be read and processed during Jekyll’s build process.</p>
298
+ <p>With gem-based themes, some of the site’s directories (such as the <code class="highlighter-rouge">assets</code>, <code class="highlighter-rouge">_layouts</code>, <code class="highlighter-rouge">_includes</code>, and <code class="highlighter-rouge">_sass</code> directories) are stored in the theme’s gem, hidden from your immediate view. Yet all of the necessary directories will be read and processed during Jekyll’s build process.</p>
305
299
 
306
300
  <p>In the case of Minima, you see only the following files in your Jekyll site directory:</p>
307
301
 
308
- <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>├── Gemfile
302
+ <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>├── Gemfile
309
303
  ├── Gemfile.lock
310
304
  ├── _config.yml
311
305
  ├── _posts
312
306
  │ └── 2016-12-04-welcome-to-jekyll.markdown
313
- ├── about.md
314
- └── index.md
307
+ ├── about.markdown
308
+ └── index.markdown
315
309
  </code></pre></div></div>
316
310
 
317
- <p>The <code class="language-plaintext highlighter-rouge">Gemfile</code> and <code class="language-plaintext highlighter-rouge">Gemfile.lock</code> files are used by Bundler to keep track of the required gems and gem versions you need to build your Jekyll site.</p>
311
+ <p>The <code class="highlighter-rouge">Gemfile</code> and <code class="highlighter-rouge">Gemfile.lock</code> files are used by Bundler to keep track of the required gems and gem versions you need to build your Jekyll site.</p>
318
312
 
319
- <p>Gem-based themes make it easy for theme developers to make updates available to anyone who has the theme gem. When there’s an update, theme developers push the update to RubyGems.</p>
313
+ <p>Gem-based themes make it easier for theme developers to make updates available to anyone who has the theme gem. When there’s an update, theme developers push the update to RubyGems.</p>
320
314
 
321
- <p>If you have the theme gem, you can (if you desire) run <code class="language-plaintext highlighter-rouge">bundle update</code> to update all gems in your project. Or you can run <code class="language-plaintext highlighter-rouge">bundle update &lt;THEME&gt;</code>, replacing <code class="language-plaintext highlighter-rouge">&lt;THEME&gt;</code> with the theme name, such as <code class="language-plaintext highlighter-rouge">minima</code>, to just update the theme gem. Any new files or updates the theme developer has made (such as to stylesheets or includes) will be pulled into your project automatically.</p>
315
+ <p>If you have the theme gem, you can (if you desire) run <code class="highlighter-rouge">bundle update</code> to update all gems in your project. Or you can run <code class="highlighter-rouge">bundle update &lt;THEME&gt;</code>, replacing <code class="highlighter-rouge">&lt;THEME&gt;</code> with the theme name, such as <code class="highlighter-rouge">minima</code>, to just update the theme gem. Any new files or updates the theme developer has made (such as to stylesheets or includes) will be pulled into your project automatically.</p>
322
316
 
323
317
  <p>The goal of gem-based themes is to allow you to get all the benefits of a robust, continually updated theme without having all the theme’s files getting in your way and over-complicating what might be your primary focus: creating content.</p>
324
318
 
@@ -326,17 +320,17 @@
326
320
 
327
321
  <p>Jekyll themes set default layouts, includes, and stylesheets. However, you can override any of the theme defaults with your own site content.</p>
328
322
 
329
- <p>To replace layouts or includes in your theme, make a copy in your <code class="language-plaintext highlighter-rouge">_layouts</code> or <code class="language-plaintext highlighter-rouge">_includes</code> directory of the specific file you wish to modify, or create the file from scratch giving it the same name as the file you wish to override.</p>
323
+ <p>To replace layouts or includes in your theme, make a copy in your <code class="highlighter-rouge">_layouts</code> or <code class="highlighter-rouge">_includes</code> directory of the specific file you wish to modify, or create the file from scratch giving it the same name as the file you wish to override.</p>
330
324
 
331
- <p>For example, if your selected theme has a <code class="language-plaintext highlighter-rouge">page</code> layout, you can override the theme’s layout by creating your own <code class="language-plaintext highlighter-rouge">page</code> layout in the <code class="language-plaintext highlighter-rouge">_layouts</code> directory (that is, <code class="language-plaintext highlighter-rouge">_layouts/page.html</code>).</p>
325
+ <p>For example, if your selected theme has a <code class="highlighter-rouge">page</code> layout, you can override the theme’s layout by creating your own <code class="highlighter-rouge">page</code> layout in the <code class="highlighter-rouge">_layouts</code> directory (that is, <code class="highlighter-rouge">_layouts/page.html</code>).</p>
332
326
 
333
327
  <p>To locate a theme’s files on your computer:</p>
334
328
 
335
329
  <ol>
336
330
  <li>
337
- <p>Run <code class="language-plaintext highlighter-rouge">bundle show</code> followed by the name of the theme’s gem, e.g., <code class="language-plaintext highlighter-rouge">bundle show minima</code> for Jekyll’s default theme.</p>
331
+ <p>Run <code class="highlighter-rouge">bundle show</code> followed by the name of the theme’s gem, e.g., <code class="highlighter-rouge">bundle show minima</code> for Jekyll’s default theme.</p>
338
332
 
339
- <p>This returns the location of the gem-based theme files. For example, the Minima theme’s files might be located in <code class="language-plaintext highlighter-rouge">/usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0</code> on macOS.</p>
333
+ <p>This returns the location of the gem-based theme files. For example, the Minima theme’s files might be located in <code class="highlighter-rouge">/usr/local/lib/ruby/gems/2.6.0/gems/minima-2.5.1</code> on macOS.</p>
340
334
  </li>
341
335
  <li>
342
336
  <p>Open the theme’s directory in Finder or Explorer:</p>
@@ -344,13 +338,23 @@
344
338
  <div class="language-sh highlighter-rouge">
345
339
  <div class="highlight"><pre class="highlight"><code><span class="c"># On MacOS</span>
346
340
  open <span class="si">$(</span>bundle show minima<span class="si">)</span>
341
+
347
342
  <span class="c"># On Windows</span>
348
- explorer /usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0
343
+ <span class="c"># First get the gem's installation path:</span>
344
+ <span class="c">#</span>
345
+ <span class="c"># bundle show minima</span>
346
+ <span class="c"># =&gt; C:/Ruby26-x64/lib/ruby/gems/2.6.3/gems/minima-2.5.1</span>
347
+ <span class="c">#</span>
348
+ <span class="c"># then invoke explorer with above path, substituting `/` with `\`</span>
349
+ explorer C:<span class="se">\R</span>uby26-x64<span class="se">\l</span>ib<span class="se">\r</span>uby<span class="se">\g</span>ems<span class="se">\2</span>.6.3<span class="se">\g</span>ems<span class="se">\m</span>inima-2.5.1
350
+
351
+ <span class="c"># On Linux</span>
352
+ xdg-open <span class="si">$(</span>bundle show minima<span class="si">)</span>
349
353
  </code></pre></div> </div>
350
354
 
351
355
  <p>A Finder or Explorer window opens showing the theme’s files and directories. The Minima theme gem contains these files:</p>
352
356
 
353
- <div class="language-plaintext highlighter-rouge">
357
+ <div class="highlighter-rouge">
354
358
  <div class="highlight"><pre class="highlight"><code> ├── LICENSE.txt
355
359
  ├── README.md
356
360
  ├── _includes
@@ -382,17 +386,17 @@ explorer /usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0
382
386
 
383
387
  <p>With a clear understanding of the theme’s files, you can now override any theme file by creating a similarly named file in your Jekyll site directory.</p>
384
388
 
385
- <p>Let’s say, for a second example, you want to override Minima’s footer. In your Jekyll site, create an <code class="language-plaintext highlighter-rouge">_includes</code> folder and add a file in it called <code class="language-plaintext highlighter-rouge">footer.html</code>. Jekyll will now use your site’s <code class="language-plaintext highlighter-rouge">footer.html</code> file instead of the <code class="language-plaintext highlighter-rouge">footer.html</code> file from the Minima theme gem.</p>
389
+ <p>Let’s say, for a second example, you want to override Minima’s footer. In your Jekyll site, create an <code class="highlighter-rouge">_includes</code> folder and add a file in it called <code class="highlighter-rouge">footer.html</code>. Jekyll will now use your site’s <code class="highlighter-rouge">footer.html</code> file instead of the <code class="highlighter-rouge">footer.html</code> file from the Minima theme gem.</p>
386
390
 
387
- <p>To modify any stylesheet you must take the extra step of also copying the main sass file (<code class="language-plaintext highlighter-rouge">_sass/minima.scss</code> in the Minima theme) into the <code class="language-plaintext highlighter-rouge">_sass</code> directory in your site’s source.</p>
391
+ <p>To modify any stylesheet you must take the extra step of also copying the main sass file (<code class="highlighter-rouge">_sass/minima.scss</code> in the Minima theme) into the <code class="highlighter-rouge">_sass</code> directory in your site’s source.</p>
388
392
 
389
393
  <p>Jekyll will look first to your site’s content before looking to the theme’s defaults for any requested file in the following folders:</p>
390
394
 
391
395
  <ul>
392
- <li><code class="language-plaintext highlighter-rouge">/assets</code></li>
393
- <li><code class="language-plaintext highlighter-rouge">/_layouts</code></li>
394
- <li><code class="language-plaintext highlighter-rouge">/_includes</code></li>
395
- <li><code class="language-plaintext highlighter-rouge">/_sass</code></li>
396
+ <li><code class="highlighter-rouge">/assets</code></li>
397
+ <li><code class="highlighter-rouge">/_layouts</code></li>
398
+ <li><code class="highlighter-rouge">/_includes</code></li>
399
+ <li><code class="highlighter-rouge">/_sass</code></li>
396
400
  </ul>
397
401
 
398
402
  <p>Note that making copies of theme files will prevent you from receiving any theme updates on those files. An alternative, to continue getting theme updates on all stylesheets, is to use higher specificity CSS selectors in your own additional, originally named CSS files.</p>
@@ -403,22 +407,22 @@ explorer /usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0
403
407
 
404
408
  <p>Suppose you want to get rid of the gem-based theme and convert it to a regular theme, where all files are present in your Jekyll site directory, with nothing stored in the theme gem.</p>
405
409
 
406
- <p>To do this, copy the files from the theme gem’s directory into your Jekyll site directory. (For example, copy them to <code class="language-plaintext highlighter-rouge">/myblog</code> if you created your Jekyll site at <code class="language-plaintext highlighter-rouge">/myblog</code>. See the previous section for details.)</p>
410
+ <p>To do this, copy the files from the theme gem’s directory into your Jekyll site directory. (For example, copy them to <code class="highlighter-rouge">/myblog</code> if you created your Jekyll site at <code class="highlighter-rouge">/myblog</code>. See the previous section for details.)</p>
407
411
 
408
412
  <p>Then you must tell Jekyll about the plugins that were referenced by the theme. You can find these plugins in the theme’s gemspec file as runtime dependencies. If you were converting the Minima theme, for example, you might see:</p>
409
413
 
410
- <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>spec.add_runtime_dependency "jekyll-feed", "~&gt; 0.9"
411
- spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
414
+ <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>spec.add_runtime_dependency "jekyll-feed", "~&gt; 0.12"
415
+ spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.6"
412
416
  </code></pre></div></div>
413
417
 
414
- <p>You should include these references in the <code class="language-plaintext highlighter-rouge">Gemfile</code> in one of two ways.</p>
418
+ <p>You should include these references in the <code class="highlighter-rouge">Gemfile</code> in one of two ways.</p>
415
419
 
416
- <p>You could list them individually in both <code class="language-plaintext highlighter-rouge">Gemfile</code> and <code class="language-plaintext highlighter-rouge">_config.yml</code>.</p>
420
+ <p>You could list them individually in both <code class="highlighter-rouge">Gemfile</code> and <code class="highlighter-rouge">_config.yml</code>.</p>
417
421
 
418
422
  <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># ./Gemfile</span>
419
423
 
420
- <span class="n">gem</span> <span class="s2">"jekyll-feed"</span><span class="p">,</span> <span class="s2">"~&gt; 0.9"</span>
421
- <span class="n">gem</span> <span class="s2">"jekyll-seo-tag"</span><span class="p">,</span> <span class="s2">"~&gt; 2.1"</span>
424
+ <span class="n">gem</span> <span class="s2">"jekyll-feed"</span><span class="p">,</span> <span class="s2">"~&gt; 0.12"</span>
425
+ <span class="n">gem</span> <span class="s2">"jekyll-seo-tag"</span><span class="p">,</span> <span class="s2">"~&gt; 2.6"</span>
422
426
  </code></pre></div></div>
423
427
 
424
428
  <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># ./_config.yml</span>
@@ -428,53 +432,54 @@ spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
428
432
  <span class="pi">-</span> <span class="s">jekyll-seo-tag</span>
429
433
  </code></pre></div></div>
430
434
 
431
- <p>Or you could list them explicitly as Jekyll plugins in your Gemfile, and not update <code class="language-plaintext highlighter-rouge">_config.yml</code>, like this:</p>
435
+ <p>Or you could list them explicitly as Jekyll plugins in your Gemfile, and not update <code class="highlighter-rouge">_config.yml</code>, like this:</p>
432
436
 
433
437
  <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># ./Gemfile</span>
434
438
 
435
439
  <span class="n">group</span> <span class="ss">:jekyll_plugins</span> <span class="k">do</span>
436
- <span class="n">gem</span> <span class="s2">"jekyll-feed"</span><span class="p">,</span> <span class="s2">"~&gt; 0.9"</span>
437
- <span class="n">gem</span> <span class="s2">"jekyll-seo-tag"</span><span class="p">,</span> <span class="s2">"~&gt; 2.1"</span>
440
+ <span class="n">gem</span> <span class="s2">"jekyll-feed"</span><span class="p">,</span> <span class="s2">"~&gt; 0.12"</span>
441
+ <span class="n">gem</span> <span class="s2">"jekyll-seo-tag"</span><span class="p">,</span> <span class="s2">"~&gt; 2.6"</span>
438
442
  <span class="k">end</span>
439
443
  </code></pre></div></div>
440
444
 
441
- <p>Either way, don’t forget to <code class="language-plaintext highlighter-rouge">bundle update</code>.</p>
445
+ <p>Either way, don’t forget to <code class="highlighter-rouge">bundle update</code>.</p>
442
446
 
443
- <p>However, if you’re publishing on GitHub Pages you should update only your <code class="language-plaintext highlighter-rouge">_config.yml</code> as GitHub Pages doesn’t load plugins via Bundler.</p>
447
+ <p>If you’re publishing on GitHub Pages you should update only your <code class="highlighter-rouge">_config.yml</code> as GitHub Pages doesn’t load plugins via Bundler.</p>
444
448
 
445
- <p>Finally, remove references to the theme gem in <code class="language-plaintext highlighter-rouge">Gemfile</code> and configuration. For example, to remove <code class="language-plaintext highlighter-rouge">minima</code>:</p>
449
+ <p>Finally, remove references to the theme gem in <code class="highlighter-rouge">Gemfile</code> and configuration. For example, to remove <code class="highlighter-rouge">minima</code>:</p>
446
450
 
447
451
  <ul>
448
- <li>Open <code class="language-plaintext highlighter-rouge">Gemfile</code> and remove <code class="language-plaintext highlighter-rouge">gem "minima", "~&gt; 2.0"</code>.</li>
449
- <li>Open <code class="language-plaintext highlighter-rouge">_config.yml</code> and remove <code class="language-plaintext highlighter-rouge">theme: minima</code>.</li>
452
+ <li>Open <code class="highlighter-rouge">Gemfile</code> and remove <code class="highlighter-rouge">gem "minima", "~&gt; 2.5"</code>.</li>
453
+ <li>Open <code class="highlighter-rouge">_config.yml</code> and remove <code class="highlighter-rouge">theme: minima</code>.</li>
450
454
  </ul>
451
455
 
452
- <p>Now <code class="language-plaintext highlighter-rouge">bundle update</code> will no longer get updates for the theme gem.</p>
456
+ <p>Now <code class="highlighter-rouge">bundle update</code> will no longer get updates for the theme gem.</p>
453
457
 
454
458
  <h2 id="installing-a-theme">Installing a gem-based theme</h2>
455
459
 
456
- <p>The <code class="language-plaintext highlighter-rouge">jekyll new &lt;PATH&gt;</code> command isn’t the only way to create a new Jekyll site with a gem-based theme. You can also find gem-based themes online and incorporate them into your Jekyll project.</p>
460
+ <p>The <code class="highlighter-rouge">jekyll new &lt;PATH&gt;</code> command isn’t the only way to create a new Jekyll site with a gem-based theme. You can also find gem-based themes online and incorporate them into your Jekyll project.</p>
457
461
 
458
- <p>For example, search for <a href="https://rubygems.org/search?utf8=%E2%9C%93&amp;query=jekyll-theme">jekyll theme on RubyGems</a> to find other gem-based themes. (Note that not all themes are using <code class="language-plaintext highlighter-rouge">jekyll-theme</code> as a convention in the theme name.)</p>
462
+ <p>For example, search for <a href="https://rubygems.org/search?utf8=%E2%9C%93&amp;query=jekyll-theme">jekyll theme on RubyGems</a> to find other gem-based themes. (Note that not all themes are using <code class="highlighter-rouge">jekyll-theme</code> as a convention in the theme name.)</p>
459
463
 
460
464
  <p>To install a gem-based theme:</p>
461
465
 
462
466
  <ol>
463
467
  <li>
464
- <p>Add the theme to your site’s <code class="language-plaintext highlighter-rouge">Gemfile</code>:</p>
468
+ <p>Add the theme gem to your site’s <code class="highlighter-rouge">Gemfile</code>:</p>
465
469
 
466
470
  <div class="language-ruby highlighter-rouge">
467
471
  <div class="highlight"><pre class="highlight"><code><span class="c1"># ./Gemfile</span>
468
472
 
469
- <span class="n">gem</span> <span class="s2">"jekyll-theme-awesome"</span>
473
+ <span class="c1"># This is an example, declare the theme gem you want to use here</span>
474
+ <span class="n">gem</span> <span class="s2">"jekyll-theme-minimal"</span>
470
475
  </code></pre></div> </div>
471
- <p>Or if you’ve started with the <code class="language-plaintext highlighter-rouge">jekyll new</code> command, replace <code class="language-plaintext highlighter-rouge">gem "minima", "~&gt; 2.0"</code> with your theme-gem:</p>
476
+ <p>Or if you’ve started with the <code class="highlighter-rouge">jekyll new</code> command, replace <code class="highlighter-rouge">gem "minima", "~&gt; 2.0"</code> with the gem you want, e.g:</p>
472
477
 
473
478
  <div class="language-diff highlighter-rouge">
474
479
  <div class="highlight"><pre class="highlight"><code><span class="err">#</span> ./Gemfile
475
480
 
476
- - gem "minima", "~&gt; 2.0"
477
- <span class="gi">+ gem "jekyll-theme-awesome"
481
+ - gem "minima", "~&gt; 2.5"
482
+ <span class="gi">+ gem "jekyll-theme-minimal"
478
483
  </span></code></pre></div> </div>
479
484
  </li>
480
485
  <li>
@@ -485,10 +490,10 @@ spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
485
490
  </code></pre></div> </div>
486
491
  </li>
487
492
  <li>
488
- <p>Add the following to your site’s <code class="language-plaintext highlighter-rouge">_config.yml</code> to activate the theme:</p>
493
+ <p>Add the following to your site’s <code class="highlighter-rouge">_config.yml</code> to activate the theme:</p>
489
494
 
490
495
  <div class="language-yaml highlighter-rouge">
491
- <div class="highlight"><pre class="highlight"><code><span class="na">theme</span><span class="pi">:</span> <span class="s">jekyll-theme-awesome</span>
496
+ <div class="highlight"><pre class="highlight"><code><span class="na">theme</span><span class="pi">:</span> <span class="s">jekyll-theme-minimal</span>
492
497
  </code></pre></div> </div>
493
498
  </li>
494
499
  <li>
@@ -500,15 +505,15 @@ spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
500
505
  </li>
501
506
  </ol>
502
507
 
503
- <p class="note info">You can have multiple themes listed in your site’s <code class="language-plaintext highlighter-rouge">Gemfile</code>, but only one theme can be selected in your site’s <code class="language-plaintext highlighter-rouge">_config.yml</code>.</p>
508
+ <p class="note info">You can have multiple themes listed in your site’s <code class="highlighter-rouge">Gemfile</code>, but only one theme can be selected in your site’s <code class="highlighter-rouge">_config.yml</code>.</p>
504
509
 
505
- <p>If you’re publishing your Jekyll site on <a href="https://pages.github.com/">GitHub Pages</a>, note that GitHub Pages supports only some gem-based themes. See <a href="https://pages.github.com/themes/">Supported Themes</a> in GitHub’s documentation to see which themes are supported.</p>
510
+ <p>If you’re publishing your Jekyll site on <a href="https://pages.github.com/">GitHub Pages</a>, note that GitHub Pages supports only <a href="https://pages.github.com/themes/">some gem-based themes</a>. GitHub Pages also supports <a href="https://help.github.com/articles/adding-a-jekyll-theme-to-your-github-pages-site/#adding-a-jekyll-theme-in-your-sites-_configyml-file">using any theme hosted on GitHub</a> using the <code class="highlighter-rouge">remote_theme</code> configuration as if it were a gem-based theme.</p>
506
511
 
507
512
  <h2 id="creating-a-gem-based-theme">Creating a gem-based theme</h2>
508
513
 
509
- <p>If you’re a Jekyll theme developer (rather than just a consumer of themes), you can package up your theme in RubyGems and allow users to install it through Bundler.</p>
514
+ <p>If you’re a Jekyll theme developer (rather than a consumer of themes), you can package up your theme in RubyGems and allow users to install it through Bundler.</p>
510
515
 
511
- <p>If you’re unfamiliar with creating Ruby gems, don’t worry. Jekyll will help you scaffold a new theme with the <code class="language-plaintext highlighter-rouge">new-theme</code> command. Run <code class="language-plaintext highlighter-rouge">jekyll new-theme</code> with the theme name as an argument.</p>
516
+ <p>If you’re unfamiliar with creating Ruby gems, don’t worry. Jekyll will help you scaffold a new theme with the <code class="highlighter-rouge">new-theme</code> command. Run <code class="highlighter-rouge">jekyll new-theme</code> with the theme name as an argument.</p>
512
517
 
513
518
  <p>Here is an example:</p>
514
519
 
@@ -529,59 +534,76 @@ Your new Jekyll theme, jekyll-theme-awesome, is ready <span class="k">for </span
529
534
  For <span class="nb">help </span>getting started, <span class="nb">read</span> /path/to/jekyll-theme-awesome/README.md.
530
535
  </code></pre></div></div>
531
536
 
532
- <p>Add your template files in the corresponding folders. Then complete the <code class="language-plaintext highlighter-rouge">.gemspec</code> and the README files according to your needs.</p>
537
+ <p>Add your template files in the corresponding folders. Then complete the <code class="highlighter-rouge">.gemspec</code> and the README files according to your needs.</p>
533
538
 
534
539
  <h3 id="layouts-and-includes">Layouts and includes</h3>
535
540
 
536
- <p>Theme layouts and includes work just like they work in any Jekyll site. Place layouts in your theme’s <code class="language-plaintext highlighter-rouge">/_layouts</code> folder, and place includes in your themes <code class="language-plaintext highlighter-rouge">/_includes</code> folder.</p>
541
+ <p>Theme layouts and includes work just like they work in any Jekyll site. Place layouts in your theme’s <code class="highlighter-rouge">/_layouts</code> folder, and place includes in your themes <code class="highlighter-rouge">/_includes</code> folder.</p>
537
542
 
538
- <p>For example, if your theme has a <code class="language-plaintext highlighter-rouge">/_layouts/page.html</code> file, and a page has <code class="language-plaintext highlighter-rouge">layout: page</code> in its YAML front matter, Jekyll will first look to the site’s <code class="language-plaintext highlighter-rouge">_layouts</code> folder for the <code class="language-plaintext highlighter-rouge">page</code> layout, and if none exists, will use your theme’s <code class="language-plaintext highlighter-rouge">page</code> layout.</p>
543
+ <p>For example, if your theme has a <code class="highlighter-rouge">/_layouts/page.html</code> file, and a page has <code class="highlighter-rouge">layout: page</code> in its front matter, Jekyll will first look to the site’s <code class="highlighter-rouge">_layouts</code> folder for the <code class="highlighter-rouge">page</code> layout, and if none exists, will use your theme’s <code class="highlighter-rouge">page</code> layout.</p>
539
544
 
540
545
  <h3 id="assets">Assets</h3>
541
546
 
542
- <p>Any file in <code class="language-plaintext highlighter-rouge">/assets</code> will be copied over to the user’s site upon build unless they have a file with the same relative path. You can ship any kind of asset here: SCSS, an image, a webfont, etc. These files behave like pages and static files in Jekyll:</p>
547
+ <p>Any file in <code class="highlighter-rouge">/assets</code> will be copied over to the user’s site upon build unless they have a file with the same relative path. You can ship any kind of asset here: SCSS, an image, a webfont, etc. These files behave like pages and static files in Jekyll:</p>
543
548
 
544
549
  <ul>
545
- <li>If the file has <a href="/docs/frontmatter/">YAML front matter</a> at the top, it will be rendered.</li>
546
- <li>If the file does not have YAML front matter, it will simply be copied over into the resulting site.</li>
550
+ <li>If the file has <a href="/docs/front-matter/">front matter</a> at the top, it will be rendered.</li>
551
+ <li>If the file does not have front matter, it will simply be copied over into the resulting site.</li>
547
552
  </ul>
548
553
 
549
- <p>This allows theme creators to ship a default <code class="language-plaintext highlighter-rouge">/assets/styles.scss</code> file which their layouts can depend on as <code class="language-plaintext highlighter-rouge">/assets/styles.css</code>.</p>
554
+ <p>This allows theme creators to ship a default <code class="highlighter-rouge">/assets/styles.scss</code> file which their layouts can depend on as <code class="highlighter-rouge">/assets/styles.css</code>.</p>
550
555
 
551
- <p>All files in <code class="language-plaintext highlighter-rouge">/assets</code> will be output into the compiled site in the <code class="language-plaintext highlighter-rouge">/assets</code> folder just as you’d expect from using Jekyll on your sites.</p>
556
+ <p>All files in <code class="highlighter-rouge">/assets</code> will be output into the compiled site in the <code class="highlighter-rouge">/assets</code> folder just as you’d expect from using Jekyll on your sites.</p>
552
557
 
553
558
  <h3 id="stylesheets">Stylesheets</h3>
554
559
 
555
- <p>Your theme’s stylesheets should be placed in your theme’s <code class="language-plaintext highlighter-rouge">_sass</code> folder, again, just as you would when authoring a Jekyll site.</p>
560
+ <p>Your theme’s stylesheets should be placed in your theme’s <code class="highlighter-rouge">_sass</code> folder, again, just as you would when authoring a Jekyll site.</p>
556
561
 
557
- <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>_sass
562
+ <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>_sass
558
563
  ├── jekyll-theme-awesome.scss
559
564
  </code></pre></div></div>
560
565
 
561
- <p>Your theme’s styles can be included in the user’s stylesheet using the <code class="language-plaintext highlighter-rouge">@import</code> directive.</p>
566
+ <p>Your theme’s styles can be included in the user’s stylesheet using the <code class="highlighter-rouge">@import</code> directive.</p>
562
567
 
563
568
  <div class="language-css highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="k">@import</span> <span class="s1">"{{ site.theme }}"</span><span class="p">;</span>
564
569
  </code></pre></div></div>
565
570
 
566
571
  <h3 id="theme-gem-dependencies350">Theme-gem dependencies<span class="version-badge" title="This feature is available starting version 3.5.0">3.5.0</span>
567
572
  </h3>
568
- <p>Jekyll will automatically require all whitelisted <code class="language-plaintext highlighter-rouge">runtime_dependencies</code> of your theme-gem even if they’re not explicitly included under the <code class="language-plaintext highlighter-rouge">plugins</code> array in the site’s config file. (Note: whitelisting is only required when building or serving with the <code class="language-plaintext highlighter-rouge">--safe</code> option.)</p>
573
+ <p>Jekyll will automatically require all whitelisted <code class="highlighter-rouge">runtime_dependencies</code> of your theme-gem even if they’re not explicitly included under the <code class="highlighter-rouge">plugins</code> array in the site’s config file. (Note: whitelisting is only required when building or serving with the <code class="highlighter-rouge">--safe</code> option.)</p>
569
574
 
570
575
  <p>With this, the end-user need not keep track of the plugins required to be included in their config file for their theme-gem to work as intended.</p>
571
576
 
577
+ <h3 id="pre-configuring-theme-gems40">Pre-configuring Theme-gems<span class="version-badge" title="This feature is available starting version 4.0">4.0</span>
578
+ </h3>
579
+ <p>Jekyll will read-in a <code class="highlighter-rouge">_config.yml</code> at the root of the theme-gem and merge its data into the site’s existing configuration data.</p>
580
+
581
+ <p>But unlike other entities loaded from within the theme, loading the config file comes with a few restrictions, as summarized below:</p>
582
+ <ul>
583
+ <li>Jekyll’s default settings cannot be overridden by a theme-config. That <em>ball is still in the user’s court.</em>
584
+ </li>
585
+ <li>The theme-config-file cannot be a symlink, irrespective of <code class="highlighter-rouge">safe mode</code> and whether the file pointed to by the symlink is a legitimate file within the theme-gem.</li>
586
+ <li>The theme-config should be a set of key-value pairs. An empty config file, a config file that simply <em>lists items</em> under a key, or a config file with just a simple string of text will simply be ignored silently. Users will not get a warning or any log output regarding this discrepancy.</li>
587
+ <li>Any settings defined by the theme-config can be overridden by the user.</li>
588
+ </ul>
589
+
590
+ <p>While this feature is to enable easier adoption of a theme, the restrictions ensure that a theme-config cannot affect the build in a concerning manner. Any plugins required by the theme will have to be listed manually by the user or provided by the theme’s <code class="highlighter-rouge">gemspec</code> file.</p>
591
+
592
+ <p>This feature will let the theme-gem to work with <em>theme-specific config variables</em> out-of-the-box.</p>
593
+
572
594
  <h3 id="documenting-your-theme">Documenting your theme</h3>
573
595
 
574
- <p>Your theme should include a <code class="language-plaintext highlighter-rouge">/README.md</code> file, which explains how site authors can install and use your theme. What layouts are included? What includes? Do they need to add anything special to their site’s configuration file?</p>
596
+ <p>Your theme should include a <code class="highlighter-rouge">/README.md</code> file, which explains how site authors can install and use your theme. What layouts are included? What includes? Do they need to add anything special to their site’s configuration file?</p>
575
597
 
576
598
  <h3 id="adding-a-screenshot">Adding a screenshot</h3>
577
599
 
578
- <p>Themes are visual. Show users what your theme looks like by including a screenshot as <code class="language-plaintext highlighter-rouge">/screenshot.png</code> within your theme’s repository where it can be retrieved programmatically. You can also include this screenshot within your theme’s documentation.</p>
600
+ <p>Themes are visual. Show users what your theme looks like by including a screenshot as <code class="highlighter-rouge">/screenshot.png</code> within your theme’s repository where it can be retrieved programmatically. You can also include this screenshot within your theme’s documentation.</p>
579
601
 
580
602
  <h3 id="previewing-your-theme">Previewing your theme</h3>
581
603
 
582
- <p>To preview your theme as you’re authoring it, it may be helpful to add dummy content in, for example, <code class="language-plaintext highlighter-rouge">/index.html</code> and <code class="language-plaintext highlighter-rouge">/page.html</code> files. This will allow you to use the <code class="language-plaintext highlighter-rouge">jekyll build</code> and <code class="language-plaintext highlighter-rouge">jekyll serve</code> commands to preview your theme, just as you’d preview a Jekyll site.</p>
604
+ <p>To preview your theme as you’re authoring it, it may be helpful to add dummy content in, for example, <code class="highlighter-rouge">/index.html</code> and <code class="highlighter-rouge">/page.html</code> files. This will allow you to use the <code class="highlighter-rouge">jekyll build</code> and <code class="highlighter-rouge">jekyll serve</code> commands to preview your theme, just as you’d preview a Jekyll site.</p>
583
605
 
584
- <p class="info note">If you do preview your theme locally, be sure to add <code class="language-plaintext highlighter-rouge">/_site</code> to your theme’s <code class="language-plaintext highlighter-rouge">.gitignore</code> file to prevent the compiled site from also being included when you distribute your theme.</p>
606
+ <p class="info note">If you do preview your theme locally, be sure to add <code class="highlighter-rouge">/_site</code> to your theme’s <code class="highlighter-rouge">.gitignore</code> file to prevent the compiled site from also being included when you distribute your theme.</p>
585
607
 
586
608
  <h3 id="publishing-your-theme">Publishing your theme</h3>
587
609
 
@@ -598,301 +620,236 @@ git commit <span class="nt">-m</span> <span class="s2">"Init commit"</span>
598
620
  </code></pre></div> </div>
599
621
  </li>
600
622
  <li>
601
- <p>Next, package your theme, by running the following command, replacing <code class="language-plaintext highlighter-rouge">jekyll-theme-awesome</code> with the name of your theme:</p>
623
+ <p>Next, package your theme, by running the following command, replacing <code class="highlighter-rouge">jekyll-theme-awesome</code> with the name of your theme:</p>
602
624
 
603
625
  <div class="language-sh highlighter-rouge">
604
626
  <div class="highlight"><pre class="highlight"><code>gem build jekyll-theme-awesome.gemspec
605
627
  </code></pre></div> </div>
606
628
  </li>
607
629
  <li>
608
- <p>Finally, push your packaged theme up to the RubyGems service, by running the following command, again replacing <code class="language-plaintext highlighter-rouge">jekyll-theme-awesome</code> with the name of your theme:</p>
630
+ <p>Finally, push your packaged theme up to the RubyGems service, by running the following command, again replacing <code class="highlighter-rouge">jekyll-theme-awesome</code> with the name of your theme:</p>
609
631
 
610
632
  <div class="language-sh highlighter-rouge">
611
633
  <div class="highlight"><pre class="highlight"><code>gem push jekyll-theme-awesome-<span class="k">*</span>.gem
612
634
  </code></pre></div> </div>
613
635
  </li>
614
636
  <li>
615
- <p>To release a new version of your theme, update the version number in the gemspec file, ( <code class="language-plaintext highlighter-rouge">jekyll-theme-awesome.gemspec</code> in this example ), and then repeat Steps 1 - 3 above. We recommend that you follow <a href="http://semver.org/">Semantic Versioning</a> while bumping your theme-version.</p>
637
+ <p>To release a new version of your theme, update the version number in the gemspec file, ( <code class="highlighter-rouge">jekyll-theme-awesome.gemspec</code> in this example ), and then repeat Steps 1 - 3 above. We recommend that you follow <a href="http://semver.org/">Semantic Versioning</a> while bumping your theme-version.</p>
616
638
  </li>
617
639
  </ol>
618
640
 
619
-
620
-
621
-
622
-
623
-
624
-
625
-
626
-
627
-
628
-
629
-
630
-
631
-
632
-
633
-
634
-
635
-
636
-
637
-
638
-
639
-
640
-
641
-
642
-
643
-
644
-
645
-
646
-
647
-
648
-
649
-
650
-
651
-
652
-
653
-
654
-
655
-
656
-
657
-
658
-
659
-
660
-
661
-
662
-
663
-
664
-
665
-
666
-
667
-
668
-
669
-
670
-
671
-
672
-
673
-
674
-
675
-
676
-
677
-
678
-
679
-
680
-
681
-
682
-
683
-
684
-
685
-
686
-
687
-
688
-
689
-
690
-
691
-
692
-
693
- <div class="section-nav">
694
- <div class="left align-right">
695
-
696
-
697
-
698
- <a href="/docs/plugins/" class="prev">Back</a>
699
-
700
- </div>
701
- <div class="right align-left">
702
-
703
-
704
-
705
- <a href="/docs/extras/" class="next">Next</a>
706
-
707
- </div>
708
- </div>
709
- <div class="clear"></div>
710
-
711
641
  </article>
712
642
  </div>
713
643
 
714
644
  <div class="unit one-fifth hide-on-mobiles">
715
645
  <aside>
716
646
 
717
- <h4>Getting Started</h4>
718
- <ul>
719
-
720
-
721
-
722
- <li class=""><a href="/docs/home/">Welcome</a></li>
723
-
724
-
725
-
726
- <li class=""><a href="/docs/quickstart/">Quick-start guide</a></li>
727
-
728
-
729
-
730
- <li class=""><a href="/docs/installation/">Installation</a></li>
731
-
732
-
733
-
734
- <li class=""><a href="/docs/windows/">Jekyll on Windows</a></li>
735
-
736
-
737
-
738
- <li class=""><a href="/docs/usage/">Basic Usage</a></li>
739
-
740
-
741
-
742
- <li class=""><a href="/docs/structure/">Directory structure</a></li>
743
-
744
-
745
-
746
- <li class=""><a href="/docs/configuration/">Configuration</a></li>
747
-
748
- </ul>
749
-
750
-
751
- <h4>Your Content</h4>
752
- <ul>
753
-
754
-
755
-
756
- <li class=""><a href="/docs/frontmatter/">Front Matter</a></li>
757
-
758
-
759
-
760
- <li class=""><a href="/docs/posts/">Writing posts</a></li>
761
-
762
-
763
-
764
- <li class=""><a href="/docs/drafts/">Working with drafts</a></li>
765
-
766
-
767
-
768
- <li class=""><a href="/docs/pages/">Creating pages</a></li>
769
-
770
-
771
-
772
- <li class=""><a href="/docs/static-files/">Static Files</a></li>
773
-
774
-
775
-
776
- <li class=""><a href="/docs/variables/">Variables</a></li>
777
-
778
-
779
-
780
- <li class=""><a href="/docs/collections/">Collections</a></li>
781
-
782
-
783
-
784
- <li class=""><a href="/docs/datafiles/">Data Files</a></li>
785
-
786
-
787
-
788
- <li class=""><a href="/docs/assets/">Assets</a></li>
789
-
790
-
791
-
792
- <li class=""><a href="/docs/migrations/">Blog migrations</a></li>
793
-
794
- </ul>
795
-
647
+ <h4>Getting Started</h4>
648
+ <ul>
649
+
650
+
651
+ <li>
652
+ <a href="/docs/">
653
+ Quickstart
654
+ </a>
655
+ </li>
656
+
657
+
658
+ <li>
659
+ <a href="/docs/ruby-101/">
660
+ Ruby 101
661
+ </a>
662
+ </li>
663
+
664
+
665
+ <li>
666
+ <a href="/docs/installation/">
667
+ Installation
668
+ </a>
669
+ </li>
670
+
671
+
672
+ <li>
673
+ <a href="/docs/community/">
674
+ Community
675
+ </a>
676
+ </li>
677
+
678
+
679
+ <li>
680
+ <a href="/docs/step-by-step/01-setup/">
681
+ Step by Step Tutorial
682
+ </a>
683
+ </li>
684
+
685
+ </ul>
796
686
 
797
- <h4>Customization</h4>
798
- <ul>
799
-
800
-
801
-
802
- <li class=""><a href="/docs/templates/">Templates</a></li>
803
-
804
-
805
-
806
- <li class=""><a href="/docs/includes/">Includes</a></li>
807
-
808
-
809
-
810
- <li class=""><a href="/docs/permalinks/">Permalinks</a></li>
811
-
812
-
813
-
814
- <li class=""><a href="/docs/pagination/">Pagination</a></li>
815
-
816
-
817
-
818
- <li class=""><a href="/docs/plugins/">Plugins</a></li>
819
-
820
-
821
-
822
- <li class="current"><a href="/docs/themes/">Themes</a></li>
823
-
824
-
825
-
826
- <li class=""><a href="/docs/extras/">Extras</a></li>
827
-
828
- </ul>
829
-
687
+ <h4>Build</h4>
688
+ <ul>
689
+
690
+
691
+ <li>
692
+ <a href="/docs/usage/">
693
+ Command Line Usage
694
+ </a>
695
+ </li>
696
+
697
+
698
+ <li>
699
+ <a href="/docs/configuration/">
700
+ Configuration
701
+ </a>
702
+ </li>
703
+
704
+ </ul>
830
705
 
831
- <h4>Deployment</h4>
832
- <ul>
833
-
834
-
835
-
836
- <li class=""><a href="/docs/github-pages/">GitHub Pages</a></li>
837
-
838
-
839
-
840
- <li class=""><a href="/docs/deployment-methods/">Deployment methods</a></li>
841
-
842
-
843
-
844
- <li class=""><a href="/docs/continuous-integration/">Continuous Integration</a></li>
845
-
846
- </ul>
847
-
706
+ <h4>Content</h4>
707
+ <ul>
708
+
709
+
710
+ <li>
711
+ <a href="/docs/pages/">
712
+ Pages
713
+ </a>
714
+ </li>
715
+
716
+
717
+ <li>
718
+ <a href="/docs/posts/">
719
+ Posts
720
+ </a>
721
+ </li>
722
+
723
+
724
+ <li>
725
+ <a href="/docs/front-matter/">
726
+ Front Matter
727
+ </a>
728
+ </li>
729
+
730
+
731
+ <li>
732
+ <a href="/docs/collections/">
733
+ Collections
734
+ </a>
735
+ </li>
736
+
737
+
738
+ <li>
739
+ <a href="/docs/datafiles/">
740
+ Data Files
741
+ </a>
742
+ </li>
743
+
744
+
745
+ <li>
746
+ <a href="/docs/assets/">
747
+ Assets
748
+ </a>
749
+ </li>
750
+
751
+
752
+ <li>
753
+ <a href="/docs/static-files/">
754
+ Static Files
755
+ </a>
756
+ </li>
757
+
758
+ </ul>
848
759
 
849
- <h4>Miscellaneous</h4>
850
- <ul>
851
-
852
-
853
-
854
- <li class=""><a href="/docs/troubleshooting/">Troubleshooting</a></li>
855
-
856
-
857
-
858
- <li class=""><a href="/docs/sites/">Sites using Jekyll</a></li>
859
-
860
-
861
-
862
- <li class=""><a href="/docs/resources/">Resources</a></li>
863
-
864
-
865
-
866
- <li class=""><a href="/docs/upgrading/0-to-2/">Upgrading from 0.x to 2.x</a></li>
867
-
868
-
869
-
870
- <li class=""><a href="/docs/upgrading/2-to-3/">Upgrading from 2.x to 3.x</a></li>
871
-
872
- </ul>
873
-
760
+ <h4>Site Structure</h4>
761
+ <ul>
762
+
763
+
764
+ <li>
765
+ <a href="/docs/structure/">
766
+ Directory Structure
767
+ </a>
768
+ </li>
769
+
770
+
771
+ <li>
772
+ <a href="/docs/liquid/">
773
+ Liquid
774
+ </a>
775
+ </li>
776
+
777
+
778
+ <li>
779
+ <a href="/docs/variables/">
780
+ Variables
781
+ </a>
782
+ </li>
783
+
784
+
785
+ <li>
786
+ <a href="/docs/includes/">
787
+ Includes
788
+ </a>
789
+ </li>
790
+
791
+
792
+ <li>
793
+ <a href="/docs/layouts/">
794
+ Layouts
795
+ </a>
796
+ </li>
797
+
798
+
799
+ <li>
800
+ <a href="/docs/permalinks/">
801
+ Permalinks
802
+ </a>
803
+ </li>
804
+
805
+
806
+ <li class="current">
807
+ <a href="/docs/themes/">
808
+ Themes
809
+ </a>
810
+ </li>
811
+
812
+
813
+ <li>
814
+ <a href="/docs/pagination/">
815
+ Pagination
816
+ </a>
817
+ </li>
818
+
819
+ </ul>
874
820
 
875
- <h4>Meta</h4>
876
- <ul>
877
-
878
-
879
-
880
- <li class=""><a href="/docs/contributing/">Contributing</a></li>
881
-
882
-
883
-
884
- <li class=""><a href="/docs/maintaining/">Maintaining Jekyll</a></li>
885
-
886
-
887
-
888
- <li class=""><a href="/docs/conduct/">Code of Conduct</a></li>
889
-
890
-
891
-
892
- <li class=""><a href="/docs/history/">History</a></li>
893
-
894
- </ul>
895
-
821
+ <h4>Guides</h4>
822
+ <ul>
823
+
824
+
825
+ <li>
826
+ <a href="/docs/plugins/">
827
+ Plugins
828
+ </a>
829
+ </li>
830
+
831
+
832
+ <li>
833
+ <a href="/docs/migrations/">
834
+ Blog Migrations
835
+ </a>
836
+ </li>
837
+
838
+
839
+ <li>
840
+ <a href="/docs/upgrading/">
841
+ Upgrading
842
+ </a>
843
+ </li>
844
+
845
+
846
+ <li>
847
+ <a href="/docs/deployment/">
848
+ Deployment
849
+ </a>
850
+ </li>
851
+
852
+ </ul>
896
853
 
897
854
  </aside>
898
855
  </div>
@@ -907,7 +864,8 @@ git commit <span class="nt">-m</span> <span class="s2">"Init commit"</span>
907
864
  <footer>
908
865
  <div class="grid">
909
866
  <div class="unit one-third center-on-mobiles">
910
- <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>
867
+ <p>Jekyll is lovingly maintained by the <a href="/team/">core team</a> of volunteers. </p>
868
+ <p>The contents of this website are <br>© 2019 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
911
869
  </div>
912
870
  <div class="unit two-thirds align-right center-on-mobiles">
913
871
  <p>
@@ -917,6 +875,14 @@ git commit <span class="nt">-m</span> <span class="s2">"Init commit"</span>
917
875
  </a>
918
876
  </p>
919
877
  </div>
878
+ <div class="unit two-thirds align-right center-on-mobiles">
879
+ <p>
880
+ Jekyll is funded thanks to its
881
+ <a href="https://github.com/jekyll/jekyll#sponsors">
882
+ sponsors!
883
+ </a>
884
+ </p>
885
+ </div>
920
886
  </div>
921
887
  </footer>
922
888