Use Mighty Studio to Build Reusable Rise Interactives
A practical walkthrough of Mighty Studio: find community templates, edit them with AI, publish to Rise, and reuse custom blocks across courses.
Custom Rise interactions used to come with a tradeoff: build it in Storyline, hand-code it, or settle for what’s already in the block library. Mighty Studio adds another path: reusable custom blocks you can author directly inside Rise without opening the code.
Here’s the practical workflow, as shown by Daniel Bedich, Director of Product Design at Maestro. In this walkthrough, Daniel outlines where Studio lives, how to use community templates, how to edit your own template with AI, and how to publish that block back into Rise.
What Mighty Studio adds to the Rise workflow#
Inside the Rise block library, Mighty adds a new area on the left called Studio Templates. That’s your entry point for custom, reusable interactions.
The important word here is reusable.
A one-off custom-coded block can be useful, but it’s often painful to maintain. If you need to swap content, share the interaction with your team, fix an accessibility issue, or reuse the same pattern across lessons and courses, you’re usually back in the code—or back in Storyline.
Mighty Studio is designed to make those custom interactions behave more like native Rise blocks:
- You can discover interactions created by the community.
- You can add them directly to a Rise course.
- You can edit content through a form, similar to authoring other Rise blocks.
- You can create and publish your own templates.
- You can update a reusable block from one source instead of hunting through every course where it appears.
That opens up a nice middle ground: more flexible than the default Rise block library, but more maintainable than scattered custom code.
Step 1: Open Studio Templates from the Rise block library#
Start in the Rise editor, inside the lesson where you want to add a custom interaction.
- Open the block library.
- Look at the left side of the library.
- Choose Studio Templates.
- Select Mighty Studio.
The first tab you’ll see is Discover.
This is where the workflow starts to feel different. Instead of choosing only from the standard Rise blocks, you can browse custom interactions shared by the Mighty community. In the video, Daniel notes that the Discover tab is approaching 200 different options.
That makes Discover useful in two ways:
- It’s a source of inspiration when you know the learning moment you need but not the exact interaction pattern.
- It’s a practical shortcut when someone has already built something close enough for your course.
Step 2: Preview a community template before adding it#
From the Discover tab, browse the available Studio templates and preview anything that looks promising.
- Click a template in Discover.
- Review the preview to see how the interaction behaves.
- Decide whether it fits the learning task in your course.
- If it works, add it to your Rise lesson.
The key difference from a traditional custom-coded embed is that you’re not stuck with fixed content. Once the template is in Rise, you can edit it through an authoring form.
In the video, the editable form appears on the left side. That form lets you change the template’s content in a way that feels much closer to working with a normal Rise block than editing code.
So if a community-built interaction has the structure you want, you can adapt the copy, labels, and available template fields for your course.
Step 3: Open Mighty Studio when you need your own block#
Discover is the fastest path when an existing template fits. But sometimes your course needs something more specific: a branded decision aid, a custom reflection layout, a niche comparison tool, or a reusable interaction your team will use again and again.
That’s when you open Studio itself.
- Go back to Mighty Studio.
- Open the Studio workspace in a new tab.
- Use this space to build or manage your own templates.
Daniel describes this as the place where you start building your own block library. If the options from Rise, Mighty, or the Discover tab aren’t quite right, you can create a custom block that’s reusable across courses.
For the sake of the video, Daniel doesn’t build a brand-new template from scratch. Instead, he edits an existing template, which is a helpful example because it shows the maintenance workflow you’ll use all the time.
Step 4: Select one of your templates to edit#
In Mighty Studio, open one of your existing templates.
When you select a template, you’ll see two important previews:
- A preview of the interaction itself.
- A preview of the authoring form that will appear inside Rise.
This is where you check both sides of the experience.
The interaction preview answers: Does this block look and behave the way learners need it to?
The form preview answers: Will authors have the right fields to customize this block later?
That second question matters. A beautiful custom interaction is less useful if every small content change requires someone to go back into the template logic. The form is what turns the interaction into a practical, reusable Rise block.
Step 5: Use “Edit with AI” to change the template#
Here’s the fun part from the walkthrough: using AI to make a specific template change without manually touching the code.
In Daniel’s example, the template has a tan background. That’s fine in some contexts, but not ideal if you want to use the same block in different lessons with different Rise block backgrounds.
So the goal is simple: make the interaction background transparent, so the author can use Rise’s block background settings instead.
The workflow looks like this:
- In Mighty Studio, click Edit with AI.
- Copy the prompt Mighty provides.
- Open your AI tool—Daniel uses Claude in the video.
- Paste the prompt into Claude.
- Let Claude connect with the context Mighty provides about the template.
At that point, Claude can understand the structure of the template and the authoring form. Daniel then gives it a plain-language request:
Let’s make the background transparent instead of the current tan color.
That’s the kind of edit that would normally send many teams into a code file. In this workflow, the AI has the Mighty-provided context it needs to make the change in a Rise-compatible way.
Daniel also calls out why that context matters: Mighty is helping guide the AI around things custom Rise blocks need to handle well, including responsiveness, accessibility, completion logic, and tracking considerations like xAPI or SCORM.
That doesn’t mean you should skip review. It means you’re not starting from a blank prompt and hoping the output behaves inside Rise.
Step 6: Review the AI’s changes in Studio#
After Claude finishes, return to the Studio preview and check what changed.
In the video, Claude reports that it made five updates to support the transparent background. At first, the tan background still appears in the preview. Then Daniel checks the template form and finds that the background color has been moved into a field near the bottom.
By clearing the Background color field, the template becomes transparent.
That detail is worth pausing on: the AI didn’t just remove a color in one place. It interpreted the request by making the background controllable through the template form. For Daniel’s use case, that works well because it gives authors a way to leave the interaction transparent and rely on Rise’s own block background settings.
So your review step should include both pieces:
- Check the learner-facing interaction preview.
- Check the authoring form fields to see how the change is exposed to future authors.
If the first pass isn’t quite right, keep going back and forth with Claude or your AI tool until the template behaves the way you need.
Step 7: Publish the draft to Rise#
Once you’re happy with the template, publish it from Mighty Studio.
In the video, Daniel describes this as publishing the draft to Rise. Practically, that means the custom block template is now available for you to use in your Rise courses.
- Confirm the template preview looks right.
- Confirm the authoring form has the controls you want.
- Choose the option to publish the draft to Rise.
- Return to the Rise editor.
This is the moment your custom interaction becomes part of your usable block library, not just an experiment sitting in a separate workspace.
Step 8: Add your published template from “Created by Me”#
Back in Rise, return to the Studio templates area.
- Open the Rise block library.
- Go to Studio Templates.
- Choose the Created by Me tab.
- Find the template you just published.
- Add it to your course.
In Daniel’s walkthrough, the updated template is an editorial-style brief. After adding it to the course, he checks whether the transparent background change worked.
It does: the interaction now lets the Rise block background show through. Instead of baking the tan color into the custom interaction, the block can use Rise’s background settings behind the layout.
That’s a small design change with a big reusability payoff. The same template can now live in different course sections with different visual treatments, without requiring a new version of the interaction each time.
Why this matters for teams#
The real value of Mighty Studio isn’t just that you can make a custom block. It’s that you can make a custom block your team can maintain.
If a block is used across several lessons, courses, or authors, a single fix can matter a lot. Daniel gives the example of an accessibility bug: instead of tracking down every instance of a custom-coded interaction, you can go back to Studio, ask your AI tool to help fix the issue, and update the source template.
That makes custom interactions more realistic for teams with brand requirements, accessibility standards, and tight timelines. You’re not choosing between “plain but maintainable” and “custom but fragile” quite as often.
It also gives your team a shared source of truth. If you create a custom interaction that fits your organization’s learning patterns, you can reuse it again and again while authoring different content inside it.
When to use Discover vs. build your own#
A simple rule of thumb:
- Use Discover when you need inspiration or when a community template already solves the interaction pattern.
- Use Created by Me when your team has a repeatable need, a brand-specific pattern, or a custom interaction you’ll maintain over time.
- Use Edit with AI when the template is close, but you need a structural or styling change that would otherwise require code.
You may still use Storyline for complex simulations or highly specialized interactions. And there will always be cases where custom development makes sense. But for many Rise authors, Mighty Studio fills the gap between native blocks and heavier custom builds.
The takeaway#
Mighty Studio gives you a practical way to add custom, reusable interactions to Rise: browse community templates, adapt them through forms, edit your own templates with AI, and publish them back into your course.
Try it the next time the Rise block library gets you 80% of the way there and you need that last 20% to be reusable, editable, and easier for your team to maintain. You can learn more about the feature on the Mighty Studio page.