The getting-started time claims disagree: two minutes, five minutes, ninety minutes

Open Beginner friendly
#237 0 comments 0 reactions 0 assignees View on GitHub

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

documentation
  • /docs/start heading: "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

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 MUKE-coder/grit

All issues in MUKE-coder/grit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.