OnePager for WordPress vs Promptless CPT Pages

This WordPress Plugin transforms children pages into OnePager sections of their respective parent page.

Promptless CPT Pages provides a constrained, opinionated primitive for repeatable structured content on custom-post-type single pages: Register custom post types from an admin UI — no ACF / MetaBox / Pods dependency. Define “groupings” per CPT — named clusters of items sharing a layout variant and a position (above main / below main / sidebar). Items follow one shape — { image-or-icon, heading, supporting_text, optional link }. Four layout variants per grouping — compact-grid, card-grid, featured-card, horizontal-row. Three source modes — manual, child_posts, taxonomy_match. Curated icon library of 53 icons across 13 categories, extensible via the pre_icon_library filter. Connector REST API + MCP tools (18 endpoints under /wp-json/post-runtime/v1/connector/) so AI assistants like Claude Cowork can register CPTs, define groupings, populate per-post values, and preview rendered output. Design-token inheritance from Promptless WP — colors, spacing, typography, radii. Graceful fallback when Promptless is not installed. Promptless CPT Pages is positioned as a free companion plugin to Promptless WP (the page builder) and Promptless Forms (the form renderer). It owns dynamic CPT single-page rendering; it does not replace Promptless for landing-page composition or Promptless Forms for forms. External Services This plugin connects to one third-party service: the Iconify API. It is used solely to display icons that you choose to use, and only when you opt into using them. If you do not use Iconify icons, no external service is ever contacted. Iconify API What it is and what it is for: the plugin bundles the open-source iconify-icon web component locally (assets/js/iconify-icon.min.js — it is shipped inside the plugin and is NOT loaded from any CDN). When a CPT single page, archive card, grouping item, or post field uses an Iconify-format icon identifier written in collection:name form (for example mdi:home or material-symbols:business-outline), the web component requests that single icon’s SVG path data from the Iconify API at render time so the icon can be displayed. This is what makes 200,000+ open-source icons available without bundling them all into the plugin. What data is sent, and when: only the icon identifier you chose to use (for example mdi:home) is sent, as part of the request URL, at the moment a page containing that icon is viewed in a visitor’s browser. The request is made by the visitor’s browser — not by your server. No personal data, no user content, no site URL, and no identifiers of any kind are transmitted. When it is NOT contacted: the plugin also ships a built-in library of 53 icons that render inline as SVG with zero network requests. If you use only those built-in icons — or no icons at all — the Iconify API is never contacted. Service provider: Iconify (Iconify OÜ). Endpoints contacted: https://api.iconify.design (primary), with https://api.simplesvg.com and https://api.unisvg.com as automatic fallbacks used only if the primary endpoint is unreachable. Terms of use: https://iconify.design/docs/api/ — the Iconify API is a free, open-source public service released under the Apache 2.0 License; the “Public API” section documents the terms of use. Privacy policy: https://iconify.design/privacy/