Guide SaaS article-image generation with up to three approved visual references, site-scoped eligibility checks, exact logo compositing, and provenance.
References guide a new visual; they do not guarantee pixel-level reproduction. Exact logo handling is deliberately separate and deterministic.
Brand asset references are approved, site-scoped visuals that an editor deliberately selects as context for a section-image generation request. Blogged accepts up to three eligible references, verifies them before queuing and again before the worker reads their bytes, and records the reference asset IDs with the generated image. An approved logo follows a separate path: the image model is not asked to redraw the mark. Blogged composites the exact supplied logo after generation and records that application in generation metadata.
Each control keeps the difference between discovery, eligibility, exact placement, and generation context visible.
An editor can send up to three eligible product assets with a manual section-image generation request.
The brand mark is resized within bounded dimensions, placed on a contrast-aware plate, and composited onto the finished visual.
Synchronous request validation catches stale choices early, while the worker repeats site, workspace, status, origin, format, and path checks.
Generated section images create catalogue records that point to the article and placement while preserving replacement history.
The workflow preserves site scope, provenance, eligibility, and editorial control instead of turning every image into automatic generation context.
Select up to three approved visuals for generation context and provide the section-specific image prompt.
The route and worker enforce eligibility, preserve the current image during replacement, and record the references used.
When eligible, the supplied logo is composited after generation; the resulting image remains subject to Editor review before publication.
Reference images can guide visual direction but do not guarantee exact layout, product fidelity, or claim accuracy. Use direct asset placement when the exact screenshot matters, and review every generated visual for text quality, relevance, and brand fit.
Clear answers about discovery, approval, provenance, privacy, placement, and generation boundaries.
A manual section-image generation request can include up to three eligible reference assets. Each reference must still be active, site-scoped, and available when the worker starts.
No. References guide generation context and visual direction; they do not guarantee pixel-level reproduction. If the exact approved screenshot is required, use direct article placement instead.
The image model is not asked to redraw the approved logo. Blogged composites the exact customer-provided logo file onto the generated result afterward using deterministic size and placement bounds.
No. Generated post-image catalogue records are excluded from normal reference selection and automated asset assistance to avoid circular, stale visual reuse.
Use approved SaaS product screenshots and diagrams in valid article sections, with high-confidence recommendations, preview control, and stable post copies.
Explore workflowManage a private SaaS product asset library with review queues, visible approvals, undo, bulk decisions, alt text, provenance, and safe archiving.
Explore workflowDiscover website images and rendered sections inside the exact root domain, subdomain, or product folder provided, with source provenance and approval before reuse.
Explore workflowBuild the library, approve what is actually useful, and choose exact placement or reference-guided generation based on the evidence the article needs.