80 lines
3.6 KiB
YAML
80 lines
3.6 KiB
YAML
uuid:
|
|
- value: 71e7e05f-a075-432a-bda3-db66b0e733cc
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T08:59:58+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: 'Upgrading incrementally'
|
|
created:
|
|
- value: '2025-04-17T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T08:59:58+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2025/04/17/incrementally
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>Did you know you can have more than one version of your website in production at the same time?</p>
|
|
|
|
<p>If you're migrating to a new platform or upgrading to a new major version, such as Drupal 7 to Drupal 11, you don't need to do it all at once.</p>
|
|
|
|
<p>You can do it incrementally, and seamlessly for end users.</p>
|
|
|
|
<p>The MVP for your new website can be a particular section or a single page that is developed and launched to production alongside the current website.</p>
|
|
|
|
<p>Depending on the path someone goes to, they'll either see the new website or the old one.</p>
|
|
|
|
<p>Focusing on delivering a single page or section of a website is much faster compared to rebuilding the entire thing, it's a lot less risky as the feedback loop is much shorter and you get feedback from real users.</p>
|
|
|
|
<p>Once you have the new MVP deployed to a hosting environment, you can configure a proxy to assign traffic between it and the existing hosting based on path, request headers, or a combination of different options.</p>
|
|
|
|
<p>This is an approach I've taken with my website as I've upgraded between different versions of Drupal and also static site generators such as Jekyll, Astro and Sculpin.</p>
|
|
|
|
<p>Instead of waiting for months to deliver a new website to production, do it in days or weeks.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>Did you know you can have more than one version of your website in production at the same time?</p>
|
|
|
|
<p>If you're migrating to a new platform or upgrading to a new major version, such as Drupal 7 to Drupal 11, you don't need to do it all at once.</p>
|
|
|
|
<p>You can do it incrementally, and seamlessly for end users.</p>
|
|
|
|
<p>The MVP for your new website can be a particular section or a single page that is developed and launched to production alongside the current website.</p>
|
|
|
|
<p>Depending on the path someone goes to, they'll either see the new website or the old one.</p>
|
|
|
|
<p>Focusing on delivering a single page or section of a website is much faster compared to rebuilding the entire thing, it's a lot less risky as the feedback loop is much shorter and you get feedback from real users.</p>
|
|
|
|
<p>Once you have the new MVP deployed to a hosting environment, you can configure a proxy to assign traffic between it and the existing hosting based on path, request headers, or a combination of different options.</p>
|
|
|
|
<p>This is an approach I've taken with my website as I've upgraded between different versions of Drupal and also static site generators such as Jekyll, Astro and Sculpin.</p>
|
|
|
|
<p>Instead of waiting for months to deliver a new website to production, do it in days or weeks.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|