The knowledge gained by sitting through the demo (and more) could be had in less time by simply using the software. I prefer to learn by doing, not watching.
We iterate on onboarding constantly. There's a few concepts that users need to understand to get to grips with using Trevor. E.g. that queries are made up of steps.
I'd prefer to use my time clicking around the site than clicking to close tooltips and modals.
I think introductory tutorials are better served by:
1. Scrollable documentation w/ images and an easily navigable sidebar that allows you to jump to specific topics that draw your attention.
2. In the case of something truly complex I like to watch videos for a more holistic perspective. Note that this is the slow and "relaxing" way of getting information. I do this primarily at night and never if I plan on using a product that same day.
I'd probably recommend a video for conveying a workflow (is the fact that queries are made up of steps best categorized as a workflow?), but make it short and focused; and support it with text so that I can quickly decide whether that video is worth clicking or not. Most of what's in the video should be readable in text on the same page as the video.
Will run this by the team tomorrow.
I looked at the repo again in more detail; and I must admit that I got distracted by the comments and missed out on the intent behind your demo.
While I am not a fan of the interactive demo before you can start using an app, I think that what you've shared is: 1. not that and 2. looks excellent for presentations and landing pages.
My feedback still stands, but I was imagining a much different use case which may not align closely with your product.
Random thought: it may be cool to see this implemented in a "picture-in-picture" fashion on a documentation site where the documentation scrolls to the relevant area as you navigate the app in the pip window.