ZIPPY
Zippy | REEID Translate Compatibility
REEID Translate Pro processes the supported visitor-facing fields documented for Zippy while the plugin remains responsible for its own structure, configuration and functionality.
AWAITING VERIFICATION
Translate documented content. Preserve plugin behaviour.
The integration defines an explicit content boundary so multilingual text can be handled separately from plugin-specific functional data.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
CONTENT BOUNDARY
Translatable content remains separate from plugin-specific functional configuration.
DEFINED SCOPE
Supported fields and limitations are documented per integration instead of assumed from the plugin category.
PRACTICAL WORKFLOW
Translation workflow
01 · Prepare the source content
Use Zippy normally to create the original WordPress experience.
02 · Identify documented fields
Use the integration record to determine which visitor-facing content is supported.
03 · Translate supported content
Process only the documented multilingual fields while preserving functional configuration.
04 · Review plugin behaviour
Test translated output and plugin-specific frontend behaviour before publication.
SUPPORTED CONTENT
Translation scope
Visitor-facing text
Replace this draft item with the exact content coverage.
Interface content
Document supported labels, titles or interface strings where applicable.
Product-specific content
Add confirmed product-specific support before publication.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Archives posts and pages into ZIP files from the WordPress admin.
- Can extract previously archived content on another site where the plugin is installed.
- Supports downloading and storing posts as ZIP archives for local backup or transfer.
- Supports archiving multiple posts in a bulk action.
- Supports custom post types.
- Can transfer attachments and images as part of the archive/import workflow.
Distinctive features
Archives posts and pages into ZIP files from the WordPress admin. Can extract previously archived content on another site where the plugin is installed. Supports downloading and storing posts as ZIP archives for local backup or transfer. Supports archiving multiple posts in a bulk action. Supports custom post types. Can transfer attachments and images as part of the archive/import workflow.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Use the integration record as the translation boundary.
REEID processes documented visitor-facing fields while Zippy retains control of plugin-specific structure, settings and functionality.
Anything outside the documented supported-content list should be treated as unverified until separately evaluated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Zippy and REEID Translate FAQ.
Does REEID Translate work with Zippy?
REEID Translate Pro processes the supported visitor-facing fields documented for this integration while Zippy retains control of its own functionality.
Does REEID take over Zippy functionality?
No. The plugin remains responsible for its own functionality and configuration.
How is supported content determined?
The Integration Factory record defines the supported visitor-facing fields and explicit limitations for this plugin.
RELATED GUIDES
Continue through the compatibility library.
OTHER INTEGRATION
Translate the documented Zippy content through REEID Translate Pro.
Keep multilingual content separate from plugin-specific functional behaviour.
Supported content and limitations are defined by the integration record.