SAPPHIREIT EDITORIAL WORKFLOW
SapphireIT Editorial Workflow compatibility with REEID Translate
SapphireIT Editorial Workflow compatibility with REEID Translate is being reviewed using official plugin documentation. Enforces a server-side state machine with six distinct workflow statuses (Draft, Writing, Review, Needs Changes, Approved, Published) and validated transition graphs. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What SapphireIT Editorial Workflow does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
SapphireIT Editorial Workflow is documented in the Other category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How SapphireIT Editorial Workflow compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Enforces a server-side state machine with six distinct workflow statuses (Draft, Writing, Review, Needs Changes, Approved, Published) and validated transition graphs.
- Operates on existing posts, pages, and custom post types using WordPress post meta, requiring no data migration or custom post type creation.
- Provides dedicated UI controls for both the Gutenberg block editor sidebar and the Classic Editor meta box.
- Includes an admin dashboard with server-side search, filtering, sorting, pagination, and bulk actions for managing up to 100 posts at once.
- Maintains a complete activity history in a dedicated indexed database table, tracking user IDs, timestamps, and workflow comments without exposing them on the front end.
- Exposes a documented REST API under `sit-cwm/v1` with eight authenticated endpoints supporting application passwords.
- Utilizes six specific WordPress capabilities (`sit_cwm_*`) for role-based access control, allowing integration with capability management plugins.
TRANSLATION BOUNDARY
SapphireIT Editorial Workflow capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
SapphireIT Editorial Workflow and REEID Translate FAQ.
What does SapphireIT Editorial Workflow do?
SapphireIT Editorial Workflow has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does SapphireIT Editorial Workflow have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from SapphireIT Editorial Workflow?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate SapphireIT Editorial Workflow in a multilingual WordPress workflow.
REEID documents SapphireIT Editorial Workflow functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.