From 62d368d69bca4e2498c9cd59472f2135d3689a11 Mon Sep 17 00:00:00 2001 From: James Date: Wed, 22 Apr 2026 18:31:19 +0000 Subject: [PATCH] docs(compositions): remove Variables section referencing unshipped syntax MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The documented `data-var-*` attribute pattern is not implemented — the parser reads `data-composition-variables` (schema JSON on ) and `data-variable-values` (instance JSON on the composition element), not per-attribute `data-var-`. There is no Studio UI, example composition, or author-facing consumer API for variables today, so the section left readers with no way to actually use what it described. Cut the section for now. The underlying parser/generator support stays in place and can be re-documented once there is a real author-facing surface (Studio UI + example + consumer pattern). Closes #416 --- docs/concepts/compositions.mdx | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/concepts/compositions.mdx b/docs/concepts/compositions.mdx index b74c75a20..2dcc96f3e 100644 --- a/docs/concepts/compositions.mdx +++ b/docs/concepts/compositions.mdx @@ -125,16 +125,6 @@ Every composition has two layers: Never use scripts to play/pause/seek media elements or to show/hide clips based on timing. The framework handles this automatically from data attributes. Scripts that duplicate this behavior will conflict with the framework. See [Common Mistakes](/guides/common-mistakes) for examples. -## Variables - -Compositions can expose variables for dynamic content: - -```html compositions/card.html -
-``` - -Variables make compositions reusable as [examples](/examples) -- the same composition can render different content by injecting variable values at render time. - ## Listing Compositions Use the [CLI](/packages/cli) to see all compositions in a project: