Choose the publishing route
One language surface, or a connected set?
Source-only
Improve the existing page in its current language. This route adds no translated reader surface.
Multilingual
Create native posts and pages for additional languages when readers need more than the source language.
One controlled job at a time
A route with a verifiable finish
01
Record the starting material
Build the complete Source Inventory, then record the explicit obligations that current and future content must cover.
02
Bound the assignment
Use one source or translation job at a time with an authenticated compatible client. A bounded proposal can be compared with the material it is meant to change.
03
Write for the decision
Produce the complete page or translation from the current evidence, including the information a person needs before acting.
04
Separate making from checking
An independent review checks the exact proposal against the same source and coverage requirements before publication can proceed.
05
Release after approval
Publish only complete content that passed review. For a multilingual result, verify localized URLs, internal links, and hreflang relationships before release.
06
Inspect the delivered page
Open the exact public page after publication; a successful publish operation alone cannot prove what people receive.
07
Expose unfinished work
Use current workflow status to distinguish verified pages from unfinished sources and translations, so the next publishing action is clear.
Where control lives
Keep the evidence strict and the content native
These boundaries show what remains native, what must stay current, and what an authenticated client needs.
01
Freeze the facts
For factual improvements, Workflow can require an immutable copy of the source supplied to WordPress. Replacing that copy makes earlier approval stale until current facts are covered and independently reviewed.
02
Keep assets in WordPress
Translated posts, pages, menus, terms, and media remain ordinary WordPress content after the plugin is removed; only Workflow services and plugin-owned workflow data are removed. Workflow manages their source relationships, localized routes, workflow progress, review evidence, and publication status without replacing WordPress as the content system. Editor, theme, SEO, and presentation integrations can extend the operation.
03
Choose any compatible client
No specific AI model or provider is required. Any authenticated client that follows the published WordPress interface contracts can participate.
04
Check the interface prerequisite
The plugin remains active without the WordPress Abilities API. Its workflow interfaces register only when an installed provider supplies wp_register_ability().
Runtime requirements
Dependencies for a self-hosted installation
Use these exact prerequisites when preparing the workflow.
6.9 or later
WordPress 6.9 or laterProvides native content, metadata, routing, taxonomy, REST, and publication services.
8.0 or later
PHP 8.0 or laterRuns Devenia Workflow on the server.
Provider available
WordPress Abilities APIProvides the registered interfaces used by authenticated workflow clients.
Stable package
Add controlled publishing to WordPress
Download the Stable self-hosted ZIP for Devenia Workflow, then choose the source-only or multilingual route that fits the people you need to reach.