TopSoil
The management layer that makes modern WordPress actually usable.
What it is
TopSoil is the admin-side management layer that sits on top of a Bedrock WordPress install. It handles the plumbing (plugin installs, updates, repo sync, deploys, backups) from inside the WordPress admin, without needing a terminal. Any developer can pick up the underlying Bedrock install and keep working.
Why it matters
Bedrock gives modern WordPress everything it needs: git version control, Composer packages, staging/production separation, secure file structure. But Bedrock also requires CLI knowledge for updates, server-level access for plugins, and a manual deployment process. That is a wall for anyone who is not a WordPress developer.
TopSoil is the ramp that lets everyday designers use Bedrock-quality WordPress without becoming sysadmins. It is plumbing, not an authoring system. It deliberately stays out of page-builder territory (Elementor, Bricks, Breakdance, Gutenberg all continue to work).
Current state
Where it is right now: plugin v6.13.49, running AnalogCirc.us in production. The work since the summer has gone into what gets built on top of the panel system: a Products module that gives a site a real catalogue spine, and the tools that run a shop on it.
The Products module is a generic item spine rather than a store. Items vary along more than one axis at once, prices cannot be set below what an item has to earn, a product can be sold as a set at one price, a design can carry more than one piece of art, and coupon codes are checked when they are made so none can sell at a loss. It is running a real shop now, which is the only proof that counts.
What is next: unchanged, and honestly so. The standalone Docker image for self-hosters and the licensing decision (source-available and free for individuals and co-ops, vs. open-core with paid modules) have been next since June. The shop took the time instead. Neither has moved.
Connections
Runs AnalogCirc.us. Meant to be the admin layer under TentCities and under any community server that comes after it.
Build log
Highlights of the last few months. Version numbers are the plugin's own; the arc between them is what's worth showing.
-
Early years
The frustration and the first prototypes
Years of trying every existing WordPress admin skin, then building throwaway prototypes to see what a real management layer for Bedrock could feel like. Everything that landed in the current framework was rewritten many times before it stabilized.
-
Oct 2025
v5 line stabilizes as the real thing
Enough of the framework has hardened that version-tracked development becomes worth it. The plugin starts being treated as a product, not an experiment.
-
Apr 22, 2026
Framework v11.0.0 · Unified Panel Architecture
Internal Framework module milestone. The panel system is unified into a single architecture.
More
- Before this, the top bar, the side panels, the module surface, and the popup layers each had their own layout code and their own quirks.
- v11 collapses all of that into one panel system: everything on screen is the same kind of thing, positioned by the same rules.
- Everything after this (bar-form modules, nested frames, docks) is only possible because the substrate is now one thing instead of four.
-
May 11, 2026
Framework v6.6.0 · Nested Frame Architecture
Frames-inside-frames land as a first-class concept.
-
Jun 3, 2026
v6.6.80 · Plugin Manager goes TopSoil-native
First OptionsPageFramework page outside the Framework Editor itself. Plugin management leaves WP-native admin.
More
- Up to this point, every TopSoil-styled screen you saw was really the Framework Editor in different modes.
- The Plugin Manager is the first real product page built on TopSoil's own page framework: the first proof that other TopSoil features can be built on the same substrate, not just the editor itself.
- WordPress-native admin no longer needed to install, update, or repo-sync a plugin.
-
Jun 6, 2026
v6.7.0 · Top/bottom panels, bar-form modules, canonical CSS
Bar-form modules ship. Canonical CSS gets promoted out of experiments.
-
Jun 11, 2026
v6.10.0 · Panels are docks
Panels reinterpreted as docks. Empty-dock states get real UI.
-
Jun 15, 2026
v6.13.0 · Bar geometry bounded to center, tabs after drag
Geometry cleanup pass. Tab behavior after drag operations gets right.
-
Jun 17, 2026
v6.13.17 · Plugin Manager API caching
Plugin Manager gets an API caching layer to stop re-fetching the world on every panel refresh.
-
Jun 22, 2026
v6.13.21 · Scheduled jobs that run on time
Real schedulers can drive background work instead of waiting for a page visit.
-
Jun 29, 2026
v6.13.42 · RUM beacon 404 fix, real-time layer scaffolded warm
Current stable at the time, running AnalogCirc.us in production and on its staging copy. The real-time layer is scaffolded and kept warm.
More
- RUM beacon fix: the real-user-monitoring beacon was 404-ing when cloud control was disabled. Silent noise for anyone running the plugin standalone. Fixed cleanly.
- Real-time layer kept warm: a socket and cache layer that could power presence, co-editing, and admin-side notifications sits scaffolded and ready. Its consumers are intentionally quiet until the API changes needed to make room-OS scene layers editable at Elementor fidelity land.
- Nothing dramatic in this release. It's the "keep the machine running well" point of the release cycle.
-
Aug 16, 2026
v6.13.44 – 6.13.49 · six releases in a day
A catch-up release run that regularized work already sitting in the tree, plus real fixes: plain-HTML admin screens finally get the workspace chrome, and the cron panel says whether cron is actually running instead of hedging about it.
More
- "Say whether cron is running, stop hedging about it" is the one worth calling out. A status panel that cannot commit to an answer is worse than no panel, because it trains you to ignore it.
- Several of these releases exist only to record work that had already shipped. Version numbers that lag the code are their own kind of lie.
-
Aug 18 – 31, 2026
The Products module Turn
TopSoil grows a catalogue spine. Not a store, and deliberately not a commerce engine: the generic layer underneath one, so a site can own its items without adopting somebody else's idea of what a product is.
More
- More than one axis. Real items vary along several dimensions at once, and a system that models only one will confidently ship the wrong thing. Getting this wrong is not a display bug, it is a fulfilment bug, which is a much more expensive class of mistake.
- Prices with a floor. An item knows what it costs to exist, and refuses to be priced below it. The interesting part is that the floor has to be computed against what checkout actually charges, not against a list price, or it quietly permits a loss.
- A fulfilment seam. Handing production to an outside supplier is a boundary, and boundaries need defending. The module assumes the other side can accept work it cannot actually perform, and checks locally rather than trusting a success response.
- All of it is being proved against a real catalogue before any of it is considered releasable. Building the general case first is how you get a general case nobody needs.
-
Aug 20 – 31, 2026
Items that describe themselves
A change to Products so an item carries its own presentation rules instead of the site being taught about each one.
More
- Items describing themselves is the same instinct as the panel unification two versions of the framework ago. When behaviour lives on the thing rather than in the renderer, adding a new kind of thing stops requiring changes to everything that displays it.
-
Sep – Oct 2026
The shop runs on it
The Products module went from proving itself to carrying a live shop. Sets of colours at one price, more than one piece of art per side, images shrunk on upload, and coupon codes checked against the price floor when they are made rather than at checkout.
-
Oct 19 – 20, 2026
The products list becomes the editor
The Products list is now where a product is edited. Title, subtitle, brand, category, label and price change right in the row, every warning opens the thing that fixes it, and every other part of a product (its description, garment, price, photos, sets and status) opens in its own panel under the row. The old card that showed everything at once is gone. Columns can be dragged into order or hidden, and each person's layout is kept. Facts that belong to a garment rather than a design, like its size chart, care, material and tags, are kept with the garment once, and every product made on it reads them from there.
-
Oct 19 – 21, 2026 You are here
TopSoil starts shedding what it no longer needs
TopSoil is being split into self-contained modules. Two old modules with nothing left to do are gone, along with everything they had left in the database, and the code that starts TopSoil is under a third of its old size. The screen for the site's scheduled jobs is the first module in its own folder, with a short page saying what it does, what it depends on and how to test it. Every step is checked by listing everything TopSoil sets up when it starts, before and after, so a change can be shown to do only what it meant to.
-
Next
Standalone Docker release + license pick
Docker image for self-hosters, and a decision between the two licensing drafts being weighed (source-available and free for individuals and co-ops, vs. open-core with paid modules). Both have been next since June. The shop took the time instead, which is the honest reason rather than an excuse.