Image workflows

Manage every cover and inline image request in one gallery.

Keep prompt slots, manual imports, AI queues, stock assets, post attachments, and orphan review connected to the content inventory.

View on GitHub Self-host BlogFactory

Cover and inline slots · Import queue · Orphan review

Content control loop

Illustrative product schematic

BlogFactory · Editorial control schematics

Evidence enters. A reviewed CMS draft leaves.

Ready

Sources

RSS · briefs · search

Scoped

MCP agent

Research · create · revise

Working

BlogFactory draft

Versioned work

Required

Human review

Preflight · destination

Draft only

CMS draft

Never live publish

Evidence readRevision trackedApproval explicitDelivery idempotent

Why BlogFactory

Make image work visible before publication.

Create exact slots

Track cover and inline requests against the draft that needs them.

Import manually

Copy prompts and bring approved assets back through upload or drag-and-drop.

See queue state

Separate queued, processing, failed, and completed requests.

Clean up safely

Review orphaned and unused assets without hiding their cost.

Image gallery

Every request stays attached to its post and slot.

The captured gallery shows request counts, prompt actions, import progress, orphan review, and total image cost without inventing a separate asset workflow.

Cover and inline prompts
Per-post import progress
Orphaned asset review

BlogFactory image gallery with cover and inline image request slots and import status — Product capture · August 23, 2026. Values shown belong to the captured workspace.

How it works

Request, import, and attach the right assets.

Create prompt slots

Generate cover and inline requirements from the draft.

Produce or select assets

Use the chosen external or connected image workflow.

Import and review

Attach the exact files and resolve orphaned or unused assets.

Capabilities and boundaries

Built for controlled content operations.

Gallery operations

The gallery owns image inventory and request state.

Cover and inline counts
Queued and failed filters
Manual imports
Post attachments

FAQ

Before you connect.

Does BlogFactory keep sites separate?

Yes. Content, sources, permissions, provider access, search properties, and destinations remain scoped to the authorized site.

Can an MCP agent publish live or delete content?

No. Agent authority stops at approved CMS draft creation. Live publishing, deletion, credentials, and account administration stay outside MCP.

Can I self-host BlogFactory now?

Yes. The public repository is available for self-hosting as a release candidate. BlogFactory Cloud is not available yet.

Run BlogFactory where your content operation lives.

Inspect the public source, then follow the source-build Docker Compose guide for the open-source release candidate.