Deliver to WordPress

Brenzuri puts an approved article on your WordPress site as a draft. Someone on your side presses Publish. Brenzuri never sends a publish status.

Set it up#

In WordPress#

1. Use a user whose role is Author or above. An Author can create posts and upload the picture; a Contributor can create drafts but not upload media, so the picture is left off (see the troubleshooting below). Make a user just for Brenzuri if you can: the name you give it appears as the author of the drafts.
2. Open Users › Profile for that user and scroll to Application Passwords.
3. Type a name such as “Brenzuri”, press Add New Application Password, and copy the password WordPress shows. It is shown once. Spaces in it do not matter.
4. Check the site is reachable over https and that /wp-json/ answers. Application passwords need https, and some security plugins and hosts switch off the REST API or strip the Authorization header; those need an exception for this user.

In Brenzuri#

1. Open Connections › New connection and choose WordPress.
2. Name it. Enter the Site address as the address that serves /wp-json, for example https://example.com. If WordPress lives in a folder, include the folder.
3. Enter the Username and the Application password. They are never shown again; leave them empty on a later edit to keep the stored ones.
4. Choose a policy. Draft and Awaiting approval both deliver a draft; see below.
5. Press Test connection. A pass says “Reached the site and authenticated. Drafts can be created.” Then Save connection and attach it to a site from the site’s Setup.

What happens, and when#

• A person approves an article of the site in Brenzuri. The approved version is delivered to the site’s connection at once.
• A Beat that writes for the site delivers its article unapproved.
• A person, or a key or an agent with the export scope, can deliver by hand with POST /articles/{id}/deliver. For a key or an agent the result is always a draft.
• A workspace rule can stop it first: approval required before export, or no export while a claim is flagged.

What arrives#

Never sent: tags, SEO fields, a canonical address, an author, a date, and any status other than draft. The one language field, lang, is sent only for an article that has language versions, and for each of them; see Language versions below.

Language versions#

Each language version of an article is its own post, delivered when that version is approved. A post of an article that has language versions, and of each version, carries lang: the language code, with bs sent for BHS. Brenzuri does nothing else with it: it does not link the posts of one article to each other in WordPress, and a site with no multilingual setup ignores the field. A version of an article a Beat wrote is a draft like everything else. A language version has no illustration of its own, so its post has no featured image from Brenzuri.

The featured image#

After the post is created or updated Brenzuri uploads the picture to the media library, sets its alt text and caption, and sets it as the post’s featured image. The picture is an AI-generated illustration and says so in its caption. If any of these steps fails the post is still delivered, and the delivery log says what was left out.

The picture is uploaded attached to the draft (?post=<id>), and under an opaque file name, illustration- and eight characters of the illustration’s id, for example illustration-3f9a1c7e.png. Both are deliberate. WordPress gives an attachment the status of its parent, so the picture of a draft is not listed publicly, and an upload with no parent is published on its own. The file itself is still reachable by anyone who has its address, which is why the name is random: it carries no word of the title, so nobody can read a draft’s title from the address of its picture, and nobody can guess the address.

Updates and rewrites#

• When a person approves a rewrite of an article that Brenzuri already delivered to this connection, the delivery updates the same post instead of making a second one. A rewrite is a new article started with supersedes; the post of the article it replaces is the one updated.
• An update replaces the title, content, slug and excerpt with the new version’s.
• An update changes the featured image only when the illustration is a different one, and never removes one.
• A featured image someone set by hand is kept. Before it uploads anything, an update reads the post’s current featured image. It replaces it only when the post has none, or when it is the picture Brenzuri attached itself the last time. Anything else is left alone, nothing is uploaded, and the delivery log says “Kept the post’s own featured image.” If the post cannot be read, the log says “Kept the post’s own featured image: it could not be checked.” A post that was just created is not read first.
• A version that is not approved always makes a new post, never an update.

The two policies#

Both deliver a draft. The difference is only how Brenzuri records it, and only for a delivery a person starts by hand: with Awaiting approval the delivery log says it is awaiting approval. The delivery that follows an approval in Brenzuri, and its retries, is logged as a plain draft whichever policy the connection has. Approval in Brenzuri adds the excerpt and the reviewed label. Publishing happens in WordPress, always.

Troubleshooting#

Open Connections, choose the connection, and open its delivery log. The reason column says what happened; Test connection on the connection checks the credentials without sending an article.