jekyll-theme-endless 0.12.3 → 0.13.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4a087ba5f9c86e99bcd3456a6ec8c33b85b365bdb79b72812918c28da0877380
-  data.tar.gz: a759e1b82fb51f937d336830ab3a6791aa76035076cfea486d8dc7a6ce321612
+  metadata.gz: a42aa548152db990d7bac3ebff1b3f4dc93e9d370b0463ebb4161171cb860725
+  data.tar.gz: 9a094c358ff5c9bf680e507d995a8cd50bfa3f1397b37119aa3a13d2db0ae0b7
 SHA512:
-  metadata.gz: 07d993b7ccb8287c3c2b4dfce3f9070082555fa5e317f62c432f40c541d4905c0ae01c31db8cfc703512ef2485a66f4c8bba9ea4792c4dea68686650cc01f09f
-  data.tar.gz: 6adfce4d8c05e32d8eeb67c30e435178da410536bcab4e9e07db386fde3174daf073127a75221b0706c4f46be5d2eb93ab9c25b8ab725d5fb855853e3091b129
+  metadata.gz: c8fa43b769dab8d11603e54078ea7d297ae48bf3a362120f29e31cab44f0d6a81c273876251ad30dce6cd568f665be3b94a3146dc8939087ba758d19e0726491
+  data.tar.gz: f562c0c1e7890b32f3f7f2a88ff414b6a2fa28363da60ae21273355e5fd833c858d05159606f1d150869ac48af234b952245bdc84e7049d634be0998b05a0b9e

data/README.adoc

@@ -226,7 +226,63 @@ Content
 
 
 `_layouts/page-postlist.html`::
-Layout of page-content with a list of blog posts at the end.
++
+--
+The page-postlist layout is designed to add a list of blog posts at the end of any page that uses this layout.
+The post list can currently be *configured* using two values via Jekyll frontmatter or page variables:
+
+`page-postlist-css-class`:
+This specifies the CSS class for the <ul> element where the posts will be listed, allowing for different list styles.
+
+`page-postlist-format-function`:
+This specifies the code to be included for generating the HTML structure of each post in the list.
+Currently, two designs are available
+(`_includes/function_post-in-list-short.html` [view link:/postlist-short/[postlist using the 'short design']]
+and `_includes/function_post-in-list-long.html` [view link:/postlist-long/[postlist using the 'long design']]), but you can create your own custom formats.
+
+To set the values, simply add them as front matter or page variables.
+For front matter (e.g., in Markdown pages, layouts, or even AsciiDoc pages), it might look like this:
+
+[source, markdown]
+----
+---
+# Layout that attaches blog posts to the end of the page-content.
+layout: page-postlist
+menu_position: 500
+page-menu_label: Blog
+summary: "150 character description of the page."
+## Configuration of the postlist layout (page-postlist.html):
+postlist-css-class: "post-list-long"
+postlist-format-function: "function_post-in-list-long.html"
+---
+# Page title
+
+Content
+----
+
+For AsciiDoc pages, you can also set it as a page variable:
+
+[source, asciidoc]
+----
+= Page title
+// Layout that attaches blog posts to the end of the page-content.
+:page-layout: page-postlist
+:page-menu_position: 500
+:page-menu_label: Blog
+:page-summary: "150 character description of the page."
+// Configuration of the postlist layout (page-postlist.html):
+:page-postlist-css-class: "post-list-short"
+:page-postlist-format-function: "function_post-in-list-short.html"
+
+Content
+----
+
+IMPORTANT: If you want to set the values for `page-tag.html`
+(the layout used by the plugin to create the tag pages),
+then the configuration must be done directly in that file,
+even if the layout `page-postlist` is defined in a downstream layout like `page-tag-template`.
+
+--
 
 
 
@@ -343,6 +399,14 @@ without having to rewrite a complete layout file.
 
 
 
+`_includes/container_head-of-document.html`::
+
+An empty file that can be overwritten by the theme user to _add content to the header of the HTML document_.
+It is included directly after the `<link>` commands for libraries and before the `<link>` command for `main.css`.
+This allows you to add libraries and modify settings in `main.css` as needed.
+
+
+
 `_includes/container_start-of-main.html`::
 
 The content of this file is inserted *above* the main content area (the section containing the page content and blog navigation). The content should be wrapped in a `<div>` element.
@@ -403,6 +467,13 @@ Generates a list containing blog posts.
 
 
 
+`_includes/function_post-in-list-long.html`::
+Generates the code to display a single post in the list of blog posts.
+An entry consists of the title of the blog post )linked to the article),
+a summary, the creation date and a list of tags associates with the post.
+
+
+
 `_includes/function_post-in-list-short.html`::
 Generates the code to display a single post in the list of blog posts.
 An entry consists of the title of the blog post linked to the article.

data/_config.yml

@@ -96,6 +96,17 @@ exclude:
 
 
 
+# compressed: Produces minified CSS in a single line, with no spaces or comments, for the smallest file size.
+# expanded: Outputs fully expanded CSS with indentation, making it easy to read but larger in size.
+# nested: Generates CSS with nested indentation, resembling the structure of the Sass code, for improved readability.
+# compact: Outputs CSS in a compact format, placing each selector on a new line, reducing file size while maintaining some readability.
+sass:
+  style: compressed
+
+
+
+
+
 # Settings for: jekyll-theme-endless
 ###############################################################################
 # These settings have been outsourced into the file `_data.yml` in this project.

data/_includes/container_head-of-document.html

@@ -0,0 +1,12 @@
+{% comment %}
+This file is intended to be replaced with user content.
+
+It can be overwritten by the theme user to add content to the header of the HTML document
+(such as adding CSS libraries within the <head>) without having to rewrite an entire layout file.
+
+The file is included directly after the <link> commands for libraries and
+before the <link> command for the main.css.
+This allows you to add libraries and adjust settings in the main.css file.
+
+{% endcomment %}
+

data/_includes/function_list-posts.html

@@ -5,15 +5,23 @@ Expects an array of post objects in the parameter `postlist`.
 Call via:
 ----
 {% include function_list-posts.html
-	postlist=POSTLIST
+	postlist = POSTLIST
+	postlist-css-class = page.postlist-css-class
+	postlist-format-function = page.postlist-format-function
 %}
 ----
 {% endcomment %}
 
-<ul>
+{% comment %}
+Set the default values for the format function an the CSS-class.
+{% endcomment %}
+{% assign design_post  = include.postlist-format-function | default: "function_post-in-list-short.html" %}
+{% assign design_class = include.postlist-css-class       | default: "post-list-short" %}
+
+<ul class="{{ design_class }}" itemscope itemtype="https://schema.org/Blog">
 {% for current_post in include.postlist %}
-	<li>
-		{% include function_post-in-list-short.html
+	<li itemscope itemtype="https://schema.org/BlogPosting">
+		{% include {{ design_post }}
 			post = current_post
 		%}
 	</li>

data/_includes/function_post-in-list-long.html

@@ -0,0 +1,49 @@
+{% comment %}
+Processes a single post for display in the list of articles.
+Expects a post object as a parameter.
+
+Call via:
+----
+<li>
+	{% include function_post-in-list-short.html
+		post=current_post
+	%}
+</li>
+----
+{% endcomment %}
+
+
+{% assign post = include.post %}
+
+<h2 itemprop="headline">
+	<a href="{{ post.url }}" itemprop="url">{{ post.title }}</a>
+</h2>
+<div>
+	{% comment %}
+		post.summary is checked first.
+		If summary is available, it is used directly without any modifications.
+
+		If summary is not available, excerpt is used as a fallback.
+		The strip_html filter removes any HTML tags from excerpt,
+		ensuring that only plain text is displayed.
+	{% endcomment %}
+	<p class="summary" itemprop="description">{{ post.summary | default: post.excerpt | strip_html }}</p>
+	<p>
+		{% include function_show-dates.html
+			created = post.date
+			edited  = post.last_modified_at
+		%}
+	</p>
+	<p>
+		{% comment %}Show tags of the post.{% endcomment %}
+		{% include function_tag-list.html
+			tags=post.tags
+		%}
+	</p>
+
+	{% comment %}
+	<meta itemprop="author" content="Author(s)" />
+	<meta itemprop="publisher" content="Brandname of Blogname" />
+	{% endcomment %}
+
+</div>

data/_includes/function_post-in-list-short.html

@@ -14,15 +14,20 @@ Call via:
 
 
 {% assign post = include.post %}
+<time itemprop="datePublished" datetime="{{ post.date | date: '%Y-%m-%d' }}">
+	{{ post.date | date: '%Y-%m-%d' }}
+</time>:
 
-{{ post.date | date: "%Y-%m-%d" }}:
 {% if post.permalink %}
 	{% comment %}
 	I use permalinks to indicate that an article was at some point considered beeing finished.
 	{% endcomment %}
 	 <i class="fa fa-link text-success" title="This article has a permalink."></i>
 {% endif %}
+
 {% comment %}
 'title' is not escaped, as the value should already be escaped by AsciiDoc through asciidocify.
 {% endcomment %}
-<a href="{{ post.url | relative_url }}">{{ post.title }}</a>
+<a href="{{ post.url | relative_url }}" itemprop="url">
+	<span itemprop="headline">{{ post.title }}</span>
+</a>

data/_includes/function_show-dates.html

@@ -1,16 +1,12 @@
-<div class="text-right">
+<time class="created" datetime="{{ include.created | date_to_xmlschema }}" itemprop="datePublished">
+	<span class="sr-only sr-only-focusable">created:</span>
+	<strong title="date of creation">{{ include.created | date: "%b %-d, %Y" }}</strong>
+</time>
 
-	<time class="created" datetime="{{ include.created | date_to_xmlschema }}" itemprop="datePublished">
-		<span class="sr-only sr-only-focusable">created:</span>
-		<strong title="date of creation">{{ include.created | date: "%b %-d, %Y" }}</strong>
-	</time>
-
-	{% if include.edited != "" and include.edited %}
-	/
-	<time class="edited" datetime="{{ include.edited | date_to_xmlschema }}" itemprop="dateModified">
-		<span class="sr-only sr-only-focusable">edited:</span>
-		<strong title="date of last edit">{{ include.edited  | date: "%b %-d, %Y" }}</strong>
-	</time>
-	{% endif %}
-
-</div>
+{% if include.edited != "" and include.edited %}
+/
+<time class="edited" datetime="{{ include.edited | date_to_xmlschema }}" itemprop="dateModified">
+	<span class="sr-only sr-only-focusable">edited:</span>
+	<strong title="date of last edit">{{ include.edited  | date: "%b %-d, %Y" }}</strong>
+</time>
+{% endif %}

data/_layouts/default-minimal.html

@@ -0,0 +1,15 @@
+---
+# Page without navigation, footer, etc.
+# Can be used for simple confirmation pages or similar, which should have a layout consistent with the main site.
+layout: html
+---
+<main class="container" aria-label="Content">
+	<div class="row">
+
+		<div class="col-lg-12">
+			{{ content }}
+		</div>
+
+	</div>
+
+</main>

data/_layouts/html.html

@@ -37,6 +37,8 @@
 			<!-- Load local versions -->
 		{% endif %}
 
+		{% include container_head-of-document.html %}
+
 		<!-- Theme CSS -->
 		<link rel="stylesheet" href="{{ '/assets/css/main.css' | relative_url }}">
 

data/_layouts/page-minimal.html

@@ -0,0 +1,17 @@
+---
+# Page without navigation, footer, etc., with a "close window" link
+# Can be used for simple confirmation pages or similar, which should maintain a layout consistent with the main site.
+layout: default-minimal
+---
+<section class="detached">
+
+	{% comment %}
+	'title' is not escaped, as the value should already be escaped by AsciiDoc through asciidocify.
+	{% endcomment %}
+	<h1 class="post-title">{{ page.title }}</h1>
+
+	{{ content }}
+
+	<p class="text-center"><a href="#" onClick="window.close()">Close window.</a></p>
+
+</section>

data/_layouts/page-postlist.html

@@ -4,8 +4,53 @@ layout: page
 ---
 {{ content }}
 
+{% comment %}
+The page-postlist layout is designed to add a list of blog posts at the end of any page that uses this layout.
+The post list can currently be configured using two values via Jekyll frontmatter or page variables:
+
+page-postlist-css-class:
+This specifies the CSS class for the <ul> element where the posts will be listed, allowing for different list styles.
+
+page-postlist-format-function:
+This specifies the code to be included for generating the HTML structure of each post in the list.
+Currently, two designs are available, but you can create your own custom formats.
+
+Planned features:
+
+page-postlist-sort-by:
+Determines the sorting method for the post list, e.g., by title (natural title), creation date, or last edit date.
+The page-postlist layout will handle the sorting.
+
+page-postlist-sort-order:
+Specifies the sorting direction, either ascending or descending.
+
+Processed data:
+
+page-postlist
+This variable holds the post list itself (default is all posts—i.e., site.posts).
+You can also pass a subset, such as only posts with a specific tag or posts created in a particular year.
+page-postlist can, for example, be set by the tag page plugin.
+Setting the variable within layouts does not seem possible because:
+* Page variables cannot be created or modified through Liquid.
+* Only static values can be assigned to a variable in front matter.
+
+{% endcomment %}
+
+{% comment %}
+The default value for the postlist is the list of all posts (i.e., site.posts),
+or otherwise, the value provided for page.postlist (e.g., only posts tagged with a specific tag).
+{% endcomment %}
+{% assign postlist = page.postlist | default: site.posts %}
+
+{% comment %}
+Perform the sorting.
+This part is not yet implemented.
+{% endcomment %}
+
 {% include function_list-posts.html
-	postlist=site.posts
+	postlist = postlist
+	postlist-css-class = page.postlist-css-class
+	postlist-format-function = page.postlist-format-function
 %}
 
 

data/_layouts/page-tag-template.html

@@ -1,5 +1,5 @@
 ---
-layout: page
+layout: page-postlist
 menu_position: -10
 ---
 {% comment %}
@@ -25,10 +25,6 @@ page.tag and page.title are set by the plugin `generate-taglist`.
 	that were already escaped by AsciiDocify, or, if special characters are present,
 	the tags were set unescaped through the Jekyll front matter.
 	{% endcomment %}
-Number of posts tagged with "<em>{{ page.tag | escape }}</em>": <strong>{{ site.tags[ page.tag ] | size }}</strong>
+	Number of posts tagged with "<em>{{ page.tag | escape }}</em>": <strong>{{ site.tags[ page.tag ] | size }}</strong>
 </p>
 
-{% assign tag_posts = site.tags[page.tag] %}
-{% include function_list-posts.html
-	postlist=tag_posts
-%}

data/_layouts/page-tag.html

@@ -1,5 +1,10 @@
 ---
 layout: page-tag-template
 menu_position: -10
+## Configuration of the postlist layout (page-postlist.html):
+postlist-css-class: "post-list-long"
+postlist-format-function: "function_post-in-list-long.html"
+#postlist-sort-by:
+#postlist-sort-order:
 ---
 

data/_layouts/post.html

@@ -17,10 +17,12 @@ layout: default
 		{% comment %}
 			Show dates of the post.
 		{% endcomment %}
-		{% include function_show-dates.html
-			created = page.date
-			edited  = edited_date
-		%}
+		<div class="text-right">
+			{% include function_show-dates.html
+				created = page.date
+				edited  = edited_date
+			%}
+		</div>
 
 		{% comment %}
 			In Markdown posts, page.title defaults to parts of the filename.

data/_sass/adoc-admonition.scss

@@ -3,6 +3,7 @@ div.admonitionblock {
 	box-shadow: 0 1px 4px #aaa;
 	background: #fff;
 	color: #111;
+	margin: 2em 0;
 }
 .admonitionblock table {
 	background-color: transparent;
@@ -21,10 +22,10 @@ span.icon>.fa {
 .admonitionblock td.icon {
 	text-align: center;
 	vertical-align: top;
-	width: 66px;
+	width: 3.7em;
 
 	[class^="fa icon-"] {
-		font-size: 1.5em;
+		font-size: 2.3em;
 		text-shadow: 1px 1px 2px rgba(0,0,0,.5);
 		cursor: default;
 	}

data/_sass/adoc-code.scss

@@ -1,28 +1,34 @@
 /**
  * Show name of the language highlighted in a code block in the upper right corner.
  */
-.listingblock .content code {
-  position: relative;
-  display: block;
-}
-
-.listingblock .content code::before {
-  content: attr(data-lang);
-  position: absolute;
-  top: 0;
-  right: 0;
-  background-color: #f0f0f0;
-  padding: 2px 5px;
-  font-size: 12px;
-  color: #333;
-  border-radius: 3px;
-  border: 1px solid #ccc;
-}
-
-/* If data-lang is empty or not set, ::before will be hidden. */
-.listingblock .content code[data-lang=""]::before,
-.listingblock .content code:not([data-lang])::before {
-  display: none;
+.listingblock {
+
+	.content {
+
+		code {
+			position: relative;
+			display: block;
+		}
+
+		code::before {
+			content: attr(data-lang);
+			position: absolute;
+			top: 0;
+			right: 0;
+			background-color: #f0f0f0;
+			padding: 2px 5px;
+			font-size: 12px;
+			color: #333;
+			border-radius: 3px;
+			border: 1px solid #ccc;
+		}
+
+		/* If data-lang is empty or not set, ::before will be hidden. */
+		code[data-lang=""]::before,
+		code:not([data-lang])::before {
+			display: none;
+		}
+	}
 }
 
 /*

data/_sass/postlists.scss

@@ -0,0 +1,46 @@
+/**
+ * Designs for the post-lists.
+ */
+
+ul.post-list-short {
+  margin-left: 0;
+}
+
+ul.post-list-long {
+
+  list-style: none;
+  padding: 0;
+  margin: 0;
+
+  li {
+    margin-bottom: 20px;
+
+    h2 {
+      margin-left: .25em;
+			font-size: 1.7em;
+    }
+
+		p.summary {
+			margin-bottom: 1.5em;
+		}
+
+    div {
+      position: relative;
+      margin-left: 3em;
+			padding: .5em 0;
+
+      // Blurred bar on the left side of the div
+      &::before {
+        content: '';
+        position: absolute;
+        left: -2em;
+        top: 0;
+        bottom: 0;
+        width: 1em;
+        background-color: rgba(0, 0, 111, 0.1);
+        filter: blur(3px);
+        border-radius: 5px;
+      }
+    }
+  }
+}

data/_sass/structure.scss

@@ -7,6 +7,13 @@ article, section {
 	}
 }
 
+/**
+ * Design settings for page-minimal.
+ */
+section.detached {
+	margin-top: 1em;
+}
+
 /*
  * Main elements (boxes for content):
  *  * <section> for pages

data/assets/css/main.scss

@@ -12,6 +12,7 @@
 @use "address";
 @use "tag-cloud";
 @use "posts";
+@use "postlists";
 @use "structure";
 
 /*

data/lib/jekyll-theme-endless/generate-tagpages.rb

@@ -84,6 +84,10 @@ module Jekyll
 				# Makes `page.tag` available in the layout file
 				self.data['tag'] = tag
 
+				# Make `site.tags[tag]` available as `page.postlist` in the layout
+				self.data['postlist'] = site.tags[tag] || []
+
+				#puts "[DEBUG] Loaded self.data: #{self.data.inspect}"
 			end
 		end
 

data/lib/jekyll-theme-endless/version.rb

@@ -1,5 +1,5 @@
 module Jekyll
 	module Endless
-		VERSION = '0.12.3'
+		VERSION = '0.13.0'
 	end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jekyll-theme-endless
 version: !ruby/object:Gem::Version
-  version: 0.12.3
+  version: 0.13.0
 platform: ruby
 authors:
 - Sven Boekhoff
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-11-01 00:00:00.000000000 Z
+date: 2024-11-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: jekyll-asciidoc
@@ -77,7 +77,6 @@ files:
 - README.adoc
 - _config.yml
 - _data.yml
-- _data/tag-description.yml
 - _includes/aside_info.html
 - _includes/aside_more.html
 - _includes/aside_navigation.html
@@ -85,6 +84,7 @@ files:
 - _includes/container_end-of-main.html
 - _includes/container_end-of-page.html
 - _includes/container_end-of-post.html
+- _includes/container_head-of-document.html
 - _includes/container_start-of-main.html
 - _includes/container_start-of-page.html
 - _includes/container_start-of-post.html
@@ -92,13 +92,16 @@ files:
 - _includes/content_footer-usernames.html
 - _includes/function_list-pages.html
 - _includes/function_list-posts.html
+- _includes/function_post-in-list-long.html
 - _includes/function_post-in-list-short.html
 - _includes/function_show-dates.html
 - _includes/function_show-prev-next-navigation.html
 - _includes/function_tag-cloud.html
 - _includes/function_tag-list.html
+- _layouts/default-minimal.html
 - _layouts/default.html
 - _layouts/html.html
+- _layouts/page-minimal.html
 - _layouts/page-postlist.html
 - _layouts/page-tag-template.html
 - _layouts/page-tag.html
@@ -119,6 +122,7 @@ files:
 - _sass/md-lists.scss
 - _sass/md-quote.scss
 - _sass/md-tables.scss
+- _sass/postlists.scss
 - _sass/posts.scss
 - _sass/rouge-highlight.scss
 - _sass/structure.scss

data/_data/tag-description.yml

@@ -1,128 +0,0 @@
-GDPR:
-  short: "GDPR (General Data Protection Regulation) is a regulation enacted by the European Union to protect individuals' privacy and personal data. It imposes strict guidelines on how organizations collect, store, process, and share personal data of EU residents. Compliance with GDPR is essential for businesses handling such data, with requirements including data protection by design, user consent, and the right to access and erase data. Non-compliance can result in significant penalties."
-Schema.org:
-  short: "Schema.org is a collaborative, standardized vocabulary that provides structured data markup to help search engines better understand the content on web pages. By adding Schema.org tags to HTML, content such as events, reviews, and products can appear as rich snippets in search results, enhancing visibility and user engagement. In Jekyll, Schema.org markup can be added to templates to improve SEO and provide more context to search engines."
-SEO:
-  short: "SEO (Search Engine Optimization) refers to strategies and practices aimed at improving a website's visibility in search engine results. Effective SEO enhances a site's ranking by optimizing content, keywords, meta tags, and site structure to attract more organic traffic. In Jekyll, SEO best practices can be implemented through plugins, structured data, and thoughtful content organization."
-known issues:
-  short: "Known issues are documented problems or limitations within a software application that are acknowledged by developers but may not yet have a solution. These can include bugs, compatibility issues, or performance limitations. Known issues are often shared in release notes or support documentation to keep users informed and to suggest potential workarounds until fixes are available."
-A&B:
-  short: "Tag for testing the escaping bahaviour of Markdown and AsciiDoc frontmatter."
-escaping:
-  short: "The process of using special characters or sequences to prevent specific symbols from being interpreted in code or markup, often necessary for handling HTML, YAML, or Markdown."
-security:
-  short: "Measures and practices used to protect software, systems, and data from unauthorized access, attacks, or vulnerabilities, essential in all stages of development."
-special chars:
-  short: "Characters with special functions in code or markup, like &, <, >, which may need to be escaped to ensure proper display or functionality in web content or code."
-test-page:
-  short: "A page created to test functionality, design, or layout before publishing. Useful for checking formatting, scripts, or custom styles in a controlled environment."
-frontmatter:
-  short: "A YAML or JSON block at the beginning of a Jekyll file that contains metadata about the page, such as title, layout, and tags, which Jekyll uses to generate content dynamically."
-permalink:
-  short: "A permalink (permanent link) is a stable URL that links to a specific page, post, or content piece on a website. Permalinks are designed to remain unchanged indefinitely, ensuring that links to the content will not break over time. In Jekyll, permalinks can be customized to control the URL structure for individual pages or posts, improving both user experience and SEO."
-release notes:
-  short: "Release notes are documents that provide information about new features, bug fixes, improvements, and known issues in a new software version. They help users and developers understand changes between versions and can include details on compatibility, upgrade steps, and resolved issues. Release notes are essential for keeping stakeholders informed about software progress and updates."
-pages:
-  short: "Static or dynamic web pages in a Jekyll site, typically containing content that isn't organized chronologically, such as 'About' or 'Contact' sections."
-_includes:
-  short: "A special directory in Jekyll where reusable code snippets or partial templates, such as headers, footers, or navigation menus, are stored. Files in the _includes folder can be inserted into other templates using Liquid tags, allowing for modular and maintainable site layouts."
-RSS:
-  short: "RSS (Really Simple Syndication) is a web feed format that allows users and applications to receive updates from websites in a standardized format. By subscribing to an RSS feed, users can stay informed about new content, such as blog posts or news articles, without visiting the site directly. RSS feeds are commonly used in news aggregators and feed readers."
-
-TOC:
-  short: "TOC (Table of Contents) is a navigational aid that lists the main sections or headings of a document, allowing readers to quickly find and jump to specific content. In web content, a TOC is often generated automatically based on headings and can be particularly useful for lengthy pages or articles."
-.gitlab-ci.yml:
-  short: "A YAML file used to define GitLab CI/CD pipeline configurations, specifying jobs, stages, and conditions for automated testing, deployment, or other tasks in GitLab."
-LICENSE.txt:
-  short: "A file in a project that outlines the terms and conditions under which the software can be used, modified, or shared, commonly chosen from open-source licenses."
-SASS:
-  short: "SASS (Syntactically Awesome Stylesheets) is a CSS preprocessor that adds advanced features like variables, nested rules, and mixins to standard CSS. SASS has two syntax options: the older indented syntax (SASS) and the newer, more CSS-like syntax (SCSS). The SASS syntax uses indentation instead of curly braces and semicolons, while SCSS is more similar to traditional CSS and is often preferred for its familiarity."
-cleanup:
-  short: "The process of removing unnecessary or temporary files, obsolete code, or outdated data from a system or project to improve performance or maintainability."
-_data.yml:
-  short: "A YAML file used to store settings required for the theme website. They were outsourced from the _config.yml file to prevent them from being loaded as default values when using the theme."
-dependencies:
-  short: "External libraries, modules, or packages required by a project or software to function properly, typically managed by package managers like bundler."
-bash:
-  short: "A popular Unix shell and command language, commonly used for scripting and automating tasks in Linux and macOS environments."
-deployment:
-  short: "The process of releasing or distributing software to a production environment, making it available for use by end users."
-
-statistics:
-  short: "Data or numerical insights gathered from various sources, often used to analyze performance, user behavior, or other measurable factors."
-bugfixes:
-  short: "Software updates or patches that resolve identified errors or malfunctions, ensuring the application runs as expected."
-quotes:
-  short: "Text or speech cited from a source, typically used to reference someone's exact words or to highlight a point. Specifically refers to the styling and formatting of quotes in this context."
-tables:
-  short: "A structured format for organizing data into rows and columns, making it easy to present and interpret information in a grid layout."
-layout:
-  short: "The structured design and positioning of elements on a webpage or document, such as text and images, to enhance user experience. In Jekyll, layout files are stored in the '_layouts/' directory."
-CDN:
-  short: "A Content Delivery Network (CDN) is a system of distributed servers that deliver web content to users based on their geographic location, improving load times and performance."
-jsdelivr:
-  short: "A free, fast, and open-source CDN that hosts JavaScript libraries, CSS files, and other web assets, helping to deliver them efficiently to users."
-i18n:
-  short: "Short for 'internationalization', i18n refers to the process of designing software to be adaptable to different languages and regions without requiring engineering changes."
-updates:
-  short: "Changes or improvements applied to software or content, typically to fix bugs, add new features, or enhance security."
-logging:
-  short: "The practice of recording system events, errors, or user activities, often used for tracking and troubleshooting."
-debugging:
-  short: "The process of finding and resolving bugs or defects in software to ensure it behaves as expected."
-Gemfile:
-  short: "A file used in Ruby projects to list the dependencies (gems) required by the project and to manage their installation."
-_data:
-  short: "A directory in Jekyll where structured data (e.g., YAML, JSON, or CSV files) is stored, which can be accessed and used across the site."
-
-_config.yml:
-  short: "A configuration file used in Jekyll to customize settings for your site."
-admonition:
-  short: "A formatted block in documentation that draws attention to important notes or warnings."
-AsciiDoc:
-  short: "A lightweight but feature-rich markup language used for writing documentation in plain text."
-Bootstrap:
-  short: "A popular front-end framework for building responsive, mobile-first websites using CSS and JavaScript components."
-CSS:
-  short: "Cascading Style Sheets, a language used for describing the presentation of a web page, including layout, colors, and fonts."
-documentation:
-  short: "Written text or resources that explain how a piece of software or technology works."
-EditorConfig:
-  short: "A file format and collection of text editor plugins for maintaining consistent coding styles across different editors."
-example:
-  short: "A sample or instance used to demonstrate how something works or can be done."
-features:
-  short: "A set of distinctive attributes or capabilities that a software or product offers."
-Font Awesome:
-  short: "A font and icon toolkit used to include scalable vector icons and social logos on websites."
-footer:
-  short: "The section at the bottom of a webpage or document, usually containing copyright information, links, or branding."
-function:
-  short: "A block of code designed to perform a specific task and which can be reused in a program."
-gemspec:
-  short: "A specification file that defines the details of a Ruby gem, including its dependencies and metadata."
-highlighting:
-  short: "A feature used to apply color to syntax in code examples, making it easier to read and understand."
-images:
-  short: "Visual elements used in websites or documents, including photos, illustrations, and graphics."
-lists:
-  short: "A collection of items organized in a sequence, either ordered or unordered."
-Markdown:
-  short: "A lightweight markup language for formatting text, used widely for creating simple, readable documentation."
-menu:
-  short: "A navigation element in a webpage that allows users to move between different sections or pages."
-posts:
-  short: "Multiple blog entries or articles displayed on a site, typically listed in reverse chronological order."
-Rouge:
-  short: "A syntax highlighter used in Jekyll and other systems to colorize code snippets in various programming languages."
-SCSS:
-  short: "A preprocessor language that extends CSS with features like variables, nested rules, and functions."
-styling:
-  short: "The process of applying styles to a webpage or document, often through CSS, to enhance its appearance."
-table:
-  short: "A structured arrangement of data in rows and columns, often used for displaying information in a grid format."
-tag-cloud:
-  short: "A visual representation of the tags used in a blog, with more frequently used tags appearing larger."
-tags:
-  short: "Keywords or labels that categorize and describe blog posts or content to make them easier to find."
-