Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
dazzatronus
force-pushed
the
add-automotive-inventory-videos
branch
from
September 22, 2026 11:57
ab22a3b to
c883b10
Compare
soniasriv
force-pushed
the
add-automotive-inventory-videos
branch
from
September 24, 2026 07:25
c883b10 to
333c0d6
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Companion code for the automotive vertical: one vertical video per vehicle in a dealer inventory.
Rebuilt 24 Sep after review. Derk asked whether these formats match what customers actually render. They did not: production renders are mostly vertical and plain, and the first version was mostly 16:9 with heavy overlays. This version copies a shape measured across the 243 production accounts with 100+ renders in the last 30 days (account-level medians, so one large account cannot set the shape). The photo-listing shape (24 accounts, 30% of that volume) has a median of 9 images, 1-2 html overlays and about 9 transitions per render, about 29 s, vertical.
What it does:
render.mjsreads a JSON stock feed and builds the Edit in code, one 3.2 s clip per photo with a fade and a pan or zoom, cropped to 1080x1920, so a 1-photo and a 7-photo vehicle both render (at least 6 s). Anhtml5card carries year, make, model, trim, price, odometer, transmission and fuel; a secondhtml5badge carries the dealer name; music underneath.Changed from the first version: vertical instead of 1280x720; the S3 option is removed (one account makes 97% of S3 renders, so it is not a pattern to teach).
Verified: prettier clean; every generated Edit JSON passes
shotstack validate; a fresh clone with no key, a wrong key and a badSHOTSTACK_ENVeach print one line and exit 1; a rejected key stops the batch after one line; README claims checked against the code; rendered end to end on stage with the ids below.Stage renders (24 Sep): STK-10482
f2963751-5146-4c8c-8f1e-dc11b56fb9d7(22.4 s, 7 photos), STK-10517bafafcfd-3a6f-495e-9981-44fb9cc586e7(12.8 s, 4 photos), STK-10533677723f9-dba7-46cf-ba0e-6a40a166258d(6 s, 1 photo).All four vertical PRs edit the example list in the root README; keep every bullet when resolving.