Design/implement better challenges interface

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

The issue names no files, tests, or entry points. Start by mapping how the tutorial/REPL selects and presents challenges, then determine how non-sequential navigation and user-submitted challenges should fit. Done requires a defined interface and an implementation supporting both paths outside the sequential tutorial.

Written by the indexing model from the issue text.

Description

enhancement teaching

We might not want to go through challenges sequentially. Additionally, we might want user submitted challenges. These both go outside the scope of the tutorial.

Dominant language
JavaScript
Stars
69
Forks
10
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 evinism/lambda-explorer

All issues in evinism/lambda-explorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.