Organizer Guide
Who This Page Is For
Section titled “Who This Page Is For”This guide is for developer communities, university instructors, hackathon organizers, ecosystem teams, and grant programs that want to use the course as onboarding infrastructure.
Delivery Modes
Section titled “Delivery Modes”| Mode | Best For | Notes |
|---|---|---|
| 2-week sprint | Hackathon prep | Fast pace, high support, project-oriented |
| 4-week cohort | Developer communities | Balanced pace with weekly guided practice |
| 6-week lab | Universities | One module per week plus final showcase |
| Self-paced | Open community learning | Requires clear self-checks and async support |
Before the Cohort Starts
Section titled “Before the Cohort Starts”Organizers should prepare:
- Target testnet or L2 testnet
- Faucet instructions
- Wallet safety guide
- Discord, Telegram, Slack, or forum channel
- GitHub template repository or repo naming convention
- Demo day schedule
- Optional self-assessment guide
Recommended Weekly Operations
Section titled “Recommended Weekly Operations”Each week:
- Publish the target module and lab.
- Remind learners of the required resources.
- Run an optional office hour.
- Invite learners to share blockers voluntarily.
- Review common errors during office hours.
- Share useful project examples.
Instructor Responsibilities
Section titled “Instructor Responsibilities”Instructors should focus on:
- Environment setup
- Debugging workflows
- Explaining concepts that videos do not make clear
- Reviewing security assumptions
- Helping learners scope capstone projects
- Keeping learners away from real-fund risk
Partner Outcomes
Section titled “Partner Outcomes”For ecosystem partners, the course should produce:
- New developers who can build and deploy a small dApp
- A portfolio of testnet projects
- Candidates for hackathons, grants, and builder programs
- Reusable labs and teaching materials
- A repeatable onboarding process
Compliance and Attribution
Section titled “Compliance and Attribution”The course curates public resources and adds sequencing, notes, labs, and evaluation. External videos, documentation, and platforms remain owned by their respective authors or organizations. Organizers should keep resource attribution visible and avoid presenting external content as owned by the course site.
Operational Metrics
Section titled “Operational Metrics”Useful metrics:
- Active learner count
- Module completion rate
- Voluntary lab participation rate
- SpeedRun challenge completion count
- Capstone completion count
- Demo day attendance
- Number of learners who continue into hackathons, grants, or ecosystem projects