Write a workshop as one plain Markdown file and run it live. Students join with a code - no accounts - and you see which step everyone is on: who's stuck, who's done, who needs help. Polls, quizzes, chat and a session report built in. Free, no credit card.
Free Options
Launch Team
TinyFishSearch, fetch and browse for AI agents. Claim 30% bonus!
Promoted
Glad it can be exported back to Markdown. I wouldn't want my workshop locked into one tool.
@bouzadamanuel0934 Exactly! that was one of my main goals - to make sure your workshop is never locked into a single tool, and that exporting it back to Markdown is always simple and straightforward.
curious how the "who's stuck" detection actually works - is it purely time-on-step (flagging anyone who's been on a step way longer than the group median), or does it also look at things like repeated back-and-forth navigation between steps as a stuck signal?
@galdayan
Right now, “who’s stuck” isn’t detected automatically.
A participant can let the teacher know they’re stuck and optionally include a private message asking for help or clarification.
The system doesn’t currently use time spent on a step or back-and-forth navigation between steps to infer that someone is stuck. That activity is only available to the teacher in the final session summary.
During the session, the teacher can still see where participants are. If some haven’t reached the current step and are falling behind, the teacher can see how many of them are at the same point and decide whether the class needs more guidance.
@yaniv_grama makes sense to keep it opt-in rather than guessing - a false "you look stuck" ping would probably annoy more people than it helps. putting time-on-step in the post-session report instead of a live alert seems like the safer call anyway.