From 013e45188cd100dab563430eaac6edbdb50e3dcb Mon Sep 17 00:00:00 2001
From: Oliver Davies <oliver@oliverdavies.uk>
Date: Fri, 16 May 2025 21:37:30 +0100
Subject: [PATCH] tome export

---
 content/meta/index.json                       |  6 ++
 ....4c9fd2d9-307a-43a1-8993-d422261eabd7.json | 92 +++++++++++++++++++
 ....3a7a13f5-0525-4037-a9a1-c9be77e0bd6a.json | 27 ++++++
 3 files changed, 125 insertions(+)
 create mode 100644 content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.json
 create mode 100644 content/path_alias.3a7a13f5-0525-4037-a9a1-c9be77e0bd6a.json

diff --git a/content/meta/index.json b/content/meta/index.json
index c46cd4977..8978146ec 100644
--- a/content/meta/index.json
+++ b/content/meta/index.json
@@ -6384,5 +6384,11 @@
     ],
     "path_alias.8941a0dc-4d03-4a42-a647-8d20898ac224": [
         "node.d5d38a64-f226-42e0-8691-6c1b128435bf"
+    ],
+    "node.4c9fd2d9-307a-43a1-8993-d422261eabd7": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "path_alias.3a7a13f5-0525-4037-a9a1-c9be77e0bd6a": [
+        "node.4c9fd2d9-307a-43a1-8993-d422261eabd7"
     ]
 }
\ No newline at end of file
diff --git a/content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.json b/content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.json
new file mode 100644
index 000000000..094609a74
--- /dev/null
+++ b/content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.json
@@ -0,0 +1,92 @@
+{
+    "uuid": [
+        {
+            "value": "4c9fd2d9-307a-43a1-8993-d422261eabd7"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "type": [
+        {
+            "target_id": "daily_email",
+            "target_type": "node_type",
+            "target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
+        }
+    ],
+    "revision_timestamp": [
+        {
+            "value": "2025-05-16T20:37:09+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": "Which would you choose?"
+        }
+    ],
+    "created": [
+        {
+            "value": "2025-05-16T20:33:13+00:00"
+        }
+    ],
+    "changed": [
+        {
+            "value": "2025-05-16T20:37:09+00:00"
+        }
+    ],
+    "promote": [
+        {
+            "value": false
+        }
+    ],
+    "sticky": [
+        {
+            "value": false
+        }
+    ],
+    "default_langcode": [
+        {
+            "value": true
+        }
+    ],
+    "revision_translation_affected": [
+        {
+            "value": true
+        }
+    ],
+    "path": [
+        {
+            "alias": "\/daily\/2025\/05\/16\/choose",
+            "langcode": "en"
+        }
+    ],
+    "body": [
+        {
+            "value": "<p>You are working on a new feature.<\/p><p>You have two options.<\/p><p>You can commit and deploy a small amount of code every day, using feature flags when needed to show and hide the changes or ensure things aren't broken whilst being developed.<\/p><p>Or, you can wait and deploy everything at once.<\/p><p>Which is the less risky approach?<\/p><p>Which, if there is an issue, would make it easier to find and fix it?<\/p><p>Is it quicker to find an issue in tens of lines of code, or hundreds or thousands?<\/p><p>Is it simpler to disable a feature flag to hide the changes or roll back by reverting the commits, re-deploying the code and going through the same process again?<\/p><p>Which would you choose?<\/p>",
+            "format": "basic_html",
+            "processed": "<p>You are working on a new feature.<\/p><p>You have two options.<\/p><p>You can commit and deploy a small amount of code every day, using feature flags when needed to show and hide the changes or ensure things aren't broken whilst being developed.<\/p><p>Or, you can wait and deploy everything at once.<\/p><p>Which is the less risky approach?<\/p><p>Which, if there is an issue, would make it easier to find and fix it?<\/p><p>Is it quicker to find an issue in tens of lines of code, or hundreds or thousands?<\/p><p>Is it simpler to disable a feature flag to hide the changes or roll back by reverting the commits, re-deploying the code and going through the same process again?<\/p><p>Which would you choose?<\/p>",
+            "summary": ""
+        }
+    ],
+    "feeds_item": []
+}
\ No newline at end of file
diff --git a/content/path_alias.3a7a13f5-0525-4037-a9a1-c9be77e0bd6a.json b/content/path_alias.3a7a13f5-0525-4037-a9a1-c9be77e0bd6a.json
new file mode 100644
index 000000000..1027d5c3a
--- /dev/null
+++ b/content/path_alias.3a7a13f5-0525-4037-a9a1-c9be77e0bd6a.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "3a7a13f5-0525-4037-a9a1-c9be77e0bd6a"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/4c9fd2d9-307a-43a1-8993-d422261eabd7"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/daily\/2025\/05\/16\/choose"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file