Add daily email

content/meta/index.json

@@ -7199,5 +7199,15 @@
     ],
     "path_alias.5260227a-6421-4bb3-b8dd-daee4ffbdd5a": [
         "node.73861efd-5d4e-4c80-8c22-57594ee43dbc"
+    ],
+    "node.f971fedc-ce38-41b4-8d1f-b37766fb06e1": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "node.9b4c39a3-702f-486c-a79b-4d7b96a4f3f6"
+    ],
+    "path_alias.8d996b82-7d43-4c34-a154-cfd0db370ea2": [
+        "node.f971fedc-ce38-41b4-8d1f-b37766fb06e1"
+    ],
+    "redirect.6cf7bed4-6f9a-48ca-bcaa-44551f6c638a": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ]
 }

content/node.73861efd-5d4e-4c80-8c22-57594ee43dbc.yml

@@ -7,7 +7,7 @@ type:
     target_type: node_type
     target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
 revision_timestamp:
-  - value: '2025-08-02T21:56:19+00:00'
+  - value: '2025-08-03T22:53:21+00:00'
 revision_uid:
   - target_type: user
     target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
@@ -20,9 +20,9 @@ uid:
 title:
   - value: "A CHANGLOG isn't just a list of Git commits"
 created:
-  - value: '2025-08-28T21:53:38+00:00'
+  - value: '2025-07-28T21:53:38+00:00'
 changed:
-  - value: '2025-08-02T21:56:19+00:00'
+  - value: '2025-08-03T22:53:21+00:00'
 promote:
   - value: false
 sticky:
@@ -32,8 +32,7 @@ default_langcode:
 revision_translation_affected:
   - value: true
 path:
-  - alias: ''
-    pid: null
+  - alias: /daily/2025/08/28/changlog-isnt-just-list-git-commits
     langcode: en
 body:
   - value: |-

content/node.f971fedc-ce38-41b4-8d1f-b37766fb06e1.yml

@@ -0,0 +1,76 @@
+uuid:
+  - value: f971fedc-ce38-41b4-8d1f-b37766fb06e1
+langcode:
+  - value: en
+type:
+  - target_id: daily_email
+    target_type: node_type
+    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
+revision_timestamp:
+  - value: '2025-08-03T22:53:00+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: 'Changelogs with Continuous Delivery'
+created:
+  - value: '2025-07-29T22:51:45+00:00'
+changed:
+  - value: '2025-08-03T22:53:00+00:00'
+promote:
+  - value: false
+sticky:
+  - value: false
+default_langcode:
+  - value: true
+revision_translation_affected:
+  - value: true
+path:
+  - alias: ''
+    pid: null
+    langcode: en
+body:
+  - value: |-
+      Over the past few days, I've written why I think it's a good idea to keep a Changelog for software projects.
+
+      I've linked to the [Keep a Changelog][0] project, which gives a format for a Changelog file.
+
+      In it, unreleased changes are grouped at the top, and released changes grouped by version number.
+
+      But, how would this work if you're doing continuous delivery?
+
+      If you're deploying once a day, it could make sense to use release versions.
+
+      But, what if you're releasing multiple times a day, or separately releasing each commit?
+
+      Is it beneficial to tag every commit with its own release number?
+
+      In that situation, I've altered the format to group commits by date, and removed the Unreleased section as it's no longer needed.
+
+      In this case, you still get the benefits of a human-readable Changelog with a simplified structure.
+
+      I like standardisation, but use the format that works for you and your project.
+
+      [0]: https://keepachangelog.com
+    format: markdown
+    processed: |
+      <p>Over the past few days, I've written why I think it's a good idea to keep a Changelog for software projects.</p>
+      <p>I've linked to the <a href="https://keepachangelog.com">Keep a Changelog</a> project, which gives a format for a Changelog file.</p>
+      <p>In it, unreleased changes are grouped at the top, and released changes grouped by version number.</p>
+      <p>But, how would this work if you're doing continuous delivery?</p>
+      <p>If you're deploying once a day, it could make sense to use release versions.</p>
+      <p>But, what if you're releasing multiple times a day, or separately releasing each commit?</p>
+      <p>Is it beneficial to tag every commit with its own release number?</p>
+      <p>In that situation, I've altered the format to group commits by date, and removed the Unreleased section as it's no longer needed.</p>
+      <p>In this case, you still get the benefits of a human-readable Changelog with a simplified structure.</p>
+      <p>I like standardisation, but use the format that works for you and your project.</p>
+    summary: ''
+field_daily_email_cta:
+  - target_type: node
+    target_uuid: 9b4c39a3-702f-486c-a79b-4d7b96a4f3f6

content/path_alias.5260227a-6421-4bb3-b8dd-daee4ffbdd5a.yml

@@ -5,6 +5,6 @@ langcode:
 path:
   - value: /node/73861efd-5d4e-4c80-8c22-57594ee43dbc
 alias:
-  - value: /daily/2025/08/28/changlog-isnt-just-list-git-commits
+  - value: /daily/2025/07/28/changlog-isnt-just-list-git-commits
 status:
   - value: true

content/path_alias.8d996b82-7d43-4c34-a154-cfd0db370ea2.yml

@@ -0,0 +1,10 @@
+uuid:
+  - value: 8d996b82-7d43-4c34-a154-cfd0db370ea2
+langcode:
+  - value: en
+path:
+  - value: /node/f971fedc-ce38-41b4-8d1f-b37766fb06e1
+alias:
+  - value: /daily/2025/07/29/changelogs-continuous-delivery
+status:
+  - value: true

content/redirect.6cf7bed4-6f9a-48ca-bcaa-44551f6c638a.yml

@@ -0,0 +1,22 @@
+uuid:
+  - value: 6cf7bed4-6f9a-48ca-bcaa-44551f6c638a
+hash:
+  - value: '-ZvIWTA4_Ght3PSQPm8RKgavNL9WOl2zL2EzOlLIIwg'
+type:
+  - value: redirect
+uid:
+  - target_type: user
+    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
+redirect_source:
+  - path: daily/2025/08/28/changlog-isnt-just-list-git-commits
+    query: {  }
+redirect_redirect:
+  - uri: 'internal:/node/65601'
+    title: null
+    options: {  }
+language:
+  - value: en
+status_code:
+  - value: 301
+created:
+  - value: '2025-08-03T22:53:21+00:00'