119 posts tagged with "WordPress"

I built this proof-of-concept to explore how a codex-style agent can assist with routine Drupal maintenance tasks -- dependency updates, configuration checks, and basic cleanup. The kind of work that is constant, easy to overlook, and expensive to do manually at scale.

The original POC had three actions -- create a node, read a node, list nodes. Enough to prove the concept, not enough to be useful. A real content operations agent needs to modify, delete, query users, browse taxonomies, and handle media. It also needs to survive flaky networks without crashing.

I built drupal-content-audit as a lightweight way to inspect and report on content in a Drupal site. It focuses on surfacing what content exists and how it is distributed, giving a quick snapshot that is easy to share with stakeholders.

I built a DDEV add-on that runs Playwright checks against local MCP endpoints using internal DDEV DNS names like web. This solves flaky localhost-based testing and gives one command for repeatable MCP smoke tests.

I built drupal-ai-module-generator-deepseek-mcp to take the repetitive, error-prone parts of module setup -- info files, boilerplate, and consistent structure -- and make them fast and repeatable. It fits naturally into agent-driven workflows where you want consistent Drupal modules without losing time to manual setup.

I built drupal-ai-views-agent because Views is powerful but repetitive. Filters, relationships, display modes, and fields add up quickly. Describing what you want in plain language and getting a valid Views config back saves the clicking and lets teams focus on validating data requirements instead of wrestling with UI details.

The first version of drupal-claude-agent-sdk-runtime gave you session management and result objects, but tools were mocked. You could simulate agent workflows inside Drupal, but you could not actually execute anything. That ceiling had to go.

DDEV 1.25.0 ships experimental support for Podman and Docker rootless. This opens up corporate-friendly runtimes, but introduces trade-offs that the announcement does not emphasize enough.

I built a CLI that audits your global_config.yaml so you know before you flip the switch.

Centarro argues you can deliver a B2B portal experience on top of a standard Drupal Commerce store without spinning up a separate platform or domain. I built a demo module to test if that claim holds up in practice.

Drupal CMS recipes are the most practical building block for AI-driven site assembly: they translate a plan into installable modules and configuration with one apply step. I built a small recipe package and a PHP blueprint helper to test how well this works in practice.

Enterprise agentic systems scale when they feel less like a demo and more like a governed service. That means routing, guardrails, and budgets are first-class citizens from day one, not afterthoughts bolted on before a compliance review.

I built a lightweight playbook that turns Netomi-style enterprise lessons into code you can run and test.

AI in Drupal CMS 2.0 gets real value when the first week produces repeatable output, not one-off experiments. I wanted a simple kit that editors can plug into their workflow on day one: clear prompts, consistent tone, and fast QA.

Most teams start with a blank prompt box. That kills adoption before it starts.

I can now treat a WordPress site like an MCP tool server -- abilities become callable tools, which turns admin tasks into agent-friendly workflows.

I sketched a traffic forensics workflow around Pantheon's new "top IPs / user agents / paths" metrics and turned it into a small, shippable reference so teams can spot noisy traffic fast and stop guessing where spikes come from.

The Hook When one Drupal module depends on another, I want to iterate across both without publishing interim versions or wiring up a private Composer repo. Path repositories give me that speed while keeping dependency boundaries honest.

I shipped a Drupal migrate mapping validator utility that catches broken mappings before they land in prod.

I outlined a practical stack for multilingual HTML email in Drupal using Mail Composer plus a dedicated HTML mailer, and packaged it as a small demo repo you can reference.

I distilled WordPress 6.9.1 RC1 into a compatibility checklist for plugins and themes before the maintenance release landed. I also packaged the checklist and notes into a small repo so teams can clone it and wire it into their own QA flow.

I turned my Drupal Canvas Full HTML notes into a clear rollout guide and backed it with a runnable repo so teams can ship rich editing without breaking permissions.