Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
68
content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.yml
Normal file
68
content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.yml
Normal file
|
@ -0,0 +1,68 @@
|
|||
uuid:
|
||||
- value: 7f8ffdde-2056-4739-bfe6-cbb0a4de37ae
|
||||
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:16+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: 'Leaving a trail of breadcrumbs'
|
||||
created:
|
||||
- value: '2024-03-30T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:16+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2024/03/30/leaving-a-trail-of-breadcrumbs
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>A great thing about committing often is that you leave a trail of breadcrumbs for yourself, and you can easily find your way back.</p>
|
||||
|
||||
<p>If you are trying to get a test to pass or fix a bug and you get a bit lost, you can see what you've changed since your last commit instead of everything since you started working on your task.</p>
|
||||
|
||||
<p>If needed, you can discard your changes and reset to your last working commit to try again, similar to using the "test and commit or revert" approach.</p>
|
||||
|
||||
<p>If I commit too often, I can squash them before pushing.</p>
|
||||
|
||||
<p>If I don't commit often enough, I can regret not committing more regularly if I get stuck or lost.</p>
|
||||
|
||||
<p>I'd rather do the former.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>A great thing about committing often is that you leave a trail of breadcrumbs for yourself, and you can easily find your way back.</p>
|
||||
|
||||
<p>If you are trying to get a test to pass or fix a bug and you get a bit lost, you can see what you've changed since your last commit instead of everything since you started working on your task.</p>
|
||||
|
||||
<p>If needed, you can discard your changes and reset to your last working commit to try again, similar to using the "test and commit or revert" approach.</p>
|
||||
|
||||
<p>If I commit too often, I can squash them before pushing.</p>
|
||||
|
||||
<p>If I don't commit often enough, I can regret not committing more regularly if I get stuck or lost.</p>
|
||||
|
||||
<p>I'd rather do the former.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue