Files
hyperframes/registry/components/bottom-up-letters/demo.html
Miguel Ángel 406bf316a3 fix(catalog): make component previews answer their variables panel (#3323)
* fix(catalog): make component previews answer their variables panel

Every control on a component's catalog page did nothing. Asking
caption-camera-follow for a violet accent rendered gold, and so did green
and blue, on 166 of the 168 components that declare variables.

A component ships a snippet, which is what the page hands you to paste and
which carries the declaration plus the script that turns a chosen value
into a CSS custom property, and a demo.html which stages and animates it.
The preview is built from the demo, and the demo was authored as a copy of
the snippet rather than a reference to it. The copies drifted until almost
none of them carried the declaration or the reader, so the payload for that
page never contained the word violet at all.

Components come in two shapes, so the repair does too.

123 ship a snippet that registers its own paused timeline. That snippet is
a whole piece, so their preview is now built from it and carries markup,
variables and motion together.

45 are markup plus a commented recipe, where the demo owns the motion.
Those demos now carry the snippet's declaration, reader and var-driven CSS
in the registry itself, written by scripts/catalog/sync-demo-variables.ts.
Nothing is patched in at build time.

A test runs that tool in dry mode and fails when a demo has drifted again,
naming the command that repairs it. It also asserts it inspected more than
a hundred components, because a check that silently matches nothing is how
this rotted in the first place.

Measured by rendering every payload in a real player rather than by reading
markup: payloads declaring their variables go from 2 of 168 to 168 of 168,
previews that animate go from 166 to 167, and nothing that moved stopped
moving. ascii-render-pass and star-rating-fill render a still frame when
built from their snippet, so they keep the demo path as a recorded
exception and stay in the state they were already in.

* refactor(catalog): give the preview pipeline one lookup and one entrypoint guard

Follow-up on the same branch, no behaviour change: 42 tests still pass and
`sync-demo-variables --check` still reports all 168 components clean.

The payload generator and the demo sync had each grown their own copy of
"given a component directory, find the snippet and the demo". Both now call
`componentFiles`, which is the same duplication-by-copying that broke the
previews in the first place.

Both catalog generators also carried a byte-identical 12-line guard for
"only run main() when this file is the entrypoint". That clone was already
in the tree, but nothing had touched both files at once before, so it had
never surfaced. It is now `runAsCommand`, and the sync script's variant of
the same condition is `isEntrypoint`.

The rest is flattening: the layering guards read as a table of conditions
instead of a chain, the reporting splits by what it reports, and the entry
resolution comes out of `buildPayload` rather than being spliced into it.

Also runs the formatter over the demos this branch rewrote. Whitespace only,
and `notes-typing` is the only component demo that renders pre-formatted
text, which this does not touch.
2026-08-18 01:37:46 -04:00

166 lines
7.4 KiB
HTML
Vendored

<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=1920, height=1080" />
<title>Bottom Up Letters - Demo</title>
<script src="https://cdn.jsdelivr.net/npm/gsap@3.14.2/dist/gsap.min.js"></script>
<style>
* {
box-sizing: border-box;
}
html,
body {
margin: 0;
width: 1920px;
height: 1080px;
overflow: hidden;
}
#demo {
width: 1920px;
height: 1080px;
display: grid;
place-items: center;
background: #16120e;
color: #f7ead6;
font-family: Inter, system-ui, sans-serif;
}
.hf-bottom-up-letters {
display: inline-block;
font-size: 180px; /* ponytail: scaled up from 126px — fills ~65% of 1920px frame width */
line-height: 1;
font-weight: 900;
letter-spacing: -0.02em;
}
.hf-bottom-up-letters-char {
display: inline-block;
opacity: 0;
transform: translate3d(0, 0.85em, 0);
will-change: transform, opacity;
}
</style>
</head>
<body>
<div
id="demo"
data-composition-id="bottom-up-letters-demo"
data-width="1920"
data-height="1080"
data-duration="4"
data-composition-variables='[
{ "id": "unit", "type": "enum", "role": "content", "label": "Split unit", "description": "What each animated span holds. Letter staggers glyph by glyph, word keeps whole words intact.", "default": "letter", "options": [{ "value": "letter", "label": "Letter" }, { "value": "word", "label": "Word" }] },
{ "id": "direction", "type": "enum", "role": "motion", "label": "Direction", "description": "Where each span starts. Up starts below the baseline and rises, down starts above and drops.", "default": "up", "options": [{ "value": "up", "label": "Up" }, { "value": "down", "label": "Down" }] },
{ "id": "travel", "type": "enum", "role": "motion", "label": "Travel", "description": "How far each span starts from its resting position, from 0.45em to 1.5em.", "default": "standard", "options": [{ "value": "close", "label": "Close" }, { "value": "standard", "label": "Standard" }, { "value": "far", "label": "Far" }] }
]'
>
<div class="hf-bottom-up-letters">Build with motion</div>
<script>
(function () {
"use strict";
var vars =
window.__hyperframes && window.__hyperframes.getVariables
? window.__hyperframes.getVariables()
: {};
// Unrecognised overrides return to their declared defaults.
function pick(table, value, fallback) {
return Object.prototype.hasOwnProperty.call(table, value) ? value : fallback;
}
var travels = { close: "0.45em", standard: "0.85em", far: "1.5em" };
var directions = { up: "1", down: "-1" };
var units = { letter: true, word: true };
var travel = travels[pick(travels, vars.travel, "standard")];
var direction = directions[pick(directions, vars.direction, "up")];
var unit = pick(units, vars.unit, "letter");
document.querySelectorAll(".hf-bottom-up-letters").forEach((el) => {
el.style.setProperty("--hf-letters-travel", travel);
el.style.setProperty("--hf-letters-direction", direction);
if (el.dataset.hfLettersReady === "1") return;
const text = el.textContent || "";
el.textContent = "";
const parts = unit === "word" ? text.split(/(\s+)/) : Array.from(text);
for (const part of parts) {
if (part === "") continue;
if (unit === "word" && /^\s+$/.test(part)) {
el.appendChild(document.createTextNode(part));
continue;
}
const span = document.createElement("span");
span.className = "hf-bottom-up-letters-char";
span.textContent = part === " " ? "\u00a0" : part;
el.appendChild(span);
}
el.dataset.hfLettersReady = "1";
});
})();
</script>
<script>
document.querySelectorAll(".hf-bottom-up-letters").forEach((el) => {
const text = el.textContent || "";
el.textContent = "";
for (const char of text) {
const span = document.createElement("span");
span.className = "hf-bottom-up-letters-char";
span.textContent = char === " " ? "\u00a0" : char;
el.appendChild(span);
}
});
const tl = gsap.timeline({ paused: true });
tl.to(
".hf-bottom-up-letters-char",
{ opacity: 1, y: 0, duration: 0.48, ease: "back.out(1.7)", stagger: 0.025 },
0.45,
);
window.__timelines = window.__timelines || {};
window.__timelines["bottom-up-letters-demo"] = tl;
</script>
</div>
<style>
element below; the runtime collects every element carrying
data-composition-variables, not just the document root. The script reads each
value, falls back to the declared default on anything missing or
unrecognised, and either changes how the text is split or writes a custom
property the CSS consumes. The timeline recipe below is untouched by them: it
still tweens opacity and y back to rest, and these decide what a single
stagger step covers and where rest is travelled from.
- unit (letter | word, default letter): what each animated span holds.
letter staggers glyph by glyph; word keeps whole words intact, so a long
line reads instead of shimmers.
- direction (up | down, default up): where the spans start. up starts
below the baseline and rises into place, down starts above and drops.
- travel (close | standard | far, default standard): how far each span
starts from rest, from 0.45em through 0.85em to 1.5em.
On every default the result is identical to the original: one span per
character, each starting 0.85em below the baseline.
-->
<style
data-composition-variables='[
{ "id": "unit", "type": "enum", "role": "content", "label": "Split unit", "description": "What each animated span holds. Letter staggers glyph by glyph, word keeps whole words intact.", "default": "letter", "options": [{ "value": "letter", "label": "Letter" }, { "value": "word", "label": "Word" }] },
{ "id": "direction", "type": "enum", "role": "motion", "label": "Direction", "description": "Where each span starts. Up starts below the baseline and rises, down starts above and drops.", "default": "up", "options": [{ "value": "up", "label": "Up" }, { "value": "down", "label": "Down" }] },
{ "id": "travel", "type": "enum", "role": "motion", "label": "Travel", "description": "How far each span starts from its resting position, from 0.45em to 1.5em.", "default": "standard", "options": [{ "value": "close", "label": "Close" }, { "value": "standard", "label": "Standard" }, { "value": "far", "label": "Far" }] }
]'
>
.hf-bottom-up-letters {
display: inline-block;
}
.hf-bottom-up-letters-char {
display: inline-block;
opacity: 0;
transform: translate3d(
0,
calc(var(--hf-letters-travel, 0.85em) * var(--hf-letters-direction, 1)),
0
);
will-change: transform, opacity;
}
</style>
</body>
</html>