Lexle

Audience

Instructional designers who want a familiar vocabulary game that can still report meaningful results to an Articulate Storyline course.

The challenge

Learning designers needed a portable vocabulary interaction that feels like a familiar word game but can still pass meaningful completion results into a Storyline course.

Constraints

• The game must remain directly testable in a browser before Storyline integration.
• Exported results need a clear contract instead of treating page load as completion.
• The focused utility should not require a larger learning platform.

Discovery

The core need was the bridge between an understandable game mechanic and a reusable authoring workflow, not another standalone Wordle clone.

The approach

Create a browser-based builder where the game can be configured and tested before export, then preserve a clear integration boundary for Storyline result handling.

What SideQuest Studio handled

Learning game design · Storyline extension design · Browser development · Export workflow · Production testing

Important decisions

• Keep the interaction usable in a normal browser before it is embedded in Storyline.
• Pass meaningful results rather than treating page load as completion.
• Use a focused tool instead of adding the workflow to a larger platform.

Learning design

• Use a familiar word-game pattern so attention can stay on the vocabulary challenge.
• Keep result reporting tied to meaningful play rather than presence on the page.

Accessibility

• Maintain keyboard-operable inputs and visible game state.
• Ensure feedback does not depend on color alone when the interaction is embedded.

Testing and iteration

• Test configuration, browser play, export, and Storyline result handling as one workflow.
• Verify direct public loading and refresh behavior for the builder route.

Current outcome

Lexle is a live public tool that demonstrates the builder and the portable learning-game pattern.

Known limitations

• Final Storyline behavior still depends on the host course and its variable/result configuration.
• The public builder demonstrates the pattern but does not replace accessibility and LMS testing inside each published course.

Next steps

• Document the result bridge with a verified example course.
• Test the exported interaction in the target LMS combinations used by future projects.