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

Learn course: track lesson progress on the index

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start with the /learn index page and the lesson pages it links to, then find how editorFontSize and the theme are already persisted so the new progress storage follows the same pattern. Decide whether a lesson counts as done when its page is opened or via an explicit mark-done control, since the issue leaves that open. Done means that after reloading /learn, finished lessons show a checkmark and a continue-where-you-left-off link appears at the top.

Written by the indexing model from the issue text.

Description

enhancement priority: low

From the 2026-07-17 UX review.

Problem

The course is 15 lessons with a well-structured index (/learn), but nothing tracks which lessons you've finished — a returning learner has no re-entry point and the course doesn't feel like a course.

Suggested fix

  • localStorage is enough (matches the existing editorFontSize / theme persistence patterns): mark a lesson visited/done when its page is opened (or via an explicit "mark done" at the lesson footer).
  • Show checkmarks on the /learn index and a "continue where you left off" link at the top.
  • Server-side persistence (per-account) could come later; don't block on it. Related: #121 (achievements/badges) covers ranked accomplishments, not course progress.

Acceptance

Reopening /learn shows which lessons are done and where to resume.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
8m
Merged PRs (30d)
8

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 LeeAdcock/robocodeJs.com

All issues in LeeAdcock/robocodeJs.com

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.