Guard against MVP scope creep toward "all 63 paper pages"

Open
#66 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript
Domain
content

Research direction

Use this issue as a scope reference while reviewing the first representative vertical slice. Keep the issue open during scope discussions, and close it only after that vertical slice ships; the payload does not identify specific files or tests.

Written by the indexing model from the issue text.

Description

type:risk

Reference point for scope discussions; close after the first representative vertical slice ships.

Dominant language
TypeScript
Stars
9
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 rubyforgood/alongwithyou

All issues in rubyforgood/alongwithyou

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.