Migrate content to YAML

content/node.6d13ed35-7c06-41c2-afe7-847072a84d7a.yml

@@ -0,0 +1,61 @@
+uuid:
+  - value: 6d13ed35-7c06-41c2-afe7-847072a84d7a
+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: |
+      Feature flags in a multi-tenancy application
+created:
+  - value: '2023-06-12T00: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/06/12/feature-flags-in-a-multi-tenancy-application
+    langcode: en
+body:
+  - value: |
+      <p>A scenario for having long-lived feature flags is in a multi-tenant application where the same codebase serves multiple projects - e.g. a multi-site Drupal application or a module reused on multiple websites.</p>
+
+      <p>This is the use case I have for a client project which uses a multi-site setup to serve multiple websites from the same Drupal codebase.</p>
+
+      <p>If I need to add a feature to sites 1 and 3 but not site 2 or test a change to only site 2, I can do this by enabling a per-site feature flag.</p>
+
+      <p>Instead of being removed, these flags will remain until the change can be made permanent on all websites, meaning it can be toggled on and off as needed - allowing each site to be configured separately whilst keeping it easy to maintain by having a single canonical codebase.</p>
+
+              
+    format: full_html
+    processed: |
+      <p>A scenario for having long-lived feature flags is in a multi-tenant application where the same codebase serves multiple projects - e.g. a multi-site Drupal application or a module reused on multiple websites.</p>
+
+      <p>This is the use case I have for a client project which uses a multi-site setup to serve multiple websites from the same Drupal codebase.</p>
+
+      <p>If I need to add a feature to sites 1 and 3 but not site 2 or test a change to only site 2, I can do this by enabling a per-site feature flag.</p>
+
+      <p>Instead of being removed, these flags will remain until the change can be made permanent on all websites, meaning it can be toggled on and off as needed - allowing each site to be configured separately whilst keeping it easy to maintain by having a single canonical codebase.</p>
+
+              
+    summary: null
+field_daily_email_cta: {  }