Fixing links

Author: Adrian Hall

Gemfile

@@ -4,6 +4,8 @@ source "https://rubygems.org"
 gem "csv" 
 gem "ostruct"
 gem "logger"
+gem "rake"
+gem "html-proofer"
 
 # Jekyll requirements
 gem "jekyll", "~> 4.4.1"

_config.yml

@@ -94,7 +94,7 @@ sass:
   verbose: true
   silence_deprecations: [ import, color-functions, global-builtin, mixed-decls, slash-div ]
 
-permalink: /:categories/:year/:year-:month-:day-:title:output_ext
+permalink: /posts/:year/:year-:month-:day-:title:output_ext
 timezone: "US/Pacific"
 
 # Pagination with jekyll-paginate-v2
@@ -196,14 +196,8 @@ defaults:
       related: false
 
 include:
-  - _data
-  - _includes
-  - _layouts
   - _pages
-  - _posts
-  - _sass
   - assets
-  - _config.yml
 exclude:
   - .devcontainer
   - .editorconfig

_data/navigation.yml

@@ -2,7 +2,5 @@
 main:
   - title: "Posts"
     url: "/posts"
-  - title: "Categories"
-    url: "/categories"
   - title: "Tags"
     url: "/tags"

_includes/breadcrumbs.html

@@ -0,0 +1,40 @@
+{% case site.category_archive.type %}
+  {% when "liquid" %}
+    {% assign path_type = "#" %}
+  {% when "jekyll-archives" %}
+    {% assign path_type = nil %}
+{% endcase %}
+
+{% if page.collection != 'posts' %}
+  {% assign path_type = nil %}
+  {% assign crumb_path = '/' %}
+{% else %}
+  {% assign crumb_path = site.category_archive.path %}
+{% endif %}
+
+<nav class="breadcrumbs">
+  <ol itemscope itemtype="https://schema.org/BreadcrumbList">
+    {% assign crumbs = page.url | split: '/' %}
+    {% assign i = 1 %}
+    {% for crumb in crumbs offset: 1 %}
+      {% if forloop.first %}
+        <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
+          <a href="{{ '/' | relative_url }}" itemprop="item"><span itemprop="name">{{ site.data.ui-text[site.locale].breadcrumb_home_label | default: "Home" }}</span></a>
+
+          <meta itemprop="position" content="{{ i }}" />
+        </li>
+        <span class="sep">{{ site.data.ui-text[site.locale].breadcrumb_separator | default: "/" }}</span>
+      {% endif %}
+      {% if forloop.last %}
+        <li class="current"{% if page.locale %} lang="{{ page.locale }}"{% endif %}>{{ page.title }}</li>
+      {% else %}
+        {% assign i = i | plus: 1 %}
+        <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
+          <span data-crumb="{{crumb}}" itemprop="name">{{ crumb | url_decode | replace: '-', ' ' | capitalize }}</span>
+          <meta itemprop="position" content="{{ i }}" />
+        </li>
+        <span class="sep">{{ site.data.ui-text[site.locale].breadcrumb_separator | default: "/" }}</span>
+      {% endif %}
+    {% endfor %}
+  </ol>
+</nav>

_includes/posts-taxonomy.html

@@ -1,27 +1,25 @@
 ---
 layout: single
 author_profile: false
-pernalink: /privacy.html
+permalink: /privacy.html
 ---
 
 # Privacy policy
 
 * We do not sell or provide our data feeds to third parties for their use.
-* We do partner with standard data gathering entities (Google and Microsoft) to collect website metrics.
+* We do partner with standard data gathering entities to collect website metrics.
 * We opt out of third party usage with those data gathering entities whenever we can.
 
 We believe we have minimized third party usage of your browsing habits.
 
 ## Our partners
 
-We partner with [Google Analytics](https://analytics.google.com) to capture basic demographic and page
-analytics to capture the most popular pages to improve our products/services.  Website usage data is
-captured using first and third-party cookies and other tracking technologies to determine the popularity
-of individual posts.
+We partner with to capture how you use and interact with our website through behavioral metrics, heatmaps,
+and session replay to improve our products/services. Website usage data is captured using first and third-party
+cookies and other tracking technologies to determine the popularity of individual posts and online activity.
+Additionally, we use this information for site optimization.
 
-We partner with [Microsoft Clarity](https://clarity.microsoft.com) to capture how you use and interact with
-our website through behavioral metrics, heatmaps, and session replay to improve our products/services. Website
-usage data is captured using first and third-party cookies and other tracking technologies to determine the
-popularity of individual posts and online activity. Additionally, we use this information for site optimization.
+For more information about how Microsoft collects and uses your data, visit the [Microsoft Privacy Statement]. 
 
-For more information about how Microsoft collects and uses your data, visit the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement).
+[Microsoft Clarity]: https://clarity.microsoft.com
+[Microsoft Privacy Statement]: https://privacy.microsoft.com/privacystatement

_pages/categories.html

@@ -3,7 +3,7 @@ title: "Building a service in the Cloud"
 categories:
   - Cloud
 tags:
-  - Serverless
+  - serverless
 ---
 
 I’ve been thinking about providing services in the cloud for a few years now.    A common question I see time and time again is this:  “What pieces of the cloud do I need to build my solution?”  The answer is always “it depends.”  This post is about those options.

_pages/privacy.html

@@ -1,10 +1,11 @@
 ---
 title: "Which is better - React Native or Xamarin Forms?"
 categories:
-  - "React Native"
-  - Xamarin
+  - Mobile
 tags:
-  - Comparisons
+  - react_native
+  - xamarin
+  - comparisons
 ---
 
 Let’s talk about a loaded question.  After my recent forays into both React Native and Xamarin Forms, I got asked on Twitter – which is better, React Native or Xamarin Forms?  Further, I should answer this for JavaScript experts, C# XAML experts and for developers with experience in both.  After all, both produce native apps and both use a common codebase.

_posts/2017/2017-05-08-building-a-service-in-the-cloud.md

@@ -1,9 +1,9 @@
 ---
 title: "The things I like (and don't like) about Swift?"
 categories:
-  - iOS
+  - Mobile
 tags:
-  - Swift
+  - swift
 ---
 
 Recently, I’ve given myself the task of learning the “native” mobile development platforms.  That means Java or Kotlin for Android and Swift or Objective-C for iOS development.  Kotlin is a ways behind Java for Android development and I already knew (somewhat) the Java language, so that one was relatively easy.  Swift is the new kid on the block, but it’s obviously the way to go for iOS Development.