Move all files to tome/

tome/content/node.024f2c81-68af-4eef-bea5-1b1d43bd1b39.yml

@@ -0,0 +1,61 @@
+uuid:
+  - value: 024f2c81-68af-4eef-bea5-1b1d43bd1b39
+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:40+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: |
+      Why is backward compatibility important?
+created:
+  - value: '2023-05-18T00:00:00+00:00'
+changed:
+  - value: '2025-05-11T09:00:40+00:00'
+promote:
+  - value: false
+sticky:
+  - value: false
+default_langcode:
+  - value: true
+revision_translation_affected:
+  - value: true
+path:
+  - alias: /daily/2023/05/18/why-is-backward-compatibility-important
+    langcode: en
+body:
+  - value: |
+      <p>In yesterday's email, I mentioned that deprecating code allows it to be backwards compatible - but what does that mean?</p>
+
+      <p>If I were to remove a function like <code>drupal_set_message()</code> that is used code elsewhere in an application, the code would no longer work and would break.</p>
+
+      <p>As a module or library maintainer, I don't want to cause applications to break by making backward incompatible changes (a "BC break" or a "breaking change").</p>
+
+      <p>Maintaining backward compatibility means that people who use the code can update to the latest version without breakages, and if they use any deprecated code, they know to update it to be compatible with future versions.</p>
+
+              
+    format: full_html
+    processed: |
+      <p>In yesterday's email, I mentioned that deprecating code allows it to be backwards compatible - but what does that mean?</p>
+
+      <p>If I were to remove a function like <code>drupal_set_message()</code> that is used code elsewhere in an application, the code would no longer work and would break.</p>
+
+      <p>As a module or library maintainer, I don't want to cause applications to break by making backward incompatible changes (a "BC break" or a "breaking change").</p>
+
+      <p>Maintaining backward compatibility means that people who use the code can update to the latest version without breakages, and if they use any deprecated code, they know to update it to be compatible with future versions.</p>
+
+              
+    summary: null
+field_daily_email_cta: {  }