Start from built-in guidance.
Author uses its built-in editorial system prompt and automatically selects a compatible configured model. The application supplies the starting guidance.
THE EDITORIAL WORKSPACE
Content work belongs
in a workflow.
AI generation is one step in an editorial process. Teams also need source material, instructions, an output destination, and a decision about when the work should run.
Author keeps those responsibilities inside WordPress. Library organises content bundles, Jobs defines the work and timing, and Settings manages editorial guidance and provider-aware configuration. Generated content becomes part of the WordPress publishing workflow.
Administrators have a path from relevant source text and prompts to drafted or optimized posts, without moving operations into a separate content platform.
NATIVE WORDPRESS AI CLIENT
The provider connection
belongs to WordPress.
Author requests AI capabilities through the WordPress AI Client, the application-facing abstraction for its editorial workflow. Publishing logic stays separate from provider-specific requests.
Install and configure a compatible provider plugin in WordPress Settings → Connectors. Provider options include OpenAI, Anthropic and Google. The installed connector and configured provider determine which models and capabilities are available.
Author can select a compatible model automatically or use a valid explicit selection. Capabilities differ across providers, so changing a connection still requires compatibility checks and workflow validation.
WordPress manages provider configuration and authentication. Author controls the requested editorial work and does not store provider credentials itself.
01 / EXMOMENT AUTHOR ↓Editorial instructions, Library, and Jobs
02 / WORDPRESS AI CLIENT ↓Application-facing AI interface
03 / CONFIGURED WORDPRESS CONNECTOR ↓Installed provider plugin & authentication
04 / PROVIDER OPTIONSOpenAI · Anthropic · Google
BEHAVIOUR MODES
Choose how editorial
guidance is prepared.
Set the balance between built-in guidance, optimized administrator instructions, and direct operator control.
Draft or publish is configured separately in the job. Choosing a behaviour mode does not replace that output decision.
LIBRARY / REUSABLE SOURCE MATERIAL
Import a content bundleZIP containing text or Markdown articles
Preview & manageCategories, files, and article content
Select for a jobRelevant source categories and usage tracking
THE LIBRARY MODULE
Prepare the source.
Keep it in the workflow.
Import structured content bundles, preview individual articles, and manage categories and files. Editorial jobs can then use relevant source material rather than starting without context.
Jobs select from configured Library categories. Used-article tracking records source usage, and uniqueness settings influence whether an article can be selected again.
Source management supports different editorial tasks, while those selection rules control how individual articles participate.
ADMINISTRATOR-ONLY JOBS
Give the work
a purpose and a time.
Jobs are private administration records. Define source categories, author, destination, and draft or publish status.
Run one task now.
Begin an immediate run when the source and instructions are ready.
Plan a one-time run.
Set a future run with source, output, and instructions configured in advance.
Define recurring work.
Use a repeating schedule governed by the job’s selection and output settings.
Global direction. Job-specific context.
A job can inherit the global editorial prompt or supply an override. Instant and scheduled work share the generation implementation. Scheduling is part of a controlled editorial workflow rather than an isolated timer.
SETTINGS & DIAGNOSTICS
Check the connection
before running the work.
Settings exposes provider connection status, compatible models, and diagnostics. WordPress Connector configuration supplies the connection Author uses.
Explicit provider and model selections must be valid for that installation. An invalid selection stops generation rather than silently moving the request to another service.
Administrators configure automation while editors work with the resulting WordPress content. Admin-only Jobs keeps job creation and operational settings within the administration boundary.
DATA BOUNDARIES
Relevant context.
A requested AI workflow.
AI requests occur through the requested plugin workflow, including configured jobs. Relevant text, instructions, and context for the task go to the configured provider through the WordPress AI Client.
- Unrelated site and user data are not automatically transmitted.
- Author does not store provider credentials itself.
- WordPress manages connection and authentication.
- The selected provider’s terms and privacy policy apply.
Optional author context is disabled by default. When enabled, it supplies the selected author’s public display name. Generation also uses relevant source labels and configured category context.
OPEN SOURCE / WORDPRESS.ORG
Inspect the product.
Understand the engineering.
ExMoment Author is available through WordPress.org as open-source software. The current listing and documentation explain its modules, configuration, and workflow.
Read the configuration details.
Use the current documentation for setup, compatibility, source selection, and job behaviour.
LET’S BUILD SOMETHING THAT HOLDS UP.
Your next system. Our engineering.
Tell us what you’re building, improving, or trying to connect.