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.e88b4449-20b6-4165-880b-6d34b9579781.json
View file

@ -82,9 +82,9 @@
],
"body": [
{
"value": "\n <p>A few years ago, \"decoupled\" or \"headless\" Drupal was a popular approach, leveraging Drupal's built-in JSON:API module to expose its data via an API which can be consumed by a separate front-end application.<\/p>\n\n<p>The front-end application would retrieve the data from Drupal via the API and generate the appropriate HTML.<\/p>\n\n<p>It's an approach I've used in the past and <a href=\"https:\/\/www.oliverdavies.uk\/presentations\/decoupling-drupal-vuejs\">spoken about at conferences<\/a>, but it comes with pros and cons.<\/p>\n\n<p>In theory, as the Drupal (or back-end application) and front-end are completely separate, there can be two separate and independent teams working on them.<\/p>\n\n<p>This adds overhead and complexity and I've found that one team will commonly be blocking the other instead of both being able to work in parallel.<\/p>\n\n<p>As I said yesterday, <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2025\/01\/26\/layout-builder\">previewing content in Drupal can be an issue<\/a> - particularly with a decoupled approach which needs a front-end to be rebuilt before the changes can be seen.<\/p>\n\n<p>If you have a separate front-end, you'll need to create everything from scratch, such as writing accessible HTML markup and othe standard features that would normally be provided by Drupal and, because you've got two separate front-end and back-end applications, you've got twice the amount of maintenance.<\/p>\n\n<p>You could also be excluding yourself from any new features that will be available in future versions of Drupal or Drupal CMS, such as the new Experience Builder.<\/p>\n\n<p>Whilst decoupled\/headless builds are a viable option and can work well in some situations, it's not something I recommend often.<\/p>\n\n ",
"value": "\n <p>A few years ago, \"decoupled\" or \"headless\" Drupal was a popular approach, leveraging Drupal's built-in JSON:API module to expose its data via an API which can be consumed by a separate front-end application.<\/p>\n\n<p>The front-end application would retrieve the data from Drupal via the API and generate the appropriate HTML.<\/p>\n\n<p>It's an approach I've used in the past and <a href=\"/presentations\/decoupling-drupal-vuejs\">spoken about at conferences<\/a>, but it comes with pros and cons.<\/p>\n\n<p>In theory, as the Drupal (or back-end application) and front-end are completely separate, there can be two separate and independent teams working on them.<\/p>\n\n<p>This adds overhead and complexity and I've found that one team will commonly be blocking the other instead of both being able to work in parallel.<\/p>\n\n<p>As I said yesterday, <a href=\"/daily\/2025\/01\/26\/layout-builder\">previewing content in Drupal can be an issue<\/a> - particularly with a decoupled approach which needs a front-end to be rebuilt before the changes can be seen.<\/p>\n\n<p>If you have a separate front-end, you'll need to create everything from scratch, such as writing accessible HTML markup and othe standard features that would normally be provided by Drupal and, because you've got two separate front-end and back-end applications, you've got twice the amount of maintenance.<\/p>\n\n<p>You could also be excluding yourself from any new features that will be available in future versions of Drupal or Drupal CMS, such as the new Experience Builder.<\/p>\n\n<p>Whilst decoupled\/headless builds are a viable option and can work well in some situations, it's not something I recommend often.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>A few years ago, \"decoupled\" or \"headless\" Drupal was a popular approach, leveraging Drupal's built-in JSON:API module to expose its data via an API which can be consumed by a separate front-end application.<\/p>\n\n<p>The front-end application would retrieve the data from Drupal via the API and generate the appropriate HTML.<\/p>\n\n<p>It's an approach I've used in the past and <a href=\"https:\/\/www.oliverdavies.uk\/presentations\/decoupling-drupal-vuejs\">spoken about at conferences<\/a>, but it comes with pros and cons.<\/p>\n\n<p>In theory, as the Drupal (or back-end application) and front-end are completely separate, there can be two separate and independent teams working on them.<\/p>\n\n<p>This adds overhead and complexity and I've found that one team will commonly be blocking the other instead of both being able to work in parallel.<\/p>\n\n<p>As I said yesterday, <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2025\/01\/26\/layout-builder\">previewing content in Drupal can be an issue<\/a> - particularly with a decoupled approach which needs a front-end to be rebuilt before the changes can be seen.<\/p>\n\n<p>If you have a separate front-end, you'll need to create everything from scratch, such as writing accessible HTML markup and othe standard features that would normally be provided by Drupal and, because you've got two separate front-end and back-end applications, you've got twice the amount of maintenance.<\/p>\n\n<p>You could also be excluding yourself from any new features that will be available in future versions of Drupal or Drupal CMS, such as the new Experience Builder.<\/p>\n\n<p>Whilst decoupled\/headless builds are a viable option and can work well in some situations, it's not something I recommend often.<\/p>\n\n ",
"processed": "\n <p>A few years ago, \"decoupled\" or \"headless\" Drupal was a popular approach, leveraging Drupal's built-in JSON:API module to expose its data via an API which can be consumed by a separate front-end application.<\/p>\n\n<p>The front-end application would retrieve the data from Drupal via the API and generate the appropriate HTML.<\/p>\n\n<p>It's an approach I've used in the past and <a href=\"/presentations\/decoupling-drupal-vuejs\">spoken about at conferences<\/a>, but it comes with pros and cons.<\/p>\n\n<p>In theory, as the Drupal (or back-end application) and front-end are completely separate, there can be two separate and independent teams working on them.<\/p>\n\n<p>This adds overhead and complexity and I've found that one team will commonly be blocking the other instead of both being able to work in parallel.<\/p>\n\n<p>As I said yesterday, <a href=\"/daily\/2025\/01\/26\/layout-builder\">previewing content in Drupal can be an issue<\/a> - particularly with a decoupled approach which needs a front-end to be rebuilt before the changes can be seen.<\/p>\n\n<p>If you have a separate front-end, you'll need to create everything from scratch, such as writing accessible HTML markup and othe standard features that would normally be provided by Drupal and, because you've got two separate front-end and back-end applications, you've got twice the amount of maintenance.<\/p>\n\n<p>You could also be excluding yourself from any new features that will be available in future versions of Drupal or Drupal CMS, such as the new Experience Builder.<\/p>\n\n<p>Whilst decoupled\/headless builds are a viable option and can work well in some situations, it's not something I recommend often.<\/p>\n\n ",
"summary": null
}
],