Fun student assessment, review and polling game. Hackathon finalist 2017.
Watch the Overview video on Youtube (Slide Deck)
Help us contribute to this! Because of the way the repo is organized, simply dumping questions/answers/links into questions.json would suffice to share questions across all cohorts, if merged in via Pull Requests.
Per Issue #42, we could deal with choosing a subset of questions at the beginning of the round, and allow categorizing of the questions via topic/module. This bears a longer discussion, but right now, fork/edit/deploy will suffice for anyone to try this tool out with their own questions.
Question Schema:
prompt: String
choices: [String]
answer: String
links: [{href(URL), text(String)}]
Currently limited to the static list of questions defined in questions.json
An authoring tool/question randomizer would be great - but meanwhile, edit the questions and redeploy
yarn build
, and commit built files.http://your-app.herokuapp.com/live
up on the shared projector display, and http://your-app.herokuapp.com/remote
up on a device.http://your-app.herokuapp.com/
Not enabled yet!
round
- the current question and any responsestitle
- the title of the gameplayers
- who's playing: map of Guid to {name}
clientId
- each browser tab is identified with a Guid stored in state here, and this is sent along with every response to the serverCurrently every connected browser gets an update of the server-side state object via a STATE_UPDATE
event.
This means everyone's response goes to everyone's browser. While that is inefficient, it is intended to be pruned down later. Per Issue #26 though, it would be nice for a user to know whether they were the first to answer, and thus some knowledge of others' responses could be useful.
The Huboard Kanban Board has a bunch of issues, which are synced to Github Issues. Huboard is awesome.
Thank you for helping to make Trilobytes awesome and improve Student fun and retention!