Problem Statement:
Both the top-level Installation section and the Contributing → Step-by-Step Guide section instruct new contributors to run:
git clone https://github.com/your-username/recode-website.git
This placeholder appears twice in the README and was clearly meant to be replaced with either the canonical recodehive/recode-website URL (for the main Installation section, where cloning the original repo makes sense for local testing) or clarified as "replace your-username with your GitHub username after forking" (for the Contributing section, where forking is the correct workflow).
Why this matters:
As written, both instances read identically and ambiguously — a first-time contributor can't tell from the text alone whether they're meant to clone the original repo directly or fork-then-clone, and copy-pasting the literal command as shown will always fail (your-username is not a real GitHub account). For a project this size (1,708 commits, 66 stars, 142 forks) actively onboarding GSSoC contributors, this is a first-impression friction point hit by essentially every new contributor who copy-pastes commands.
Proposed Solution:
In the Installation section (aimed at anyone running the site, not necessarily contributing), change the clone URL to the canonical https://github.com/recodehive/recode-website.git.
In the Contributing → Step-by-Step Guide section (aimed at contributors who should fork first), keep the your-username placeholder but add an explicit inline note: "Replace your-username with your GitHub username after forking the repository."
Search the rest of the repo (community/contributing-guidelines.md, docs/) for the same placeholder pattern to ensure consistency.
Impact: Removes ambiguity from the single most-copied command in the README for a project with a very large first-time-contributor funnel.
Problem Statement:
Both the top-level Installation section and the Contributing → Step-by-Step Guide section instruct new contributors to run:
git clone https://github.com/your-username/recode-website.git
This placeholder appears twice in the README and was clearly meant to be replaced with either the canonical recodehive/recode-website URL (for the main Installation section, where cloning the original repo makes sense for local testing) or clarified as "replace your-username with your GitHub username after forking" (for the Contributing section, where forking is the correct workflow).
Why this matters:
As written, both instances read identically and ambiguously — a first-time contributor can't tell from the text alone whether they're meant to clone the original repo directly or fork-then-clone, and copy-pasting the literal command as shown will always fail (your-username is not a real GitHub account). For a project this size (1,708 commits, 66 stars, 142 forks) actively onboarding GSSoC contributors, this is a first-impression friction point hit by essentially every new contributor who copy-pastes commands.
Proposed Solution:
In the Installation section (aimed at anyone running the site, not necessarily contributing), change the clone URL to the canonical https://github.com/recodehive/recode-website.git.
In the Contributing → Step-by-Step Guide section (aimed at contributors who should fork first), keep the your-username placeholder but add an explicit inline note: "Replace your-username with your GitHub username after forking the repository."
Search the rest of the repo (community/contributing-guidelines.md, docs/) for the same placeholder pattern to ensure consistency.
Impact: Removes ambiguity from the single most-copied command in the README for a project with a very large first-time-contributor funnel.