[BUG] Tutorial on the site is glitchy

[ash-heinz]

Bug description
When next is clicked in the demo, it glitches out and does things like text hint escaping the screen width, auto skipping through the tutorial without giving time to user to read, and user being able to scroll through the tutorial rendering the glow regions created useless.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to the site
2. Click next on the tutorial

Expected behavior
The tutorial waits for user to click next before going to next hint, with text boxes clearly visible.

Actual behavior
The text boxes escape the screen and goes through the tutorial very fast automatically

Browser and OS info

• OS: Windows 11
• Browser: Chrome
• Version: latest as of 23 April 2026

Screenshots/screen recording

I would like to work on this issue under GSSoC'26

[github-actions]

👋 Thanks for opening an issue, @ash-heinz!

Our maintainers will review this shortly 🚀

Before you start working

• 📖 Read the CONTRIBUTING.md guide
• 💬 Wait for a maintainer to assign you the issue before starting work
• 🔍 Search for existing issues to avoid duplicates

For GSSoC'26 contributors

If you're contributing under GirlScript Summer of Code 2026, please mention it in your comment when requesting assignment:

"I'd like to work on this — contributing under GSSoC'26"

Architecture notes

Reframe is a static Next.js app with output: "export". Key points:

• All video processing uses FFmpeg.wasm (client-side, no server)
• headers() in next.config.ts won't work — use vercel.json instead
• not-found.tsx requires public/404.html + vercel.json routes config

Happy contributing! ⭐ Star the repo if you find it useful!

[Flux07-gezz]

/assign

[github-actions]

Hey @Flux07-gezz, this issue has been assigned to you! 🎉 Please make progress within 5 days or it will be automatically unassigned due to inactivity.

[ash-heinz]

@Flux07-gezz can you unassign?
I was unaware the assigning system was changed so i didnt do that. Would really appreciate you handing over the issue to me as i opened it and intended to work on it.
Thanks!

[Flux07-gezz]

@ash-heinz i dont think i can unassign myself .. lets try /unassign
i am ready to get unassigned but u have to ask the reviewer .. to uassign

[ash-heinz]

@Flux07-gezz is the command not working?

[Flux07-gezz]

@ash-heinz no i dont think there is such a command ..
lets try again for you
/unassign

[ash-heinz]

@Flux07-gezz could you try typing just /unassign in the comment?

[Flux07-gezz]

/unassign

[github-actions]

Hey @Flux07-gezz, you have been unassigned from this issue. It is now open for anyone to pick up — comment /assign to claim it! 👋

[ash-heinz]

/assign