opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

tome export

Browse source
This commit is contained in:
Oliver Davies 2025-05-30 02:14:32 +01:00
parent 52278c3a53
commit 7a52afab5f
960 changed files with 3670 additions and 2229 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json
View file

@ -82,15 +82,15 @@
],
"body": [
{
"value": "\n <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>\n\n<p>I've been a DDEV user, and I've also used most, if not all, of the other popular Drupal development environments.<\/p>\n\n<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>\n\n<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>\n\n<h2 id=\"collaboration-is-key\">Collaboration is key<\/h2>\n\n<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>\n\n<h2 id=\"but-what-about-existing-teams-and-projects%3F\">But what about existing teams and projects?<\/h2>\n\n<p>If your company or team already uses another option, you can continue to use it.<\/p>\n\n<p>If you have an existing solution, I don't think it will be removed or abandoned in the near future.<\/p>\n\n<p>But, for new Drupal users and teams, one official development environment would be a big plus.<\/p>\n\n ",
"value": "\n <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>\n\n<p>I've been a DDEV user, and I've also used most, if not all, of the other popular Drupal development environments.<\/p>\n\n<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>\n\n<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>\n\n<h2 id=\"collaboration-is-key\">Collaboration is key<\/h2>\n\n<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>\n\n<h2 id=\"but-what-about-existing-teams-and-projects%3F\">But what about existing teams and projects?<\/h2>\n\n<p>If your company or team already uses another option, you can continue to use it.<\/p>\n\n<p>If you have an existing solution, I don't think it will be removed or abandoned in the near future.<\/p>\n\n<p>But, for new Drupal users and teams, one official development environment would be a big plus.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <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>\n\n<p>I've been a DDEV user, and I've also used most, if not all, of the other popular Drupal development environments.<\/p>\n\n<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>\n\n<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>\n\n<h2 id=\"collaboration-is-key\">Collaboration is key<\/h2>\n\n<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>\n\n<h2 id=\"but-what-about-existing-teams-and-projects%3F\">But what about existing teams and projects?<\/h2>\n\n<p>If your company or team already uses another option, you can continue to use it.<\/p>\n\n<p>If you have an existing solution, I don't think it will be removed or abandoned in the near future.<\/p>\n\n<p>But, for new Drupal users and teams, one official development environment would be a big plus.<\/p>\n\n ",
"processed": "\n <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>\n\n<p>I've been a DDEV user, and I've also used most, if not all, of the other popular Drupal development environments.<\/p>\n\n<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>\n\n<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>\n\n<h2 id=\"collaboration-is-key\">Collaboration is key<\/h2>\n\n<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>\n\n<h2 id=\"but-what-about-existing-teams-and-projects%3F\">But what about existing teams and projects?<\/h2>\n\n<p>If your company or team already uses another option, you can continue to use it.<\/p>\n\n<p>If you have an existing solution, I don't think it will be removed or abandoned in the near future.<\/p>\n\n<p>But, for new Drupal users and teams, one official development environment would be a big plus.<\/p>\n\n ",
"summary": null
}
],
"feeds_item": [
{
"imported": "1970-01-01T00:33:45+00:00",
"imported": "1970-01-01T00:32:50+00:00",
"guid": null,
"hash": "6549977c5d3e11dfcbc2dadcbeef7dea",
"target_type": "feeds_feed",