FE-756: petrinaut product walkthrough#8789
Conversation
PR SummaryLow Risk Overview The petrinaut website enables the tour with three app-specific steps and demo videos, and updates favicon/PWA assets ( Reviewed by Cursor Bugbot for commit d1ced95. Bugbot is set up for automated code reviews on this repo. Configure here. |
🤖 Augment PR SummarySummary: This PR adds a first-visit product walkthrough (“tour”) to the Petrinaut website/editor. Changes:
Technical Notes: The walkthrough auto-opens on first visit (tracked via a dedicated localStorage key) and is designed so embedders provide content via 🤖 Was this summary useful? React with 👍 or 👎 |
kube
left a comment
There was a problem hiding this comment.
Beautiful, just a comment on the LocalStorage usage.
See the output of git range-diff at https://github.com/hashintel/hash/actions/runs/26683862492
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 6358594. Configure here.

🌟 What is the purpose of this PR?
Adds a product walkthrough to the petrinaut website. The logic for the new walkthrough lives inside the petrinaut library so that it can be kept in sync with any changes to the petrinaut ui and/or interact with other modals - however the content (copy + any video animations + their urls) is passed in by the consuming application by including the WalkthroughProvider - not including a walkthrough provider means that no preview will be rendered.
We track whether the user has seen the walkthrough in its own localstorage variable rather than the userSettings variable in order to keep the data better co-located with the context + provider and avoid situations where a provider is added in the wrong order.
The animations in this PR are not final yet, and still need polish @kube has graciously offered to record the experiments animation over the weekend. Will update the PR once they are done.
Pre-Merge Checklist 🚀
🚢 Has this modified a publishable library?
This PR:
📜 Does this require a change to the docs?
The changes in this PR: