diff --git a/content/blog/ci-shootout-conclusion.md b/content/blog/ci-shootout-conclusion.md
index 2bbf83ec..565ffb75 100644
--- a/content/blog/ci-shootout-conclusion.md
+++ b/content/blog/ci-shootout-conclusion.md
@@ -1,9 +1,9 @@
 ---
 author: Daniel Jones
-date: "2022-01-14"
+date: "2022-01-19"
 heroImage: /img/blog/ci-shootout/goodbadugly.jpg
 title: "CI Shootout: Conclusion"
-draft: true
+
 heading: Our
 headingBold: blog
 Description: Get the very latest updates about recent projects, team updates, thoughts and industry news from our team of EngineerBetter experts.
diff --git a/content/blog/ci-shootout-getting-started.md b/content/blog/ci-shootout-getting-started.md
index 2ddfc58d..46c20b17 100644
--- a/content/blog/ci-shootout-getting-started.md
+++ b/content/blog/ci-shootout-getting-started.md
@@ -26,7 +26,7 @@ Across a series of blog posts, we'll be evaluating how each CI system supports t
 * [_Second post_](/blog/ci-shootout-inputs-and-outputs) - 5. Write **outputs externally** (like making a Git commit or pushing a file to S3)
 * [_Third post_](/blog/ci-shootout-reuse) - 6. **Re-use** pipeline configuration
 * [_Third post_](/blog/ci-shootout-reuse) - 7. Use the CI system as a **build monitor**
-* _Final post_ - 8. Conclusion
+* [_Final post_](/blog/ci-shootout-conclusion) - 8. Conclusion
 
 In this post we'll explore the first two of the use cases listed above. In each section we'll give each CI system a rating of either *Poor*, *Mediocre*, *Good* or *Great*.
 
diff --git a/content/blog/ci-shootout-inputs-and-outputs.md b/content/blog/ci-shootout-inputs-and-outputs.md
index 8d2bc905..8420b69f 100644
--- a/content/blog/ci-shootout-inputs-and-outputs.md
+++ b/content/blog/ci-shootout-inputs-and-outputs.md
@@ -18,7 +18,7 @@ In [the previous blog](/blog/ci-shootout-getting-started/) we looked at getting
 * _This post_ - [5. Write **outputs externally** (like making a Git commit or pushing a file to S3)](#5-writing-output-to-external-resources)
 * [_Third post_](/blog/ci-shootout-reuse) - 6. **Re-use** pipeline configuration
 * [_Third post_](/blog/ci-shootout-reuse) - 7. Use the CI system as a **build monitor**
-* _Final post_ - 8. Conclusion
+* [_Final post_](/blog/ci-shootout-conclusion) - 8. Conclusion
 
 ## 3. Trigger pipeline runs
 
diff --git a/content/blog/ci-shootout-reuse.md b/content/blog/ci-shootout-reuse.md
index 58ee48a5..c954775b 100644
--- a/content/blog/ci-shootout-reuse.md
+++ b/content/blog/ci-shootout-reuse.md
@@ -18,7 +18,7 @@ In [the previous blog](/blog/ci-shootout-inputs-and-outputs) we compared the act
 * [_Second post_](/blog/ci-shootout-inputs-and-outputs) - 5. Write **outputs externally** (like making a Git commit or pushing a file to S3)
 * _This post_ - 6. [**Re-use** pipeline configuration](#6-composability-of-tasks)
 * _This post_ - 7. [Use the CI system as a **build monitor**](#7-using-the-ci-system-as-a-build-monitor)
-* _Final post_ - 8. Conclusion
+* [_Final post_](/blog/ci-shootout-conclusion) - 8. Conclusion
 
 ## 6. Composability of tasks