Rise 360 & Articulate Storyline Patterns

Technical patterns and workflows observed across projects using Rise 360 for course authoring and Articulate Storyline for interactive modules, including LMS publishing and version management practices.

Rise 360 Authoring

Locating Content for Edits

Rise 360's block-based structure can make it non-obvious where specific text lives, particularly inside interactive components. Common places where text hides:

• Labeled graphics — text labels on image hotspots are a frequent source of overlooked copy. When a stakeholder flags a specific phrase, check labeled graphics in addition to standard text blocks.
• Lesson-level blocks — feedback on a specific lesson page may point to any block type on that page; systematically expand each block to find the target text.

Example: On the Agility Recovery SOAR course, a stakeholder flagged the word "remediation" (should be "recovery"). The term was found inside a labeled graphic in Lesson 1 — not in a standard text block — requiring a targeted search through interactive components. (Source: ^[1])

Making Edits

• Edits must be made inside Rise 360 (the web authoring environment), not in the exported/published output or in Articulate Review.
• After editing, the course must be re-published to push changes to the LMS.

LMS Publishing & Version Management

Publish Workflow

1. Make content edits in Rise 360.
2. Publish a new version from within Rise 360.
3. In the LMS: delete (or replace) the old published version and upload the new package.
4. Archive the prior review/draft version within Rise 360 for organizational clarity — do not leave stale versions active alongside the current one.

Version Hygiene

• Keep a clear distinction between the review version (used for stakeholder feedback via Articulate Review) and the published LMS version.
• Archive review versions after approval to avoid confusion when multiple versions accumulate in the Rise 360 dashboard.
• Deleting the old LMS entry and uploading fresh prevents learners from accessing outdated content and keeps reporting clean.

Example: After correcting the "remediation → recovery" terminology, the updated SOAR course was published to the LMS the same day, the old LMS version was deleted, and the review version was archived in Rise 360. (Source: ^[1])

Articulate Storyline Patterns

Platform Requirements

• Storyline editing requires a Windows machine (or a PC-accessible environment). Working from a Mac-only setup blocks the ability to open and edit .story files.
• Plan Storyline revision sprints around hardware availability — do not commit to same-week turnarounds if the Windows machine is unavailable.

Review & Approval Flow

• Share Storyline output via Articulate Review for stakeholder feedback before locking the file.
• Confirm explicit approval (verbal or written) before making final edits, to avoid rework cycles.
• Communicate agreed edits via email so there is a written record of scope before the editing session begins.

Example: Co-pilot Storyline edits for Agility Recovery were scoped via email prior to the review meeting; Gus confirmed approval on the call, and Isalia committed to completing edits that week. (Source: ^[1])

Related

• ^[1]
• ^[2]
• ^[3]
• ^[4]