classic-jekyll-theme 1.9.2 → 1.9.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 4740375dbd332a0c6cebc64ba6593e7c36a59b54
-  data.tar.gz: 2456e1de193797b1c8a1a34a5615de22dff7bc96
+  metadata.gz: 5afb06bcd3a7d3d37457db9e43c64b5628b89d55
+  data.tar.gz: 54511e50b300ba23973cdfa238d37e30bf637205
 SHA512:
-  metadata.gz: '086689359df8d7486b7b58eb7b1000c87e6ba9f82f90a4fcd73dc48bfe2cbc06127a93fc90ca89d039415f1c5b04177734faee84e3f270479dead4c5bc5ac71e'
-  data.tar.gz: 91748fe02212d80a9679085b608c38f969375366541d8486213c87af85b2dcaf418f4977f5cbf4ca9c6c5390367ce916b2b862029bc5c64d09b8ab27fe838712
+  metadata.gz: fc7e0fc511c13340bb43f5ba63d870ba34778cdafd4baad198bbc8695e1da6b8d120a46637f6a8cc468cc7a565e6ba12b67881dcfc23a3dbd5d508ff8af7d847
+  data.tar.gz: 7a1b60b2de726465789cc58f483615dd60013f71a39ad6a0d3a9f5733439a1726355a2144caa9dfab4c7b919e23b3d5fc74c2fafc5c9af62d3330b8e919254ed

data/README.md

@@ -1,4 +1,4 @@
-# Classic-Jekyll-Theme v1.9.2
+# Classic-Jekyll-Theme v1.9.3
 
 Welcome to Classic-Jekyll-Theme. This theme centers around one of the most used website structures on the web. A banner, navigation menu (dropdown), (up to) three columns and a footer. The design is fully responsive for three different screen widths: wide, medium and narrow. It is probably best shown in an example:
 
@@ -93,7 +93,6 @@ Change in the Gemfile:
 Change in the `_config.yml`:
 
 	From `theme: minima` to `theme: classic-jekyll-theme`
-	Add `jekyll-data` to the gems.
 
 Delete the file `about.md`:
 
@@ -155,7 +154,7 @@ The following values are configurable:
 	`top`: The navigation banner will be placed over the entire site (all columns)
 	`main`: The navigation banner will be placed at the top of the main column. Possibly next to or in between the secondary and tertiary columns.
 
-- useSeparateNavBanner:
+- use-separate-navbanner:
 
 	`yes`: Use a separate file for the navigation banner. This may cause a slight performance hit for browsers, but is a huge performance enhancement for the site generation process. Note that this option necessitates a JQuery library. By default the google JQuery library is loaded. Update the `_includes/head.html` if a different JQuery library should be used or if the library should be upgraded.
 	`no`: Generate the navigation banner in-line into the posts and pages.
@@ -202,7 +201,7 @@ Typically you will need to copy some files from the gem itself to the project (w
 - `_data/text-for.yml` for configuration.
 - `_includes/secondary-column.html` for the secondary column contents.
 - `_includes/tertiary-column.html` for the tertiary column contents.
-- `navbanner.md` for the navigation bar menu. This is mandatory if the `useSeparateNavBanner` setting is used, optional when not. Hence its easier to always copy this file.
+- `navbanner.md` for the navigation bar menu. This is mandatory if the `use-separate-navbanner` setting is used, optional when not. Hence its easier to always copy this file.
 
 These files can be found in the gem directory. Try the command `bundle show classic-jekyll-theme` to see where the theme is located. When you copy these files, make sure they are in the same relative directory as in the gem itself.
 
@@ -250,6 +249,40 @@ To create a page that must be included in the menu bar, add the following front
 
 For a consistent user experience in the narrow layout, it is recommended not to link pages to top level menu items if these menu items have a drop-down submenu.
 
+### Alternate method for sub-menu's
+
+In addition to the method described above there is another way to generate the sub-menu items. This method is especially handy if multiple sub-menu entries must be made for a single page using Anchor-Id's.
+To create multiple sub menu entries:
+
+    ---
+    ...
+    menuInclude: yes
+    menuTopTitle: Classic
+    menuSubs:
+    -
+       title: Sub Menu Title
+       index: 3
+       anchorId: id-of-html-tag
+       url: /pages/menupage.html
+    -
+       title: '-------'
+       index: 4
+       link: no
+    -
+       title: Menu title below separator
+       index: 5
+       anchorId: second-anchor
+    ...
+    ---
+
+The fields of the menuSubs YAML tag are interpreted as follows:
+
+- title: The title of the submenu item in the drop down menu.
+- index: The place of the submenu item within the dropdown menu. Lower numbers will go above higher numbers. This theme only sorts on menuIndex numbers, not on other properties.
+- anchorId: The id of an HTML tag that the link will be made to. Do not include the '#' tag as this is gerenated automatically. I.e. the relative URL of the first entry above will be: `/pages/menupage.html#id-of-html-tag`.
+- url: The url of the page to link to. If no url is specified it will link to the page this YAML matter is in.
+- link: Set to 'no' to disable a link creation from the navigation bar to this page. However the submenu title will be included. The default behaviour assumes 'yes'. So not including this tag will create a link. Note: This probably only makes sense if some kind of "divider" must be shown. Otherwise showing a submenu item without a link will probably confuse users.
+
 ## Creating pages with custom second and tertiary columns
 
 There are 4 YAML tags that control the custom placement and content of the secondary and tertiary columns:
@@ -317,6 +350,15 @@ Release 1.9.2
 - Bugfix: David Crossley fixed a bug where the filename of the column content was not properly used.
 - Removed pre v1.8.0 notes and update instructions to shorten the readme.
 
+Release 1.9.3
+
+- Version constraint on jekyll-data from 0.4 up to < 2.0 (Ashmaroli)
+- Requires at least jekyll 3.5.1 (Ashmaroli)
+- Typo's fixed (David Crossley)
+- Added older-posts.html widget (Rien)
+- Added image to posts (Rien)
+- Added support for sub-menu links with anchor id's. Allows multiple sub-menu entries per file. (Rien)
+
 ## Upgrade information
 
 ### from 1.8.0 to 1.8.1
@@ -361,6 +403,24 @@ No changes needed.
 
 The file `_layouts/default.html` was updated.
 
+### from 1.9.2 to 1.9.3
+
+- Added a new widget: `_includes/widgets/older-posts.html`
+- Updated the following files:
+
+~~~~
+	_config.yml
+	classic-jekyll-theme.gemspec
+	_data/setup.yml
+	_data/text-for.yml
+	_includes/secondary-column.html
+	_includes/navbanner.html
+	_layouts/post.html
+	_sass/classic/_widget-support.scss
+	pages/classic/categories.md
+	pages/classic/pages.md
+~~~~
+
 ## Feedback
 
 Comments, bug reports, feature requests and improvements are eagerly anticipated via email: rien@balancingrock.nl or via [github](https://github.com/Balancingrock/classic-jekyll-theme).

data/_data/setup.yml

@@ -48,7 +48,7 @@ enable-cookies-policy: yes
 # Values: top | main
 # - top: The navigation banner will be placed above all the columns
 # - main: The navigation banner will be placed inside the main column at the top.
-# This is the default value, it may be overriden by YAML frontmatter.
+# This is the default value, it may be overridden by YAML frontmatter.
 #
 # Hint: It may be advantageous to set the $navbanner-include-banner value in the classic-jekyll-theme.scss to 'false' if this value here is set to 'true'.
 #
@@ -57,11 +57,11 @@ navbanner-position: top
 # Create a separate file containing the Navigation & Banner
 # Values: yes | no
 #
-# Using a separate navbanner file will speed up jekyll compilation a lot. However it also means that the browser has to make two additional fetches: the navbanner file and the JQuery library (the later from google). However this is mitigated by the fact that both files can be cached by the browser.
-# If another JQuery library has to be used, edit the _includes/head.html file accordingly.
+# Using a separate navbanner file will speed up jekyll compilation a lot. However it also means that the browser has to make two additional fetches: the navbanner file and the jQuery library (the latter from google). However this is mitigated by the fact that both files can be cached by the browser.
+# If another jQuery library has to be used, edit the _includes/head.html file accordingly.
 #
 # Note: If this option is set to 'yes', then make sure the file 'navbanner.md' is present (can be found in the theme folder) in the same project folder as the index.md file.
 
 use-separate-navbanner: yes
 
-# End of file
+# End of file

data/_data/text-for.yml

@@ -38,3 +38,10 @@ tCookieOk: OK
 
 # More cookie info text
 tMoreInfo: More info
+
+# Title for Older Posts widget output
+tOlderPosts: Older Posts
+
+# Month names for Older Posts widget output
+# Note: Must start with 'None' because of index starting at 0
+tMonths: [None, January, February, March, April, May, June, July, August, September, October, November, December]

data/_includes/navbanner.html

@@ -39,8 +39,100 @@
 		{% for topTitle in topTitles %}
 		
 			<!-- Create a list of sub menu item titles -->
-			{% assign subTitles = site.pages | where:'menuInclude', true | where:'menuTopTitle', topTitle | where_exp:'item', 'item.menuSubTitle != nil' | sort: 'menuSubIndex', 'last' %}
+			
+			{% comment %}<!-- note: the html comment tags are for editor coloring support
+			
+			Due to the poor support for variables in Liquid we have to resort to some fairly laborious code.
+			
+			First determine all pages that contain sub menu information for the running top menu item. These are collected in "titlePages"
+			
+			Then create four lists containing the sub menu title, index, url and link respectively. These lists are all in the same sequence such that entry [n] is applicable to the same sub menu in all lists. (I.e. they are synchronous)
+			
+			Then sort the lists into four new lists. Again these lists must be kept synchronous.
+			
+			Lastly, step through the lists to create the actual sub menu's
+			
+			-->{% endcomment %}
+			
+			{% assign titlePages = site.pages | where:'menuInclude', true | where:'menuTopTitle', topTitle %}
+			
+			{% assign subMenuTitles = "" | split: "" %}
+			{% assign subMenuIndexes = "" | split: "" %}
+			{% assign subMenuUrls = "" | split: "" %}
+			{% assign subMenuLinks = "" | split: "" %}
 
+			{% for ape in titlePages %}
+				{% if ape.menuSubTitle != nil %}
+					{% assign subMenuTitles = subMenuTitles | push: ape.menuSubTitle %}
+					{% if ape.menuSubIndex != nil %}
+						{% assign subMenuIndexes = subMenuIndexes | push: ape.menuSubIndex %}
+					{% else %}
+						{% assign subMenuIndexes = subMenuIndexes | push: -1 %}
+					{% endif %}
+					{% assign subMenuUrls = subMenuUrls | push: ape.url %}
+					{% if ape.menuLink != nil %}
+						{% assign subMenuLinks = subMenuLinks | push: ape.menuLink %}
+					{% else %}
+						{% assign subMenuLinks = subMenuLinks | push: true %}
+					{% endif %}
+				{% endif %}
+				{% if ape.menuSubs != nil %}
+					{% for sub in ape.menuSubs %}
+						{% assign subMenuTitles = subMenuTitles | push: sub.title %}
+						{% if sub.index != nil %}
+							{% assign subMenuIndexes = subMenuIndexes | push: sub.index %}
+						{% else %}
+							{% assign subMenuIndexes = subMenuIndexes | push: -1 %}
+						{% endif %}
+						{% if sub.url != nil %}
+							{% if sub.anchorId != nil %}
+								{% assign urlWithAnchorId = sub.url | append: '#' | append: sub.anchorId %}
+							{% else %}
+								{% assign urlWithAnchorId = sub.url %}
+							{% endif %}
+						{% else %}
+							{% if sub.anchorId != nil %}
+								{% assign urlWithAnchorId = ape.url | append: '#' | append: sub.anchorId %}
+							{% else %}
+								{% assign urlWithAnchorId = ape.url %}
+							{% endif %}
+						{% endif %}
+						{% assign subMenuUrls = subMenuUrls | push: urlWithAnchorId %}
+						{% if sub.link != nil %}
+							{% assign subMenuLinks = subMenuLinks | push: sub.link %}
+						{% else %}
+							{% assign subMenuLinks = subMenuLinks | push: true %}
+						{% endif %}
+					{% endfor %}
+				{% endif %}
+			{% endfor %}
+
+			{% assign sortedSubMenuTitles = "" | split: "" %}
+			{% assign sortedSubMenuIndexes = subMenuIndexes | sort %}
+			{% assign sortedSubMenuUrls = "" | split: "" %}
+			{% assign sortedSubMenuLinks = "" | split: "" %}
+
+			{% for menuIndex in sortedSubMenuIndexes %}
+				{% if menuIndex != -1 %}
+					{% for aMenuIndex in subMenuIndexes %}
+						{% if aMenuIndex == menuIndex %}
+							{% assign sortedSubMenuTitles = sortedSubMenuTitles | push: subMenuTitles[forloop.index0] %}
+							{% assign sortedSubMenuUrls = sortedSubMenuUrls | push: subMenuUrls[forloop.index0] %}
+							{% assign sortedSubMenuLinks = sortedSubMenuLinks | push: subMenuLinks[forloop.index0] %}
+							{% continue %}
+						{% endif %}
+					{% endfor %}
+				{% endif %}
+			{% endfor %}
+			{% for aMenuIndex in subMenuIndexes %}
+				{% if aMenuIndex == -1 %}
+					{% assign sortedSubMenuTitles = sortedSubMenuTitles | push: subMenuTitles[forloop.index0] %}
+					{% assign sortedSubMenuUrls = sortedSubMenuUrls | push: subMenuUrls[forloop.index0] %}
+					{% assign sortedSubMenuLinks = sortedSubMenuLinks | push: subMenuLinks[forloop.index0] %}
+					{% continue %}
+				{% endif %}
+			{% endfor %}
+			
 			<li>
 
 				<!-- Create top menu item -->
@@ -49,7 +141,7 @@
 					<div class="menu-item-separator"><p><!-- empty but necessary --></p></div>
 					<div class="menu-item">
 						<div class="menu-item-symbol">
-						{% if subTitles.size > 0 %}
+						{% if sortedSubMenuTitles.size > 0 %}
 							<p><!-- will be filled by disclosure indicator --></p>
 						{% endif %}
 						</div>
@@ -57,7 +149,7 @@
 							<!-- Find page to link to -->
 						{% assign pageFound = false %}
 						{% for ape in site.pages %}
-							{% if ape.menuTopTitle == topTitle and ape.menuSubTitle == nil %}
+							{% if ape.menuTopTitle == topTitle and ape.menuSubTitle == nil and ape.menuSubs == nil %}
 								{% if ape.menuLink == false %}
 									<p>{{ topTitle }}</p>
 								{% else %}
@@ -75,15 +167,15 @@
 				</label>
 				
 				<!-- Create sub menu items -->
-				{% if subTitles.size > 0 %}
+				{% if sortedSubMenuTitles.size > 0 %}
 					<ul>
-					{% for subTitle in subTitles %}
-						{% if subTitle.menuLink != false %}
+					{% for subTitle in sortedSubMenuTitles %}
+						{% if sortedSubMenuLinks[forloop.index0] != false %}
 						<li>
 							<div class="menu-subitem">
 								<div class="menu-subitem-symbol"></div>
 								<div class="menu-subitem-title">
-									<a href="{{ subTitle.url }}"><p>{{ subTitle.menuSubTitle }}</p></a>
+									<a href="{{ sortedSubMenuUrls[forloop.index0] }}"><p>{{ subTitle }}</p></a>
 								</div>
 							</div>
 						</li>
@@ -91,7 +183,7 @@
 						<li>
 							<div class="menu-subitem">
 								<div class="menu-subitem-symbol"></div>
-								<div class="menu-subitem-title"><p>{{ subTitle.menuSubTitle }}</p></div>
+								<div class="menu-subitem-title"><p>{{ subTitle }}</p></div>
 							</div>
 						</li>
 						{% endif %}

data/_includes/secondary-column.html

@@ -10,3 +10,7 @@
 <div class="widget-divider"></div>
 
 <div class="widget">{% include widgets/subscribe.html %}</div>
+
+<div class="widget-divider"></div>
+
+<div class="widget">{% include widgets/older-posts.html %}</div>

data/_includes/widgets/older-posts.html

@@ -0,0 +1,50 @@
+{% comment %}
+
+Usage:
+
+Translations can be configure in the _data/text-for.yml file for the items `tOlderPosts` and `tMonths`.
+
+{% endcomment %}
+<div class="older-posts">
+	{% assign olderPosts = 'Older Posts' %}
+	{% if site.data.text-for.tOlderPosts %}{% assign olderPosts = site.data.text-for.tOlderPosts %}{% endif %}
+	{% assign currentYear = "" %}
+	{% assign currentMonth = "" %}
+	{% assign yearDetails = 'no' %}
+	{% assign monthDetails = 'no' %}
+	<h1>{{ olderPosts }}:</h1>
+	{% for post in site.posts %}
+		{% assign postYear = post.date | date: "%Y" %}
+		{% assign postMonth = post.date | date: "%m" %}
+		{% if postYear != currentYear %}
+			{% assign currentYear = postYear %}
+			{% if monthDetails == 'yes' %}</details>{% assign monthDetails == 'no' %}{% endif %}
+			{% if yearDetails == 'yes' %}</details>{% assign yearDetails == 'no' %}{% endif %}
+			<details class="year-details"><summary>{{ currentYear }}</summary>
+			{% assign yearDetails = 'yes' %}
+		{% endif %}
+		{% if postMonth != currentMonth %}
+			{% if postMonth == '01' %}{% assign monthString = site.data.text-for.tMonths[1] %}
+			{% elsif postMonth == '02' %}{% assign monthString = site.data.text-for.tMonths[2] %}
+			{% elsif postMonth == '03' %}{% assign monthString = site.data.text-for.tMonths[3] %}
+			{% elsif postMonth == '04' %}{% assign monthString = site.data.text-for.tMonths[4] %}
+			{% elsif postMonth == '05' %}{% assign monthString = site.data.text-for.tMonths[5] %}
+			{% elsif postMonth == '06' %}{% assign monthString = site.data.text-for.tMonths[6] %}
+			{% elsif postMonth == '07' %}{% assign monthString = site.data.text-for.tMonths[7] %}
+			{% elsif postMonth == '08' %}{% assign monthString = site.data.text-for.tMonths[8] %}
+			{% elsif postMonth == '09' %}{% assign monthString = site.data.text-for.tMonths[9] %}
+			{% elsif postMonth == '10' %}{% assign monthString = site.data.text-for.tMonths[10] %}
+			{% elsif postMonth == '11' %}{% assign monthString = site.data.text-for.tMonths[11] %}
+			{% elsif postMonth == '12' %}{% assign monthString = site.data.text-for.tMonths[12] %}
+			{% endif %}
+			{% assign currentMonth = postMonth %}
+			{% if monthDetails == 'yes' %}</details>{% assign monthDetails == 'no' %}{% endif %}
+			<details class="month-details"><summary>{{ monthString }}</summary>
+			{% assign monthDetails = 'yes' %}
+		{% endif %}
+		<p><a href="{{ post.url }}">{{ post.title }}</a></p>
+	{% endfor %}
+	{% if monthDetails == yes %}</details>{% assign monthDetails == no %}{% endif %}
+	{% if yearDetails == yes %}</details>{% assign yearDetails == no %}{% endif %}
+</div>
+

data/_layouts/post.html

@@ -6,6 +6,7 @@ layout: default
   <header class="post-header">
     <h1 class="post-title" itemprop="name headline">{{ page.title | escape }}</h1>
     <p class="post-meta"><time datetime="{{ page.date | date_to_xmlschema }}" itemprop="datePublished">{{ page.date | date: "%F" }}</time>{% if page.author %} • <span itemprop="author" itemscope itemtype="http://schema.org/Person"><span itemprop="name">{{ page.author }}</span></span>{% endif %}</p>
+	{% if page.image %}<img class="image-float-right" src="{{ page.image }}">{% endif %}
   </header>
 
   <div class="post-content" itemprop="articleBody">

data/_sass/classic/_widget-support.scss

@@ -19,4 +19,24 @@
 		width: 100%;
 		height: 100%;
 	}
+}
+
+// Used by the older-posts widget
+.older-posts {
+	h1 {
+		margin-bottom: $vspacing-unit/2;
+	}
+	.year-details {
+		summary {
+			outline: none; // Prevent blue input-active activity border
+		}
+		.month-details {
+			padding-left: $hspacing-unit;
+			p {
+				padding: 0 0 0 (2 * $hspacing-unit);
+				margin: 0 0 0 0;
+				text-indent: -$hspacing-unit;
+			}
+		}
+	}
 }

data/pages/classic/categories.md

@@ -8,6 +8,6 @@ menuSubTitle: "About Categories"
 excerpt: "An excerpt is used as the page description and can be up to 160 characters long..."
 ---
 
-The "Categories" navigation menu is created automatically. However the website designer has to specify which categories must be included in the menu. This can be done by adding a page with the layout set to "category-page". This kicks off the creation of a page for the categorie specified in the `title` of that page's YAML matter.
+The "Categories" navigation menu is created automatically. However the website designer has to specify which categories must be included in the menu. This can be done by adding a page with the layout set to "category-page". This kicks off the creation of a page for the categories specified in the `title` of that page's YAML matter.
 
-The html content of that page will be ignored. An example can be seen in the `pages/categories/classic.md` file.
+The html content of that page will be ignored. An example can be seen in the `pages/categories/classic.md` file.

data/pages/classic/pages.md

@@ -18,6 +18,6 @@ Pages in classic can be linked to from the navigation menu. To do so there are s
 - menuSubTitle: The title of the submenu item in the drop down menu.
 - menuSubIndex: The place of the submenu item within the dropdown menu. Lower numbers will go above higher numbers. This theme only sorts on menuIndex numbers, not on other properties.
 
-For a consistent user experience in the narrow layout, it is recommened not to link pages to top level menu items if these menu items have a drop-down submenu.
+For a consistent user experience in the narrow layout, it is recommended not to link pages to top level menu items if these menu items have a drop-down submenu.
 
-Submenu's only go one level deep. If deeper nesting is necessary, send me a mail at: rien@balancingrock.nl
+Submenus only go one level deep. If deeper nesting is necessary, send me a mail at: rien@balancingrock.nl

metadata

@@ -1,57 +1,69 @@
 --- !ruby/object:Gem::Specification
 name: classic-jekyll-theme
 version: !ruby/object:Gem::Version
-  version: 1.9.2
+  version: 1.9.3
 platform: ruby
 authors:
 - Rien
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-08-06 00:00:00.000000000 Z
+date: 2017-09-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: jekyll-feed
+  name: jekyll
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.8'
+        version: '3.5'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 3.5.1
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.8'
+        version: '3.5'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 3.5.1
 - !ruby/object:Gem::Dependency
-  name: jekyll-data
+  name: jekyll-feed
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.4'
+        version: '0.8'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.4'
+        version: '0.8'
 - !ruby/object:Gem::Dependency
-  name: jekyll
+  name: jekyll-data
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '3.3'
-  type: :development
+        version: '0.4'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '2.0'
+  type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0.4'
+    - - "<"
       - !ruby/object:Gem::Version
-        version: '3.3'
+        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -109,6 +121,7 @@ files:
 - _includes/tertiary-column.html
 - _includes/widgets/browser-info.html
 - _includes/widgets/cookie-consent.html
+- _includes/widgets/older-posts.html
 - _includes/widgets/recent-posts.html
 - _includes/widgets/social-media-res/icon-github.html
 - _includes/widgets/social-media-res/icon-github.svg