supanova-deploy

To automate landing-page deployment, you provide Pinterest references, a Gemini video, and template HTML. The process converts the video to WebP frames, assembles a reproducible output folder with index.html, assets, and frames, and deploys via Netlify Drop.

WebP frame conversion for landing-page deployment works by post-processing a 16:9 Gemini Pro video into individual WebP frames. Claude Code facilitates this conversion, creating frame assets that are then assembled into a static HTML template for deployment.

Yes, you need to prepare three specific assets before starting the landing-page deployment workflow: Pinterest reference images, a generated Gemini video, and a template HTML file. These inputs allow the skill to generate a reproducible output folder for deployment.

Yes, you can use Netlify Drop to deploy static HTML assembled from video frames. The workflow validates the assembled index.html and asset paths, ensuring the reproducible folder structure is correct before executing the Netlify Drop deployment.

Limitations of automated landing-page deployment from visuals include safety checks that prevent missing assets or incorrect paths. The workflow requires strict adherence to a reproducible folder output structure containing index.html, assets, and frames directories for successful validation and deployment.