webrune-tim / webrune-tim/The-Autonomy-Protocol

Self-governance tracking tools and progress states

Open
#44 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

curriculum help wanted site-content
Dominant language
JavaScript
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Objective

Rewrite copy across student progress dashboards, streak trackers, and accountability logs.

Key Focus Areas

  • Metric Cards: Direct titles and metric summaries (e.g., tracking consistency, task completion, reflection cadence).
  • Milestone States: Grounded recognition of completed cycles that celebrates discipline and earned progress rather than unearned praise.
  • Recovery/Reset Copy: Encouraging, objective copy for when streaks break or commitments are missed, framing failure as data rather than moral collapse.

Tone & Voice

  • Factual and stoic.
  • Avoids gamified gimmicks, confetti-culture phrasing, and participation trophies.

Acceptance Criteria

  • Progress card headers, stat labels, and descriptions updated.
  • Streak reset and failure-state messages revised to emphasize immediate resumption of discipline.
  • Milestone badges/cards updated with authentic text.

Contributor guide

Open the 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.

Research direction

Start by locating the student progress dashboards, streak trackers, accountability logs, metric cards, milestone states, and recovery messages described in the issue. Review the existing labels and copy for tone, then update the identified UI text. Done means all progress headers, stat descriptions, reset messages, and milestone text meet the listed acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
content, frontend
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.