PANTHEON CONTENT PUBLISHER
Pantheon Content Publisher compatibility with REEID Translate
Pantheon Content Publisher compatibility with REEID Translate is being reviewed using official plugin documentation. Google Drive/Google Docs publishing workflow: connects to Google Drive via a management token and enables publishing content from Google Docs into WordPress. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Pantheon Content Publisher 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
Pantheon Content Publisher is documented in the Other category with 6 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 Pantheon Content Publisher 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
- Google Drive/Google Docs publishing workflow: connects to Google Drive via a management token and enables publishing content from Google Docs into WordPress.
- Real-time preview in WordPress: provides document previews within the WordPress environment as they would appear live on the web.
- One-click publishing from Google Docs to WordPress.
- Custom post type support: can publish to any public post type registered on the WordPress site, including custom post types, with an option for authors to choose the target post type via wp-post-type metadata.
- ACF integration with metadata field mapping: maps Pantheon Content Publisher metadata fields (case-sensitive) to Advanced Custom Fields (ACF) fields per post type; mapped values are applied on every publish; integration tab shows sync errors and auto-clears after one hour; requires the ACF plugin to be installed and active.
- Connection/disconnection behavior: disconnecting from Google Drive leaves already-created posts/pages on the WordPress site, but prevents editing them from Google Docs.
TRANSLATION BOUNDARY
Pantheon Content Publisher 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 context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Pantheon Content Publisher and REEID Translate FAQ.
What does Pantheon Content Publisher do?
Pantheon Content Publisher has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Pantheon Content Publisher 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 Pantheon Content Publisher?
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 Pantheon Content Publisher in a multilingual WordPress workflow.
REEID documents Pantheon Content Publisher 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.