Chapter 8: Running your site

What this chapter covers

Beyond the writing, somebody has to look after a site: its health, its settings, its plugins and themes, its look and its updates. If that is you, this chapter is for you. Most of it needs the Administrator role, and the Workbench only offers what your role can use.

You will read your site’s overview and health, change its settings, look after plugins, themes and fonts, change the site’s look and its templates, and see what needs updating. You will also meet the tools for the jobs WordPress only does in wp-admin.

By the end you will know how your site is, and how to keep it that way. Everything that changes the site shows you what will change, and asks first.

QUILL asks the site first

Sites differ. One runs the newest WordPress with a block theme, another an older version with a classic theme and a security plugin. QUILL reads what each site offers, once a session, before it offers anything. A command your site does not have, or your role cannot use, says why in one sentence, such as “Community Radio does not offer this. It may be turned off, or the site may need a newer WordPress.” Nothing is sent.

The site at a glance

Each site’s Overview in the Workbench (Ctrl+2) is wp-admin’s Dashboard, in words. It has three places:

Site Health

Tools > WordPress > Site Health Check opens the Workbench at the site’s Site Health. It lists what the site says about its own health, critical things first: the WordPress version, HTTPS, the time zone, readable addresses, and every Site Health test the site runs, each in one line. **Needs My Attention

Site Health** gathers the problems from every site, worst first.

If the authorization header test fails, the row explains that application passwords cannot work on that site until the host fixes it. That one line has saved many people an afternoon.

WordPress gives each problem a label and not much else. In the Workbench, Enter on a Site Health row is Explain: what the problem means for the people who visit your site, what usually causes it, and the steps to fix it, followed by WordPress’s own description. The row’s context menu has three more:

The same commands work on Needs My Attention > Broken Links. There, Fix… asks for the right address, shows how many times the post holds the old one, and changes it after you say yes; Ctrl+Z puts the old link back. Open in Editor opens the post that holds the link, when you would rather change the words around it too.

Under Site Health:

Search and Upkeep, in each site’s branch, covers whether search engines may list the site, its sitemap, scheduled posts that missed their time, the site’s certificate, and who is editing what. Every row ends with where QUILL’s answer came from.

Only scheduled posts and pages can be checked for a missed time from here. WordPress does not share its other scheduled tasks with QUILL, and the WP Crontrol plugin, which lists them all with any that are late, has no way in from outside either. The Other scheduled tasks row says so. Where WP Crontrol is active on the site, Open Where It Is Checked on that row opens its Tools > Cron Events screen in your browser.

Site settings

Tools > WordPress > Site Settings… opens the Workbench at the site’s Settings: the title, tagline, language, time zone, date format, front page, posts page, site icon and more, each on its own row.

To change one, arrow to it and press Alt+Enter. Change the value and press OK. QUILL reads the setting again first, and checks afterwards that the site kept it.

Each row says what the setting does on your site, with your own example: your posts page by name, what a date looks like in your date format. Below the settings you can change are the ones WordPress keeps to wp-admin, still explained with your own site:

Open in Dashboard, on any of these, opens the wp-admin screen that changes it.

The site language matters more than it looks. It decides which voice a visitor’s screen reader uses for the whole site. Language Pack Status…, on a setting’s context menu, says each site’s language and whether WordPress.org has its translation for that WordPress version. It asks WordPress.org, so QUILL asks you first, naming the address and what is sent.

Plugins

Tools > WordPress > Manage > Plugins… opens the Workbench at the site’s Plugins: every plugin, whether it is active, and its version.

What WordPress cannot do from outside. WordPress lets apps install, activate, deactivate and delete plugins, but not update them, and there is no way to put back an earlier version. If a plugin causes trouble, deactivate or delete it. An earlier version only comes back from the site’s own backup, or an upload in wp-admin.

Themes and fonts

Tools > WordPress > Manage > Themes… opens Appearance > Themes: the installed themes and what the active one supports. WordPress does not let apps switch or install themes, so Activate… and Open in Dashboard take you to the right wp-admin screen. Find a Theme on WordPress.org… searches the theme directory, after asking.

Tools > WordPress > Manage > Fonts… opens Appearance > Fonts. Each font is described in words, such as “serif, suits body text”.

Updates

Needs My Attention > Updates lists, for every site, WordPress itself with its version, every plugin and theme with the version installed, and, where the site runs it, Site Health’s automatic updates test.

WordPress does not tell apps whether a newer version is waiting, so the Update column says “Not reported over REST” unless the site itself says otherwise. QUILL never guesses. Enter on any row opens that site’s Dashboard > Updates in your browser, where updates are run. The Workbench never updates anything itself.

Check for Updates on WordPress.org…, on a plugin, theme or Updates row, asks WordPress.org which versions are current, after you agree. For a plugin with an update waiting, it also reads the plugin’s changelog for the versions you would skip. The row then says how many versions those are, and says plainly when the changelog mentions security fixes, breaking changes or a database update. A database update is the one to back up for, because turning the plugin off afterwards does not undo it. Read in Full shows what the changelog says for each of those versions, as plain text.

To hear about updates as they come, turn on the Watch for them, below.

The site’s look

The look of a block theme lives in Appearance in the Workbench. You need to be an Administrator for all of it, and QUILL tells you before any window opens if you are not.

Global Styles lists the theme’s colours and font sizes. Each colour says how it contrasts with the page text and background. Change… previews a new value, with its contrast, and Ctrl+Z puts it back.

Templates and Template Parts list the theme’s templates, such as Single Posts, and its parts, such as the header. On one:

Additional CSS has one row. On a block theme, Edit Additional CSS… opens the CSS as text, warns that it changes every page, and reads the change back before saving. CSS with tags in it, or braces that do not pair up, is refused before anything is sent. A classic theme keeps its CSS in the Customizer, so its row opens that in your browser.

Patterns lists the synced patterns, the blocks you reuse and change in one place. Tools > WordPress > Manage > Synced Patterns… opens it.

Widgets and Sidebars lists a classic theme’s widget areas, such as the sidebar or the footer. Tools > WordPress > Manage > Widgets… opens it. On an area:

Each one is previewed, Ctrl+Z undoes it, and a widget somebody changed in the meantime is never overwritten.

The look, from the editor

These are in Tools > WordPress > Design and Manage, for sites with a block theme:

The shape of the site

Content Model, in each site’s branch, lists every kind of content, every way of grouping it, and every group of fields the site has, with who added each one. Field groups include the registered fields on each kind of content, Advanced Custom Fields and Meta Box fields, every pod Pods keeps and every CMB2 box.

WordPress does not say which plugin added a type, so QUILL names one only when the site shows it: QUILL Site Types keeps it, a field plugin lists it, or it lives under a plugin’s own part of the site’s REST API. Otherwise it says unknown, and the row’s detail says why. When Custom Post Type UI is active, the detail says that plugin may be the one, because it keeps its types in wp-admin where QUILL cannot see them.

These are defined in a plugin’s or theme’s code, so they are read only here. Their items are still edited in their own lists.

When the site has QUILL Site Types, Copy to QUILL Site Types… on the context menu copies a post type, taxonomy or field group into it under the same name, after a preview. This is how you move a definition away from another plugin. Nothing is deleted from the original. QUILL Site Types will not take a post type or taxonomy that something else still registers, so turn it off in its plugin first; its posts stay. A field group can be copied straight away, and values already saved under its field names show up as custom fields. The preview names anything that will not come across.

Jobs only wp-admin does

Some of WordPress has no way in from outside: updates, switching themes, privacy requests, most of Site Health’s Info tab. QUILL says so on the row where it matters, before you act, and takes you to the right screen.

AI Abilities and Ask the Site

WordPress 6.9 lets a site offer actions to AI, called abilities, such as “list upcoming events” or “create a draft”.

Asking about what the site says. Any site can be asked, abilities or not. When no ability is turned on, or the site offers none, Ask the Site answers from the site’s own writing instead: “Which pages mention our old address?” or “What did we post about the fundraiser?”

  1. Type your question.
  2. Choose what it may read: published posts and pages only, or drafts, pending, scheduled and private items as well. Those are not public, so include them only if the AI you chose may see them.
  3. QUILL reads the most recently changed posts and pages, then tells you how many it will send, whether any are not public, and which AI gets them. Nothing is sent until you choose Send.

The answer names the pages it came from, and ends by saying how many posts and pages it read. A very large site is cut to its newest writing, and the AI is told the answer may be incomplete.

Watches

Watches tell you when something happens on your sites while QUILL is open. They are all off until you turn them on.

  1. In the Workbench, choose Tools > Workbench Options… (Ctrl+Shift+O).
  2. Check the Watches you want, and press OK.

You can watch for new comments waiting, new form responses, plugin updates available, scheduled posts going live, a site not answering and answering again, items with a reviewer leaving the queue, Site Health status changes, and form spam questions, once a week. Site Health stays silent for an account that is not an administrator.

A few more are there for the things that are easy to miss:

Each site is checked no more often than every fifteen minutes. The first check is silent, so you only hear about what changes after it. Go > Watches (Ctrl+5) says when the last round ran and whether each site is answering, then lists what Watches have said, newest first, so a sentence you missed is still there to read.

When a round finds several things, you hear them as one announcement that starts with how many there are. If a site refuses one Watch’s question (a plugin list an editor may not read, say), that Watch tells you once and skips the site; every other Watch carries on there, and you hear when it reads the site again.

The REST Console

For anything a site offers that has no command of its own, Tools > REST Console… (Ctrl+Shift+T) in the Workbench sends a request to any route the site has. It completes route names as you type, the Accepts box lists what a request takes, and What It Returns says what comes back. A change is previewed first, with any missing or unknown arguments named, and goes in Change History.

Save Request keeps a request you use often. Tools > Saved Requests lists them, numbered 1 to 9, and Tools > Run a Saved Request… (Ctrl+Alt+Q) opens the console with one. Tools > Forget a Saved Request… (Ctrl+Alt+Shift+F) removes one.

Before a big change

Take a snapshot first. Site > Take a Snapshot… (Ctrl+Alt+S) saves the site’s content on this computer, and Site > Put Back from a Snapshot… (Ctrl+Alt+Shift+S) sets it back. Chapter 9 shows how.

Signing out of a site

Tools > WordPress > Manage > Sign Out This Site… revokes QUILL’s own application password on the site, as Chapter 1 describes.

Across all your sites

These are in Tools > WordPress > Your Sites, and look at every site you have connected:

The Workbench’s Across Sites and Fleet do much more, and Chapter 9 covers them.

Where to next