{GSSoC'26} Docs: Fix clone URLs and enhance README structure

[abhinavkdeval08-design]

Hi @sunilkumar2170,

I am participating in GSSoC '26 and noticed a few areas in the README.md that can be improved for better developer experience. I would love to work on this!

Proposed Changes:

1. Fix Clone URLs: The current local development instructions point to the original upstream repository (xitanggg/open-resume) instead of this repository (sunilkumar2170/Auto-Fill-Tool). I will fix this so new contributors clone the correct repo.
2. Add Prerequisites: Specify the requirement for Node.js and npm/Docker before the installation steps.
3. Add a Table of Contents (TOC): To make navigation easier for readers.
4. Add a Contributing Section: A short guide/link to help new open-source contributors get started.

Could you please assign this issue to me?

Labels: gssoc26, level 1, documentation

[preetik92002-tech]

Hi @sunilkumar2170,

I’m a GSSoC '26 contributor, and after reviewing the current README.md, I noticed it still contains references and clone links for the upstream xitanggg/open-resume repository. This can lead to confusion for new contributors trying to set up the project locally.

I propose a comprehensive update to align the documentation with this fork:

Repository Synchronization: Update all git clone commands and links to point to sunilkumar2170/Auto-Fill-Tool.

Unified Branding: Standardize naming to "Auto-Fill Tool" throughout the file.

Improved UX: Add a clickable Table of Contents for faster navigation.

Prerequisites: Add a section for required Node.js and Docker versions to reduce setup errors.

GSSoC Guide: Include a "How to Contribute" section specifically for GSSoC participants.

I have a clear plan and can submit a PR as soon as this is assigned.

Labels: gssoc26 documentation level1

[preetik92002-tech]

"As you can see in the screenshot, the current setup instructions actually direct developers to clone the upstream xitanggg repo instead of yours. I'll fix these links and standardize the branding to Auto-Fill Tool so the documentation is 100% accurate for this repository."

[abhinavkdeval08-design]

Hi @sunilkumar2170,

Just following up! Since I opened this issue, I have already forked the repository, set up the local environment, and prepared the required README updates (including the URL fixes, Prerequisites, and the TOC).

My code is ready to be pushed. Please assign this to me so I can raise the PR immediately. Looking forward to contributing! ✨

[sunilkumar2170]

Assigned to @abhinavkdeval08-design. Please submit PR within 2 days

[abhinavkdeval08-design]

Hi @sunilkumar2170, I have submitted the PR (#6) for this issue with the complete README revamp and URL fixes. Please let me know if any further changes are required. Ready to help!
Thanks :)

[abhinavkdeval08-design]

Hi @sunilkumar2170, thank you for accepting my PR (#6)!

I noticed that I haven't been officially added to the Assignees section on the right panel, and the issue currently has no labels. Since I am participating in GSSoC '26, could you please officially assign this issue to me and add the gssoc26 and level 1 labels? This will ensure the GSSoC bot tracks my contribution correctly.

I've already submitted the PR with the complete README revamp. Looking forward to your review!

[KshitijDhariwal]

Hi @sunilkumar2170! I am participating in GSSoC '26 and I would love to take this on as my first contribution. Could you please assign this issue to me?