werun.Toolkit
The plugin on every WordPress site we run: security, email delivery, an activity log and a branded sign-in, one switch per module.
40
Settings on one screen
Written into theme.json, so the editor and the page match
$0
What we charge for it
Included on the sites we build, with its child theme
7
Colour roles
Blocks use the role, so a new value never breaks them
0
Stylesheets of its own on the page
Structure only: the CSS on a site is the client’s
Parent and child
Two themes, and each one has a job.
The parent is ours and the child is the client's. Keeping them apart is what lets one be updated and the other never be.
Ours
werun.BlocksTheme, the parent
- Templates for posts, pages, archives and everything else
- A header and a footer as template parts, edited in the Site Editor
- Neutral options in theme.json: colour roles, system fonts, a fluid type scale and a spacing scale
- The settings page, the Elementor support and the update channel
- Updated by werun.dev, never edited on the site
The client's
werun.BlocksThemeChild, the child
- Starts empty
- The brand's values, in a theme.json of its own
- Templates, parts and patterns that replace the parent's by name
- CSS that theme.json cannot express, loaded on the site and in the editor
- Never updated: it holds the client's work
Where a value comes from
Four layers, lowest first. Each one overrides the one below it, and the editor and the page read the same result.
The parent's theme.json
The neutral starting point every site shares.
The child's theme.json
The brand, when it is written into the code.
The settings page
Only the values changed there, stored apart from the theme.
The Site Editor's styles
WordPress's own controls, for anything the settings page does not cover.
One screen for the brand
The brand in one screen, written where WordPress reads it.
Appearance → werun.BlocksTheme writes its values into the theme.json data WordPress reads, through the filter WordPress provides for it, so nothing is generated, cached or copied. Only the values that differ from the theme are stored.
Opens at full size.7 settings
Colors
One colour per role: background, text, muted text, surface, border, accent and text on the accent. Blocks and patterns use the role, so changing a value never breaks them.
17 settings
Typography
Body and heading fonts, from the theme or from WordPress's Font Library, the body size and line height, the headings' weight, line height and letter spacing, and the type scale on a phone and on a desktop.
7 settings
Layout
The content and wide widths, the space at the sides of the screen, the gap between blocks and the spacing scale every block uses.
8 settings
Elements
Page background and text, link colours at rest and on hover, whether links are underlined, and the buttons’ colours and corners.
1 setting
Advanced
Whether the editor offers WordPress's generic colours, gradients and sizes next to the brand's. Off as it ships, so editors pick from the brand.
Reset
Three things that can go back to how the theme ships: the settings, the templates saved in the Site Editor and its styles. Content is never touched.
Opens at full size.
Opens at full size.A way back
Undo the design, and leave the content alone.
A site edited for a year in the Site Editor collects changes nobody remembers making. The Reset tab says what was changed and takes it back, one part at a time.
Three parts, chosen separately
The values on the settings page, the templates and template parts saved in the Site Editor, and the Site Editor’s styles, Additional CSS included.
It says what changed
Each part is marked as shipped or customised, and lists the settings and templates that differ, before anything is chosen.
Content is never touched
Pages, posts, menus and the fonts installed in the Font Library stay as they are.
Nothing goes without a confirmation
The reset asks you to confirm that it cannot be undone, and does nothing until you do.
Opens at full size.Elementor
Works with Elementor, and with Elementor Pro's Theme Builder.
Some of the sites we run are built in Elementor. The theme takes them as they are.
None of it runs when Elementor is not active.
Elementor Canvas and Full Width
Both of Elementor's page templates work, with the theme's own header and footer where the template has them.
Every Theme Builder location
All of Elementor Pro's locations are registered. A Pro header or footer replaces the theme's own whenever its display conditions match.
Elementor sets the width
A page built with Elementor drops the content width in every template, so its containers decide how wide they are.
"Hide title" works
Elementor's page setting hides the page title, with no CSS.
What is in it
Structure, and nothing to undo.
What the parent theme brings to a site, and what it leaves to the client’s child theme and to the blocks.
What it ships
The frame of a site.
- Templates: the blog index, a single post, a page and an archive
- Template parts: the header and the footer
- Two patterns: the copyright line and the message for an empty search
- English and Spanish, with every Spanish locale reading Spain’s
What it leaves out
Whatever a brand would have to override.
- CSS: the parent ships none
- Web fonts: system fonts until you pick one
- WordPress's own block patterns, which carry a style of their own
- A header builder or a library of starter sites: the Site Editor and werun.Blocks do that work
Client savings
What you stop paying for, and what you stop undoing.
werun.BlocksTheme costs you nothing: it is included on the WordPress sites we build. The themes a site would use instead are free to start with, so the saving is not a stack of licences. It is the paid tier a site buys when the free one stops short, and the work of undoing a theme’s own look.
| Theme you would use | What its paid tier charges | With werun.BlocksTheme | Here it comes from |
|---|---|---|---|
| Hello Elementor | FreeFree, with no paid tier. Its site-wide colours and fonts live in Elementor's own settings, so it suits sites built entirely in Elementor. | Included | Elementor Canvas, Full Width and the Theme Builder |
| Astra | $69 / yearGlobal colours, type and spacing are free in a limited form. The full controls and the site layouts are in Astra Pro, sold for up to three sites. | Included | The settings page and the Site Editor’s styles |
| GeneratePress | $59 / yearColours and typography are free. Uploading your own fonts, or keeping Google Fonts on the site, is in GP Premium. | Included | WordPress's Font Library, picked on the settings page |
| Blocksy | $69 / yearPalettes and Google Fonts are free. Uploaded fonts, and Google Fonts kept on the site, are in its Personal plan. | Included | WordPress's Font Library, picked on the settings page |
Read on Oct 20, 2026: each theme's page on wordpress.org and its vendor's own pricing page. Every one of them is free to start with; a price is the cheapest paid tier that sells what werun.BlocksTheme does, for one year, in the vendor's currency. A theme does more than its row says: the row is only what it shares with ours.
What the paid route costs, per site and year
Astra$69 / year
GeneratePress$59 / year
Blocksy$69 / year
From$59 / year
These are the other themes’ prices, not ours: list prices for one year. A site uses one theme, so they are alternatives and are not added up; the figure is the cheapest of them.
What a client saves in upkeep
The part with no price tag.
- No theme styles to override before the brand goes on
- A child theme that no update ever overwrites
- One update channel, from the team that wrote the theme
- A reset that knows what the Site Editor changed
- The theme itself: we charge nothing for it
Good to know
Fonts live on the site.
A font is installed once in WordPress's Font Library (Appearance → Editor → Styles → Typography) and then picked on the settings page. A font installed from Google's collection is downloaded to the site, so the page does not ask Google for it.
What it does not replace
A base, not a finished design.
- The design of the brand
- werun.Blocks, for the sections core blocks do not cover
- A page builder, on a site built in one
The theme gives a site its structure and a place to put the brand. The brand, the sections and the content are still the work.
Our tooling
The rest of what we write for the sites we run.
The plugin, the blocks, the theme, the A/B tests and the feedback extension go on the sites we build and run, and we charge nothing for any of them.
werun.Blocks
The Gutenberg block library we write for the sites we build: heroes, pricing tables, FAQs, jobs from your ATS and a query builder for any post type.
werun.Experiments
A/B and Split URL tests on the sites we run: a 7 KB script, a visual editor on the real page and Bayesian results in our CRM.
werun.dev - Client Feedback
Clients click any element of their site and leave a comment. It becomes a task in the CRM project, with a screenshot and the page details.
Theme questions