First public release on WordPress.org.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Onboarding \u2014 pick how this site participates: Publish, Subscribe, or Both.","2":"Library \u2014 list of components published from this site, with version, cache TTL, and the live REST endpoint.","3":"Component editor \u2014 slug, name, type, value (or file URL), cache TTL.","4":"Sources \u2014 components pulled from a remote Host, refreshable on demand.","5":"Settings \u2014 capability toggles, CORS policy, authentication, and connection test."}},"plugin_section":[],"plugin_tags":[146,141196,1118,23853,1558],"plugin_category":[52],"plugin_contributors":[241942],"plugin_business_model":[],"class_list":["post-318891","plugin","type-plugin","status-publish","hentry","plugin_tags-cache","plugin_tags-headless","plugin_tags-json","plugin_tags-rest-api","plugin_tags-sync","plugin_category-performance","plugin_contributors-artificialpoets","plugin_committers-artificialpoets"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/artificial-poets-reusable-components-cdn.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
WP Components<\/strong> lets one WordPress site act as a Host that publishes a Library of named pieces of content \u2014 a logo, a tagline, a social-links JSON blob, a privacy notice \u2014 and any number of other sites act as Receivers that subscribe to that Host and consume those components instantly.<\/p>\n\n Every component has a stable slug, a type ( A single site can also act as both<\/strong> Host and Receiver \u2014 publish your own Library while subscribing to one or more remote Hosts.<\/p>\n\n Yes. The Host's Yes. Set Publish Library<\/strong> and Subscribe to Source<\/strong> both ON in Settings. You'll see your own Library and the remote Source in separate tabs in the admin menu.<\/p><\/dd>\n Every save bumps the component's version, which is also the No. All data stays on your own WordPress sites. There are no calls to third-party servers, no telemetry, no SaaS dependencies.<\/p><\/dd>\n Yes. On the Host: Components \u2192 Settings \u2192 Library Publishing \u2192 Access<\/strong> can require an Application Password. On the Receiver: Settings \u2192 Source Subscription \u2192 Authentication<\/strong> lets you send Application Password credentials when fetching.<\/p><\/dd>\n Nothing. The plugin is GPL-2.0-or-later and free to use commercially.<\/p><\/dd>\n\n<\/dl>\n\n\njson<\/code>, text<\/code>, or file<\/code>), a per-component cache TTL, and an auto-incrementing version number that becomes its HTTP ETag<\/code>. Subscribers fetch the latest version on demand and revalidate cheaply with 304 Not Modified<\/code> for unchanged content.<\/p>\n\nUse cases<\/h4>\n\n
\n
Key features<\/h4>\n\n
\n
\/raw<\/code> response sends ETag<\/code>, Last-Modified<\/code>, and Cache-Control: public, max-age=<TTL>, must-revalidate<\/code>. Conditional requests get 304 Not Modified<\/code>.<\/li>\n*.example.com<\/code> wildcard support).<\/li>\nREST endpoints (Host mode)<\/h4>\n\n
\n
GET \/wp-json\/wp-components\/v1\/components<\/code> \u2014 list all published components<\/li>\nGET \/wp-json\/wp-components\/v1\/components\/{slug}<\/code> \u2014 fetch one as JSON metadata<\/li>\nGET \/wp-json\/wp-components\/v1\/components\/{slug}\/raw<\/code> \u2014 fetch with type-appropriate Content-Type<\/code> (text\/plain, application\/json, or proxied file bytes)<\/li>\n<\/ul>\n\n\n\n
.zip<\/code> via Plugins \u2192 Add New \u2192 Upload Plugin<\/strong>.<\/li>\n\n
Does this work for headless WordPress \/ Next.js \/ Astro frontends?<\/h3><\/dt>\n
\/wp-json\/wp-components\/v1\/components\/{slug}\/raw<\/code> endpoint returns the content with the right Content-Type<\/code> header and proper Cache-Control<\/code> \/ ETag<\/code>, so a frontend can fetch()<\/code> it directly. For images, an <img src=\"\"><\/code> works without any client-side glue.<\/p><\/dd>\nCan one site be both Host and Receiver?<\/h3><\/dt>\n
How is the cache invalidated when I update a component?<\/h3><\/dt>\n
ETag<\/code>. The next request from a subscriber gets a fresh response; subsequent requests with If-None-Match<\/code> get a fast 304 Not Modified<\/code>.<\/p><\/dd>\nDoes the plugin require an external service?<\/h3><\/dt>\n
Can I require authentication between Host and Receiver?<\/h3><\/dt>\n
What does it cost?<\/h3><\/dt>\n
0.1.0<\/h4>\n\n
\n
304 Not Modified<\/code> support.<\/li>\n