Make all links relative
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:
parent
0d359f81d6
commit
7a7dc297ca
349 changed files with 698 additions and 698 deletions
|
|
@ -82,9 +82,9 @@
|
|||
],
|
||||
"body": [
|
||||
{
|
||||
"value": "\n <p>Today I noticed that Drupal's Experience Builder project <a href=\"https:\/\/www.drupal.org\/project\/experience_builder\/issues\/3454669\">has adopted architectural decision records<\/a>.<\/p>\n\n<p>From the issue:<\/p>\n\n<blockquote>\n <p>I proposed [...] to start adopting ADRs to document decisions that were made. That\u2019d allow us to stop rehashing past conversations and allow people to onboard with fewer meetings.\n \u2026 or so I think.\n Because I think that ADRs could be an excellent way to scale this project up to A) many people, B) many timezones.<\/p>\n<\/blockquote>\n\n<p>I like this decision and have adopted and <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/06\/12\/recording-architectural-decisions\">written about ADRs before<\/a>.<\/p>\n\n<p>I also like that the documents <a href=\"https:\/\/git.drupalcode.org\/project\/experience_builder\/-\/tree\/0.x\/docs\/adr?ref_type=heads\">are stored as markdown files in the repository<\/a>, alongside the code, making it easy for everyone to view or change.<\/p>\n\n<p>As the work on Experience Builder continues, new contributors can read these documents and understand why previous decisions were made, which is extremely valuable.<\/p>\n\n<p>I'm interested to see how ADRs work for the Experience Builder project and whether they're adopted more widely in other parts of the Drupal ecosystem.<\/p>\n\n ",
|
||||
"value": "\n <p>Today I noticed that Drupal's Experience Builder project <a href=\"https:\/\/www.drupal.org\/project\/experience_builder\/issues\/3454669\">has adopted architectural decision records<\/a>.<\/p>\n\n<p>From the issue:<\/p>\n\n<blockquote>\n <p>I proposed [...] to start adopting ADRs to document decisions that were made. That\u2019d allow us to stop rehashing past conversations and allow people to onboard with fewer meetings.\n \u2026 or so I think.\n Because I think that ADRs could be an excellent way to scale this project up to A) many people, B) many timezones.<\/p>\n<\/blockquote>\n\n<p>I like this decision and have adopted and <a href=\"/daily\/2024\/06\/12\/recording-architectural-decisions\">written about ADRs before<\/a>.<\/p>\n\n<p>I also like that the documents <a href=\"https:\/\/git.drupalcode.org\/project\/experience_builder\/-\/tree\/0.x\/docs\/adr?ref_type=heads\">are stored as markdown files in the repository<\/a>, alongside the code, making it easy for everyone to view or change.<\/p>\n\n<p>As the work on Experience Builder continues, new contributors can read these documents and understand why previous decisions were made, which is extremely valuable.<\/p>\n\n<p>I'm interested to see how ADRs work for the Experience Builder project and whether they're adopted more widely in other parts of the Drupal ecosystem.<\/p>\n\n ",
|
||||
"format": "full_html",
|
||||
"processed": "\n <p>Today I noticed that Drupal's Experience Builder project <a href=\"https:\/\/www.drupal.org\/project\/experience_builder\/issues\/3454669\">has adopted architectural decision records<\/a>.<\/p>\n\n<p>From the issue:<\/p>\n\n<blockquote>\n <p>I proposed [...] to start adopting ADRs to document decisions that were made. That\u2019d allow us to stop rehashing past conversations and allow people to onboard with fewer meetings.\n \u2026 or so I think.\n Because I think that ADRs could be an excellent way to scale this project up to A) many people, B) many timezones.<\/p>\n<\/blockquote>\n\n<p>I like this decision and have adopted and <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/06\/12\/recording-architectural-decisions\">written about ADRs before<\/a>.<\/p>\n\n<p>I also like that the documents <a href=\"https:\/\/git.drupalcode.org\/project\/experience_builder\/-\/tree\/0.x\/docs\/adr?ref_type=heads\">are stored as markdown files in the repository<\/a>, alongside the code, making it easy for everyone to view or change.<\/p>\n\n<p>As the work on Experience Builder continues, new contributors can read these documents and understand why previous decisions were made, which is extremely valuable.<\/p>\n\n<p>I'm interested to see how ADRs work for the Experience Builder project and whether they're adopted more widely in other parts of the Drupal ecosystem.<\/p>\n\n ",
|
||||
"processed": "\n <p>Today I noticed that Drupal's Experience Builder project <a href=\"https:\/\/www.drupal.org\/project\/experience_builder\/issues\/3454669\">has adopted architectural decision records<\/a>.<\/p>\n\n<p>From the issue:<\/p>\n\n<blockquote>\n <p>I proposed [...] to start adopting ADRs to document decisions that were made. That\u2019d allow us to stop rehashing past conversations and allow people to onboard with fewer meetings.\n \u2026 or so I think.\n Because I think that ADRs could be an excellent way to scale this project up to A) many people, B) many timezones.<\/p>\n<\/blockquote>\n\n<p>I like this decision and have adopted and <a href=\"/daily\/2024\/06\/12\/recording-architectural-decisions\">written about ADRs before<\/a>.<\/p>\n\n<p>I also like that the documents <a href=\"https:\/\/git.drupalcode.org\/project\/experience_builder\/-\/tree\/0.x\/docs\/adr?ref_type=heads\">are stored as markdown files in the repository<\/a>, alongside the code, making it easy for everyone to view or change.<\/p>\n\n<p>As the work on Experience Builder continues, new contributors can read these documents and understand why previous decisions were made, which is extremely valuable.<\/p>\n\n<p>I'm interested to see how ADRs work for the Experience Builder project and whether they're adopted more widely in other parts of the Drupal ecosystem.<\/p>\n\n ",
|
||||
"summary": null
|
||||
}
|
||||
],
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue