WordPress AI Content & Scheduling Plugin
WordPress plugin that turns a one-line brief into a full article with images and schedules it for a future publish date.
From one-line brief to scheduled Gutenberg post.
Editors type one line — the plugin generates the article with the editor's own OpenAI or Gemini key, pulls matching Unsplash imagery, lays everything out as native Gutenberg blocks, and hands scheduling off to WordPress's own cron. Uninstall the plugin and every scheduled post still publishes on time.
AI Content Studio
One-line brief → full article with imagery
This is an animated mockup of the AI-content-plugin capability — not a live product. Article titles, image matches, and token usage are illustrative.
One-line brief → full article
Editors type one line and get a complete draft — outline, intro, sections, conclusion — streamed straight into the WordPress editor.
Bring-your-own OpenAI / Gemini key
Users supply their own API key. Token costs flow directly to the model vendor and drafts stay inside the user's own WordPress database.
Unsplash imagery + auto-attribution
Section-aware image search via the Unsplash API. CC licensing is respected and attribution is inserted into each image-block caption automatically.
Native Gutenberg blocks
Output is standard Gutenberg blocks — no shortcodes, no proprietary markup. Uninstalling the plugin leaves every post intact.
WordPress native scheduled-post engine
Leans on WordPress's built-in scheduled-post system rather than reinventing a queue — and posts keep publishing even after uninstall.
Marketing site on Next.js 16 + React 19
The plugin's marketing site is a separate Next.js 16 + React 19 build with the React Compiler enabled and Tailwind v4 design tokens.
WordPress plugin that turns a one-line brief into a full article with images and schedules it for a future publish date.
Bring-your-own OpenAI/Gemini key for generation, Unsplash for imagery, and WordPress's native scheduled-post system for the queue.
Output is standard Gutenberg blocks — no shortcodes, no lock-in. Uninstalling the plugin leaves every scheduled post in place. The marketing site is a separate Next.js 16 + React 19 build with the React Compiler enabled.
How a request flows through it
Each request enters at the top of the diagram, flows through every box, and lands at the bottom — exactly the way the production system behaves. The scan-line traces where a live request would be right now.
What it's built with
The interesting parts
Bring-your-own key
User supplies their own OpenAI/Gemini key — token costs flow directly to the model vendor, drafts stay in the user's own WordPress database.
Gutenberg-native output
Articles published as standard Gutenberg blocks rather than shortcodes — uninstalling leaves every post intact.
Native scheduled-post engine
Leans on WordPress's built-in scheduled-post system rather than reinventing a queue.
Marketing site on Next.js 16
Separate Next.js 16 + React 19 site with the React Compiler enabled and Tailwind v4 design tokens.
The calls that did most of the work
A handful of engineering choices shape how a system feels. Here are the ones we'd still defend — alongside what each one cost.
Bring-your-own API key
Token costs go directly to the model vendor, drafts stay in the user's own WordPress database, and there's no operating-cost ceiling pushing the plugin toward a paid tier.
Tradeoff: Onboarding is rougher — users have to set up an OpenAI/Gemini account before they can generate their first article.
Native Gutenberg blocks over shortcodes
Standard block output means the content stays editable, copy-paste-able, and survives uninstalling the plugin. Shortcodes would lock the post into the plugin forever.
Tradeoff: The Gutenberg block API is more involved to author than emitting a shortcode string — more upfront engineering for cleaner output.
Lean on WordPress's native scheduled-post system
WordPress already runs a scheduling engine on every install, battle-tested across millions of sites. Reinventing it is cost without upside.
Tradeoff: WP cron only fires on page traffic, so very-low-traffic sites need a server-cron fallback to keep scheduling reliable.
Tell us what you're building.
Free 30-minute call. Real humans, real timelines, no follow-up emails forever.