Migrate content to YAML

content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.yml

@@ -0,0 +1,80 @@
+uuid:
+  - value: b3a28a86-02c5-45ea-8a51-32508cd34b7d
+langcode:
+  - value: en
+type:
+  - target_id: daily_email
+    target_type: node_type
+    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
+revision_timestamp:
+  - value: '2025-05-11T09:00:06+00:00'
+revision_uid:
+  - target_type: user
+    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
+revision_log: {  }
+status:
+  - value: true
+uid:
+  - target_type: user
+    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
+title:
+  - value: 'Drupal adopts ADRs'
+created:
+  - value: '2024-09-21T00:00:00+00:00'
+changed:
+  - value: '2025-05-11T09:00:06+00:00'
+promote:
+  - value: false
+sticky:
+  - value: false
+default_langcode:
+  - value: true
+revision_translation_affected:
+  - value: true
+path:
+  - alias: /daily/2024/09/21/drupal-adopts-adrs
+    langcode: en
+body:
+  - value: |
+      <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>
+
+      <p>From the issue:</p>
+
+      <blockquote>
+        <p>I proposed [...] to start adopting ADRs to document decisions that were made. That’d allow us to stop rehashing past conversations and allow people to onboard with fewer meetings.
+        … or so I think.
+        Because I think that ADRs could be an excellent way to scale this project up to A) many people, B) many timezones.</p>
+      </blockquote>
+
+      <p>I like this decision and have adopted and <a href="/daily/2024/06/12/recording-architectural-decisions">written about ADRs before</a>.</p>
+
+      <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>
+
+      <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>
+
+      <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>
+
+              
+    format: full_html
+    processed: |
+      <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>
+
+      <p>From the issue:</p>
+
+      <blockquote>
+        <p>I proposed [...] to start adopting ADRs to document decisions that were made. That’d allow us to stop rehashing past conversations and allow people to onboard with fewer meetings.
+        … or so I think.
+        Because I think that ADRs could be an excellent way to scale this project up to A) many people, B) many timezones.</p>
+      </blockquote>
+
+      <p>I like this decision and have adopted and <a href="http://default/daily/2024/06/12/recording-architectural-decisions">written about ADRs before</a>.</p>
+
+      <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>
+
+      <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>
+
+      <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>
+
+              
+    summary: null
+field_daily_email_cta: {  }