Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Attend a demo session

Open
#918 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
25/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Start with the issue instructions and the linked presenting guide. Check Slack for a Tuesday or Friday demo session, attend or give a 1–10 minute demo, and submit a screenshot showing an eligible CYF team member on the call.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 📅 Sprint 1 📅 Sprint 3 Module-Onboarding Recurring Submit:None

Presenting information is really important. You need to start practicing giving demos.

During this module, you must attend at least one demo session. We highly recommend you give at least one demo in a demo session, as well. We recommend you come to more, and give more. Your demo can be on anything you want. You can attend this demo session in any sprint. After this module, you will be required to give at least one demo per module.

There are demo sessions every Tuesday evening and Friday morning. They are advertised on Slack.

Aim for a 5 minute demo. But your demo must be at least 1 minute and at most 10 minutes long. Check out our guide about presenting.

You will need to attach a screenshot when submitting your Step for this Module. Make sure to take a screenshot of you on the call, showing that one of the following members of the CYF team was on your call:

  • Daniel Wagner-Hall
  • Karen Klein
  • Colin Farquhar
  • Poonam Rajput
  • Léon McGregor
  • Peter Mudra
  • Liam Greenfield

If you are not available during any of the demo times, please message on Slack to arrange an alternate time.

Dominant language
JavaScript
Stars
3
Forks
546
Avg merge
9h 40m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

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-JavaScript-Fundamentals

All issues in CodeYourFuture/Module-JavaScript-Fundamentals

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.