Fixing tagging around reliability risk

docs/risks/Communication-Risks/On-Messages.md

@@ -5,7 +5,6 @@ description: Messages can be a source of Communication Risk
 sidebar_position: 4
 
 tags:
- - Risks
  - Communication Risk
 ---
 

docs/risks/Dependency-Risks/Deadline-Risk/Deadline-Risk.md

@@ -76,7 +76,7 @@ So, these are two separate concepts, both useful in software development and oth
 
 :::tip Anecdote Corner
 
-In July 2003, the second Tomb Raider film, "Lara Croft: Tomb Raider - The Cradle of Life" was being released.Eidos, the publishers of Tomb Raider games put pressure on their developers, Core Design, to release ["Tomb Raider- Angel of Darkness"](https://en.wikipedia.org/wiki/Tomb_Raider:_The_Angel_of_Darkness#Release) to tie in with this. Core Design met the deadline but the game buggy, badly received and regarded as a poor sequel despite having some interesting ideas.  Following this, Eidos transferred production of the franchise to a new developer.
+In July 2003, the second Tomb Raider film, "Lara Croft: Tomb Raider - The Cradle of Life" was being released. Eidos, the publishers of Tomb Raider games, put pressure on their developers, Core Design, to release ["Tomb Raider- Angel of Darkness"](https://en.wikipedia.org/wiki/Tomb_Raider:_The_Angel_of_Darkness#Release) to tie in with this. Core Design met the deadline but the game buggy, badly received and regarded as a poor sequel despite having some interesting ideas.  Following this, Eidos transferred production of the franchise to a new developer.
 
 For a software-based example, we can turn to the [Mars Pathfinder mission (1997)](https://en.wikipedia.org/wiki/Mars_Pathfinder#On-board_computer).  The mission was jeopardised by a long-running communications task which had higher priority than a bus management task.  If the communication task took too long, the lander computer reset itself.  This was debugged and fixed remotely by engineers on Earth.
 

docs/risks/Dependency-Risks/Dependency-Risks.md

@@ -0,0 +1,56 @@
+---
+title: Dependency Risks
+description: Risk faced by depending on something else,  e.g. an event, process, person, piece of software or an organisation. 
+
+featured: 
+  class: c
+  element: '<risk class="dependency" />'
+sidebar_position: 6
+tags:
+ - Dependency Risk
+tweet: yes
+slug: /risks/Dependency-Risks
+part_of: Operational Risk
+---
+
+# Dependency Risks
+
+[Dependency Risk](/tags/Dependency-Risk) is the risk you take on whenever you have a dependency on something (or someone) else.   <!-- tweet-end -->
+
+One simple example could be that the software service you write might depend on hardware to run on:  if the server goes down, the service goes down too.  In turn, the server depends on electricity from a supplier, as well as a network connection from a provider.  If either of these dependencies aren't met, the service is out of commission.
+
+Dependencies can be on _events_, _people_, _teams_, _work_, _processes_, _software_, _services_, _money_ and pretty much _any resource_, and while every project will need some of these, they also _add risk_ to any project because the reliability of the project itself is now a function involving the reliability of the dependency.  
+
+In order to avoid repetition, and also to break down this large topic, we're going to look at this over 7 sections:   
+
+ - This first section will look at dependencies _in general_, and some of the variations of [Dependency Risk](/tags/Dependency-Risk).
+ - Next, we'll look at [Scarcity Risk](/tags/Scarcity-Risk), because time, money and staff are scarce resources in every project.
+ - We'll cover [Deadline Risk](/tags/Deadline-Risk), and discuss the purpose of Events and Deadlines, and how they enable us to coordinate around dependency use.
+ - Then, we'll move on to look specifically at [Software Dependency Risk](/tags/Software-Dependency-Risk), covering using libraries, software services and building on top of the work of others.
+ - Then, we'll take a look at [Process Risk](/tags/Process-Risk), which is still [Dependency Risk](/tags/Dependency-Risk), but we'll be considering more organisational factors and how bureaucracy comes into the picture.
+ - After that, we'll take a closer look at [Boundary Risk](/tags/Boundary-Risk) and [Dead-End Risk](/tags/Dead-End-Risk).  These are the risks you face in making choices about what to depend on.
+ - Finally, we'll wrap up this analysis with a look at some of the specific problems around depending on other people or businesses in [Agency Risk](/tags/Agency-Risk).
+
+## Why Have Dependencies?
+
+Luckily for us, the things we depend on in life are, for the most part, abundant:  water to drink, air to breathe, light, heat and most of the time, food for energy.  
+
+This isn't even lucky though: life has adapted to build dependencies on things that it can _rely_ on.  
+
+Although life exists at the bottom of the ocean around [hydrothermal vents](https://en.wikipedia.org/wiki/Hydrothermal_vent), it is a very different kind of life to ours and has a different set of dependencies given its circumstances. 
+
+This tells us a lot about [Dependency Risk](/tags/Dependency-Risk) right here:
+
+ - On the one hand, _depending on something_ is very often helpful, and quite often essential.  (For example, all life seem to depend on water).
+ - Successful organisms _adapt_ to the dependencies available to them (like the thermal vent creatures).
+ - However, as soon as you have dependencies, you need to take into account their _reliability_. (Living near a river or stream gives you access to fresh water, for example).
+So, dependencies are a trade-off.  They give with one hand and take with the other.  Our modern lives are full of dependency (just think of the chains of dependency needed for putting a packet of biscuits on a supermarket shelf, for example), but we accept this risk because it makes life _easier_. 
+ - There is likely to be _competition_ for a dependency when it is scarce (think of droughts and famine).
+
+
+## Types Of Dependency Risk
+
+<TagList tag="Dependency Risk"  /> 
+
+
+

docs/risks/Dependency-Risks/Reliabiliity-Risk/Reliability-Risk.md → docs/risks/Dependency-Risks/Reliability-Risk/Reliability-Risk.md

@@ -8,10 +8,7 @@ featured:
   element: '<risk class="reliability" />'
 sidebar_position: 1
 tags:
- - Dependency Risk
- - Fit Risk
  - Reliability Risk
- - Invisibility Risk
  - Risks
 tweet: yes
 part_of: Dependency Risk

docs/risks/Dependency-Risks/Schedule-Risk/Schedule-Risk.md

@@ -13,7 +13,7 @@ tags:
  - Risks
  - Funding Risk
  - Schedule Risk
-part_of: Scarcity Risk
+part_of: Dependency Risk
 ---
 
 <RiskIntro fm={frontMatter} />

docs/risks/Dependency-Risks/_category_.yaml

@@ -1,4 +1,4 @@
 position: 6
 link:
   type: doc
-  id: Dependency-Risk
+  id: Dependency-Risks

docs/risks/Dependency-Risks/Dependency-Risk.md → docs/risks/Dependency-Risks/fit-managing.md-unused

@@ -1,55 +1,3 @@
----
-title: Dependency Risks
-description: Risk faced by depending on something else,  e.g. an event, process, person, piece of software or an organisation. 
-
-featured: 
-  class: c
-  element: '<risk class="dependency" />'
-sidebar_position: 6
-tags:
- - Dependency Risk
- - Fit Risk
- - Reliability Risk
- - Invisibility Risk
- - Risks
-tweet: yes
-slug: /risks/Dependency-Risks
-part_of: Operational Risk
----
-
-# Dependency Risks
-
-[Dependency Risk](/tags/Dependency-Risk) is the risk you take on whenever you have a dependency on something (or someone) else.   <!-- tweet-end -->
-
-One simple example could be that the software service you write might depend on hardware to run on:  if the server goes down, the service goes down too.  In turn, the server depends on electricity from a supplier, as well as a network connection from a provider.  If either of these dependencies aren't met, the service is out of commission.
-
-Dependencies can be on _events_, _people_, _teams_, _work_, _processes_, _software_, _services_, _money_ and pretty much _any resource_, and while every project will need some of these, they also _add risk_ to any project because the reliability of the project itself is now a function involving the reliability of the dependency.  
-
-In order to avoid repetition, and also to break down this large topic, we're going to look at this over 7 sections:   
-
- - This first section will look at dependencies _in general_, and some of the variations of [Dependency Risk](/tags/Dependency-Risk).
- - Next, we'll look at [Scarcity Risk](/tags/Scarcity-Risk), because time, money and staff are scarce resources in every project.
- - We'll cover [Deadline Risk](/tags/Deadline-Risk), and discuss the purpose of Events and Deadlines, and how they enable us to coordinate around dependency use.
- - Then, we'll move on to look specifically at [Software Dependency Risk](/tags/Software-Dependency-Risk), covering using libraries, software services and building on top of the work of others.
- - Then, we'll take a look at [Process Risk](/tags/Process-Risk), which is still [Dependency Risk](/tags/Dependency-Risk), but we'll be considering more organisational factors and how bureaucracy comes into the picture.
- - After that, we'll take a closer look at [Boundary Risk](/tags/Boundary-Risk) and [Dead-End Risk](/tags/Dead-End-Risk).  These are the risks you face in making choices about what to depend on.
- - Finally, we'll wrap up this analysis with a look at some of the specific problems around depending on other people or businesses in [Agency Risk](/tags/Agency-Risk).
-
-## Why Have Dependencies?
-
-Luckily for us, the things we depend on in life are, for the most part, abundant:  water to drink, air to breathe, light, heat and most of the time, food for energy.  
-
-This isn't even lucky though: life has adapted to build dependencies on things that it can _rely_ on.  
-
-Although life exists at the bottom of the ocean around [hydrothermal vents](https://en.wikipedia.org/wiki/Hydrothermal_vent), it is a very different kind of life to ours and has a different set of dependencies given its circumstances. 
-
-This tells us a lot about [Dependency Risk](/tags/Dependency-Risk) right here:
-
- - On the one hand, _depending on something_ is very often helpful, and quite often essential.  (For example, all life seem to depend on water).
- - Successful organisms _adapt_ to the dependencies available to them (like the thermal vent creatures).
- - However, as soon as you have dependencies, you need to take into account their _reliability_. (Living near a river or stream gives you access to fresh water, for example).
-So, dependencies are a trade-off.  They give with one hand and take with the other.  Our modern lives are full of dependency (just think of the chains of dependency needed for putting a packet of biscuits on a supermarket shelf, for example), but we accept this risk because it makes life _easier_. 
- - There is likely to be _competition_ for a dependency when it is scarce (think of droughts and famine).
 
 
 Let's look at four types of risk that apply to every dependency:  Fit, Reliability, Invisibility and Complexity.
@@ -94,8 +42,3 @@ Arguably, managing [Dependency Risk](/tags/Dependency-Risk) is _what Project Man
 There are some tools for managing dependency risk:  [Gantt Charts](https://en.wikipedia.org/wiki/Gantt_chart) for example, arrange work according to the capacity of the resources (i.e. dependencies) available, but also the _dependencies between the tasks_.   If task **B** requires the outputs of task **A**, then clearly task **A** comes first and task **B** starts after it finishes.  We'll look at this more in [Process Risk](/tags/Process-Risk). 
 
 We'll look in more detail at project management in Part 3, later.   But now, let's get into specifics with [Scarcity Risk](/tags/Scarcity-Risk).
-
-## Types Of Dependency Risk
-
-<TagList tag="Dependency Risk" filter="risks/Dependency-Risks" /> 
-

docs/risks/Feature-Risks/Feature-Risk.md → docs/risks/Feature-Risks/Feature-Risks.md

@@ -1,17 +1,15 @@
 ---
-title: Feature Risk
+title: Feature Risks
 description: Risks you face when providing features for your clients.
 
 
 featured: 
   class: c
   element: '<risk class="feature" />'
 tweet: yes
-slug: /risks/Feature-Risk
+slug: /risks/Feature-Risks
 tags: 
- - Risks
  - Feature Risk
-part_of: Operational Risk
 ---
 [Feature Risks](/tags/Feature-Risk) are types of risks to do with functionality that you need to have in the software you're building.  
 

docs/risks/Feature-Risks/_category_.yaml

@@ -1,4 +1,4 @@
 position: 3
 link:
   type: doc
-  id: Feature-Risk
+  id: Feature-Risks

src/plugins/category-listing/index.js

@@ -8,6 +8,7 @@ module.exports = async function myPlugin(context, options) {
         allVersions.forEach(version => {
             const docs = version.docs;
 
+			docs.forEach(d => console.log(d))
 
             // build the mapping of tags to docs
             const tagToDocMap = {};