Inconsistent Rendering and Playback of Interactive Culver Menu Content

I am facing a technical issue with a Culver menu website that includes interactive content published using Articulate tools (Storyline/Rise) and embedded within a standard website. The purpose of the site is to present a structured, interactive Culver-style menu with clickable categories, item descriptions, and visual elements. While the content works as expected during testing, the live environment shows inconsistent behavior where parts of the menu do not always render correctly.

 

The main problem is that certain menu sections randomly fail to appear for users. For example, interactive buttons or layers representing burgers, sides, or desserts sometimes do not load, even though the content exists and is properly configured in the Articulate project. Reloading the page or reopening the content occasionally resolves the issue, but this is not reliable and negatively impacts the user experience.

 

Another issue is that updates made to the menu content in Articulate do not always reflect immediately on the live website. After republishing the project and replacing the output files, some users still see older versions of the menu, including outdated prices or descriptions. This suggests that caching at the browser, server, or CDN level may be serving stale Articulate output rather than the latest published files.

 

From a technical perspective, the Articulate content is embedded using an iframe and relies on JavaScript for navigation, triggers, and state management. I suspect the issue may be related to how the iframe is being loaded, file path references, or browser security restrictions affecting scripts within the Articulate output. I have checked for console errors, but they appear inconsistently and are difficult to reproduce across different browsers.

 

I am also concerned that responsive behavior or device-specific scaling could be contributing to the problem. On some screen sizes or mobile devices, interactive elements either overlap incorrectly or fail to respond to user input, making parts of the Culver menu prices inaccessible. This is especially problematic because the menu is intended to be used across desktops, tablets, and mobile devices.

 

I would appreciate any guidance from the community on best practices for hosting and embedding Articulate content in a live website. Has anyone experienced similar issues with intermittent loading, caching, or responsiveness when using Articulate for interactive menu-style content? Any troubleshooting steps, recommended publishing settings, or known limitations would be extremely helpful in ensuring the Culver menu displays consistently for all users.