> **SETTLED DECISION (2026-07-15): target Drupal version = 11.4.** > The core version is now conclusive — **Drupal 11.4** (not 10.x / not 12 yet). > This resolves the D10/D11 drift across the migration docs and MVP issues. > To be recorded canonically as ADR `0002-target-drupal-version` (see #3578796). ## Context This project vendors in a curated subset of an internal process framework ("playbook") as plain tracked files under a `playbook/` directory (path/structure up to you, mirroring the source's layout for whatever you bring across). It's copied in **once** — no submodule, no subtree, no ongoing dependency on the source repo, and **no external organization name** referenced anywhere in this project (issues, code, docs, commit messages). The word "playbook" itself is fine to keep. **Source:** the playbook lives at **`~/Projects/playbook`** (a local working copy) — vendor from there. > **Do #3578765 (the `.agents/skills/` convention) first.** Not a hard dependency, but the > skills convention gives the reference for routing content during the triage below: some > workflow/process items may belong as **shipped `.agents/skills/<name>/SKILL.md` skills** > (#3578765) rather than dev-only `playbook/` files. Establish that pattern first so this > copy-in sends each item to the right home instead of dumping everything into `playbook/`. ## Step 1 — Research current Drupal (11.4) to scope relevance **This module is now a Drupal 11 scaffold** — `1.x` carries `groupsdrupalorg.info.yml` with `core_version_requirement: ^11` (bootstrapped in #3578754, merged). *(The legacy D6 `groupsorg.*` files live only on the old `master` / `6.x-1.x` / `7.x-1.x` branches — not on `1.x`.)* So the conventions we bring in should reflect **modern Drupal 11**, which is what future work targets. Before touching the playbook, research: - Drupal 11.4 (current stable) and what's changed architecturally since D6/D7 — Composer-based, Symfony components, Twig, plugin/attribute-based systems, configuration management, etc. - Drupal core's **HTMX** integration: HTMX shipped as a new core subsystem in Drupal 11.3 (intended to replace the jQuery-based Ajax API), including a PHP factory class for generating HTMX attributes. - Other recent core-adopted frontend/tooling shifts (Single Directory Components, etc.) that affect which `frameworks/` / `languages/` playbook docs are actually relevant. Starting points (verify and expand, don't treat as exhaustive): - https://www.drupal.org/blog/drupal-11-3-0 - https://events.drupal.org/chicago2026/session/htmx-new-toolset-drupal-core - https://www.drupal.org/project/htmx - https://www.drupal.org/about/core ## Step 2 — Review the source playbook and decide scope Go through **every** top-level folder of the source (`~/Projects/playbook`) and, file by file, decide in/out based on relevance to (a) this being a **Drupal 11 module** project and (b) the modern stack from Step 1. The actual top-level folders (verified against the source, 2026-07-06) are: ``` admin_tools agent architecture architecture-audit developer_setup docs frameworks ide infrastructure languages migration patterns pipelines projects security snippets testing themes workflow ``` Rough expectations — **confirm each yourself**, don't assume: - **Likely in:** `workflow/`, plus the Drupal-relevant parts of `architecture/`, `testing/`, `security/`, `patterns/`, `developer_setup/`. - **Likely out:** most of `frameworks/` (node, fastify, htmx-as-a-standalone-JS-lib, mikro-orm, docker, better-auth, grafana), `infrastructure/` (Coolify runbooks), `themes/`, `ide/`, `admin_tools/`, `projects/`. - **⚠️ Route these two carefully — they overlap already-shipped work:** - **`agent/`** — AI-agent material. Some likely belongs as **shipped `.agents/skills/<name>/SKILL.md` skills** (#3578765 — the convention now exists) rather than dev-only `playbook/` files. Triage per the sequencing note above. - **`pipelines/`** — overlaps the existing **AI Pipeline** docs page (`src/content/docs/ai-pipeline.mdoc`). Decide whether to vendor, link, or fold into that page rather than duplicating. ## Step 3 — Copy in, same folder structure For everything marked "in," copy the files into this repo preserving the source's relative folder structure (under `playbook/`, except anything routed to `.agents/skills/` per Step 2). **Strip any internal-organization branding** from the copied content itself. ## Step 4 — CI: exclude `playbook/` from cspell `playbook/` is a large body of process prose full of jargon, and the drupalci **cspell** job scans the whole repo — so **add `playbook/` to `_CSPELL_IGNORE_PATHS` in `.gitlab-ci.yml`** (mirror how `docs/` is already handled there) or the first push fails CI on the vendored content's terminology. (Content routed to `.agents/skills/` is small and still gets spell-checked, which is fine.) ## Deliverable In this issue (or the resulting MR description), post an explicit list: what came across (path by path), what was routed to `.agents/skills/` vs `playbook/`, and what was deliberately left out — with a one-line reason for each exclusion. ## Packaging The `playbook/` directory is **development-only** — exclude it from the packaged release. Add `/playbook export-ignore` to `.gitattributes` (which already carries the dev-only paths from #3578754), so it stays in the repo and clones but never ships in the drupal.org package. *(Anything routed to `.agents/skills/` instead **ships** — see #3578765.)* Verify with `git archive HEAD | tar -t`: `playbook/` absent, `.agents/skills/` present. _Refined 2026-07-06: fixed the stale "D6-only" premise (module is a D11 scaffold now), refreshed the folder list from the live source (19 folders, incl. `agent/`+`pipelines/`), added the cspell-ignore step, and named the source location._