Prepare a demo for Q&A workshop

Open Beginner friendly
#484 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Domain
content

Research direction

Read the linked demoing guide and review the day plan mentioned in the issue. Choose an existing demo or prepare a short topic with the needed materials and presentation, then consider the task done when it is ready to use at Saturday's Q&A workshop.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Data-Flows Submit:None
Learning Objectives
  • Have a demo ready to give at the workshop on Saturday
Why are we doing this?

At the next class on Saturday, you will take part in a workshop based on giving questions and answers during a demo.
In order to do this, you need a short demo ready to use.

It does not need to be a new demo, you can re-use a demo you have already given. You do not need to spend lots of time preparing this, just make sure you have the materials/presentation/topic needed ready to demo on saturday.

The purpose of this workshop is to practice giving questions and answers in a professional demo setting, it is not for feedback on the demo itself, so don't worry about having a perfect demo ready.

You can find out more about the workshop on the day plan.

Maximum time in hours

1

How to get help

General advice on asking for help can be found on the curriculum pages.

You can always share your blockers in your class channel and get help from your colleagues.

If you need a refresher on how to prepare a demo, check out this guide.

Submission & Review

There is no submission step, just turn up to class on Saturday and enjoy taking part in the workshop!

Dominant language
JavaScript
Stars
0
Forks
276
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Data-Flows

All issues in CodeYourFuture/Module-Data-Flows

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.