
Block Transition
Transitions
A vertical page transition that lifts one route into the next for brand sites, campaign pages, and editorial journeys that need a clean upward motion.
Ascend Transition makes the route change feel like an upward handoff.
Instead of cutting from one page to the next, a solid colour panel rises from the bottom of the screen, grows to full size, then fades away to reveal the destination, and the navigation moment feels cleaner than a hard fade.
Use Ascend Transition when a brand, portfolio, editorial site, or launch page wants route changes to feel light, elevated, and directional. The page job is upward continuity: the visitor should understand that the current page is leaving and the next one is arriving, without feeling blocked by the transition.
The production risk is timing. A vertical route transition can quickly feel like scroll-jacking if it is too slow, too tall, or too similar to normal page scroll. The transition should be brief, unmistakably tied to navigation, and respectful of reduced motion.
(Next.js App Router only. Requires next-transition-router for route-transition lifecycle hooks and renders its TransitionRouter itself, so no separate provider is needed. This effect will not function in plain React or in the Next.js Pages Router.)
import AscendTransition from "@/components/effects/ascend-transition";import React from "react"; export default function layout({ children }: { children: React.ReactNode }) { return ( <AscendTransition> {children} </AscendTransition> );}A product launch microsite can use Ascend Transition between short campaign pages. A colour panel rises over each route and fades away on the next, giving the site a light, progressive rhythm. The outcome is elevation: navigation feels intentional without becoming heavy.
Not for long documentation, dashboards, checkout flows, product apps, or any route where users navigate frequently and expect instant response.
Not for pages where upward motion would be confused with normal scrolling.
Use transform and opacity, keep duration short, avoid forcing layout during route change, and clean up route listeners or animation timelines after completion.
Move focus to the destination main region or heading after navigation. On mobile, reduce travel distance so the transition does not feel like forced scroll. Reduced-motion users should get instant navigation or a short fade.
| Prop | Type | Default | Description |
|---|---|---|---|
bgColor | string | #ffffff | Background color of the covering panel that rises and reveals the new page. |
duration | number | 0.9 | Base duration of the rise/reveal phase; related scale-up and fade timings scale with it. |
Use it when a route change should feel like a clean upward handoff between brand, campaign, or portfolio pages.
Ascend Transition is tied to route change, not page scrolling. It should happen briefly during navigation and then stop.
By default the panel wipes up over 0.9s, holds for 0.12s, then fades out over 0.35s, roughly 1.4s in total. The duration prop (default 0.9) scales every phase, so lower it if navigation feels delayed.
Mount it in your root layout around {children}, as in the usage code. Ascend Transition renders TransitionRouter from next-transition-router itself, so it stays mounted across navigations and no separate provider or template is needed.
With reduced motion enabled, the component skips the clip wipe and scale. The colour panel stays hidden, so navigation waits about 0.2s and the new page appears without a visible transition.
Yes. A custom version should define vertical distance, easing, route integration, focus restoration, scroll behavior, mobile fallback, reduced-motion handling, source handoff, and implementation notes.
Need a custom effect? Tell us what to create.