Sections · Component Template
Integration Beams
Sources on the left, destinations on the right, and a hub that routes every event between them. Comets of light travel the wires, and each one that arrives changes a number.
Live demo
Point at a source to trace its routes. Click it to send a burst of events.
The Prompt
Build an integrations diagram that is visibly carrying traffic. Four glass source cards on the left, a hub in the middle, four destination cards on the right, joined by fine curved wires. Events travel the wires as small comets of light in each source's color: one arrives, the hub flares in that color and throws a ring, and the event fans out to every destination that source is routed to, whose counters tick and borders flash. Point at a source and only its routes stay lit; click it and it fires a burst. The comets are plain elements moved by CSS motion path, and the wires are measured from the real boxes, so the layout can reflow freely. It is for Tributary, an event router. Match my project's existing stack, conventions, and design tokens. If there are none, output a single HTML file with inline CSS and JavaScript and zero dependencies. No canvas, no animation library.
LOOK
- Page #05060A, text #F2F2F5, secondary at 64%. Four source colors carry all the color on the page: cyan #4DD8FF, violet #9B7BFF, lime #B6F36A, coral #FF7A66.
- Glass cards: tint #1A1D2A at 48%, backdrop blur 22px, a hairline edge, radius 18px. Two large blurred discs of blue and violet drift slowly behind the diagram so the glass has light to bend. Film grain at 9%.
- ui-sans-serif, system-ui. Heading "Collect every event once. Send it everywhere." at clamp(38px, 5.2vw, 84px), weight 640, letter-spacing -0.05em.
- Header row: the heading left; right, one paragraph ("Tributary sits between the places your data is made and the tools that need it. Point at a source to see where its events go. Click one to send a burst.") and a pill "Connect a source".
THE DIAGRAM
- A three-column grid with a wide gap: sources, hub, destinations. Each node has a 40px tinted icon tile (icon drawn with clip-path), a name and a running count ("38,205 today").
- Sources, as buttons: Web app, iOS and Android, Backend services, Billing webhooks. Destinations: Warehouse, Product analytics, Lifecycle email, On-call alerts.
- Routing: Web app goes to Warehouse, Product analytics and Lifecycle email. iOS and Android to Warehouse and Product analytics. Backend services to Warehouse and On-call alerts. Billing webhooks to Warehouse, Lifecycle email and On-call alerts.
- Hub: a rounded square about 120px, dark gradient, top highlight, a simple merge glyph, a soft outer glow whose color is a custom property, and under it "3,033 events a second", wandering by a few hundred.
- Under the diagram one status line. At rest: "Four sources, four destinations, one place to change the plumbing." While a source is active: "Backend services sends to Warehouse and On-call alerts."
WIRES
- An SVG laid over the diagram with a viewBox equal to its pixel size. After layout, measure every node and the hub with getBoundingClientRect relative to the diagram.
- Each wire is one cubic Bezier from a source's right edge to the hub's left edge, or from the hub's right edge to a destination's left edge, with both control points at the horizontal midpoint so it leaves and arrives level. Spread the four attachment points on the hub 9px apart.
- Source wires are stroked in their source's color at 20% opacity; destination wires in white at 10%. Re-measure on resize and after the entrance transition ends.
- Under 760px the columns stack (nodes two by two) and the same code draws vertical curves from bottom edges to top edges.
PACKETS
- Each event is one small element: 34 by 3px, a gradient from transparent through the source color to white at the head, with a glow. Give it offset-path: path("…") using the wire's own path data, offset-rotate: auto and offset-anchor at its head, and animate offset-distance from 0% to 100% with the Web Animations API over 620 to 880ms on a slow-in, fast-out curve. Remove it when it finishes.
- On arrival at the hub: set the hub's glow color, play a ring (scale 0.92 to 1.5, fading, 520ms), then launch one packet down each routed destination wire, 70ms apart.
- On arrival at a destination: add one to its count and flash its border and glow in the packet's color for 700ms.
- Traffic: every 230ms pick a source by weight (Web app and Backend services four times as often as the others) and emit one event. Source counts tick when they emit.
INTERACTION
- Hovering or focusing a source: it slides 6px toward the hub and takes a colored outline; the other sources dim to 40% using :has(); its own wire and its destination wires go to 75% opacity in its color while every other wire drops to 5%; and all traffic comes from it until the pointer leaves.
- Clicking a source sends ten events 55ms apart.
- Cards carry a pool of light and a bright stretch of border under the pointer.
MOTION
- Load: heading words rise from clipping boxes; the paragraph, the diagram and the status line sharpen from a blur and settle on a CSS spring (a damped spring sampled into linear()).
ACCESSIBILITY
- Sources are real buttons, reachable by Tab, and focus does everything hover does. The status line is a status region.
- The wire SVG, packets and icons are aria-hidden. Counts are real text.
- Stop emitting while the tab is hidden.
- prefers-reduced-motion: no packets, rings or counter changes. Hover and focus still light the routes and update the status line.
NEVER
- No logos of real products. Sources and destinations are kinds of thing, with drawn icons.
- No wires drawn at fixed coordinates.
- No dashed "marching ants". Movement is discrete events.
- No pulses with nowhere to go: every packet that leaves a source arrives somewhere and changes a number.
- CopyThe full prompt, one click.
- PasteInto Cursor, Claude Code, or any agent.
- CompareAgainst the live demo above.