uuid:
  - value: 266918e6-af3d-48f8-89d4-657ff2214626
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:26+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: |
      Building your own in-house Drupal distribution
created:
  - value: '2023-12-15T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:26+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2023/12/15/building-your-own-in-house-drupal-distribution
    langcode: en
body:
  - value: |
      <p>On several occasions, I've seen companies who build a lot of Drupal projects creating their own in-house [Drupal distribution] for new projects.</p>

      <p>Whilst this seems like a good idea, the ones I've seen are either not well maintained due to limited time between projects, or they're bloated with features and trying to include too much out of the box.</p>

      <p>If you maintain an in-house distribution, or are thinking of creating one, my advice is to ensure it's maintained by allocating enough time for this, and to keep it lean and only include the minimum amount of required functionality.</p>

      <p>Alternatively, maybe keep a template composer.json file to base new projects on instead of a full distribution.</p>

      <p>That could declare the modules and themes you want to include, without the additional overhead.</p>

      <p><a href="/daily/2023/12/14/save-time-and-effort-with-drupal-distributions">drupal distribution</a></p>

              
    format: full_html
    processed: |
      <p>On several occasions, I've seen companies who build a lot of Drupal projects creating their own in-house [Drupal distribution] for new projects.</p>

      <p>Whilst this seems like a good idea, the ones I've seen are either not well maintained due to limited time between projects, or they're bloated with features and trying to include too much out of the box.</p>

      <p>If you maintain an in-house distribution, or are thinking of creating one, my advice is to ensure it's maintained by allocating enough time for this, and to keep it lean and only include the minimum amount of required functionality.</p>

      <p>Alternatively, maybe keep a template composer.json file to base new projects on instead of a full distribution.</p>

      <p>That could declare the modules and themes you want to include, without the additional overhead.</p>

      <p><a href="/daily/2023/12/14/save-time-and-effort-with-drupal-distributions">drupal distribution</a></p>

              
    summary: null
field_daily_email_cta: {  }