Add a quiet daily puzzle

Open
#25 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
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
accessibility, frontend, testing

Research direction

Read the existing untimed submit-and-reveal journey, persistence, and curated puzzle library first; no specific files or entry points are named. Run the deterministic date-selection and timezone checks, then exercise fresh, resumed, and submitted daily states in a browser. Done means the acceptance criteria hold for account-free, static-hostable, accessible daily play.

Written by the indexing model from the issue text.

Description

Goal

Offer one quiet daily puzzle without streak pressure, countdowns, or a required account.

Background

Daily play can create a gentle return rhythm, but it should not punish missed days or undermine the interruption-friendly character of the game.

Acceptance criteria

  • The same dated puzzle is selected deterministically for every player without a required backend.
  • Missing a day does not break a streak or remove access to ordinary puzzles.
  • The daily puzzle can be interrupted and resumed locally.
  • Date and timezone behaviour is explicit and tested.
  • The daily surface does not reveal the solution total.
  • The experience remains account-free and static-hostable.
  • Accessibility and input equivalence match the ordinary puzzle journey.

Verification

  • Add deterministic date-selection and timezone tests.
  • Exercise fresh, resumed, and submitted daily states in a browser.

Dependencies

  • The untimed submit-and-reveal journey, persistence, and curated puzzle library.
Dominant language
JavaScript
Stars
1
Forks
0
Avg merge
5m
Merged PRs (30d)
14

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 glowkeeper/rectangle-react

All issues in glowkeeper/rectangle-react

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.