Why a Larger Local Model Still Needs Drupal Development Regression Checks

A bigger local coding model writes more confident Drupal code, not more correct Drupal code — regression tests are what tells the difference.

A bigger local coding model writes more confident Drupal code, not more correct Drupal code — regression tests are what tells the difference.

Drupal's AI migration modules draft field mappings, but core's Migrate API — not AI — still moves the actual content.

A practical checklist for testing AI-generated Drupal configuration suggestions against your real site before they reach production.

A tier-by-tier look at where Drupal's AI modules actually store API keys, and why coding assistants leak them more than developers expect.

A practical look at how Drupal's service container works and where a locally run AI model genuinely helps—and where it misleads.

A local-first way to pair Drupal's deterministic module scans with Ollama-run AI commentary, and why neither replaces checking branch-specific patch levels.

A branded 503 page means Drupal chose to pause; a blank browser error means the server itself stopped answering.

A quick guide to telling a stale Drupal page apart from a stale DNS lookup, and clearing the right one first.

A 403 on uploaded Drupal files traces to either file-system permissions or a mismatch between the configured and actual storage URL — not the same fix.

Composer audit should run on every CI build plus a recurring cron job, because advisory data changes even when a Drupal site's code doesn't.