10 posts tagged with "Animation"

The question: We're adding an "Add entrance animations" checkbox to the Site Converter that gives a converted page sequential reveal-on-scroll motion. The user framed it as "use the deterministic with the help of the local AI." Where should the intelligence actually live — does the AI decide the animations, or does the deterministic converter, with the AI as a helper?

The question: Now that image-picker choices in the popover can be deselected (clearing the selection means "none"), should we remove the standalone "Enable page transitions" style switches across Site-wide UX and let "no image selected" mean "off"?

The question: A converted button (scandi-haven-shop's hero "Shop Now") dropped its hover animation — a translucent overlay that rises from the bottom to fill the button. The effect lives entirely on .btn-premium::after + .btn-premium:hover::after, which getComputedStyle(el) never exposes. Once we teach the capture to harvest those rules, what do we DO with them: reproduce the source CSS verbatim on the button, or map it to one of the theme's named hover-effect presets?

The question: Phase 0 of the Animation Engine's motion roadmap is "make scrolling feel effortless everywhere, and give every scroll-driven effect one shared clock." That raised two forks. (1) Where should the new inertia smooth-scroll live — a new engine module, or an extension of the theme's existing anchor-link "Smooth Scroll"? (2) How do we unify the scroll-reactive modules so they stay in lockstep — port them all to GSAP's ScrollTrigger, or reuse the engine's own shared animation loop?

The question: the Scroll Motion Custom Code (Motion Snippet) field lets an author hand-write GSAP, but a newcomer faces a blank editor with no idea of the API surface. A code generator would help — but how much of GSAP should it expose: everything (a general GSAP playground), or only what the field actually gives you?

The question: the roadmap's Phase 1 is "a real motion timeline" for the builder — keyframing several properties over one scrubbable axis. How much timeline do we actually build: a dynamic keyframe editor, or something smaller that still covers the need? And what drives the scrub?

The question: the Animated Icons extension has per-technology toggles (Lottie, Rive, Animated SVG, Animated raster). Should they live on the extension's own Settings page, or move into Theme Settings → Icons — perhaps as a new tab?

The question: the Animated icon kind plays Lottie animations from a URL/upload as raw Lottie JSON. Should it also accept .lottie (dotLottie) files, and would that help pages that show many animated icons at once?

The question: a reference site's scroll section plays as a sequence of batches — each batch is a set of photos that scatters onto the surface, holds around a centered line of text, then scatters away as the next batch (with different photos and a different line) arrives. How do we build that so each batch has its own images, its own text, and its own entrance/exit — and stays editable in the builder?

The question: a reference site's scene sections look like a film camera slowly glides across the scene as you scroll — a genuinely cinematic touch. Is that a real 3D camera move (rendered footage), and if not, how do we reproduce it in UnysonPlus without baking a video?