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.98d20258-bdbe-4286-a2d2-36dc4722cac1.json

@@ -82,9 +82,9 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently saw a post with a screenshot of some code they'd written using Tailwind CSS.<\/p>\n\n<p>Reading the comments, it had the usual \"re-inventing the wheel\" and \"just use inline styles\" comments, which, to me, didn't seem very helpful and not the point of the post.<\/p>\n\n<p>When I've given a <a href=\"https:\/\/www.oliverdavies.uk\/presentations\/taking-flight-with-tailwind-css\">talk on Tailwind CSS<\/a>, I've acknowledged that people have common initial reactions and suggested people try it for a week or so and see how it works for them before making up their minds.<\/p>\n\n<p>Someone did after a conference and posted this on Twitter:<\/p>\n\n<blockquote>\n  <p>I saw a talk on tailwind at a conference. Spent 15 minutes afterwards \"discussing\" with the presenter how it was horrible and against the neat way of CSS and so on. But promised to try it just once as he said it feels better than it looks.<\/p>\n  \n  <p>He was right. It's so freeing.<\/p>\n<\/blockquote>\n\n<p>The same approach applies to many other things, such as pair programming, automated testing, test-driven development, static analysis, Scrum, Linux and Vim - to name a few.<\/p>\n\n<p>If you use it and don't like it, don't continue and return to what you did before.<\/p>\n\n<p>Whether you keep it or not, you better understand what you're evaluating and not dismiss it out of hand.<\/p>\n\n        ",
+            "value": "\n          <p>I recently saw a post with a screenshot of some code they'd written using Tailwind CSS.<\/p>\n\n<p>Reading the comments, it had the usual \"re-inventing the wheel\" and \"just use inline styles\" comments, which, to me, didn't seem very helpful and not the point of the post.<\/p>\n\n<p>When I've given a <a href=\"/presentations\/taking-flight-with-tailwind-css\">talk on Tailwind CSS<\/a>, I've acknowledged that people have common initial reactions and suggested people try it for a week or so and see how it works for them before making up their minds.<\/p>\n\n<p>Someone did after a conference and posted this on Twitter:<\/p>\n\n<blockquote>\n  <p>I saw a talk on tailwind at a conference. Spent 15 minutes afterwards \"discussing\" with the presenter how it was horrible and against the neat way of CSS and so on. But promised to try it just once as he said it feels better than it looks.<\/p>\n  \n  <p>He was right. It's so freeing.<\/p>\n<\/blockquote>\n\n<p>The same approach applies to many other things, such as pair programming, automated testing, test-driven development, static analysis, Scrum, Linux and Vim - to name a few.<\/p>\n\n<p>If you use it and don't like it, don't continue and return to what you did before.<\/p>\n\n<p>Whether you keep it or not, you better understand what you're evaluating and not dismiss it out of hand.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently saw a post with a screenshot of some code they'd written using Tailwind CSS.<\/p>\n\n<p>Reading the comments, it had the usual \"re-inventing the wheel\" and \"just use inline styles\" comments, which, to me, didn't seem very helpful and not the point of the post.<\/p>\n\n<p>When I've given a <a href=\"https:\/\/www.oliverdavies.uk\/presentations\/taking-flight-with-tailwind-css\">talk on Tailwind CSS<\/a>, I've acknowledged that people have common initial reactions and suggested people try it for a week or so and see how it works for them before making up their minds.<\/p>\n\n<p>Someone did after a conference and posted this on Twitter:<\/p>\n\n<blockquote>\n  <p>I saw a talk on tailwind at a conference. Spent 15 minutes afterwards \"discussing\" with the presenter how it was horrible and against the neat way of CSS and so on. But promised to try it just once as he said it feels better than it looks.<\/p>\n  \n  <p>He was right. It's so freeing.<\/p>\n<\/blockquote>\n\n<p>The same approach applies to many other things, such as pair programming, automated testing, test-driven development, static analysis, Scrum, Linux and Vim - to name a few.<\/p>\n\n<p>If you use it and don't like it, don't continue and return to what you did before.<\/p>\n\n<p>Whether you keep it or not, you better understand what you're evaluating and not dismiss it out of hand.<\/p>\n\n        ",
+            "processed": "\n          <p>I recently saw a post with a screenshot of some code they'd written using Tailwind CSS.<\/p>\n\n<p>Reading the comments, it had the usual \"re-inventing the wheel\" and \"just use inline styles\" comments, which, to me, didn't seem very helpful and not the point of the post.<\/p>\n\n<p>When I've given a <a href=\"/presentations\/taking-flight-with-tailwind-css\">talk on Tailwind CSS<\/a>, I've acknowledged that people have common initial reactions and suggested people try it for a week or so and see how it works for them before making up their minds.<\/p>\n\n<p>Someone did after a conference and posted this on Twitter:<\/p>\n\n<blockquote>\n  <p>I saw a talk on tailwind at a conference. Spent 15 minutes afterwards \"discussing\" with the presenter how it was horrible and against the neat way of CSS and so on. But promised to try it just once as he said it feels better than it looks.<\/p>\n  \n  <p>He was right. It's so freeing.<\/p>\n<\/blockquote>\n\n<p>The same approach applies to many other things, such as pair programming, automated testing, test-driven development, static analysis, Scrum, Linux and Vim - to name a few.<\/p>\n\n<p>If you use it and don't like it, don't continue and return to what you did before.<\/p>\n\n<p>Whether you keep it or not, you better understand what you're evaluating and not dismiss it out of hand.<\/p>\n\n        ",
             "summary": null
         }
     ],