Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
85
content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.yml
Normal file
85
content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.yml
Normal file
|
@ -0,0 +1,85 @@
|
|||
uuid:
|
||||
- value: 11b6429c-7f14-436c-a3cc-f5cfad7b63c0
|
||||
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:30+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: |
|
||||
Is decoupled Drupal still a thing?
|
||||
created:
|
||||
- value: '2023-10-26T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:30+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2023/10/26/is-decoupled-drupal-still-a-thing
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>A few years ago, decoupled or headless Drupal - where Drupal is used as an API with a separate front-end - was very popular with some large Drupal agencies and clients using it.</p>
|
||||
|
||||
<p><a href="/talks/decoupling-drupal-vuejs">I gave a conference talk</a> about how to use Drupal as a backend application for a Vue.js frontend.</p>
|
||||
|
||||
<p>Recently, though, I haven't heard much about it.</p>
|
||||
|
||||
<p>Some previous advocates have moved back to the more traditional approach.</p>
|
||||
|
||||
<p>Interestingly, though, I did hear quite a bit about it at DrupalCon and about Drupal and Next.js in particular.</p>
|
||||
|
||||
<p>I want to try using Drupal with Astro in the future and see what the landscape is like now.</p>
|
||||
|
||||
<h2 id="what-about-you%3F">What about you?</h2>
|
||||
|
||||
<p>Do you use Drupal in a decoupled or headless way? If so, what do you use for the frontend?</p>
|
||||
|
||||
<p>If not, or if you've moved back to a more traditional approach, why?</p>
|
||||
|
||||
<p>Reply and let me know.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>A few years ago, decoupled or headless Drupal - where Drupal is used as an API with a separate front-end - was very popular with some large Drupal agencies and clients using it.</p>
|
||||
|
||||
<p><a href="http://default/talks/decoupling-drupal-vuejs">I gave a conference talk</a> about how to use Drupal as a backend application for a Vue.js frontend.</p>
|
||||
|
||||
<p>Recently, though, I haven't heard much about it.</p>
|
||||
|
||||
<p>Some previous advocates have moved back to the more traditional approach.</p>
|
||||
|
||||
<p>Interestingly, though, I did hear quite a bit about it at DrupalCon and about Drupal and Next.js in particular.</p>
|
||||
|
||||
<p>I want to try using Drupal with Astro in the future and see what the landscape is like now.</p>
|
||||
|
||||
<h2 id="what-about-you%3F">What about you?</h2>
|
||||
|
||||
<p>Do you use Drupal in a decoupled or headless way? If so, what do you use for the frontend?</p>
|
||||
|
||||
<p>If not, or if you've moved back to a more traditional approach, why?</p>
|
||||
|
||||
<p>Reply and let me know.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue