76 lines
3.4 KiB
YAML
76 lines
3.4 KiB
YAML
uuid:
|
||
- value: 0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c
|
||
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:18+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: 'Just say Drupal'
|
||
created:
|
||
- value: '2024-03-14T00:00:00+00:00'
|
||
changed:
|
||
- value: '2025-05-11T09:00:18+00:00'
|
||
promote:
|
||
- value: false
|
||
sticky:
|
||
- value: false
|
||
default_langcode:
|
||
- value: true
|
||
revision_translation_affected:
|
||
- value: true
|
||
path:
|
||
- alias: /daily/2024/03/14/just-say-drupal
|
||
langcode: en
|
||
body:
|
||
- value: |
|
||
<p>Today, I've been following a conversation on Twitter and reading a blog post about Drupal naming and removing the version number from promotional materials.</p>
|
||
|
||
<p>In the post, the author recommends stopping using the version number and "just say Drupal" and referring to Drupal 7 and older as "Legacy Drupal".</p>
|
||
|
||
<p>Here's a quote from the article that stood out to me:</p>
|
||
|
||
<blockquote>
|
||
<p>This is no longer true! We have successfully eliminated the need for organizations to leave Drupal because “it’s cheaper to just rebuild it in Wordpress than upgrade from 8 to 9 or from 9 to 10.” We’ve made it easier for our clients to spend less on major upgrades, we should be proud!</p>
|
||
</blockquote>
|
||
|
||
<p>Another suggestion was to also use the term "Modern Drupal" for anything since Drupal 8.</p>
|
||
|
||
<p>I've been doing this or calling it "Drupal 8+" on streams and podcast episodes, but I like this approach and I'm going to standardise on this, help change the perception of Drupal and that large rebuilds are no longer needed to upgrade as they were between the older legacy versions.</p>
|
||
|
||
<p><a href="https://ten7.com/blog/post/just-say-drupal">Read the article</a> for more information about this.</p>
|
||
|
||
|
||
format: full_html
|
||
processed: |
|
||
<p>Today, I've been following a conversation on Twitter and reading a blog post about Drupal naming and removing the version number from promotional materials.</p>
|
||
|
||
<p>In the post, the author recommends stopping using the version number and "just say Drupal" and referring to Drupal 7 and older as "Legacy Drupal".</p>
|
||
|
||
<p>Here's a quote from the article that stood out to me:</p>
|
||
|
||
<blockquote>
|
||
<p>This is no longer true! We have successfully eliminated the need for organizations to leave Drupal because “it’s cheaper to just rebuild it in Wordpress than upgrade from 8 to 9 or from 9 to 10.” We’ve made it easier for our clients to spend less on major upgrades, we should be proud!</p>
|
||
</blockquote>
|
||
|
||
<p>Another suggestion was to also use the term "Modern Drupal" for anything since Drupal 8.</p>
|
||
|
||
<p>I've been doing this or calling it "Drupal 8+" on streams and podcast episodes, but I like this approach and I'm going to standardise on this, help change the perception of Drupal and that large rebuilds are no longer needed to upgrade as they were between the older legacy versions.</p>
|
||
|
||
<p><a href="https://ten7.com/blog/post/just-say-drupal">Read the article</a> for more information about this.</p>
|
||
|
||
|
||
summary: null
|
||
field_daily_email_cta: { }
|