PODIE by world of creator homeComponents ↗

Scroll and landing page animations for React

Choose whether an effect belongs to your page or to a self-contained scene. That decision determines who owns scrolling, styles and accessible content.

Native components and isolated scenes

Skiper scroll components are installed as React source and declare their animation dependencies. Codrops entries in this selection run their original scene inside a React iframe wrapper. The wrapper separates scene styles and document scrolling from the host page.

Choose a native React effect when it must share the page layout or respond to your application state. Choose an isolated scene when preserving its visual composition is the priority. A scene iframe does not turn its internal copy into the surrounding page’s semantic content.

Scroll ownership is the integration risk

Card Stack Scroll declares Lenis alongside Framer Motion. Before combining it with an existing smooth-scroll controller, review which component owns the listeners and animation loop. For iframe scenes, give the wrapper an explicit height and test how touch scrolling moves between the two documents.

Keep your main heading and useful explanatory text in the host page. Check a short viewport, reduced motion, keyboard navigation and a static fallback. Build success alone does not establish scrolling quality or Core Web Vitals.

Components to consider

Related reading and evidence

Last updated: .