A Box Could Show Which Phase an Item Is In, From Phases Named in the Front Matter
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript, markdown, yaml
- Domain
- tooling
Research direction
The issue names no files or tests. Start by reading how the existing staged-box syntax and its front matter (multibox, stages) are parsed and rendered in the repository. Nothing here is ready to build: the issue is posted for discussion and asks four open design questions. Done means a maintainer has answered them and the syntax is settled, not that code is merged.
Written by the indexing model from the issue text.
Description
Reviews now track each item through three phases, Heard, Agreed and Done. Staged boxes can already do that:
---
multibox:
stages: heard, agreed, done
---
- [x][ ][ ] Rename the setting
- [x][x][ ] Drop the old flag
- [x][x][x] Fix the tried Try's label
Each click fills the next box, and the stage reached shows beside it. What's written is a count, though: [x][x][ ] has to be read as "the second stage" and looked up in the front matter, and an item can only go forward one stage at a time.
The idea
Give each phase a key, and let one box hold the key of the phase it's in:
---
phases:
- Heard, h
- Agreed, a
- Done, d
---
- [h] Rename the setting
- [a] Drop the old flag
- [d] Fix the tried Try's label
- [a]reads as "agreed" in the source, and is shorter than[x][x][ ].- reader shows the phase's name beside the box, as it does a stage's.
- Elsewhere, GitHub shows
[h]as text, where[x][ ][ ]shows as text too, so neither is worse there.
Questions
- Is this worth a second syntax, next to staged boxes, or should staged boxes write the stage's key instead (
[x][x][ ]→[a])? - Does a click step through the phases in order, as a staged box does, or pick one?
- Do
[x]and[ ]still mean done and not started, alongside the keys? - Should
progress:[]count an item as done only at the last phase?
Came up in the 2026-11-01 retro. It isn't yet clear it's worth it; this is for discussion.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 26
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jzheaux/reader
-
polish
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
polish
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Maintainers usually reply within 1 day
Similar issues
-
Radix number block generates NaN after switching a negative or decimal number to binary, octal or hexPossibly taken @matthewalberto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mit-cml/appinventor-sources#4246 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
accessibility good first issue languages
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 2 days
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100