Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
76
content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.yml
Normal file
76
content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.yml
Normal file
|
@ -0,0 +1,76 @@
|
|||
uuid:
|
||||
- value: 03bbb03d-5963-477a-a904-19e2c1f1a581
|
||||
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:02+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: 'Refactor, remove or replace'
|
||||
created:
|
||||
- value: '2025-01-09T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:02+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2025/01/09/rrr
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>There are three things you can do with legacy code.</p>
|
||||
|
||||
<p>Refactor it, remove it or replace it.</p>
|
||||
|
||||
<p>You can refactor it to make it easier to maintain and change in the future.</p>
|
||||
|
||||
<p>If it's not needed, you can remove it.</p>
|
||||
|
||||
<p>If it's not used, there's no need to keep it.</p>
|
||||
|
||||
<p>Or you can replace it with something else.</p>
|
||||
|
||||
<p>There isn't one right answer and the correct approach will depend on the situation and objective.</p>
|
||||
|
||||
<p>In a future email, I'll give some examples of how I refactor legacy code.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>There are three things you can do with legacy code.</p>
|
||||
|
||||
<p>Refactor it, remove it or replace it.</p>
|
||||
|
||||
<p>You can refactor it to make it easier to maintain and change in the future.</p>
|
||||
|
||||
<p>If it's not needed, you can remove it.</p>
|
||||
|
||||
<p>If it's not used, there's no need to keep it.</p>
|
||||
|
||||
<p>Or you can replace it with something else.</p>
|
||||
|
||||
<p>There isn't one right answer and the correct approach will depend on the situation and objective.</p>
|
||||
|
||||
<p>In a future email, I'll give some examples of how I refactor legacy code.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue