The getting-started time claims disagree: two minutes, five minutes, ninety minutes
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, go, nextjs, typescript
- Domain
- documentation
Research direction
Open docs/app/docs/start/page.tsx and look at the headline near line 141 and the seven-step summary near line 203, then docs/getting-started/quick-start near line 29. Decide the two numbers you want to keep (time at the keyboard vs. time on a fresh machine) and rewrite all three mentions so they agree. Done when the start page and the quick-start page state the same figures with the same qualifier, and the site still builds.
Written by the indexing model from the issue text.
Description
/docs/startheading: "build a full-stack app in under two minutes" (docs/app/docs/start/page.tsx:141)- the same page: "Seven steps, about ninety minutes end to end" (line ~203)
/docs/getting-started/quick-start: "running in five minutes" (line ~29)
All three can be true (typing the commands, a prepared machine, the full path), but the page doesn't say which is which. A beginner installing Go, Node, pnpm and Docker for the first time will take much longer than any of them, and reads the gap as "I'm doing it wrong".
Proposal: one honest line in both places, for example: "About two minutes of commands. On a fresh machine, allow 15 to 30 minutes for installing Go, Node, pnpm and Docker."
Filed from a docs and developer-experience review of gritframework.dev and this repository (November 2026).
Generated by Claude Code
- Dominant language
- Go
- Stars
- 152
- Forks
- 20
- Avg merge
- 1d 49m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 MUKE-coder/grit
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 72/100
MUKE-coder/grit#243 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MUKE-coder/grit#242 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MUKE-coder/grit#240 ·
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MUKE-coder/grit#236 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
MUKE-coder/grit#235 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tencentyun/cos-go-sdk-v5#364 ·
-
area: agents-mcp priority: normal
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
timwhitez/agent-sdk-golang#318 ·
Maintainers usually reply within 1 day