oliverdavies.uk/content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.yml

85 lines
4.2 KiB
YAML

uuid:
- value: 73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc
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:28+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: |
One official Drupal development environment?
created:
- value: '2023-10-31T00:00:00+00:00'
changed:
- value: '2025-05-11T09:00:28+00:00'
promote:
- value: false
sticky:
- value: false
default_langcode:
- value: true
revision_translation_affected:
- value: true
path:
- alias: /daily/2023/10/31/one-official-drupal-development-environment
langcode: en
body:
- value: |
<p>Yesterday, I read <a href="https://kevinquillen.com/ddev-being-considered-official-drupal-development-environment">a post by Kevin Quillen</a> titled 'DDEV being considered as the "official" Drupal development environment'.</p>
<p>I've been a DDEV user, and I've also used most, if not all, of the other popular Drupal development environments.</p>
<p>These days, I use <a href="/daily/2022/08/21/2022-08-21">my own Docker Compose-based setup</a>, but I feel having an official development environment would be an excellent move for the Drupal community and project - and for new Drupal users, evaluators and contributors in particular.</p>
<p>Anything that lowers the barrier to using or contributing to Drupal is a good thing and allows for more focused documentation and a simpler onboarding experience, similar to what other projects have - such as Laravel with Homestead, Valet and now, Sail.</p>
<h2 id="collaboration-is-key">Collaboration is key</h2>
<p>Instead of multiple similar projects creating the same features and fixing the same issues, there could be an opportunity to collaborate or even combine projects and resources in the future.</p>
<h2 id="but-what-about-existing-teams-and-projects%3F">But what about existing teams and projects?</h2>
<p>If your company or team already uses another option, you can continue to use it.</p>
<p>If you have an existing solution, I don't think it will be removed or abandoned in the near future.</p>
<p>But, for new Drupal users and teams, one official development environment would be a big plus.</p>
format: full_html
processed: |
<p>Yesterday, I read <a href="https://kevinquillen.com/ddev-being-considered-official-drupal-development-environment">a post by Kevin Quillen</a> titled 'DDEV being considered as the "official" Drupal development environment'.</p>
<p>I've been a DDEV user, and I've also used most, if not all, of the other popular Drupal development environments.</p>
<p>These days, I use <a href="http://default/daily/2022/08/21/2022-08-21">my own Docker Compose-based setup</a>, but I feel having an official development environment would be an excellent move for the Drupal community and project - and for new Drupal users, evaluators and contributors in particular.</p>
<p>Anything that lowers the barrier to using or contributing to Drupal is a good thing and allows for more focused documentation and a simpler onboarding experience, similar to what other projects have - such as Laravel with Homestead, Valet and now, Sail.</p>
<h2 id="collaboration-is-key">Collaboration is key</h2>
<p>Instead of multiple similar projects creating the same features and fixing the same issues, there could be an opportunity to collaborate or even combine projects and resources in the future.</p>
<h2 id="but-what-about-existing-teams-and-projects%3F">But what about existing teams and projects?</h2>
<p>If your company or team already uses another option, you can continue to use it.</p>
<p>If you have an existing solution, I don't think it will be removed or abandoned in the near future.</p>
<p>But, for new Drupal users and teams, one official development environment would be a big plus.</p>
summary: null
field_daily_email_cta: { }