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.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json

@@ -82,9 +82,9 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A couple of weeks ago, I wrote that <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/08\/17\/types-add-context\">using types adds context to code<\/a>, making it easier to read and understand.<\/p>\n\n<p>Something else that also adds context is <a href=\"https:\/\/www.php.net\/manual\/en\/functions.arguments.php#functions.named-arguments\">named arguments<\/a>, which were introduced to PHP in version 8.0.0.<\/p>\n\n<p>I particularly like them when making assertions within tests, where getting the expected and actual values in the wrong order can create some confusing output.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">self::assertSame(expected: 'My Drupal website', actual: $node-&gt;label());\n<\/code><\/pre>\n\n<p>While I can tell from the assertion that I'm checking two values are the same, adding the argument names makes it clear which is the expected value and which is the actual value.<\/p>\n\n<p>In fact, if you use named arguments, the order no longer matters, so I can put them in whichever order I want and it will work the same way.<\/p>\n\n        ",
+            "value": "\n          <p>A couple of weeks ago, I wrote that <a href=\"/daily\/2024\/08\/17\/types-add-context\">using types adds context to code<\/a>, making it easier to read and understand.<\/p>\n\n<p>Something else that also adds context is <a href=\"https:\/\/www.php.net\/manual\/en\/functions.arguments.php#functions.named-arguments\">named arguments<\/a>, which were introduced to PHP in version 8.0.0.<\/p>\n\n<p>I particularly like them when making assertions within tests, where getting the expected and actual values in the wrong order can create some confusing output.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">self::assertSame(expected: 'My Drupal website', actual: $node-&gt;label());\n<\/code><\/pre>\n\n<p>While I can tell from the assertion that I'm checking two values are the same, adding the argument names makes it clear which is the expected value and which is the actual value.<\/p>\n\n<p>In fact, if you use named arguments, the order no longer matters, so I can put them in whichever order I want and it will work the same way.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>A couple of weeks ago, I wrote that <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/08\/17\/types-add-context\">using types adds context to code<\/a>, making it easier to read and understand.<\/p>\n\n<p>Something else that also adds context is <a href=\"https:\/\/www.php.net\/manual\/en\/functions.arguments.php#functions.named-arguments\">named arguments<\/a>, which were introduced to PHP in version 8.0.0.<\/p>\n\n<p>I particularly like them when making assertions within tests, where getting the expected and actual values in the wrong order can create some confusing output.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">self::assertSame(expected: 'My Drupal website', actual: $node-&gt;label());\n<\/code><\/pre>\n\n<p>While I can tell from the assertion that I'm checking two values are the same, adding the argument names makes it clear which is the expected value and which is the actual value.<\/p>\n\n<p>In fact, if you use named arguments, the order no longer matters, so I can put them in whichever order I want and it will work the same way.<\/p>\n\n        ",
+            "processed": "\n          <p>A couple of weeks ago, I wrote that <a href=\"/daily\/2024\/08\/17\/types-add-context\">using types adds context to code<\/a>, making it easier to read and understand.<\/p>\n\n<p>Something else that also adds context is <a href=\"https:\/\/www.php.net\/manual\/en\/functions.arguments.php#functions.named-arguments\">named arguments<\/a>, which were introduced to PHP in version 8.0.0.<\/p>\n\n<p>I particularly like them when making assertions within tests, where getting the expected and actual values in the wrong order can create some confusing output.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">self::assertSame(expected: 'My Drupal website', actual: $node-&gt;label());\n<\/code><\/pre>\n\n<p>While I can tell from the assertion that I'm checking two values are the same, adding the argument names makes it clear which is the expected value and which is the actual value.<\/p>\n\n<p>In fact, if you use named arguments, the order no longer matters, so I can put them in whichever order I want and it will work the same way.<\/p>\n\n        ",
             "summary": null
         }
     ],