Fenwick Trust
A Drupal 11 site on the Olivero theme. Ask for a change to a theme file.
Drupal changes without the config drift.
We have run 11 Drupal client projects through the Orchestrator. Entities, views, config sync, module and PHP upgrades: each change is planned, approved and proved.
The Drupal jobs agencies hand us.
The work that fills a Drupal agency's week, and the work that is hard to staff.
- Entities and content types
- Content types, fields and displays, set up so editors can use them.
- Views and listings
- Views, filters and listings, tested with the content a visitor sees.
- Config sync
- Config exported, reviewed and imported, so staging and live stay in step.
- Module and PHP upgrades
- Drupal 9 to 10 upgrades, module updates and PHP compatibility checks.
- Themes and builder pages
- Base theme overrides and pages built in a page builder such as DXPR Builder.
- Hosting and deploys
- Access rules, file permissions and deploys from git, handled alongside the code.
The Orchestrator on Drupal.
11 client projects have run through our own Orchestrator. This is how a Drupal job goes.
One agent per site, with its own memory.
Each site's project agent remembers the modules, the theme, the config and every change made so far. A new job starts from that history, not from a blank page.
- Entities, views and config sync
- Module updates and PHP upgrades
- Limited to that one project's files, enforced in code
Drupal client board
- Acme client · Events viewWorking
- Larch client · Module updateReview
- Northgate client · Config exportComplete
- Hale client · New content typePlanning
Plans that name what they will touch.
Anything that changes a site starts as a short numbered plan. It says which config and files will change and how to put them back. Nothing moves before you approve it.
- Config export and import planned, not guessed
- A written way back on every plan
- Approve from the board, the chat or your phone
Larch client · Module update
Project agent · Drupal
PLAN
- Export the current config and keep a copy.
- Update the module and check it on a copy.
- Export again and compare it with live.
RISK: medium · config will change
UNDO: one git commit
Nothing changes until you approve.Approve plan
Proof, and rules learned the hard way.
Every job ends with a written validation: what changed, what was tested and what is still open. The Drupal playbook carries what went wrong on earlier sites, so the same mistake is not made twice.
- Checks listed with pass or fail
- Screenshots on desktop and phone
- Proof that an upgrade landed, not just that the tool said so
Validation
Complete- Events view shows the new field
- Config import reports no differences
- A signed-out visitor sees the page
Evidence: 3 screenshots · 3 of 3 checks passed
Webgentic for sites on Drupal.
Webgentic for sites adds a request bar to one Drupal site. On Drupal it changes files only: theme templates, styles and scripts. Content kept in Drupal's database is out of reach.
| On a Drupal site | Today | In practice |
|---|---|---|
| Site files | Yes | The files that make up your site: theme templates, styles and scripts. |
| Restoring files | Yes | Any earlier version of a file can be put back in one click. |
| Database content | Not built | Changing content kept in the database. |
| Database settings | Not built | Changing settings kept in the database. |
| Restoring beyond files | Not built | Restore covers files only. |
A plan comes first and you see each change appear as it is made. Stop cancels the job on our server. Every change is saved with a plain-English note, and any earlier version of a file can be put back in one click.
No approval step in Webgentic for sites.
The change is made as you watch, and every earlier version is kept. Plan approval belongs to the Orchestrator. See how Webgentic for sites works
An Orchestrator job, start to finish.
Every image on a Drupal site returns an error.
Brief
Hale client reports that every image under the site's files folder shows an error.
Plan
The agent plans a read-only check first: read the access rules from the top of the site downwards, and compare the site's settings with healthy sites on the same setup.
Approve
You read the plan, its risk and its way back, then approve it.
Deliver
The config sync directory had been set to the site's own folder, so Drupal wrote a deny-all rule into it. Of 8 sites compared, 6 had the standard value and the 2 broken ones had a hand-written path. The agent fixed the setting, not the rule file, because Drupal rewrites that file.
Prove
The validation lists what changed and what was checked, with screenshots of the images loading again.
What the Drupal playbook covers.
Each job loads the playbook topics that match it, so past mistakes are not repeated. The playbook is reviewed every night, so what one job learns reaches the next.
- Checking a module for PHP 8 traps before it breaks the site
- Upgrading Drupal 9 to 10, with a PHP compatibility checklist
- DXPR Builder pages, and checking they survive a save
- The config sync directory and the access rule Drupal writes for it
- Deprecation sweeps after an upgrade
- Overriding a shared base theme safely
- Shipping a database content change through git, with a dry run first
- Checking what a search crawler sees
- Proving that a core upgrade actually landed
Try it on a Drupal demo site.
All 13 demo sites reset every night at 03:30. They are invented businesses with no real customer data.
Apex Polymers
A second Drupal 11 site on the Olivero theme. Try a change to a file, then restore it.
Drupal questions agencies ask first
Can Webgentic for sites change Drupal content?
Not today. On Drupal it works on the site's files only, so it cannot change content or settings kept in the database. Restore covers files only.
Can you work with our config sync workflow?
Yes. Config export and import is a standard part of a Drupal job, and our playbook covers the traps around the sync directory.
Which Drupal versions do you work on?
Our playbook covers upgrading Drupal 9 to 10, and our demo sites run Drupal 11.
Does anything change on a live site without my approval?
The Orchestrator plans first, and nothing changes until you approve. Webgentic for sites has no approval step: each change appears as it is made, Stop cancels the job on our server, and earlier versions of the files can be put back in one click.
Can the Orchestrator change database content?
Yes, and it is planned like any other change. Our playbook ships a database content change as a guarded script that does a dry run first.
Something else on your mind?
Ask us directly and a developer will reply.
Ask a question
Bring us your Drupal sites.
Join the waiting list. When your place comes up, we will show you the Orchestrator running on one of your real jobs in the first call.