Tomohiro Shiotani

Content Bridge for Commerce provides a lightweight REST API endpoint that allows external commerce platforms such as Shopify to fetch WordPress editorial content.
This plugin does not sync databases or duplicate content. It simply exposes your WordPress posts through a clean, structured JSON API designed for external consumption.
<h3>Key Features</h3>
<ul>
<li>Fetch latest WordPress posts via REST API</li>
<li>Filter posts by category or tag (using slug)</li>
<li>Return featured image, excerpt, and publish date</li>
<li>Optional conversion of Jetpack (i0.wp.com) CDN image URLs back to original URLs</li>
<li>Configurable default post count and limits</li>
<li>Built-in transient cache (5 minutes) to reduce database load</li>
<li>No data duplication or migration required</li>
</ul>
<h3>REST API Endpoint</h3>
Base endpoint:
<pre><code>/wp-json/content-bridge/v1/posts
</code></pre>
Examples:
Latest posts: 
 /wp-json/content-bridge/v1/posts?per_page=4
Posts filtered by tag: 
 /wp-json/content-bridge/v1/posts?tax=post_tag&term=guidi&per_page=4
Posts filtered by category: 
 /wp-json/content-bridge/v1/posts?tax=category&term=news&per_page=4
If no taxonomy is specified, the API returns the latest posts from all published posts.
<h4>Authentication</h4>
This plugin protects its REST API using a simple API key mechanism.
Requests must include a valid API key via the following HTTP header:
X-Content-Bridge-Key: YOUR_API_KEY
If the API key is missing or invalid, the endpoint will return a 401 Unauthorized response.
The API key can be configured in the plugin settings screen.
The API key can be manually set or generated from the plugin settings screen.
<h3>Settings</h3>
Settings → Content Bridge for Commerce
<ul>
<li>Default number of posts</li>
<li>Maximum allowed posts per request</li>
<li>Image size (thumbnail / medium / large / full)</li>
<li>Excerpt length (word count)</li>
<li>Enable or disable Jetpack CDN URL unwrapping</li>
</ul>
<h3>Privacy</h3>
Content Bridge for Commerce does not collect, store, or transmit any personal data.
The plugin only exposes publicly available WordPress post data (such as title, excerpt, featured image, and permalink) via a REST API endpoint.
No data is sent to external servers by this plugin.

Content Bridge for Commerce

Bridge WordPress editorial content to Shopify and other commerce platforms via a simple REST API.

Joe Fusco

Jason Bahl

WPGraphQL IDE is a next-generation query editor for WPGraphQL, built on WordPress’s component library and CodeMirror 6. It replaces the bundled legacy GraphiQL interface with a faster, more extensible IDE that feels native to wp-admin.
Three ways to open the IDE:
<ul>
<li>Dedicated page at <code>wp-admin/admin.php?page=graphql-ide</code></li>
<li>Drawer — slide-up panel triggered from the admin bar, available on every wp-admin and front-end page</li>
<li>Public endpoint mode (opt-in) — visiting the GraphQL endpoint URL in a browser renders the IDE shell instead of returning JSON. Anonymous visitors get a read-only schema browser; signed-in administrators get the full editor.</li>
</ul>
Editor features:
<ul>
<li>Multi-tab editor with auto-save and overflow tab dropdown</li>
<li>Schema-aware autocomplete, hover-doc tooltips, and inline lint warnings (powered by CodeMirror 6 + cm6-graphql)</li>
<li>Cmd-click navigation from any field, type, or argument straight to the Docs Explorer</li>
<li>Response panes: JSON viewer, table view, status code / duration / size / resolver-count badges, request tracing, query log, N+1 detection</li>
<li>Variables and headers editors with their own autocomplete</li>
<li>Per-document settings (description, alias names, max-age cache hint, allow/deny)</li>
<li>Execution history persisted to localStorage, scoped per WordPress user and IDE context — available to anonymous public-endpoint visitors too</li>
<li>Saved Queries panel with personal collections and share links (when WPGraphQL Smart Cache is also active)</li>
<li>Full keyboard support: Cmd+Enter to execute, Ctrl+Shift+P to prettify, arrow keys to switch tabs</li>
</ul>
What’s new in 5.0:
<ul>
<li>Rebuilt UI on <code>@wordpress/components</code> and <code>@wordpress/data</code>. The legacy GraphiQL wrapper is gone — see the Upgrade Notice if you have customizations.</li>
<li>Smart Cache integration. Saved documents now live in <code>wp-graphql-smart-cache</code>‘s <code>graphql_document</code> post type — one canonical primitive for the WPGraphQL ecosystem. The IDE works standalone when Smart Cache isn’t installed; Saved Queries / Document Settings / share links light up when it is.</li>
<li>Three render modes (above), each individually configurable.</li>
<li>Schema-typed data layer. Document and collection operations run through WPGraphQL itself instead of the WordPress REST API.</li>
<li>Full internationalization. Every UI string passes through <code>@wordpress/i18n</code> under the <code>wpgraphql-ide</code> text domain.</li>
<li>Auto-upgrade from 4.x. Open tabs and query history saved by the legacy GraphiQL UI migrate forward on first 5.0 load.</li>
</ul>
For the complete breaking-change list and 4.x → 5.0 migration guide, see <code>UPGRADE-5.0.md</code> in the plugin or the project’s GitHub releases.
<h3>Privacy Policy</h3>
WPGraphQL IDE uses <a href="https://appsero.com" rel="nofollow ugc">Appsero</a> SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster and make product improvements.
Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice.
When you opt in, each telemetry request is sent to Appsero and a duplicate is sent in a non-blocking request to WPGraphQL-operated infrastructure at https://telemetry.wpgraphql.com (the same categories of data as described for Appsero below).
Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses this data</a>.

WPGraphQL IDE

Modern GraphQL IDE for WPGraphQL — schema-aware editor, execution history, saved queries, and a public endpoint mode.

Content Bridge for Commerce vs WPGraphQL IDE