Improve README with beginner-friendly contributiors.

[shikhasharma-passion]

This PR improves the README by adding clear guidance
for new contributors and GSoC aspirants.
No policy or rule changes included.

Summary by CodeRabbit

• Documentation
  • Updated README with a new "Getting Started for New Contributors" section providing onboarding guidance.
  • Added "Google Summer of Code (GSoC)" section with participation recommendations.
  • Added "Important Files in This Repository" section highlighting key documentation resources for contributors.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

README.md expanded with three new sections: "Getting Started for New Contributors" providing onboarding steps, "Google Summer of Code (GSoC)" detailing participation recommendations, and "Important Files in This Repository" listing three referenced markdown documents.

Changes

Cohort / File(s)	Summary
Documentation Additions README.md	Added three new sections: (1) "Getting Started for New Contributors" with contributor onboarding guidance; (2) "Google Summer of Code (GSoC)" with participation details; (3) "Important Files in This Repository" cross-referencing GoogleSummerOfCode.md, CommunicationGuidelinesAndRules.md, and SocialMediaGuidelines.md. No existing content modified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Hops with glee through README's page,
New sections brighten up the stage!
Contributors welcome, GSoC awaits,
Important files open wide the gates!
Documentation blooms, so fresh and bright,
A rabbit's joy—all text, no fight! ✨

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The PR title 'Improve README with beginner-friendly contributiors' contains a typo ('contributiors' instead of 'contributors') and is only partially related to the changeset. While it references improving the README for beginners, it doesn't capture the main additions: Getting Started section, GSoC section, and Important Files listing.	Correct the typo to 'contributors' and consider a more specific title like 'Add Getting Started and GSoC sections to README' to better reflect the actual changes made.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b92e761 and aad27fe.

📒 Files selected for processing (1)

• README.md

🔇 Additional comments (2)

README.md (2)

6-31: Great addition—content is clear and beginner-friendly.

The three new sections provide helpful structure for onboarding contributors and GSoC participants. The advice is practical, actionable, and aligns well with open-source best practices. Once the file references are verified, this will be a solid enhancement to the repository documentation.

---

6-31: All referenced files exist in the repository — no broken documentation links.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Clarify the reference to match the actual filename.

Line 13 says "Go through the Communication Guidelines" but the file listed later is CommunicationGuidelinesAndRules.md. Either update the reference text to match the actual filename or ensure consistency across the document.

🔎 Proposed fix

- - Go through the Communication Guidelines
+ - Read the CommunicationGuidelinesAndRules.md file

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- Go through the Communication Guidelines
	- Read the CommunicationGuidelinesAndRules.md file

🤖 Prompt for AI Agents

In README.md around line 13, the text "Go through the Communication Guidelines"
does not match the actual filename `CommunicationGuidelinesAndRules.md`; update
the reference so they are consistent—either change the sentence to explicitly
reference `CommunicationGuidelinesAndRules.md` (e.g., "Go through
CommunicationGuidelinesAndRules.md") or rename the linked filename/anchor
elsewhere to use "Communication Guidelines" consistently; ensure any link
targets or table-of-contents entries are updated to match the chosen wording.