Features/Interactions

Interactions

Build animations and behaviour without code: pick an event, then chain actions like animate, class, show/hide or scroll.

Interactions are the no-code way to make a site move and react. Each interaction has an event (click, hover, view, while scrolling, page load...) and a list of actions that run on a target. Interactions can be attached to one element, to a class (every element with that class) or to the whole site (Global). They are edited in the Interactions tab of the right sidebar, with a preview button and a Live Mode to tweak values on the canvas. Use them for entrance animations, hover effects, menus, tabs, modals, scroll-driven motion and small logic like setting a cookie or redirecting.

How it works

  • Places: tag (properties.interactions), class (class interactions), global (site setting dh.interactions). The Interactions tab shows Tag, Class or Global depending on what is selected.
  • Interaction fields: Name, Event (default On Page Load), Once (yes/no), Loop (yes/no), Execution (Asynchronous: actions start together; Synchronous: each after the previous completes), Stagger (ms pause between elements), Scope, Pin (While Scrolling only).
  • Action fields: Name, Action type, Target (default self; chain of jQuery-style functions Prev, Next, Parent, Find, Closest, Custom selector), Duration (ms), Delay (ms), Initial State (apply the from state on page load), Variable (for actions that store a value), plus the action's own fields.
  • Timeline: actions can be placed with labels and 'at' positions (<, >, +=100, -=50, a label).
  • Preview runs the actions on the canvas; Live Mode edits values while previewing.
  • Saving is guarded by a revision check: if interactions were changed elsewhere the editor answers 'Interactions were changed elsewhere.
  • New interactions run on engine 2 (dh.interactions engine); Scope and Pin are only available on engine 2.
  • Reduced motion: every event and action declares its behaviour under prefers-reduced-motion (for example animations jump to their end state).

When to use it

  • Fade sections in as they enter the viewport
  • Open and close a mobile menu
  • Animate a card on hover
  • Run a scroll-scrubbed hero animation

Limitations

  • Custom @keyframes cannot be written in a class; motion uses interactions, transitions or plugins.
  • Two transform animations on the same element replace each other (the last one wins).

Availability

  • Works in Designer and MCP.
  • Included in every plan.

How to use it.

  1. Select an element (or a class, or nothing for Global).
  2. Open the Interactions tab in the right sidebar.
  3. Add an interaction and choose its event.
  4. Add actions, set target, duration and delay.
  5. Use Preview or Live Mode, then Save.

Questions.

Do I need GSAP or code?

Can one interaction affect many elements?

Related features.

No card needed

Build it today.Pay when it goes live.

Every feature is unmetered while you build. Checkout opens the first time you publish.