Move all files to sculpin/
This commit is contained in:
parent
c5d71803a5
commit
0f61b4e9ee
1514 changed files with 0 additions and 0 deletions
23
sculpin/source/_posts/2023-12-15.md
Normal file
23
sculpin/source/_posts/2023-12-15.md
Normal file
|
@ -0,0 +1,23 @@
|
|||
---
|
||||
title: >
|
||||
Building your own in-house Drupal distribution
|
||||
pubDate: 2023-12-15
|
||||
permalink: >-
|
||||
daily/2023/12/15/building-your-own-in-house-drupal-distribution
|
||||
tags:
|
||||
- software-development
|
||||
- php
|
||||
- drupal
|
||||
---
|
||||
|
||||
On several occasions, I've seen companies who build a lot of Drupal projects creating their own in-house [Drupal distribution] for new projects.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Alternatively, maybe keep a template composer.json file to base new projects on instead of a full distribution.
|
||||
|
||||
That could declare the modules and themes you want to include, without the additional overhead.
|
||||
|
||||
[drupal distribution]({{site.url}}/daily/2023/12/14/save-time-and-effort-with-drupal-distributions)
|
Loading…
Add table
Add a link
Reference in a new issue