WordPress¶

What this helps you do¶

Connect a WordPress site to Hi, Moose so the desktop app can stage and apply content edits directly — FAQs, key points, brief-driven drafts, and AEO audit recommendations — with a preview and approval step before anything goes live.

How the connection works¶

The desktop app is the active side of this connection: it resolves the target post, fetches its current content, builds the proposed change locally, and calls your WordPress site's REST endpoints directly over HTTPS to stage the change. Your WordPress site stays passive — it exposes an endpoint that waits to be called and never needs to reach out to Hi, Moose on its own.

This means:

• Your site token and connection credentials are never held by the renderer UI — only by the desktop app's background process.
• In BYOK modes, the local model steps involved in preparing an edit (like finding the exact section of content to replace) run using your own OpenRouter key, not a Hi, Moose-hosted call.

Setting up a connection¶

1. Open Connections in the desktop app and choose WordPress.
2. Download the connector plugin, install it in your WordPress admin, then paste your site URL and this project's API key into the plugin settings.
3. Back in Hi, Moose, save the connection and confirm the connector reports a successful ping from your site.

Environments¶

Each WordPress install you connect — production, staging, or both — is its own environment with its own site token and HMAC secret, kept fully isolated from one another. Choose which environment is the default target for new edits, and switch between them at any time. If a staging site sits behind HTTP Basic Auth, you can save those credentials for that environment specifically so Hi, Moose can reach it.

Patches¶

Every WordPress edit — whether it comes from FAQs, key points, a draft, or a manual find-and-replace text change you create directly — is tracked as a patch: a local, per-environment ledger entry with its own status.

A patch moves through explicit states: Draft, Staged, Applied, Discarded, Rolled back, or Failed. From the Patches list you can:

• Stage a patch to your WordPress site for preview.
• Apply a staged patch to make it live.
• Discard a patch you don't want to use.
• Roll back an applied patch.
• Promote a patch to another environment (for example, staging to production) to re-stage it there for review.

Listen to this Article plugin¶

The separate Listen to This Article WordPress plugin embeds the audio player and transcript generated by the legacy web app's audio feature. See Listen to this Article for how that feature works today, and install the plugin from wordpress.org/plugins/listen-to-this-article.

Requirements¶

• WordPress 6.0 or higher, with administrator access to install the connection on your site.
• A project set up in the desktop app.