Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
80
content/node.68c7948f-c44c-46e2-878f-432616c7e365.yml
Normal file
80
content/node.68c7948f-c44c-46e2-878f-432616c7e365.yml
Normal file
|
@ -0,0 +1,80 @@
|
|||
uuid:
|
||||
- value: 68c7948f-c44c-46e2-878f-432616c7e365
|
||||
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: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: 'Legacy code is anything older than...'
|
||||
created:
|
||||
- value: '2025-03-22T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:00+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2025/03/22/legacy
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>How do you define legacy code?</p>
|
||||
|
||||
<p>Code that was written by someone else?</p>
|
||||
|
||||
<p>Code that doesn't have tests?</p>
|
||||
|
||||
<p>Any code that has been released to production?</p>
|
||||
|
||||
<p>Code that's more than a day old?</p>
|
||||
|
||||
<p>In a talk I recently watched, the speaker suggested that any code written more than thirty minutes ago is legacy code.</p>
|
||||
|
||||
<p>Once you've written some code and left it for half an hour, you need to re-read it to remember and re-learn what the code does and decide how you want to implement your next requirement.</p>
|
||||
|
||||
<p>This is the same approach for code that was written longer ago or written by someone else.</p>
|
||||
|
||||
<p>What do you think?</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>How do you define legacy code?</p>
|
||||
|
||||
<p>Code that was written by someone else?</p>
|
||||
|
||||
<p>Code that doesn't have tests?</p>
|
||||
|
||||
<p>Any code that has been released to production?</p>
|
||||
|
||||
<p>Code that's more than a day old?</p>
|
||||
|
||||
<p>In a talk I recently watched, the speaker suggested that any code written more than thirty minutes ago is legacy code.</p>
|
||||
|
||||
<p>Once you've written some code and left it for half an hour, you need to re-read it to remember and re-learn what the code does and decide how you want to implement your next requirement.</p>
|
||||
|
||||
<p>This is the same approach for code that was written longer ago or written by someone else.</p>
|
||||
|
||||
<p>What do you think?</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue