Migrate content to YAML

content/node.47749b6f-e118-4fe5-b13d-11fe1189d77d.yml

@@ -0,0 +1,76 @@
+uuid:
+  - value: 47749b6f-e118-4fe5-b13d-11fe1189d77d
+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:20+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: "TDD doesn't mean you know everything upfront"
+created:
+  - value: '2024-01-30T00:00:00+00:00'
+changed:
+  - value: '2025-05-11T09:00:20+00:00'
+promote:
+  - value: false
+sticky:
+  - value: false
+default_langcode:
+  - value: true
+revision_translation_affected:
+  - value: true
+path:
+  - alias: /daily/2024/01/30/tdd-doesnt-mean-you-know-everything-upfront
+    langcode: en
+body:
+  - value: |
+      <p>I'm in the final phase of a Drupal development project for a customer.</p>
+
+      <p>It has some custom modules and code I wrote with automated tests and test-driven development.</p>
+
+      <p>Today, the client reported a bug.</p>
+
+      <p>But, instead of something working incorrectly, this was a use case I hadn't considered.</p>
+
+      <p>The tests were passing, but there wasn't one for this.</p>
+
+      <p>I wrote the code for the use cases I was aware of when I started, and now I'm aware of another, I can add a test for it and ensure it's tested and working.</p>
+
+      <p>To do test-driven development, you don't need to know all the use cases and functionality upfront.</p>
+
+      <p>Write for what you know at the time, then expand and iterate in the future.</p>
+
+              
+    format: full_html
+    processed: |
+      <p>I'm in the final phase of a Drupal development project for a customer.</p>
+
+      <p>It has some custom modules and code I wrote with automated tests and test-driven development.</p>
+
+      <p>Today, the client reported a bug.</p>
+
+      <p>But, instead of something working incorrectly, this was a use case I hadn't considered.</p>
+
+      <p>The tests were passing, but there wasn't one for this.</p>
+
+      <p>I wrote the code for the use cases I was aware of when I started, and now I'm aware of another, I can add a test for it and ensure it's tested and working.</p>
+
+      <p>To do test-driven development, you don't need to know all the use cases and functionality upfront.</p>
+
+      <p>Write for what you know at the time, then expand and iterate in the future.</p>
+
+              
+    summary: null
+field_daily_email_cta: {  }