# ``
An element whose children are **real HTML**: the browser lays them out at the element's box size and the result is drawn into the box via the [html-in-canvas](https://github.com/WICG/html-in-canvas) API. The Diffusion Studio app ships with this API enabled, so `` is always available — reach for it liberally. It is the recommended way to build motion graphics, overlays, and any UI-heavy content: styled cards, tables, code blocks, flex/grid layouts — anything painful to assemble from `` and ``.
Driving the markup with an [anime.js](https://animejs.com) timeline is **recommended** — it keeps the animation frame-accurate: build the timeline with `autoplay: false`, then `seek` it from the [`useTicker`](./lifecycle.md#useticker) playhead so it follows scrubbing and exports rather than the wall clock. anime.js works in milliseconds, so the playhead is scaled by 1000 on the way into `seek`.
```tsx
import { createTimeline, type Timeline } from "animejs";
import { useTicker } from "@diffusionstudio/jsx";
import { createEffect, onMount } from "solid-js";
export default function Intro() {
const { time } = useTicker();
let index!: HTMLSpanElement;
let label!: HTMLSpanElement;
let tl!: Timeline;
// anime.js resolves targets at tween creation and refs are only assigned
// during render, so build the timeline in onMount — it runs before the
// effect below.
onMount(() => {
tl = createTimeline({ autoplay: false })
.add(index, { opacity: { from: 0, to: 1 }, x: { from: -24, to: 0 }, ease: "outQuad", duration: 400 }, 0)
.add(label, { opacity: { from: 0, to: 1 }, ease: "outQuad", duration: 400 }, 200);
});
createEffect(() => tl.seek(time() * 1000));
return (
01Introduction
);
}
```
Prefer this timeline over hand-animating styles: keep the markup static and let the paused anime.js timeline own every moving value, so one `seek` keeps the whole host frame-accurate. A static `style` may be a plain string, but one spanning multiple lines has to be a template literal in braces (`style={`…`}`), as above. Reach for a derived style only for values the timeline does not drive, and write it as a **style object** (`style={{ color: c() }}`) rather than interpolating the signal into a style string, so each property updates independently.
The `` box carries all [common props](./elements.md#common-props). Its paint child form, [``](./paints.md), draws the same reactive HTML onto any existing filled geometry; `` is just a `` that carries one.
## Reactivity
The children are part of the project's Solid graph: signals in attributes and text update the live DOM, and the drawn content follows on the next frame. A mounted project stays live, so the graph keeps running and `useTicker` or timers can drive the markup:
```tsx
const [count, setCount] = createSignal(0);
setInterval(() => setCount((c) => c + 1), 1000);
{count()}
```
## Images
`` takes the same sources as a composition [`src`](./media.md): a path, an asset id, or a URL. The host resolves them exactly as it does for [``](./image.md)
## Props
`` takes all [common props](./elements.md#common-props). `` takes:
| Prop | Type | Default | Meaning |
| ---- | ---- | ------- | ------- |
| `opacity` | `number` | `1` | Paint opacity, `0`-`1`. |
Like all paints, `` stacks with siblings in document order and clips to the parent's box (including `cornerRadius`).
## Persistence and export
The module is re-executed in every context: on reload, export, and [`capture`](../tools/capture.md) the engine re-executes it and rebuilds the DOM content in that context. Exports wait for the browser's rendering update before sampling each frame, so the drawn HTML appears in the output; ticker-driven signals follow the playhead and animate frame-accurately. This assumes the module's structure is deterministic (`Math.random()`/`Date.now()` must not decide the shape of the tree).
## Requirements and limitations
- `