Create get-started-with-recode.md

[nancy-verma780]

Closes #1899

Changes Made:

• Created a new documentation page titled "Get Started with Recode".
• Added step-by-step instructions for local setup and dependencies.
• Followed maintainer guidelines to avoid updating the README file.

[vercel]

@nancy-verma780 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

1. Get free Consultation use code recode50 to get free: Mentorship for free.

2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[github-actions]

✅ Synchronized metadata from Issue #1899:

• Labels: level 1, recode, Enhacement, level2, medium, gssoc:approved, type:docs
• Milestone: recode:launch 3.0

[nancy-verma780]

Hi @sanjay-kv @Adez017 @iitzIrFan,

I have created the new documentation page exactly as requested, keeping the installation guide clear and leaving the README untouched.

Since I am committing directly through the GitHub web UI for GSSoC'26, I am unable to run the local npm run build environment to generate a local screenshot. The Vercel preview check is currently pending authorization from a team maintainer.

Could you please authorize the Vercel preview deployment and review the Markdown file? Looking forward to your feedback and getting this merged!