deploy: 2fdd41b

easy-installation-instructions-for-jekyll.html

@@ -92,7 +92,7 @@
 				"name": "Easy instructions for installing Jekyll",
 				"headline": "Easy instructions for installing Jekyll",
 				"keywords": "",
-				"description": "This post is still a work in progress as of 5/18/2024",
+				"description": "A blog post that provides easy instructions for installing Jekyll.",
 				"articleBody": "This post is still a work in progress as of 5/18/2024\n\nThe goal for this blog post is to provide easy instructions for installing Jekyll.\n\nIf you follow these steps, you should be able to create a new Jekyll web site utilizing GitHub and GitHub Pages to host your repository and web site.\n\nWe will walk you through the process of cloning the repository, making some changes to the site to configure it to be your own, and then ultimately getting your website published using your own custom domain name.\n\nA couple of assumptions to start:\n\n  You have a GitHub account created.\n  You have already purchased a custom domain name to use (you can bypass this and create a site using SITENAME.github.io)\n  You have Git tools installed (if you’re using Windows, use Git For Windows)\n  You have Visual Studio Code installed, or some other text editor that you’re comfortable with.\n\n\nPrecursor\nThis page is a work in progress, if you find something missing or wrong, let me know! You can create an issue on the GitHub repo!\n\nInstructions\n\n\n  Create a new Organization on GitHub\n    \n      A free organization account will be sufficient. For our example organization, we will used JekyllExampleWeb (JekyllExample was already taken).\n      Creating a new organization for each custom domain name you are going to use makes it easier to setup and manage multiple sites. You theoretically could get by with one Organization or just multiple projects under your user account, but I find it easier to manage multiple sites this way.\n    \n  \n  Create a new repository based off the JekyllExample repository\n    \n      While logged into GitHub, you should see a button that says “Use this template” next to the Code button in the JekyllExample repo, creating on the Use this template button will allow you to create a fork that is disconnected from the original repo and doesn’t bring over all the change history.\n      Be sure to check the “Include all branches” option when doing this, otherwise MAIN won’t come over and the workflow won’t work.\n    \n  \n  Rename the repository to match the domain name that you want to use for GitHub Pages\n    \n      As soon as you fork the repository, you can rename it. You will want to rename it to match the domain name that you want to use for GitHub Pages, for example we use jekyllexample.com, so the repository is jekyllexample.github.io.\n    \n  \n  Clone the repository to your local machine for editing\n    \n      You can clone the repository to your local machine using the following command, (assuming you have Git installed, start up Git Bash and then navigate to the folder where you want to clone the repository to)\n        1\n git clone https://github.com/ORGANIZATION/SITENAME.github.io.git\n        \n      \n      Where SITENAME is the name of your repository that you modified in Step 3.\n    \n  \n  Open the repository in Visual Studio Code\n    \n      You can open the repository in Visual Studio Code using the following command:\n        1\n code SITENAME.github.io\n        \n      \n      Where SITENAME is the name of your repository that you modified in Step 3.\n    \n  \n  Navigate to the Repository Settings in GitHub\n    \n      Navigate to the Actions/General Settings\n        \n          Under Workflow Permissions be sure to choose “Read and write permissions” for the Actions workflow to be able to push changes to the repository. (If you are unable to set this, try changing it at the Organization level first, then this individual repo)\n        \n      \n    \n  \n  Change the _config.yml file\n    \n      This file has a number of variables for options for your site, such as Title, Description, Author, etc. You will want to customize these to start to brand and name your site.\n      If you’re using Google Analytics you can configure the MEASUREMENT ID here as well.\n    \n  \n  Edit the CNAME file in the root of the repository to match your custom domain name\n    \n      If you’re not using a custom domain name, you can delete this file.\n    \n  \n  Commit your changes to the GitHub repository and push them.\n    1\n2\n3\n git add .\n git commit -m \"Some updated comment about the commit here\"\n git push\n    \n    \n      You may be prompted to configure your GitHub credentials at this point, here’s an approach on how to do that.\n    \n  \n  Configure the repository settings for GitHub Pages and Workflow to allow for deployment\n    \n      In the GitHub Repository Settings, you will want to configure the following:\n        \n          Under the GitHub Settings find the GitHub Pages section\n          Under Source choose “Deploy from a branch”\n          Under Branch choose “main” and “/(root)”\n        \n      \n    \n  \n  Configure your DNS for your domain to point to GitHub pages\n    \n      You will need to do this before step 10 so that GitHub can verify and find your custom domain name configured properly.\n      You basically need to setup A records for your domain name that point to the following IP addresses:\n        \n          185.199.108.153\n          185.199.109.153\n          185.199.110.153\n          185.199.111.153\n        \n      \n      \n        I use CloudFlare for my domains, so the DNS entries are configured as follows:\n\n      \n      You would replace jekyllexample.com with your domain in your DNS settings.\n    \n  \n  Configure your custom Domain Name\n    \n      Under the GitHub Settings find the GitHub Pages section\n      Under Custom Domain, enter your custom domain name (ex: jekyllexample.com)\n    \n  \n  Navigate to the Actions tab in the GitHub interface\n    \n      You should see your commit that you pushed in step 8, and you should see a workflow that is running (or has ran).\n      After that you should see a second action that is running (or has ran) something like “pages build and deployment”\n      If both of those actions have completed successfully, you should be able to navigate to your custom domain name and see your site.\n    \n  \n  Next steps! Edit the blog posts in the _posts folder, or delete them and create your own posts.\n    \n      The easiest way to create a new post is to simply copy and paste one of the existing posts\n        \n          Rename the file to match the date and title of your post\n          Edit the file to change the content/title and importantly be sure to update the published date to the dat you want the post to be.\n          Commit and push your changes to GitHub and you should see your new post on your site after the workflow completes.\n        \n      \n    \n  \n\n\n",
 				"datePublished": "2023-02-01 10:00:15 +0000",
 				"dateModified": "2024-05-16T08:05:00+00:00",

feed.xml

@@ -5,8 +5,8 @@
     <description>A sample website built on the Jekyll platform designed to make it easy for you to get a website of your own up and running.</description>
     <link>https://www.jekyllexample.com/</link>
     <atom:link href="https://www.jekyllexample.com/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Fri, 21 Jun 2024 16:04:25 +0000</pubDate>
-    <lastBuildDate>Fri, 21 Jun 2024 16:04:25 +0000</lastBuildDate>
+    <pubDate>Mon, 24 Jun 2024 15:18:35 +0000</pubDate>
+    <lastBuildDate>Mon, 24 Jun 2024 15:18:35 +0000</lastBuildDate>
     <generator>Jekyll v4.3.3</generator>
 
       <item>

first-blog-post.html

@@ -92,7 +92,7 @@
 				"name": "First Blog Post",
 				"headline": "First Blog Post",
 				"keywords": "",
-				"description": "This is the first blog post using JekyllExample.com.",
+				"description": "A sample blog post for JekyllExample.com",
 				"articleBody": "This is the first blog post using JekyllExample.com.\n\n\n  This is a quote inside that first blog post\n\n\n\n  This is a list item\n    \n      This is a nested list item\n    \n  \n  This is a second list item\n    \n      This is a nested list item\n        \n          This is a nested-nested list item\n        \n      \n    \n  \n\n\nHeader 1\nSome text under header 1\n\nHeader 2\nSome text under header 2\n\nHeader 3\nSome text under header 3\n\nThis is a link\n\nThis template is from Chris Hammond\n\n",
 				"datePublished": "2022-07-10 23:00:15 +0000",
 				"dateModified": "2024-05-16T08:05:00+00:00",

getting-started-with-jekyll.html

@@ -92,7 +92,7 @@
 				"name": "Getting started with Jekyll",
 				"headline": "Getting started with Jekyll",
 				"keywords": "",
-				"description": "So you want to get started with Jekyll?",
+				"description": "A simple list of steps to get started with Jekyll.",
 				"articleBody": "So you want to get started with Jekyll?\n\nWell, you’ve come to the right place. This post will walk you through the steps to get you going if you’re new to Jekyll and want to get it up and running with a clean instance.\nWe recommend if you’re brand new to Jekyll though you use our other instructions that utilize this site as a template for you to build your own site, complete with theme and sample content.\n\nGet Started\n\nFirst, you’ll need to install Jekyll. You can do this by running the following command:\n\n1\ngem install jekyll\n\n\nCreate a New Site\n\nNow that you have Jekyll installed, you can create a new site. To do this, run the following command:\n\n1\njekyll new my-awesome-site\n\n\nServe Your Site\n\nNow that you have a site, you can serve it locally. To do this, run the following command:\n\n1\n2\ncd my-awesome-site\njekyll serve\n\n\nMake Some Changes\n\nNow that you have a site, you can make some changes. To do this, open the _config.yml file in your favorite text editor and make some changes.\n\nCommit Your Changes\n\nNow that you have made some changes, you can commit them. To do this, run the following command:\n\n1\n2\ngit add .\ngit commit -m \"Made some changes\"\n\n\nPush Your Changes\n\nNow that you have committed your changes, you can push them. To do this, run the following command:\n\n1\ngit push origin master\n\n\nConclusion\n\nAnd that’s it! You’ve now got a Jekyll site up and running. You can now make some changes and push them to GitHub Pages.\n",
 				"datePublished": "2023-01-31 10:00:15 +0000",
 				"dateModified": "2024-05-16T08:05:00+00:00",

jekyll-on-ubuntu.html

@@ -95,7 +95,7 @@
 				"name": "Installing Jekyll locally on Ubuntu and getting it running using Windows Hyper-V",
 				"headline": "Installing Jekyll locally on Ubuntu and getting it running using Windows Hyper-V",
 				"keywords": "",
-				"description": "This post is still a work in progress as of 05/17/2024",
+				"description": "A blog post that provides easy instructions for installing Jekyll locally on Ubuntu running in a Windows Hyper-V Virtual Machine.",
 				"articleBody": "This post is still a work in progress as of 05/17/2024\n\n\n  Create a new Hyper-V VM installing Ubuntu 22.04\n  Run updates for Ubuntu (reboot if necessary)\n  Install GIT\n    \n      sudo apt install git\n    \n  \n  Install Bundler\n    \n      sudo apt install bundler\n    \n  \n  Install RBEnv to allow for multiple versions of Ruby\n  Install Jekyll GEM\n  Install other required libraries\n    \n      sudo apt install libvips-tools\n    \n  \n  Create a projects directory via a terminal:\n    \n      mkdir projects\n    \n  \n  Navigate into the project directory:\n    \n      cd projects\n    \n  \n  Clone the JekyllExample repository, from a Terminal in Ubunty type\n    \n      git clone https://github.com/ChrisHammond/jekyllexample.github.io.git\n    \n  \n  Navigate into the new directory\n    \n      cd jekyllexample.github.io\n    \n  \n  Run the following terminal command to get everything installed properly\n    \n      bundle install\n    \n  \n  Run Jekyll to start a local webserver\n    \n      bundle exec jekyll serve\n    \n  \n  Browse to http://127.0.0.1:4000 in your web browser\n\n\nNext steps:\n\n  If you have a large repository, or a large number of repositories, you might run out of disk space on your Hyper-V VM, if that’s the case check out this tutorial for how to expand your Ubuntu disk.\n  Install Homebrew and Git Credential Manager\n    \n      /bin/bash -c “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)”\n    \n  \n\n\n\n  brew tap microsoft/git\nbrew install –cask git-credential-manager-core\n\n",
 				"datePublished": "2024-04-18 10:00:15 +0000",
 				"dateModified": "2024-04-18 10:00:15 +0000",

sample-jekyll-sites.html

@@ -85,7 +85,7 @@
 				"name": "Example Jekyll Sites based on this Repository",
 				"headline": "Example Jekyll Sites based on this Repository",
 				"keywords": "",
-				"description": "This blog post will be an ongoing list with some examples of websites that have been built based on this template/sample/repository! If you have a site built on this template that you would like highlighted, please contact Chris Hammond",
+				"description": "A list of sites built on this template",
 				"articleBody": "This blog post will be an ongoing list with some examples of websites that have been built based on this template/sample/repository! If you have a site built on this template that you would like highlighted, please contact Chris Hammond\n\n\n  AutocrossBlog - A simple blog for 24+ years of autocross\n  ProjectVW - Help Chris find his first car, a 1973 VW Super Beetle\n  BicycleTips - Tips and tricks for gravel bike riding\n\n",
 				"datePublished": "2023-02-01 10:00:15 +0000",
 				"dateModified": "2024-05-16T08:05:00+00:00",

second-blog-post.html

@@ -92,7 +92,7 @@
 				"name": "Non-featured Blog Post",
 				"headline": "Non-featured Blog Post",
 				"keywords": "",
-				"description": "This is the second blog post, the difference is that this one is not featured.",
+				"description": "A description for this non-featured blog post",
 				"articleBody": "This is the second blog post, the difference is that this one is not featured.\n\n\n  This is a quote inside that first blog post\n\n\n\n  This is a list item\n  This is a second list item\n\n\nHeader 1\nSome text under header 1\n\nHeader 2\nSome text under header 2\n\nHeader 3\nSome text under header 3\n\nThis is a link\n\n",
 				"datePublished": "2022-11-01 01:00:15 +0000",
 				"dateModified": "2022-11-01 01:00:15 +0000",

structured-content-in-jekyll.html

@@ -95,7 +95,7 @@
 				"name": "Using structured content in Jekyll for your own website",
 				"headline": "Using structured content in Jekyll for your own website",
 				"keywords": "",
-				"description": "Introduction",
+				"description": "A blog post showing how Structured Content can be leveraged using this JekyllExample project to help get your content out to the masses.",
 				"articleBody": "Introduction\n\nIn the ever-evolving world of SEO and web development, structured content has become a cornerstone for creating high-performing, search-engine-friendly websites. For those who use static site generators like Jekyll, leveraging structured content can significantly enhance your site’s visibility and usability. In this blog post, we’ll explore the benefits of using structured content with Jekyll, specifically focusing on the JekyllExample.com template/repo.\n\nWhat is Structured Content?\n\nStructured content is a way of organizing information on your website so that it is easily understood by search engines and other web services. This is often achieved using schema markup (or structured data), which provides context to your content, making it more accessible and indexable. Common types of structured data include information about articles, events, products, and reviews, among others.\n\nBenefits of Structured Content\n\nImproved SEO\n\nOne of the primary benefits of structured content is its impact on SEO. By adding schema markup to your Jekyll site, you provide search engines with detailed information about your content. This can result in better indexing and higher rankings, as search engines can more accurately understand and present your content to users.\n\nEnhanced Rich Snippets\n\nStructured data can enhance the appearance of your site in search results by generating rich snippets. These are enhanced listings that show additional information, such as ratings, authors, and dates, directly in the search results. Rich snippets can improve your click-through rates by making your listings more attractive and informative.\n\nBetter Content Organization\n\nUsing structured content helps you maintain a consistent and organized format for your information. This is particularly useful for larger websites with diverse content types. It ensures that each piece of content follows a set structure, making it easier to manage and update.\n\nImproved Accessibility\n\nStructured content can also improve the accessibility of your site. By providing clear, well-defined data structures, you make it easier for assistive technologies, like screen readers, to interpret and present your content to users with disabilities.\n\nUsing the JekyllExample.com Template\n\nThe JekyllExample.com template/repo is an excellent starting point for those looking to implement structured content on a Jekyll-based website. This template comes with built-in support for structured data, specifically using the BlogPosting schema type. If your site requires a different content type, such as Article, you can easily modify the schema type to fit your needs.\n\nConclusion\n\nIntegrating structured content into your Jekyll site using the JekyllExample.com template can significantly enhance your site’s SEO, user experience, and accessibility. By providing clear, organized data to search engines and assistive technologies, you make your content more discoverable and user-friendly. Start leveraging the power of structured content today and watch your Jekyll site soar in the search rankings.\n",
 				"datePublished": "2024-06-21 10:00:15 +0000",
 				"dateModified": "2024-06-21 10:00:15 +0000",