The Mighty Transition block: smooth scroll animations in Rise without code

Articulate Rise is built around one motion primitive: scroll. You scroll down, the next block appears. That's it. There's no slide transition, no fade between sections, no parallax — and no toggle in the editor to add one. For a long time the only way to get a real animated transition in Rise was to inject CSS into a Custom HTML block and pray that nothing else broke.

The Mighty Transition block replaces all of that with a dropdown. Drop it between any two existing blocks, pick a transition style, and that's the whole interaction.

The five transitions Mighty ships#

• Fade — the previous block softly fades out while the next one fades in. Use for editorial pacing — moving from a section header into the supporting content.
• Slide-up reveal — the next block slides up over the previous one as the learner scrolls. The default "feels animated but doesn't distract" choice.
• Parallax — the previous block scrolls slower than the page, so the next block appears to slide over the top of it. Best between an image-heavy block and the next concept.
• Zoom out — the previous block shrinks slightly as it leaves the viewport. Reads as "we're done with that idea, here's the next one." Subtle. Don't overuse it.
• Flip — the previous block flips on a horizontal axis to reveal the next. Use sparingly. Great for an answer reveal or a "versus" comparison; not great between two paragraphs of text.

How it actually works#

The Transition block adds a thin marker into the Rise course structure that survives the SCORM publish step. At runtime, a tiny shim (loaded with the course, not from a CDN) reads the marker and applies the right CSS transform as the learner scrolls. There is no Mighty dependency at view time — your learners don't install anything. Once you publish, your course stands on its own.

Important consequence: the transition is configured in the editor and persisted in the published course. You don't have to re-apply anything on each publish, and it ships to Review 360, Reach 360, and your own LMS the same way.

When to reach for it#

We see customers misuse transitions one of two ways: either they don't use them at all (the course feels like a wall of scroll), or they put a different transition between every block (the course feels like a flipbook). The sweet spot is one transition style per section, used between the section's hero block and its first body block, and again between the last body block and the next section.

Gotchas#

• Don't transition into a quiz. Rise quizzes have their own scroll-snap behavior. A fade or zoom right before a quiz block fights with that and feels janky. Park transitions in your editorial sections.
• Test on mobile. Parallax and flip in particular look very different on a phone than they do in the desktop editor preview. We have a one-click "open on phone" QR code in the Mighty toolbar to make this easy.
• Reduced-motion learners. Mighty automatically respects the OS-level "reduce motion" setting. Learners who have that on get a static cut between blocks instead of the transition. You don't have to configure anything.

Worth knowing#

The Transition block is the most-installed Mighty block in the public Discover library. If you want to see how other teams are using it before you commit to a style, browse the Transition collection on the Studio page — every template there is forkable into your own Rise course.