visual-html-renderer

To render and preview HTML from a structured document model, provide a document-model.json input to trigger the renderer CLI, which builds the model, validates structure, and returns a session-scoped preview URL.

Yes, you can validate HTML structure, assets, and schemas before generating a preview; the renderer CLI executes a validation step to ensure final HTML integrity and verify diagram blocks and image attachments.

To include Mermaid diagrams and images when generating HTML bundles, the renderer processes semantic HTML blocks and attaches images via the CLI, validating the assets before presenting the final preview URL.

The best way to automate HTML generation from agent-generated documents is to use a unified renderer that translates document models into verifiable HTML bundles, offloading heavy processing to scripts while managing safety gates.

Yes, you need a structured document-model.json format to start the HTML rendering CLI, which uses this input to execute the build-model, attach-image, check-model, render, validate, and preview lifecycle steps.

Your HTML rendering pipeline may fail during the validation step if the document model contains invalid schemas, missing image attachments, or malformed diagram blocks, which the strict HTML representation design actively rejects.