Publishing, with a named approver

Built, not yet live

The approval rule is live in the database and tested, and a WordPress connector is written. Nothing has ever been published to a real site.

What it will do

Approving words and putting them live are two decisions, taken at two moments, often by two different people. ShownTrue keeps them apart on purpose.

A change will arrive on your own site as a draft, or as a change you can read line by line before accepting it. Going live stays a separate act with a name against it, and the record of who did it is not editable afterwards.

The screen today

Publishing, with a named approver: the /content screen in the ShownTrue app
The /content screen on 14 October 2026, from a demo workspace labelled as test data. Nothing has been imported into it, so this is what a new account sees first.

What exists today

  • The rule itself, in the database. A publishing job set to go live is refused unless it carries an approver and the moment they approved, and the refusal holds even for the internal account that bypasses every other access rule.
  • Approval is final. Once set it cannot be moved to somebody else, re-pointed at different content, or deleted, and each of those refusals is a separate error with its own test.
  • Edits never overwrite. Changing an approved draft writes a new version instead, so the words that were approved stay readable beside the words that went out.
  • A WordPress connector. It is the first thing that can actually put an approved change on a site.

What is missing

  • WordPress only. A static site, and anything else, still has no connector.
  • Nothing has been published. The connector has never written to a real WordPress site, so what it does to one is a claim rather than a record.
  • No approval screen. Approval happens through an action rather than a page somebody can sit in front of and read.

Measured against the code in this repository. When the code moves, this page moves with it, because both read the same list.