PROMPTLESS CPT PAGES
Promptless CPT Pages compatibility with REEID Translate
Promptless CPT Pages compatibility with REEID Translate is being reviewed using official plugin documentation. Registers custom post types via an admin UI (no ACF/MetaBox/Pods dependency). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Promptless CPT Pages 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
Promptless CPT Pages is documented in the Other category with 8 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 Promptless CPT Pages 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
- Registers custom post types via an admin UI (no ACF/MetaBox/Pods dependency).
- Defines per-CPT “groupings” as named clusters of items with a shared layout variant and a position (above main / below main / sidebar).
- Renders CPT single pages using a constrained item shape (image-or-icon, heading, supporting_text, optional link) and supports four layout variants per grouping (compact-grid, card-grid, featured-card, horizontal-row).
- Supports three source modes for grouping items: manual, child_posts, and taxonomy_match.
- Provides a connector REST API under `/wp-json/post-runtime/v1/connector/` with MCP tools/endpoints to register CPTs, define groupings, populate per-post values, and preview rendered output.
- Implements design-token inheritance from Promptless WP (inherits `–aisb-*` tokens when Promptless WP is active) with graceful fallback when Promptless WP is not installed.
- Stores CPT and grouping definitions in `wp_options` and per-post grouping values in WordPress post meta (no custom database tables).
- Optionally uses the Iconify API at render time in the visitor’s browser to fetch SVG icon data when Iconify-format icon identifiers are used; if only the built-in 53 icons are used, the Iconify API is not contacted.
TRANSLATION BOUNDARY
Promptless CPT Pages 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
Promptless CPT Pages and REEID Translate FAQ.
What does Promptless CPT Pages do?
Promptless CPT Pages has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does Promptless CPT Pages 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 Promptless CPT Pages?
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 Promptless CPT Pages in a multilingual WordPress workflow.
REEID documents Promptless CPT Pages 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.