opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Make all links relative

Browse source 
Now the abs_to_rel module is enabled, links can be made relative so they
work on the current environment.
This commit is contained in:
Oliver Davies 2025-05-29 16:42:25 +01:00
parent 0d359f81d6
commit 7a7dc297ca
349 changed files with 698 additions and 698 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/node.b5b7cf41-fa32-4c63-a182-9b048c290f05.json
View file

@ -82,9 +82,9 @@
],
"body": [
{
"value": "\n <p>Something I mentioned during my <a href=\"https:\/\/www.oliverdavies.uk\/podcast\/7-mike-karthauser-testing-legacy\">podcast episode with Mike Karthauser<\/a> is a quote I saw recently:<\/p>\n\n<blockquote>\n <p>Code is a liability, not an asset.<\/p>\n<\/blockquote>\n\n<p>The more code you write, the more you have to maintain.<\/p>\n\n<p>The more complex the code is, the harder it is to maintain.<\/p>\n\n<p>For example, when adding a new page to a Drupal application, should you write a custom route, a Controller, and a Repository and write accompanying tests, or should you use the Views module?<\/p>\n\n<p>Both can give the same result.<\/p>\n\n<p>One involves writing and maintaining custom code; the other uses a no-code approach available in Drupal, which creates the page and output based on your selections.<\/p>\n\n<p>There isn't a correct answer.<\/p>\n\n<p>The option you choose will depend on what problem you're solving, what deadlines you're working to, and any precedents set within the project.<\/p>\n\n<p>It also depends on whether you want to maintain the code you write over time, fix any bugs, refactor it, and upgrade it as part of major Drupal version upgrades.<\/p>\n\n<p>Like a house, car or pet, any code you write will need ongoing care and maintenance in the future - not just now.<\/p>\n\n ",
"value": "\n <p>Something I mentioned during my <a href=\"/podcast\/7-mike-karthauser-testing-legacy\">podcast episode with Mike Karthauser<\/a> is a quote I saw recently:<\/p>\n\n<blockquote>\n <p>Code is a liability, not an asset.<\/p>\n<\/blockquote>\n\n<p>The more code you write, the more you have to maintain.<\/p>\n\n<p>The more complex the code is, the harder it is to maintain.<\/p>\n\n<p>For example, when adding a new page to a Drupal application, should you write a custom route, a Controller, and a Repository and write accompanying tests, or should you use the Views module?<\/p>\n\n<p>Both can give the same result.<\/p>\n\n<p>One involves writing and maintaining custom code; the other uses a no-code approach available in Drupal, which creates the page and output based on your selections.<\/p>\n\n<p>There isn't a correct answer.<\/p>\n\n<p>The option you choose will depend on what problem you're solving, what deadlines you're working to, and any precedents set within the project.<\/p>\n\n<p>It also depends on whether you want to maintain the code you write over time, fix any bugs, refactor it, and upgrade it as part of major Drupal version upgrades.<\/p>\n\n<p>Like a house, car or pet, any code you write will need ongoing care and maintenance in the future - not just now.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>Something I mentioned during my <a href=\"https:\/\/www.oliverdavies.uk\/podcast\/7-mike-karthauser-testing-legacy\">podcast episode with Mike Karthauser<\/a> is a quote I saw recently:<\/p>\n\n<blockquote>\n <p>Code is a liability, not an asset.<\/p>\n<\/blockquote>\n\n<p>The more code you write, the more you have to maintain.<\/p>\n\n<p>The more complex the code is, the harder it is to maintain.<\/p>\n\n<p>For example, when adding a new page to a Drupal application, should you write a custom route, a Controller, and a Repository and write accompanying tests, or should you use the Views module?<\/p>\n\n<p>Both can give the same result.<\/p>\n\n<p>One involves writing and maintaining custom code; the other uses a no-code approach available in Drupal, which creates the page and output based on your selections.<\/p>\n\n<p>There isn't a correct answer.<\/p>\n\n<p>The option you choose will depend on what problem you're solving, what deadlines you're working to, and any precedents set within the project.<\/p>\n\n<p>It also depends on whether you want to maintain the code you write over time, fix any bugs, refactor it, and upgrade it as part of major Drupal version upgrades.<\/p>\n\n<p>Like a house, car or pet, any code you write will need ongoing care and maintenance in the future - not just now.<\/p>\n\n ",
"processed": "\n <p>Something I mentioned during my <a href=\"/podcast\/7-mike-karthauser-testing-legacy\">podcast episode with Mike Karthauser<\/a> is a quote I saw recently:<\/p>\n\n<blockquote>\n <p>Code is a liability, not an asset.<\/p>\n<\/blockquote>\n\n<p>The more code you write, the more you have to maintain.<\/p>\n\n<p>The more complex the code is, the harder it is to maintain.<\/p>\n\n<p>For example, when adding a new page to a Drupal application, should you write a custom route, a Controller, and a Repository and write accompanying tests, or should you use the Views module?<\/p>\n\n<p>Both can give the same result.<\/p>\n\n<p>One involves writing and maintaining custom code; the other uses a no-code approach available in Drupal, which creates the page and output based on your selections.<\/p>\n\n<p>There isn't a correct answer.<\/p>\n\n<p>The option you choose will depend on what problem you're solving, what deadlines you're working to, and any precedents set within the project.<\/p>\n\n<p>It also depends on whether you want to maintain the code you write over time, fix any bugs, refactor it, and upgrade it as part of major Drupal version upgrades.<\/p>\n\n<p>Like a house, car or pet, any code you write will need ongoing care and maintenance in the future - not just now.<\/p>\n\n ",
"summary": null
}
],