Interface craft
Choreograph the scroll, protect the reading
Use GSAP to introduce rhythm and emphasis while keeping content visible, navigation predictable, and reduced motion deliberate.
Scroll animation works best when it explains the page’s structure. A diagram can reveal its stages as an accompanying explanation advances. A section heading can settle into place as a new subject arrives. Motion has a job when it directs attention to a relationship the reader needs to understand.
Start by writing that job down. “Make it feel premium” leaves every decision open. “Show how these three components connect” gives you something concrete to evaluate.
Design the still version first
Lay out the complete page with every important word visible. Check the reading order and whether links remain easy to identify. Make sure a reader can understand the diagram in its final state.
Only then decide which transitions improve the explanation. A static version is also a useful reference: if the moving version takes longer to understand, the choreography needs revision.
Choose a small motion vocabulary
Use short entrance movements for orientation and reserve larger changes for a meaningful shift in the story. Repeating one quiet pattern can make a page feel coherent. Animating every card independently can make the reader wait for content they have already chosen to read.
GSAP’s ScrollTrigger can connect animations to scroll positions, scrub progress with scrolling, and pin elements. These are distinct tools. A brief reveal rarely needs pinning; a staged explanatory diagram may benefit from it.
Before pinning a section, ask how much scrolling it demands and whether that space buys real understanding. Keep navigation and the next section easy to reach.
Plan reduced motion as a complete composition
A reduced-motion version should present the same information in a stable arrangement. Put a diagram in a useful final state, show text immediately, and remove movement that is merely decorative.
gsap.matchMedia() supports conditional animation setup through media queries and reverts its collected animations when those conditions stop matching. Its documentation includes reduced-motion examples. Use those conditions to define a coherent alternate presentation rather than only shortening every animation.
Check the awkward moments
Scroll quickly past a section, then return. Resize the window halfway through an animation. Open a link directly to a lower heading. Follow links using the keyboard. Switch the operating system’s motion preference and confirm that the page still makes sense.
These are proposed checks for an implementation, not claims that this site’s motion has passed them. They reveal issues that a smooth top-to-bottom demonstration can hide: overlapping text, stranded pinned elements, or focus landing outside the visible area.
The final editorial test is simple. Read a full article without thinking about the animation. Motion has done its work when the ideas remain the memorable part.