CODOC
codoc compatibility with REEID Translate
codoc compatibility with REEID Translate is being evaluated from available plugin evidence. Enables content monetization through article paywalls, one-time purchases, and Reader Plans (subscription/membership). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for codoc.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
codoc is documented in the Membership category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How codoc compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Enables content monetization through article paywalls, one-time purchases, and Reader Plans (subscription/membership).
- Restricts access to content placed below a specific codoc block, hiding it from non-buyers while keeping preceding content public.
- Integrates with Stripe for payment processing, supporting credit cards, Apple Pay, Google Pay, and Konbini in JPY, USD, or EUR.
- Provides buyer authentication and purchase restoration mechanisms directly within the WordPress post view.
- Supports both Gutenberg and Classic Editor interfaces for inserting paywall blocks and configuring per-article settings.
- Offers customization options including CSS overrides and custom HTML insertion before or after paywall tags.
CONTENT BOUNDARY
codoc capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
codoc and REEID Translate FAQ.
What does codoc do according to the available plugin evidence?
codoc has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for codoc?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for codoc?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate codoc in a multilingual WordPress workflow.
REEID documents codoc functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.