Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
42
content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.yml
Normal file
42
content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.yml
Normal file
|
@ -0,0 +1,42 @@
|
|||
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: ''
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue