CMS
DJINN + WordPress
Publishing with the drafts, the review and the approval trail attached.
How it connects
Drafts land as drafts
Content is written into the CMS as a draft with its sources attached. Publishing is a person's decision.
The site is a system, not a page
Publishing coordinates with the SEO monitor and the analytics read, so a post's effect is measured rather than assumed.
Connector spec
- Auth
- oauth2 · wordpress_v1
- Host
- https://public-api.wordpress.com
Scopes requested
GET rest/v1.1/sites/${source.ID}/posts
Emits post · incremental on modified · cursor pagination
Declared boundary: anyone in the workspace
This spec parses and validates, and it has not been run against a live WordPress account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Documents
WordPress setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupREST API credentials
- RunbookDraft and publish workflow
Want WordPress wired into your own company brain?