Manage a private SaaS product asset library with review queues, visible approvals, undo, bulk decisions, alt text, provenance, and safe archiving.
Product screenshots, brand visuals, diagrams, logos, and other visuals remain filterable by origin and lifecycle state.
A governed product asset library is a site-scoped workspace for visual files that may be placed directly in articles or used as controlled image-generation context. Blogged stores a label, description, accessible alt text, visual kind, tags, dimensions, format, origin, status, and source provenance with each asset. Website discoveries require approval, approved decisions stay visible and can be undone, deliberate uploads enter as approved, and archived assets stop being available for new use without breaking existing placements.
Each control keeps the difference between discovery, eligibility, exact placement, and generation context visible.
Needs review and Approved are visible states with per-item editing, page-level bulk decisions, discard, and undo.
Labels, descriptions, alt text, kinds, tags, dimensions, origins, and source URLs make the library useful to people and workflows.
Archiving removes a visual from future eligibility while existing post placements remain unchanged and traceable.
JPEG, PNG, and WebP uploads are decoded as images, rotated, bounded by size and pixels, resized without enlargement, and stored as WebP.
The workflow preserves site scope, provenance, eligibility, and editorial control instead of turning every image into automatic generation context.
Upload an intentional file during onboarding or later, or run site discovery to create pending candidates with provenance.
Confirm the kind, label, description, alt text, tags, source, and status before approving a discovered item.
Approved assets become available to supported article workflows; later archiving blocks new use without altering existing placements.
Governance makes reuse safer, but approval is not a perpetual truth claim. Teams should update or archive visuals when the product changes, keep alt text contextual, and review the final article before publication.
Clear answers about discovery, approval, provenance, privacy, placement, and generation boundaries.
Asset records are scoped to the workspace and active site. They remain private until a user deliberately attaches or applies one in a post; API access is role-checked.
Yes. Upload a JPEG, PNG, or WebP screenshot or diagram when the website cannot expose it. Because the customer chose the file, it enters the approved library directly.
Blogged accepts valid JPEG, PNG, and WebP image files up to 7 MB. Accepted uploads are normalized to WebP and resized without enlargement when needed.
The asset stops being eligible for normal new placements and reference selection. Existing post placements remain unchanged because articles use their own attached copy.
Discovered candidates may arrive with derived metadata, but the library exposes alt text for human review and editing. The final alt text should match the asset's actual role in the article.
Discover website images and rendered sections inside the exact root domain, subdomain, or product folder provided, with source provenance and approval before reuse.
Explore workflowUse approved SaaS product screenshots and diagrams in valid article sections, with high-confidence recommendations, preview control, and stable post copies.
Explore workflowGuide SaaS article-image generation with up to three approved visual references, site-scoped eligibility checks, exact logo compositing, and provenance.
Explore workflowBuild the library, approve what is actually useful, and choose exact placement or reference-guided generation based on the evidence the article needs.