Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
77
content/node.1f9686d7-f067-4253-88a6-639125a625a6.yml
Normal file
77
content/node.1f9686d7-f067-4253-88a6-639125a625a6.yml
Normal file
|
@ -0,0 +1,77 @@
|
|||
uuid:
|
||||
- value: 1f9686d7-f067-4253-88a6-639125a625a6
|
||||
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:36+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: |
|
||||
Laravel Prompts and framework-agnostic tools
|
||||
created:
|
||||
- value: '2023-08-04T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:36+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2023/08/04/laravel-prompts
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>Although I wouldn't consider myself a "Laravel Developer", I enjoy watching the talks from the Laravel conferences, most recently Laracon US, that took place last week.</p>
|
||||
|
||||
<p>I like to learn from other communities and adopt relevant practices or tools within my projects. I did this with Laravel Collections, which I use on nearly every project.</p>
|
||||
|
||||
<h2 id="laravel-prompts">Laravel Prompts</h2>
|
||||
|
||||
<p>I watched Jess Archer's talk on the new Laravel Prompts and was happy when she said it worked with plain PHP projects, not just Laravel.</p>
|
||||
|
||||
<p>This means I can potentially use it with Drupal and Drush or Symfony Console applications, too, such as my build configuration file generator.</p>
|
||||
|
||||
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
||||
|
||||
<p>I like tools I can use across multiple technologies and prefer framework-agnostic tools to specific ones.</p>
|
||||
|
||||
<p>Then, if I'm working on a different project, I can use the tools I already know instead of learning something different just for that.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>Although I wouldn't consider myself a "Laravel Developer", I enjoy watching the talks from the Laravel conferences, most recently Laracon US, that took place last week.</p>
|
||||
|
||||
<p>I like to learn from other communities and adopt relevant practices or tools within my projects. I did this with Laravel Collections, which I use on nearly every project.</p>
|
||||
|
||||
<h2 id="laravel-prompts">Laravel Prompts</h2>
|
||||
|
||||
<p>I watched Jess Archer's talk on the new Laravel Prompts and was happy when she said it worked with plain PHP projects, not just Laravel.</p>
|
||||
|
||||
<p>This means I can potentially use it with Drupal and Drush or Symfony Console applications, too, such as my build configuration file generator.</p>
|
||||
|
||||
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
||||
|
||||
<p>I like tools I can use across multiple technologies and prefer framework-agnostic tools to specific ones.</p>
|
||||
|
||||
<p>Then, if I'm working on a different project, I can use the tools I already know instead of learning something different just for that.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue