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.

Michael Sablone

LLM Markdown exposes your public WordPress posts and pages as real <code>.md</code> routes. Simply append .md to any supported post or page URL to access its Markdown representation.
Each Markdown document includes structured YAML front matter and clean content extracted from the rendered HTML.
Designed for:
<ul>
<li>LLM and AI ingestion</li>
<li>Headless and hybrid workflows</li>
<li>Content export pipelines</li>
<li>SEO-friendly alternate representations</li>
</ul>
Example:
<pre><code>https://example.com/my-post.md
</code></pre>
Features:
<ul>
<li>Real <code>.md</code> URLs</li>
<li>YAML front matter (title, dates, taxonomy, URL)</li>
<li>Selector-based content extraction</li>
<li>Respects password protection</li>
<li>Optional respect for noindex</li>
<li>Per-post-type control</li>
<li>Caching for performance</li>
<li>Adds <code><link rel="alternate" type="text/markdown"></code></li>
</ul>
No Gutenberg lock-in. No content duplication. No custom post types required.

LLM Markdown – Expose Content as .md

Expose WordPress posts and pages as real .md URLs with YAML front matter for LLMs, AI ingestion, and headless workflows.

Content Bridge for Commerce vs LLM Markdown – Expose Content as .md