feat(demo): scene protocol docs page + SEO pass - #26
Merged
Conversation
- New /scene-protocol page: manifest format, postMessage wire protocol, trust boundaries, host/scene/embed usage. Route avoids /scenes, which the static demo scenes.html shadows in both dev (Vite html resolution) and prod (asset html_handling beats the SPA fallback). - The SPA served one head for every URL, so crawlers and link scrapers that skip JS never saw per-page meta. demo/seo.json now drives a post-build prerender (pnpm build:demo) stamping per-route title/description/canonical/OG into a static HTML copy per route, plus sitemap.xml, robots.txt, an OG image, and runtime head sync on client-side navigation. CI builds the demo to keep it honest. - Remove the film-grain overlay. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
kino | dda37af | Commit Preview URL Branch Preview URL |
Jul 21 2026, 05:00 PM |
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
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.
What
Three things in one docs-site pass:
New docs page:
/scene-protocol. Documents the scenes system end to end: theSceneManifestformat (contiguity rule, trailing-silence semantics, sidecar captions/storyboard), thekino:-namespaced postMessage wire format with a per-message table and the ready→init handshake, trust boundaries on both sides of the iframe (origin + source checks, the document-pip opener case),createSceneHostusage, scene authoring against theSceneClock, and theScenesPlayerembed. Carries the same copy-as-markdown mirror as the other pages. Route is/scene-protocolrather than/scenesbecause the static demoscenes.htmlshadows/scenesin both dev (Vite html resolution) and production (assethtml_handlingruns before the SPA fallback).SEO. The SPA served one identical head for every URL — crawlers and link scrapers that don't execute JS never saw per-page meta. Now
demo/seo.jsonis the single source of truth for per-route title/description, consumed twice:demo/prerender.ts(newpnpm build:demo= vite build + prerender) stamps title, description, canonical, OG, and Twitter tags into a static HTML copy per route (install.html,scene-protocol.html, …) that the Worker's html handling serves for the clean URL, and emitssitemap.xml. Throws if a tag pattern stops matching.usePageMetaindemo/seo.tskeeps the head in sync during client-side navigation and marks the 404 routenoindex.Plus: full default head in
index.html(OG/Twitter cards withog.pngfrom the repo banner),robots.txt, real meta onscenes.html,noindexon thescenes-host.htmlfixture, and a CI step that runspnpm build:demoso the prerender pass stays exercised.Film grain removed —
film-grainoverlay span + its CSS utility are gone.Why not TanStack Start
A framework migration rewrites the site and the deploy model to fix what is, for a five-page docs site, a head-tags problem. The prerender pass gets crawler-visible per-route meta with zero new dependencies. If full static HTML bodies ever matter, that's the point to revisit SSG/SSR.
Verification
pnpm format:check,typecheck,lint,test(188) all green;pnpm build:demooutput inspected — per-route titles/canonicals and sitemap correct.noindex; zero console/page errors; grain element absent.🤖 Generated with Claude Code