Homepage: explain the version number in one line

Open Beginner friendly
#243 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
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The change belongs on the gritframework.dev landing page, next to the version badge showing v3.559.0; the payload does not name the source file, so locate where that badge is rendered. Confirm that the /docs/versioning route exists and check its wording before linking to it. Done when a one-line explanation with a link to /docs/versioning appears beside the version badge.

Written by the indexing model from the issue text.

Description

documentation

v3.559.0 reads oddly to anyone used to semver minor versions moving a few times a year, and the first question it raises is "is this stable?". /docs/versioning answers it well, but the landing page doesn't link to it near the version.

Proposal: next to the version badge: "Every merged change is a release. Breaking changes are labelled. How versions work" linking to /docs/versioning.


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.