How TAW fits together
The pieces of TAW: taw/core and its taw command, the two themes, taw-fleet, the companion and the installer. What each one is, where it runs, and how a release reaches a live site.
TAW is a few pieces that work together. At the center are two tools: the taw command, which runs inside one theme, and taw-fleet, which looks after every TAW site on your Mac and their production copies. The rest is the framework those tools work on.
The pieces
| Piece | What it is | Where it runs | Get it |
|---|---|---|---|
| taw/core | The framework, as a Composer package: the data layer, the block-editor features, the classic-theme toolkit, and the taw command | Inside each theme, in vendor/ | composer update taw/core |
The taw command | vendor/bin/taw: scaffold blocks, read and write fields, move content, sync the framework, update the site | In a theme folder, on your Mac or in CI | Ships with taw/core 1.90+ |
| TAW Theme | The classic starter theme: PHP blocks, metaboxes, Vite, Tailwind, Alpine | WordPress, one copy per site | taw/create |
| TAW Gutenberg | The block theme (full site editing). Its data comes from taw/core | WordPress, one copy per site | taw/create |
| taw/create | The installer: asks which theme to start from and installs it | Once, when a site starts | composer create-project taw/create |
| taw-fleet | A terminal app that finds every TAW site on your Mac and shows its status, versions, git, pull requests, deploys, production and client feedback | Your Mac (macOS, with Local) | brew install Relmaur/tap/taw-fleet |
| TAW Companion | A small plugin that answers taw-fleet's signed requests on a live site: health, plugins, vulnerabilities, logs, published content, and publishing from Local when the site turns it on | Each production site, as an mu-plugin | A theme's composer.json |
Where each tool fits in a day
- Starting a site:
taw-fleet create(ornin the dashboard) makes a Local site and installs a TAW theme withtaw/create. Without taw-fleet, runcomposer create-project taw/createyourself. See the Quickstart. - Building it: in the theme folder,
taw make:blockscaffolds blocks,fields:getandfields:setread and write content, andschema:validatechecks the data layer. - Keeping it current:
taw update, oruin taw-fleet, updates taw/core and the framework's files in one step and opens a pull request. See Updating a site. - Running many sites: taw-fleet shows which sites are behind, dirty, failing CI or waiting on a deploy. It updates one site or all of them through
taw update, merges pull requests, pulls production content into Local, and starts Claude Code on a site's skills. - Moving content:
taw content:exportandcontent:importmove content as one JSON file. taw-fleet'spullbrings a live site's published content to Local through the companion, andpublishsends Local's changes back after you review them field by field.
How a release reaches a site
taw/core and both themes have their own version numbers. A change travels in this order:
taw/core is tagged
A new version, such as v1.91.0. Nothing downstream changes yet: themes install taw/core by tag, not from its main branch.
The themes lock it
TAW Theme and TAW Gutenberg update their composer.lock to the new taw/core, then get their own release. A brand-new site starts from that lock.
Each site updates
A site's theme runs taw update, or composer update taw/core, and merges the pull request. If the site's repository has a deploy workflow, merging deploys production. The scaffolds don't ship one: each site sets up its own.
Versions
As of October 27, 2026:
| Piece | Version |
|---|---|
| taw/core | 1.100.0 |
| TAW Theme | 1.12.80 |
| TAW Gutenberg | 0.3.81 |
| taw-fleet | 1.34.1 |
| TAW Companion | 0.5.0 |
| taw/create | 0.1.0 |
The Changelog has every release.