Skip to main content
An order target moves existing elements. Each variant is a complete sequence of the same item IDs.

Map the items

For this page:
Define the movable items and allowed orders:
Save this target through configuration as code and bind it to the page. The sponsor stays in its slot. Mapped nodes move with their existing handlers and state.

When an order can change

Automatic ordering stops once the list has been visible or interacted with. It also skips a currently visible or focused list. A manual preview can still show each order. Use this for sections below the fold. If the initial order above the fold is essential, use server rendering.
Each selector must identify one direct child, either by matching the child or a descendant. Different items must resolve to different children. Every variant includes every item ID exactly once.Missing, ambiguous, or replaced nodes invalidate the mapping. Appended items stay in place. Restoration returns captured nodes to their original mapped slots.
Without order.items, the legacy adapter requires a data-section ID on every child and reorders all children. It lacks the native adapter’s unmapped-slot preservation and visibility lock.For omitted blocks and multi-pass selection, use the separate funnel library.