Enhance Your Rise Courses with Mighty Snippets—No Code Required

Sometimes the smallest customization is what makes a Rise course really stand out: a shimmer on a key button or a confetti moment after a checkpoint. Mighty Snippets gives you a way to add those enhancements without writing the code yourself.

How to Enhance Your Rise Course with Snippets — Zero Code!

If you’ve ever looked at a Rise block and thought, “I wish I could add a custom behavior here,” Snippets are built for that exact middle ground: more flexible than native Rise settings, but much more approachable than hand-writing custom JavaScript.

What Mighty Snippets are#

Mighty Snippets are packaged code enhancements that you can import into a Rise 360 course, then enable and scope to the right place. To add a Mighty Snippet, you’ll download what you want from the Maestro Community Code Catalog, then import the snippet to the Mighty PowerUps Custom Code area.

When you use a snippet, you aren’t pasting or editing code line by line. You are importing a snippet file, then using Mighty’s controls to decide where that snippet applies.

In the demo video, Maestro CEO Nate Norman shows some example snippets from the Code Catalog that add:

• A confetti drop when a learner clicks a button
• A subtle shimmer effect on Rise buttons
• An emoji reaction interaction that persists in the learner’s browser
• A snowflake background effect

This is what Snippets are best at: small, focused course enhancements that sit on top of Rise’s existing blocks and behaviors.

Where Snippets fit in the Rise workflow#

Rise is excellent for building clean, responsive lessons quickly. But there are moments where native Rise doesn’t offer the exact behavior or finish you want. That’s where Mighty Snippets come in.

Use Snippets when you want to:

• Add a specific visual or interactive behavior to an existing Rise block
• Reuse a proven effect from the Maestro Code Catalog
• Avoid maintaining custom code yourself
• Scope an enhancement to a whole course, a lesson, or a specific block
• Prototype a polished interaction quickly for stakeholders

Don’t reach for Snippets when a native Rise setting already does the job. If you only need to change theme fonts, colors, or button styling that Rise already supports, start there. Snippets are for the layer Rise does not expose natively.

Step 1: Find a snippet in the Maestro Code Catalog#

Mighty Snippets live in the Maestro Community Code Catalog. And because this is a community space, other learning professionals are uploading new snippets all the time.

Here’s how to find the best snippet for your needs:

1. Go to Maestro Community Code Catalog.
2. Use the category filter for Snippets.
3. Choose the snippet you want to use.
4. Read the instructions on that snippet’s page.
5. Download the provided JSON file or files.

Quick note: Some effects are not a single file. For example, in the confetti snippet, there are two JSON files:

• One snippet makes the confetti library available
• The other snippet fires the confetti effect on a button click

You need both for the effect to work.

This two-part pattern is a common code reality hidden behind a friendlier workflow: some effects need a library or dependency available before the visible behavior can run. Mighty does not make you write that setup code, but you still need to import the supporting snippet when the instructions call for it.

Step 2: Import the snippet into Mighty#

Once you have the JSON files downloaded, go back to your Rise course.

1. Open the course in the Rise editor.
2. Make sure Mighty is installed and active.
3. Open PowerUps.
4. Select Custom Code.
5. Find the Snippets area.
6. Click Import Snippet.
7. Select the downloaded JSON file.
8. Click Open.

Mighty adds the snippet to your list in a disabled state. This means importing a snippet does not immediately alter your course. You get a chance to inspect it, set the scope, and intentionally enable it.

If you imported a duplicate or the wrong file, you can delete it from the Snippets list before it ever affects the course.

Step 3: Enable only what you need#

After importing, open the snippet and review its settings. For a no-code workflow, the main things you care about are:

• Is the snippet enabled?
• What is its scope?
• Does this snippet need to run across the entire course, or only in one place?

For the Make confetti library available snippet, the correct scope is the entire course. That makes the confetti library available wherever the course needs to use it—it’s the underlying resource that the button-click snippet depends on.

So, for a snippet that merely makes an effect available, you’ll want to:

1. Click Edit.
2. Confirm the scope is set to Entire course.
3. Enable the snippet.
4. Save.

Step 4: Scope the visible behavior to the right block#

After the “make confetti library available” snippet is activated and scoped for the entire course, you can strategically scope the second snippet: “fire confetti on button click.”

In the demo, Nate scopes this snippet to Blocks and selects the specific Rise block containing the Continue button.

Here is the workflow:

1. Open PowerUps.
2. Go to Custom Code.
3. Find the imported Fire confetti on button click snippet.
4. Click Edit.
5. Set the scope to Blocks.
6. Scroll to the block list.
7. Check the block that contains the button you want to target.
8. Save.
9. Run or preview to test the effect.

In the demo, the selected block is the one with the Continue button. When the learner clicks Continue, the confetti drops.

In short: Scope the snippet broadly when it needs to be available, but scope the learner-facing behavior narrowly when it should only happen in a specific moment.

A good rule of thumb:

• Use Entire course for resources or effects that truly need to be globally available.
• Use Lesson scope when the effect belongs to one section of the course.
• Use Block scope when the behavior should attach to a specific interaction, button, or moment.

Block scope is especially useful in Rise because courses often repeat similar patterns. You may have several Continue buttons, button blocks, or scenario moments. Scoping to the exact block prevents an enhancement from appearing in places you did not intend.

What “zero code” really means here#

Zero code does not mean there is no code involved. It means you aren’t the one writing it.

The JSON file you import contains the snippet. Mighty reads that package and gives you a course-author-friendly way to manage it: import, enable, scope, save, and test.

That is an important distinction for teams with brand, accessibility, or IT review requirements. You can still say, honestly, that custom code is being used in the course. But the authoring experience does not require you to open a code editor or understand the implementation.

If your organization has governance around custom scripts, treat Snippets as custom-code enhancements and review them accordingly. The advantage is that the snippet is packaged and reusable, rather than improvised differently in every course.

A closer look at some sample Snippets#

Confetti drop

The confetti drop is tied to a button click. In the demo, it appears after the learner clicks a Continue button.

This is best used sparingly: after a correct knowledge check, a completed section, a key milestone, or a moment where the course genuinely wants to acknowledge progress.

Remember, you need both the snippet that makes the confetti library available and the snippet that fires confetti on click. If you only import the button-click snippet, the behavior may not have what it needs to run.

Button shimmer

The shimmer effect is applied to buttons, including the course’s Begin button and a Continue button in the demo.

This is a visual attention cue. It can help draw the learner’s eye to a primary action, especially on a designed cover page or a dense lesson screen.

Use it with restraint. A shimmer on the one button you want learners to notice can be helpful. Shimmering every interactive element can work against clarity and accessibility, especially for learners who are sensitive to motion.

Emoji reaction

The emoji reaction snippet adds a persistent reaction layer to a course moment. In the demo, it appears after a scenario, where the learner can indicate how they felt: sad, loved it, pondering, and so on.

Nate notes that the selected reaction persists in the learner’s browser. So if the learner leaves and comes back, they can still see how they responded.

He also mentions that tracking could be added from an LMS perspective if desired, but that is not part of the basic behavior shown.

Use this pattern when you want reflection, affective response, or lightweight learner agency. If you need formal reporting, plan that separately.

Snowflake background

The snowflake background is an ambient visual effect. In the demo, it appears as a subtle background after the confetti moment.

This is the kind of snippet that works well for themed courses, seasonal experiences, or internal campaigns where a little atmosphere is part of the brief.

The caution is the same as with any ambient motion: subtle beats distracting. Test the course as a learner, not just as a designer admiring the effect.

Testing and troubleshooting#

After you scope a snippet, save it. You always need to save before running or previewing the result.

If something does not appear to work, check these in order:

1. Did you import every required JSON file?
2. Is the snippet enabled?
3. Did you save after changing the settings?
4. Is the scope correct?
5. If scoped to blocks, is the correct block checked?
6. Are you testing the actual button or interaction the snippet targets?

For button-based snippets, remember that the snippet is usually listening for a button inside the selected block. If you select the wrong block, nothing may happen. If you scope too broadly, the effect may happen in more places than intended.

How small snippets make real impacts#

Most Rise teams are balancing speed, polish, and control. Stakeholders want the course to feel custom. Brand teams want consistency. Learners need clarity. And you probably do not have extra days to build and QA a one-off interaction from scratch.

Mighty Snippets give you a practical path: start with a templated effect from the Code Catalog, import it into the course, and apply it only where it earns its place.

Snippets are not there to decorate every screen. They are there to support meaningful moments: draw attention, reinforce progress, invite reflection, or add atmosphere when the course context calls for it.

Try one small enhancement in your next Rise course: a shimmer on the primary button, a confetti drop after a checkpoint, or a reaction moment after a scenario. Keep it purposeful, test it in Preview, and let the interaction do one clear job.