Everything you reach for mid-build, on one page: the Rise-vs-Storyline decision, trigger
recipes, states and variables, publish formats, an accessibility checklist, and the honest subscription
map. Bookmark it and keep it open while you work. We never quote prices or hard limits — check
articulate.com/pricing for current details.
🔀 1. Rise vs. Storyline — Which Tool?
Reach for Rise 360 when…
Reach for Storyline 360 when… Windows only
It's mostly content and you want it fast
You need a custom interaction Rise can't make
It must be responsive / mobile-first (automatic)
You need precise timing, animation, or layout control
You want a consistent, polished look with little effort
You're building a game, simulation, or complex branching
You're on a Mac/Chromebook/tablet (browser-based)
You're doing a software simulation (View/Try/Test)
Speed and ease matter more than fine control
You need fine-grained accessibility control (focus order, etc.)
💡 The one-liner: Rise for a good course fast; Storyline for a
custom interaction. And you can embed a published Storyline interaction inside a Rise course with
the Storyline block.
Every trigger = an Action + a "When" (event) + optional
Conditions. Triggers run top-down. Common combinations:
Goal
Action
When (event)
Condition (optional)
Go to the next slide
Jump to slide (Next)
User clicks Start
—
Reveal a pop-up
Show layer "Detail"
User clicks the marker
—
Mark an item explored
Change state to Visited
User clicks the item
—
Count explored items
Adjust variable NumVisited + 1
User clicks the item
—
Gate the Continue button
Change state of Continue to Normal
Variable NumVisited changes
NumVisited = 4
Greet by name
Set text variable Name = (entry)
Control loses focus / user clicks Submit
—
Branch on a choice
Jump to slide 2.3
User clicks Choice A
—
Play narration on entry
Play media Narration
Timeline starts
—
Open a resource
Open URL / file
User clicks the link
—
🎭 4. States Cheat
State
What it's for
How it changes
Normal
The default look
Starting state
Hover
Mouse is over the object
Automatic
Down
Object is being pressed
Automatic
Visited
Object has been clicked before
Automatic (buttons) or via trigger
Selected
Object is chosen/toggled on
Interaction or trigger
Disabled
Not yet clickable (e.g., a gated button)
Set as start state; trigger to Normal
Hidden
Present but not shown
Trigger (change state / show)
Custom (e.g., "Complete")
Any look you design
Edit States + a trigger to switch to it
🧠 5. Variables Cheat
Type
Holds
Typical use
Text
Words
A learner's name → greet with %Name%
Number
A value you can add to/compare
Count visited items; running score
True/False
A yes/no flag
"Has the learner agreed?"; a gate flag
Reference in text: wrap the name in percent signs — %Score%,
%Name%.
Set vs. adjust:Set replaces the value; Adjust adds/subtracts
(numbers).
Read with conditions: use a variable in a trigger's "on condition" to gate or
branch (e.g., Score >= 80, AllVisited = True).
🧩 6. Rise Interactive Blocks — Best Use
Block
Best for…
Accordion
FAQs; a few related sub-topics, one open at a time
Tabs
A few parallel topics viewed side-by-side
Labeled Graphic
"The parts of a thing" — markers on an image
Process
Ordered steps in a procedure
Timeline
Events in chronological order (history, project phases)
Flashcard Grid
Term/definition or Q/A recall practice
Sorting Activity
"Which category does this belong in?"
Button / Button Stack
Choices, calls to action, jumping to content
Scenario
Decision practice with branching outcomes
Knowledge Check
Ungraded practice questions with instant feedback
Quiz (lesson)
Graded assessment with a passing score
🚀 7. Publish & LMS Formats
Target / format
Use it when…
SCORM 1.2
Your LMS needs tracking — the safe, widely supported default
SCORM 2004
You need finer sequencing / richer completion status
xAPI (Tin Can)
You want granular tracking of what learners do (via an LRS)
cmi5
Modern xAPI-based profile with standardized launch/reporting
AICC
A legacy LMS specifically requires it
Web / HTML5
A shareable course with no tracking (great for a portfolio)
Review 360
You want on-slide comments/feedback before it's final
Reach 360Add-on
Deliver & track to learners without a separate LMS
Video
You need an MP4 of the course
Word
A printable review/handout of slide content
💡 Don't forget: set a completion rule (passing score or slides viewed) in the
publish settings, or the LMS may never mark anyone complete.
♿ 8. Accessibility Quick Checklist
Aim for POUR — Perceivable, Operable, Understandable, Robust:
☐ Meaningful alt text on informative images; decorative images marked decorative
☐ Logical focus order set on interactive slides (Storyline's Focus Order editor)
☐ Closed captions for all audio and video
☐ Sufficient color contrast; readable text size
☐ Never rely on color alone to convey meaning
☐ Everything is keyboard-operable (no mouse-only interactions)
☐ Accessible labels/accessible text on custom objects
☐ Avoid auto-play surprises and flashing content
☐ Rise is responsive & accessible by default — but you still own the alt text and captions
💳 9. The Subscription Map
Badge
What it means
Trial / Paid
The whole suite — you need an active trial or subscription to author. Learners you publish to don't.
Teams
Team/organization-plan features: shared team folders, some collaboration controls.
Add-on
Metered or seat-based, often billed separately: heavy AI Assistant use, Reach 360.
Windows only
Storyline 360 is a Windows desktop app. On a Mac, run it in a Windows VM. Rise works anywhere.
The honest shape: no permanent free tier, but a full
30-day free trial covers this whole course. Learners never need a subscription.
Prices, plans, and limits change — check articulate.com/pricing.
🛠️ 10. Workflow & Shortcut Tips
Plan before you build — objectives → storyboard → build. It always saves time.
Set the Rise theme once, up front — colors, fonts, cover, logo — so blocks inherit it.
Build, then polish — get all content in first; refine spacing and wording last.
Preview constantly — Rise on mobile; Storyline slides after each new trigger.
Triggers run top-down — if logic misfires, check trigger order first.
Name variables clearly — NumVisited beats Var1.
Save versions of your .story file — don't rely on the cloud alone.
Standard editor shortcuts work — copy/paste, undo, duplicate — much like other
desktop apps (Articulate updates specifics, so confirm in your version).
Test the published output, not just the preview — that's what learners get.