nexya translate

Folders to sort the media library, and thumbnail regeneration in the background, in batches, carrying on when you close the tab — and telling you when it is finished

The panel that gathers every nexya plugin. A module you switch on, a module you switch off — and nothing running on the WordPress site while it is off

The WordPress admin as the client sees it: menus cut down to what is useful, a tidy admin bar, and the dashboard in your own colours right through to the login page

Duplicate, reorder, add — three gestures placed on the WordPress content lists, so you stop doing them by hand

WordPress capabilities filed under the plugin that creates them, readable at last. And the menu cut down to what the person in front of it actually has to do

Who changed what on the WordPress site, and when. Down to the ACF fields, with the value before and the value after — and the button to put it back

Cookie consent, and the blocking that goes with it. Nothing runs before the visitor agrees — not the scripts, not the embedded videos, not the remote fonts

What the WordPress site says about itself to search engines — and what it shows when someone pastes its address somewhere. Written once, applied everywhere, checked before publishing

The WordPress site’s emails actually go out — and you know which ones did not, with the exact reason given by the SMTP server

The 404 errors picked up as visits happen, and the 301 redirect suggested before anyone goes looking for it. With the number of hits, so you know which ones count

The HTTP security headers set without breaking the site, the watch on vulnerabilities in the WordPress plugins installed, and the eye on what moves in the files

The operations you carry out on the WordPress site rather than in it: closing it for an intervention, slimming its database down, taking a copy

Each page kept as a file and handed to the next visitor before WordPress loads — then thrown away as soon as something changes it.