Make all links relative

Now the abs_to_rel module is enabled, links can be made relative so they
work on the current environment.

content/node.274408ed-379c-4eaf-914d-7f5599f513d3.json

@@ -82,9 +82,9 @@
     ],
     "body": [
         {
-            "value": "\n          <p>How do you know if a commit to your codebase is deployable?<\/p>\n\n<p>What gives you confidence if a change will work once it's released?<\/p>\n\n<p>This can be from manual testing but also automated testing and quality checks from tools such as static analysis and code linting.<\/p>\n\n<p>However, this relies on every Developer running them before pushing each change and for their development environments to be consistent and matching the target environment.<\/p>\n\n<p>This can be automated by using a CI pipeline - a series of checks that are run automatically for each code push.<\/p>\n\n<p>This can include running automated tests, linting code and running static analysis and anything else you need.<\/p>\n\n<p>This is what determines if the change is deployable.<\/p>\n\n<p>If your CI pipeline passes, the commit is good can be deployed.<\/p>\n\n<p>If it fails, the commit should not be deployed and you should get it passing again as quickly as possible as <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2023\/06\/28\/theres-no-value-in-a-broken-ci-pipeline\">there's no value in a broken CI pipeline<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>How do you know if a commit to your codebase is deployable?<\/p>\n\n<p>What gives you confidence if a change will work once it's released?<\/p>\n\n<p>This can be from manual testing but also automated testing and quality checks from tools such as static analysis and code linting.<\/p>\n\n<p>However, this relies on every Developer running them before pushing each change and for their development environments to be consistent and matching the target environment.<\/p>\n\n<p>This can be automated by using a CI pipeline - a series of checks that are run automatically for each code push.<\/p>\n\n<p>This can include running automated tests, linting code and running static analysis and anything else you need.<\/p>\n\n<p>This is what determines if the change is deployable.<\/p>\n\n<p>If your CI pipeline passes, the commit is good can be deployed.<\/p>\n\n<p>If it fails, the commit should not be deployed and you should get it passing again as quickly as possible as <a href=\"/daily\/2023\/06\/28\/theres-no-value-in-a-broken-ci-pipeline\">there's no value in a broken CI pipeline<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>How do you know if a commit to your codebase is deployable?<\/p>\n\n<p>What gives you confidence if a change will work once it's released?<\/p>\n\n<p>This can be from manual testing but also automated testing and quality checks from tools such as static analysis and code linting.<\/p>\n\n<p>However, this relies on every Developer running them before pushing each change and for their development environments to be consistent and matching the target environment.<\/p>\n\n<p>This can be automated by using a CI pipeline - a series of checks that are run automatically for each code push.<\/p>\n\n<p>This can include running automated tests, linting code and running static analysis and anything else you need.<\/p>\n\n<p>This is what determines if the change is deployable.<\/p>\n\n<p>If your CI pipeline passes, the commit is good can be deployed.<\/p>\n\n<p>If it fails, the commit should not be deployed and you should get it passing again as quickly as possible as <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2023\/06\/28\/theres-no-value-in-a-broken-ci-pipeline\">there's no value in a broken CI pipeline<\/a>.<\/p>\n\n        ",
+            "processed": "\n          <p>How do you know if a commit to your codebase is deployable?<\/p>\n\n<p>What gives you confidence if a change will work once it's released?<\/p>\n\n<p>This can be from manual testing but also automated testing and quality checks from tools such as static analysis and code linting.<\/p>\n\n<p>However, this relies on every Developer running them before pushing each change and for their development environments to be consistent and matching the target environment.<\/p>\n\n<p>This can be automated by using a CI pipeline - a series of checks that are run automatically for each code push.<\/p>\n\n<p>This can include running automated tests, linting code and running static analysis and anything else you need.<\/p>\n\n<p>This is what determines if the change is deployable.<\/p>\n\n<p>If your CI pipeline passes, the commit is good can be deployed.<\/p>\n\n<p>If it fails, the commit should not be deployed and you should get it passing again as quickly as possible as <a href=\"/daily\/2023\/06\/28\/theres-no-value-in-a-broken-ci-pipeline\">there's no value in a broken CI pipeline<\/a>.<\/p>\n\n        ",
             "summary": null
         }
     ],