Drupal

DDEV

brooke — Mon, 02 Nov 2026 19:59:42 +0000

DDEV

Just some notes about DDEV

ddev snapshot --name=seed

ddev delete

ddev start

Addons for base Drupal configurations

Descriptions of 4 common ways to setup DDEV

Add-on	Best for	Typical project layout
`UltraBob/ddev-drupal-code-quality`	Full Drupal website projects where your site repo already contains Drupal code and custom code.	Existing site/project repo; installs code-quality configs and IDE shims in-place.
`ddev/ddev-drupal-contrib`	Drupal contrib module/theme development where the contrib project is the center of the repo.	Contrib project repo with Drupal scaffolded around it (symlink workflow).
`justafish/ddev-drupal-core-dev` / `joachim-n/ddev-drupal-core-dev`	Drupal core development.	Drupal core checkout or core-dev project template.
https://addons.ddev.com/addons/amateescu/ddev-drupal-dev	Drupal core and contrib combined, see below	core git checkout as the project root.

DDEV Drupal Dev from Andrei Mateescu of Tag1

A DDEV add-on for working on Drupal core and contrib modules together, using a core git checkout as the project root.

Other add-ons target either core or contrib in isolation. This one is for when you need both: developing a contrib module against the latest core, fixing a core bug that affects contrib, or running contrib tests on a core patch.

Extra dependencies (contrib modules, Drush, dev tools) are managed through a composer.local.json overlay, keeping core's composer.json and composer.lock untouched.

"You can work on multiple modules this way; each gets its own git checkout that you can commit and push to independently."

brooke Mon, 2 Nov 2026 - 11:59

Tags

Drupal

DDEV

Contrib Drupal Module Development

brooke — Mon, 02 Nov 2026 19:58:32 +0000

Contrib Drupal Module Development

One way to set up local Development for a contrib module using e0ipso's AI suite. See Agentic Coding Harness for Drupal

opt out of T3 telemetry by adding the following to ~/.ddev/.env
- T3CODE_TELEMETRY_ENABLED=false
Install https://github.com/e0ipso/self-review
Then:

BDEV_CURRENT_SITE="config_suite"
cd ~/Sites
git clone git@git.drupal.org:project/$BDEV_CURRENT_SITE.git
cd $BDEV_CURRENT_SITE
cp ~/projects/.gitignore-ddev .gitignore
ddev config --project-type=drupal11 --docroot=web
orb
ddev add-on get ddev/ddev-drupal-contrib
ddev add-on get hanoii/ddev-drupal-contrib-extras
ddev start
ddev poser

ddev symlink-project
ddev config --update
ddev restart
ddev drush si -y
ddev drush en $BDEV_CURRENT_SITE -y
open $(ddev drush uli)
ddev exec "cd web/core && yarn install"

# Temporary workaround on Mac because e0ipso's plugin only works for Linux for importing local OpenCode config
mkdir -p $HOME/Sites/$BDEV_CURRENT_SITE/.ddev/homeadditions/.local/share
ln -s $HOME/.local/share/opencode $HOME/Sites/$BDEV_CURRENT_SITE/.ddev/homeadditions/.local/share/opencode

ddev add-on get e0ipso/ddev-playwright-cli
ddev add-on get e0ipso/ddev-assistant-opencode
ddev add-on get e0ipso/ddev-assistant-t3
ddev restart

# Allows running playwright-cli from inside the container
#   without having to use the --config option
# Symlinks .claude playwright skills to .agents folder for other harnesses. 
ddev ssh

rm .playwright/cli.config.json
ln -s "$(pwd)/.ddev/playwright-cli/cli.config.json" .playwright/cli.config.json
mkdir -p .agents/skills
ln -s "$(pwd)/.claude/skills/playwright-cli" .agents/skills/playwright-cli
exit

npx kenkeep init --harnesses opencode
npx kenkeep doctor
npx kenkeep pack import e0ipso/kenkeep-pack-drupal
npx strikethroo init --harnesses opencode
npx skills add e0ipso/strikethroo

Strikethroo workflow: https://strikethroo.canpicasoft.com/workflow.html Kenkeep docs: https://kenkeep.canpicasoft.com/

ddev t3 start
npx strikethroo serve
/st-create-plan display a welcome message to new users
/st-refine-plan 1, see review.xml
/st-execute-blueprint 1
/st-code-review 1, line 95 in example.module has a typo: "piece" should be "peace"

brooke Mon, 2 Nov 2026 - 11:58

Tags

Drupal

DDEV

Notes for: Site Analysis and AI's Strengths and Limits, By David Hobbs

brooke — Mon, 02 Nov 2026 19:04:39 +0000

Notes for: Site Analysis and AI's Strengths and Limits, By David Hobbs

Just copying over some notes from a great video, in case it ever goes away:

Site Analysis and AI's Strengths and Limits

By David Hobbs

Progression of content analysis

#	Type	Example	Automation at scale?	Use Al?	Quantitative or Qualitative?
1	Traditional Automation	Crawl with [[Screaming Frog]]	Yes	No	Quantitative
2	Manual	Line-by-line qualitative audit	No	No	Qualitative
3	One-off Al	Ask ChatGPT a question about a site	No	Yes, one time	Qualitative
4	LLM → Deterministic	Have Claude write a script to run reading level analysis on every page	Partial	Yes, one time	Quantitative
5	Scaled Al	Pass thousands of pages to low power LLM to categorize	Yes	Yes, every page	Qualitative
Note: Al allows us to do some qualitative analysis that is NOT manual.

Advantages of particular types of content analysis


#	Type	Advantages
1	Traditional Automation	Easy to get basic information on many pages.
2	Manual	The approach everyone knows, and it feels like things are being done in a high quality manner (even before Al this was often the feeling).
3	One-off Al	Easy to get analysis that might be outside your expertise for a subset of pages.
4	LLM → Deterministic	Only use Al once, and then have all the advantages of traditional automation.
5	Scaled Al	Get qualitative information over a large swath of content (possibly impossible otherwise).

Disadvantages of the manual approach

Almost certainly leads to restricting the number of pages that are analyzed.
Very difficult to iterate or change course (such as if you decide to change the definition of audience)
Very difficult to merge analysis from multiple people.
Very difficult to be consistent.
Difficult to track over time.
Likely to encourage team to take action on content while analyzing it.

Disadvantages of one-off Al

Generally low transparency (How did it come up with the answer? Did it look at any pages? Did it consider your existing analysis?)
Related to the above, it can definitely hallucinate or over-extrapolate.
Generally requires powerful LLM
Can short circuit critical thinking of the analyst
NOT for pervasive analysis across a digital presence

Tip: If you do one-off chatbot analysis, explicitly ask how it came up with the answer and its sources. ie., "Explain to me in detail how you determined this. What sources did you use? What did you derive from each source? What confidence do you have in this answer?"

Disadvantages of LLM → Deterministic

Depending on skillset, can be difficult to evaluate whether the script is doing what you want it to do
Can be difficult to clearly specify the requirements
One-off efforts to write scripts can be difficult to reconcile together into a coherent whole

Keep in mind non-LLM automated analysis options

Near-text duplicate analysis
Graph database analysis (analysis of linkages between content / sections)
Scraping out information and component analysis
PDF analysis
Merge information (for instance from Google Analytics)
Reading level analysis
Charting
HTML structure analysis
Over-time analysis
Logo analysis
Formulas, maps, and rules
Technology analysis (such as with wappalyzer)

Tip: Consider converting problems to deterministic ones with AI

Disadvantage of Scaled Al

Difficult to develop on your own
Heavy processing is in the backend (not in chatbot)

TIp: Clearly differentiate between what's EASY to analyze and what's IMPORTANT to analyze.

Note: Far too often teams just revert to what's simple to analyze when that will not help them achieve their real business goals. For example, you can't analyze for consolidation if you only look at a small subset of pages because then you would be able to use a spreadsheet.

Summary

There is lots of automation that can be applied outside of LLMs.
For some questions, you really do need to look at the entire digital presence.
Al can help you accomplish qualitative assessments that required manual intervention before.
There are a variety of ways of using Al for site analysis.

Tips

Focus on refining the QUESTIONS you need answered.
If you do one-off chatbot analysis, explicitly ask how it came up with the answer in its sources.
Consider converting problems to deterministic ones with Al.
Clearly differentiate between what's EASY to analyze and what's IMPORTANT to analyze.

brooke Mon, 2 Nov 2026 - 11:04

Tags

Drupal

AI Ethics

brooke — Mon, 02 Nov 2026 18:58:09 +0000

AI Ethics

The Environment

From When the Clock Ticks Closer: AI, Ethics, and Drupal's Responsibility to the Public Good April 1, 2026

Data centers are multiplying across the globe drawing enormous quantities of power and water
from communities already under resource strain.
The raw materials required for AI hardware involve
- environmentally damaging extraction processes
- energy-intensive manufacturing
- growing mountains of electronic waste

"This is not an abstraction for the Drupal community. As an ecosystem that powers a substantial share of the world's web infrastructure - from small nonprofits to national governments - the collective energy footprint of Drupal-based sites and the hosting decisions behind them carries real weight. Organizations within the community have begun pushing for greener hosting choices, leaner architectures, and more deliberate thinking about when AI features add genuine value versus when they simply add compute."

brooke Mon, 2 Nov 2026 - 10:58

Tags

Drupal

Drupal Headless Code Components Setup - My First Attempt

brooke — Wed, 07 Oct 2026 01:06:33 +0000

Drupal Headless Code Components Setup - My First Attempt

Overview

This is an overview of my first attempt at working with Drupal Code Components and headless Next.js. The purpose of this page is to document my poor understanding of how to set this up so that I may revisit it when I know better and so that I may mentor other people to do better.

See https://project.pages.drupalcode.org/canvas/headless/setup/ for the offical documentation.

Outline of Setup Steps

Create a folder for the project and cd into it.
Configure DDEV for Drupal with some extra modules needed for the Canvas Headless (canvas_headless) module
Create a folder to store OAuth keys.
Enable the Canvas Headless and the Canvas OAuth modules
Log in with Chrome (the docs say you have to use a Chromium-based browser, so no Firefox of Safari..)
Scaffold the Canvas Headless code, in a new folder called headless, with support for Next.js
Get Vercel AI agent skills to help your agents understand the Next/React conventions.
Get Drupal Canvas AI agent skills
Install Canvas CLI
Start the Canvas Headless Next.js server.
Initialize a git repo with a default .gitignore
Generate OAuth keys
Setup a consumer
Add the Frontend in the Canvas editor
Login with Canvas CLI
Push the default Code Components to Drupal
Edit a page in the Canvas editor in Drupal
View the site in the Next.js app in the browser

Detailed Setup Steps

cd ~/Sites
mkdir headless
cd headless


ddev config --project-type=drupal11 --docroot=web
ddev start

ddev composer create-project drupal/recommended-project
ddev composer require --dev 'drush/drush'
ddev composer require 'drupal/canvas' 'drupal/consumers' 'drupal/custom_elements' 'drupal/simple_oauth'

ddev restart

mkdir keys
ddev drush si -y
ddev drush en canvas_headless, canvas_oauth -y
open -a "Google Chrome" "$(ddev drush uli)"

npx @drupal-canvas/create@latest headless \
  --template nextjs \
  --site-url https://headless.ddev.site \
  --agents none

cd headless
npx skills add vercel-labs/agent-skills --yes
npx skills add drupal-canvas/skills --yes
npm install @drupal-canvas/cli
npm run dev

Open up a new terminal window.

Remove the newly added .git folder that the scaffolding added (~/Sites/headless/headless/.git).
Init a git repo for the whole project instead.
Make an initial commit so that later, you can get a clear picture of what Canvas CLI creates or pulls in.

rm -rf ~/Sites/headless/headless/.git
cd ~/Sites/headless/
git init .
echo "web/sites/default/files" >> .gitignore
echo "vendor" >> .gitignore
git add . && git commit -m 'initial commit'

Open http://headless.ddev.site/admin/config/people/simple_oauth and click "Generate keys" button, then enter the folder that was created in the steps above:

/var/www/html/keys

Make sure to click the "Save configuration" button.

Open http://headless.ddev.site/admin/config/services/consumer and click "+ Add Consumer", then set the following field values:

Label: Code Components
Client ID: code-components
Grant types (enable both):
- JWT bearer (preview assertion)
- Authorization Code
Authorization Code settings
- Enable all scopes
- Enable "Automatic authorization", "Remember previous approval", "Use PKCE?"
- Redirect URIs:

http://localhost:4444/callback

Disable "Is this consumer 3rd party?"
Disable "Is Confidential?"
Set "Access token expiration time" to 86400 (one day)
Click Save
Open http://headless.ddev.site/admin/content/pages and click "Add Page", which opens up a new Canvas editing screen at canvas/editor/canvas_page/1
Click the icon in the left rail for "Headless frontends"
Click "Add frontend".
- For the Frontend URL field, use the following (no trailing slash, no query, and no fragment):

http://localhost:3000

If everything went as expected, the "Frontends" section will show http://localhost:3000 as being "Ready".

Change the default OS browser to Chrome; the Canvas CLI login command will open a browser and it needs to be Chrome (or Chromium-based).

Cd into the headless folder in the directory of the site.
- In this example, the site and the folder are both named headless.
Login with Canvas CLI using the OAuth consumer client id from the step above (code-components).

cd ~/Sites/headless/headless
npx canvas login --client-id code-components

That will open a browser window to a link on the Drupal site, which redirects you to a localhost page that shows you a success/failure message. If everything went well, you can now use Canvas CLI (npx canvas) to push and pull components between Drupal and Next. Since the scaffolding created some new components, use the push command to get them to the Drupal site:

npx canvas push

Now, you can create a page in Drupal and the components from the Next.js app should appear there. Build out a page, change some css in the code if you want (headless/app/globals.css for example, maybe change the body background color), and watch things change in the edit screen in realtime. Then, save your changes in Canvas, just like when you are in regular non-headless mode, and view your site at http://localhost:3000.

Notes

The example above doesn't use Astro, but if you do use Astro:

npx astro telemetry disable

brooke Tue, 6 Oct 2026 - 18:06

Tags

Drupal

Bash scripts for Drupal, DDEV, and Tome

brooke — Wed, 17 Sep 2025 20:46:57 +0000

Bash scripts for Drupal, DDEV, and Tome

This website is made with Drupal. Local development is done with DDEV configured to use Orbstack for container management. The Tome Drupal module exports the dynamic site to a static site. Python is used to preview the site locally. Public hosting is provided free by Github.

Here are some custom bash aliases and functions I use to make common local tasks easy. Concurrently is used to run two processes in one terminal session.

alias brookemahoneycomCd='cd ~/Sites/brookemahoneycom'
brookemahoneycomLaunch () {
  # Starts Orbstack if it isn't running.
  orb
  brookemahoneycomCd
  cd drupal
  ddev launch
}

brookemahoneycomPreview () {
  brookemahoneycomCd
  cd docs
  concurrently 'python -m http.server' 'open "http://localhost:8000"'
}

brookemahoneycomBuild() {
  # Starts Orbstack if it isn't running.
  orb
  # Changes to the drupal directory.
  cd ~/Sites/brookemahoneycom/drupal
  # Clears caches.
  ddev drush cr
  # Exports the site with Tome.
  ddev drush tome:static --uri=https://brookemahoney.com
  # Removes old docs directory.
  rm -rf ~/Sites/brookemahoneycom/docs
  # Copies the Tome build directory to docs for Github hosting.
  cp -R ~/Sites/brookemahoneycom/drupal/html ~/Sites/brookemahoneycom/docs
  # Copies over static files, such as CNAME for Github hosting.
  cp -R ~/projects/brookemahoneycom/sync/ ~/Sites/brookemahoneycom/docs
}

All the code for the Drupal install is in this site's Github repo.

brooke Wed, 17 Sep 2025 - 13:46

Tags

Drupal