>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3588808. --> Reported by: [ajv009](https://www.drupal.org/user/3653917) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Currently the migrate-site skill has no phase for setting up the content model on the target Acquia Source instance. Phase 7 (content composition) assumes content types already exist. When a site has dynamic content (events, blog posts, news items, team members), the required Drupal content type bundles and taxonomy vocabularies must exist before content can be composed. Without a dedicated phase, implementers must manually create content types via the Drupal admin UI before running Phase 7 &mdash; an undocumented prerequisite that causes failures when skipped.</p> <p>Four new Acquia Source / canvas_oauth scopes &mdash; <code>content_type:administer</code>, <code>content_type:administer_fields</code>, <code>taxonomy:administer</code>, <code>taxonomy:administer_fields</code> &mdash; would in principle enable a programmatic Phase 1.5 that the skill executes automatically. This also enables 8-02 (Canvas content templates): page templates are typically tied to content types; if the content type doesn't exist when Phase 4.5 runs, template creation fails.</p> <p><strong>Empirical status (probed 2026-05-01): currently BLOCKED on Acquia endpoint shipping.</strong> All four scopes mint tokens successfully (HTTP 200 on <code>POST /oauth/token</code>), but no API endpoints exist for content type or taxonomy vocabulary management on the test Acquia Source release:</p> <ul> <li><code>content_type:administer</code>: <code>/api/node_type</code>, <code>/api/node_type/node_type</code>, <code>/api/content_type</code>, <code>/api/content_type/content_type</code>, <code>/api/node-type</code> &mdash; all 404.</li> <li><code>taxonomy:administer</code> (vocabularies): <code>/api/taxonomy_vocabulary</code>, <code>/api/taxonomy_vocabulary/taxonomy_vocabulary</code>, <code>/api/vocabulary</code> &mdash; all 404.</li> <li>Partial: taxonomy <em>terms</em> work at <code>/api/taxonomy/categories</code> and <code>/api/taxonomy/tags</code> (specific exposed bundles), but vocabulary-level management has no endpoint.</li> </ul> <p>Phase 1.5 via API is not viable on the current instance. Browser automation through the Drupal admin UI remains required for all content model configuration. The issue stays open; once Acquia ships endpoints, the API path becomes the primary implementation. 1-08 (verify-scopes preflight) detects this state automatically and writes <code>scope-availability.json</code> entries that gate this phase.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Run migrate-site against a source site with dynamic content types where the target Drupal instance does not have those bundles configured.</li> <li>Observe Phase 7 failure: content composer attempts to create nodes of bundle <code>event</code>, server returns 422 (bundle does not exist).</li> <li>Observe no recovery path: the skill has no phase to bootstrap the missing bundle; user must manually create it via admin UI.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p><strong>Step 1 &mdash; Verify endpoint surface for all four scopes.</strong> Probe candidates (current instance returns 404; re-probe required when Acquia announces endpoint availability):</p> <pre>GET /jsonapi/node_type/node_type (content_type:administer) GET /jsonapi/field_config/field_config (content_type:administer_fields) GET /jsonapi/taxonomy_vocabulary/taxonomy_vocabulary (taxonomy:administer)</pre><p>Document confirmed endpoints and response shapes in <code>gotchas.md</code>. If any scope returns 403/405, flag as unavailable and route that capability through browser-fallback.</p> <p><strong>Step 2 &mdash; Extend Phase 1 site-analyzer discovery output.</strong> Detect dynamic content types from URL patterns and repeated card structures. Output to <code>plan.md</code>:</p> <pre>content_types: - name: event source_url_pattern: /events/* detected_fields: [title, date, image, body, location] taxonomy_refs: [event_category] - name: blog_post source_url_pattern: /blog/* detected_fields: [title, date, author, image, body, tags] taxonomy_refs: [blog_tag]</pre><p><strong>Step 3 &mdash; Add Phase 1.5 to <code>migrate-site/SKILL.md</code></strong> between Phase 1 (site-analyzer) and Phase 2 (component-builder):</p> <pre>PHASE 1.5 &mdash; Content model setup (conditional: skip if plan.md has no content_type entries) Read scope-availability.json (from 1-08 preflight). For each content_type detected in Phase 1: 1. Verify content type exists on target: GET /jsonapi/node_type/node_type/&lt;bundle&gt; 2. If not found: - if content_type:administer endpoint is "confirmed" &rarr; create via API - if "issuance-only" or "denied" &rarr; use browser session (admin UI) 3. For each required field: create field definition via content_type:administer_fields 4. For each required taxonomy vocabulary: create via taxonomy:administer 5. Log workflow/phase1.5-content-model-checklist.json</pre><p><strong>Step 4 &mdash; Write <code>scripts/setup-content-model.mjs</code></strong> (reads <code>plan.json</code> content_types &rarr; creates Drupal content types + fields + taxonomies). Script structure:</p> <pre>for (const ct of plan.content_types) { await ensureContentType(token, ct.name, ct.label); for (const vocab of ct.taxonomy_refs) { await ensureTaxonomyVocabulary(taxToken, vocab); } for (const field of ct.detected_fields) { await ensureField(fieldToken, 'node', ct.name, field); } await appendChecklist('workflow/phase1.5-content-model-checklist.json', { ct: ct.name, status: 'created' }); }</pre><p><strong>Step 5 &mdash; Phase 7 precondition.</strong> Phase 7 (content composition) verifies <code>workflow/phase1.5-content-model-checklist.json</code> exists and all content_types show <code>status: created</code> or <code>verified</code>. If Phase 1.5 was skipped (no content types in plan.md), proceed. If Phase 1.5 failed, do not proceed to Phase 7.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Re-probe content_type and taxonomy endpoints on the latest Acquia Source release; update <code>SCOPE-PROBE-FINDINGS</code> when endpoints ship.</li> <li>Extend <code>site-analyzer.md</code> with content-type detection and <code>content_types</code> array in <code>plan.md</code>.</li> <li>Add Phase 1.5 section to <code>SKILL.md</code> with conditional skip logic and scope-availability gating.</li> <li>Write <code>scripts/setup-content-model.mjs</code>.</li> <li>Add Phase 7 precondition check referencing the Phase 1.5 checklist.</li> <li>Until API endpoints ship, document the browser-fallback path through Drupal admin UI as the active implementation.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>None directly. Indirect: when API endpoints ship, removes the manual admin-UI prerequisite for Phase 7 on sites with new content types.</p> <h3 id="summary-api-changes">API changes</h3> <p>The phase consumes (does not introduce):</p> <ul> <li><code>POST/PATCH /jsonapi/node_type/node_type</code> with <code>content_type:administer</code> token (currently 404 on Acquia Source).</li> <li><code>POST /jsonapi/field_config/field_config</code> with <code>content_type:administer_fields</code> token (currently 404).</li> <li><code>POST /jsonapi/taxonomy_vocabulary/taxonomy_vocabulary</code> with <code>taxonomy:administer</code> token (currently 404).</li> </ul> <h3 id="summary-data-model-changes">Data model changes</h3> <p>New <code>plan.md</code> field <code>content_types[]</code>. New artifact <code>docs/migration/workflow/phase1.5-content-model-checklist.json</code>.</p> <h3 id="summary-internal-references">Internal references</h3> <ul> <li>Source markdown: <code>RESEARCH-2026-04-28/99-final/ISSUES/Sprint-8-Patterns-To-Encode/07-NEW-9-content-model-setup-phase.md</code> (id: NEW-9)</li> <li>Scope reference: <code>RESEARCH-2026-04-28/99-final/SCOPE-REFERENCE-2026-05-01.md</code> &sect; "CRITICAL impact &mdash; content_type:administer, taxonomy:administer"</li> <li>Empirical probe results: <code>RESEARCH-2026-04-28/99-final/SCOPE-PROBE-FINDINGS-2026-05-01.md</code> &sect; 7 (no endpoints shipped for site_settings, content_type, page_template, taxonomy_vocabulary, media_type)</li> <li>Q4 post-mortem (origin of the gap): <code>RESEARCH-2026-04-28/03-efi-ed-source/Q4-records-8651-to-11536/post-mortem-learnings.md</code></li> <li>Preflight dependency: <code>Sprint-1-Foundations/08-NEW-11-verify-scopes-preflight.md</code> (issue 1-08)</li> <li>Downstream consumer: <code>Sprint-8-Patterns-To-Encode/02-NEW-2-canvas-content-templates-phase.md</code> (issue 8-02)</li> </ul> <h3 id="summary-open-questions">Open questions</h3> <ul> <li>Do the Acquia Source-specific scope endpoints follow Drupal's standard JSON:API convention for entity type management, or is there a Canvas-specific API layer?</li> <li>Creating content type fields via JSON:API requires both field storage config and field instance config &mdash; two separate POST operations. Does <code>content_type:administer_fields</code> cover both?</li> <li>Risk of field naming conflicts if the target Drupal instance already has shared field storage with the same name but different settings (e.g. <code>field_image</code> globally).</li> <li>For taxonomy: does <code>taxonomy:administer</code> allow term creation as well as vocabulary creation, or is term creation covered by a separate scope?</li> <li>Does the Drupal #3584714 install-order gotcha (for <code>canvas:media:image:create</code>) apply to these scopes? If yes, preflight must distinguish "scope not registered &mdash; run <code>drush updb</code>" from "scope registered, endpoint missing".</li> </ul>