Move all files to tome/

tome/content/node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.yml

@@ -0,0 +1,105 @@
+uuid:
+  - value: 0fb3ebe0-46c3-4e9c-9961-e62aa512fab3
+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:36+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: |
+      Maintaining a module used on 35,000 Drupal websites
+created:
+  - value: '2023-08-01T00:00:00+00:00'
+changed:
+  - value: '2025-05-11T09:00:36+00:00'
+promote:
+  - value: false
+sticky:
+  - value: false
+default_langcode:
+  - value: true
+revision_translation_affected:
+  - value: true
+path:
+  - alias: /daily/2023/08/01/maintaining-a-module-used-on-35000-drupal-websites
+    langcode: en
+body:
+  - value: |
+      <p>Note: The numbers within this post are taken from my <a href="/presentations/tdd-test-driven-drupal">Test-Driven Drupal talk</a>, in which I also talk about this.</p>
+
+      <p>My first commit to the 7.x-1.x branch of the Override Node Options module was in March 2012. According to Drupal.org, the module was used on 9,212 websites then.</p>
+
+      <p>As well as the 7.x-1.x branch, there's the 8.x-2.x branch which supports Drupal 9 and 10, and previously Drupal 8.</p>
+
+      <p>The most recent statistics show the module is currently used on 34,981 websites and is consistently around 35,000.</p>
+
+      <h2 id="what-does-that-mean%3F">What does that mean?</h2>
+
+      <p>The module is considered feature complete, but I'm not ruling out any new additions.</p>
+
+      <p>The main thing is ensuring that any changes don't break 35,000 websites!</p>
+
+      <p>I do this by relying on the module's automated test suite and ensuring that tests are added for any features or bugs and that the tests are passing before any new release.</p>
+
+      <h2 id="this-has-worked-well">This has worked well</h2>
+
+      <p>A few years ago, I committed a feature request to both versions. While it didn't include additional tests, I verified the existing functionality worked after resolving a large merge conflict by ensuring the original tests passed.</p>
+
+      <p>More recently, a colleague and I refactored the module and split each override into its own class, making adding and maintaining overrides easier.</p>
+
+      <p>Because the tests were still passing, we knew our refactor was successful and not causing regressions.</p>
+
+      <h2 id="here%27s-the-thing">Here's the thing</h2>
+
+      <p>Having automated tests and ensuring they're always passing has allowed me to add features and refactor code that I wouldn't have done or had the confidence to do otherwise.</p>
+
+      <p>It's great to have a popular module, but on the other hand, I don't want to break 35,000 websites which makes the tests invaluable.</p>
+
+              
+    format: full_html
+    processed: |
+      <p>Note: The numbers within this post are taken from my <a href="/presentations/tdd-test-driven-drupal">Test-Driven Drupal talk</a>, in which I also talk about this.</p>
+
+      <p>My first commit to the 7.x-1.x branch of the Override Node Options module was in March 2012. According to Drupal.org, the module was used on 9,212 websites then.</p>
+
+      <p>As well as the 7.x-1.x branch, there's the 8.x-2.x branch which supports Drupal 9 and 10, and previously Drupal 8.</p>
+
+      <p>The most recent statistics show the module is currently used on 34,981 websites and is consistently around 35,000.</p>
+
+      <h2 id="what-does-that-mean%3F">What does that mean?</h2>
+
+      <p>The module is considered feature complete, but I'm not ruling out any new additions.</p>
+
+      <p>The main thing is ensuring that any changes don't break 35,000 websites!</p>
+
+      <p>I do this by relying on the module's automated test suite and ensuring that tests are added for any features or bugs and that the tests are passing before any new release.</p>
+
+      <h2 id="this-has-worked-well">This has worked well</h2>
+
+      <p>A few years ago, I committed a feature request to both versions. While it didn't include additional tests, I verified the existing functionality worked after resolving a large merge conflict by ensuring the original tests passed.</p>
+
+      <p>More recently, a colleague and I refactored the module and split each override into its own class, making adding and maintaining overrides easier.</p>
+
+      <p>Because the tests were still passing, we knew our refactor was successful and not causing regressions.</p>
+
+      <h2 id="here%27s-the-thing">Here's the thing</h2>
+
+      <p>Having automated tests and ensuring they're always passing has allowed me to add features and refactor code that I wouldn't have done or had the confidence to do otherwise.</p>
+
+      <p>It's great to have a popular module, but on the other hand, I don't want to break 35,000 websites which makes the tests invaluable.</p>
+
+              
+    summary: null
+field_daily_email_cta: {  }