Many instructional designers who want to add game-based engagement to Storyline find that custom interactions take too long to build, are fragile, and often depend on one person who knows how to code or vibe code. That creates a scalability problem. Teams hesitate to adopt these solutions because content updates feel risky and changes fall on a single developer. As a result, even good ideas get shut down before they ever make it into production.

In this session, I addresses that challenge with a practical, field-tested workflow. You'll see how I turn vibe-coded games into Portable Web Objects that are stable in Storyline and designed for team use. The game logic stays intact, while the learning content lives externally in a simple spreadsheet, so non-technical teammates can update questions and reuse the interaction across different trainings without rebuilding or touching code. We will walk through the full process end to end, including the decisions that make these interactions maintainable over time. You'll leave with prompts, templates, and files you can use.

In this session, you will learn to:

• Explain what a Portable Web Object is and when it makes sense to use one in Storyline
• Convert a vibe-coded game into a reusable, Storyline-ready web object
• Separate game logic from learning content so updates can be made by non-technical team members
• Apply a reuse strategy so one interaction can support multiple trainings, audiences, or brands

This session assumes familiarity with Articulate Storyline and comfort building basic interactions, inserting web objects, and publishing courses. No traditional coding experience is required, but you should be open to working with AI-assisted, prompt-based workflows often referred to as vibe coding. Prior experience with vibe coding is not required. Familiarity with spreadsheets, such as editing CSV files, is helpful since learning content is managed externally. Absolute beginners may find some sections technical, but they can still benefit by understanding how these workflows support scalable, team-friendly development.