Participant Workbook Solution
Recommended individualized participant workflow using an embedded browser workbook engine plus optional Forms, Sheets, and Apps Script.
What now exists in the public site
The public site now includes an embedded browser workbook engine that lets participants move through one multi-step workbook flow, keep notes private in the browser, and resume on the same device if they leave and return later.
Why the embedded workbook engine still has limits
The embedded browser workbook engine is the right live-session fallback and private participant notebook. It still does not become a true organizer-tracked LMS by itself. If each participant needs centralized workflow tracking, response capture, or emailed summaries, the solution still needs a structured forms layer beyond GitHub Pages alone.
Recommended tool pattern
| Need | Recommended tool | Why it fits |
|---|---|---|
| Live participant workbook flow | GitHub Pages plus embedded browser workbook engine | Supports private step-by-step progression, local save, resume, print, and download without a backend. |
| Per-participant tracked workflow | Google Forms with section branching | Provides structured interaction, required fields, section logic, and response capture. |
| Response store | Google Sheets | Easy operational visibility and exports. |
| Participant-specific links | Google Forms prefilled URLs | Lets each learner start from a personalized or pathway-specific form without building a custom app. |
| Optional end-of-flow email or PDF automation | Google Apps Script | Adds the missing LMS-like completion layer without forcing a full backend into the public site. |
Suggested workflow
| Step | Experience |
|---|---|
| 1. Live session default | Participant starts in the browser workbook flow on GitHub Pages and moves step by step through the event. |
| 2. Private note retention | The workbook engine saves progress in the browser so the learner can continue on the same device. |
| 3. Organizer-tracked option | If the organizer wants structured tracking, the learner uses an issued workbook form link instead. |
| 4. Prompt selection | The learner chooses from starter prompt options or a guided level path. |
| 5. Note capture | The learner records what they changed, what result they got, and what gap remained. |
| 6. Adaptive progression | Branching or workbook helper logic sends learners to Guided, Build, Remix, or Stretch follow-up items. |
| 7. Completion output | If the tracked path is used, the response lands in Sheets and can optionally trigger an Apps Script summary email or PDF workflow. |
Right-sized recommendation
The practical answer is not to build a full LMS. It is to use the embedded browser workbook engine for the default live session, then add a participant workbook Google Form with section branching and prefilled links only if the organizer actually needs central tracking.