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.c027d77e-97c4-43eb-99cd-672dedcf8f14.yml
Normal file
68
content/node.c027d77e-97c4-43eb-99cd-672dedcf8f14.yml
Normal file
|
@ -0,0 +1,68 @@
|
|||
uuid:
|
||||
- value: c027d77e-97c4-43eb-99cd-672dedcf8f14
|
||||
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:22+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: 'Write once, manage forever'
|
||||
created:
|
||||
- value: '2024-01-26T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:22+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2024/01/26/write-once-manage-forever
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>I built my <a href="/build-config">Build Configs</a> tool because I only wanted to write a file once and re-use it instead of writing it over again or copying and pasting between projects.</p>
|
||||
|
||||
<p>Having standardised templates for different languages and project types, I can easily set up new projects and get them running in a few minutes.</p>
|
||||
|
||||
<p>If I need to add a feature or fix a bug, I can do it once in the Build Configs tool and easily regenerate the configuration files for all projects, and they'll all get the updated files.</p>
|
||||
|
||||
<p>There's no "I need to copy this feature from project A or this bug fix from project B." when starting on project C.</p>
|
||||
|
||||
<p>As I only work on fixed-price engagements, it's in my interest to be able to create and maintain projects in a fast and efficient manner.</p>
|
||||
|
||||
<p>The Build Configs tool enables me to do that.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>I built my <a href="http://default/build-config">Build Configs</a> tool because I only wanted to write a file once and re-use it instead of writing it over again or copying and pasting between projects.</p>
|
||||
|
||||
<p>Having standardised templates for different languages and project types, I can easily set up new projects and get them running in a few minutes.</p>
|
||||
|
||||
<p>If I need to add a feature or fix a bug, I can do it once in the Build Configs tool and easily regenerate the configuration files for all projects, and they'll all get the updated files.</p>
|
||||
|
||||
<p>There's no "I need to copy this feature from project A or this bug fix from project B." when starting on project C.</p>
|
||||
|
||||
<p>As I only work on fixed-price engagements, it's in my interest to be able to create and maintain projects in a fast and efficient manner.</p>
|
||||
|
||||
<p>The Build Configs tool enables me to do that.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue