@Adez017 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

@sanjay-kv

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! 😊

✅ Synchronized metadata from Issue #1421:

• Labels: enhancement, level 1, recode
• Milestone: None

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
recode-website	Ready	Preview, Comment	May 6, 2026 3:19pm

This is well written blog, i requested few backlink and image changes.

🔴 One Concern Worth Flagging The sentence structure explaining flat namespace vs. hierarchical namespace closely parallels Ken Muse's 2021 blog post, which explains that in traditional Azure Storage, a file path like "myfolder/myfile.txt" has no real folder underneath — the SDKs merely split on "/" to simulate folder existence. The core idea and even the illustrative example (path with slashes that aren't real separators) match closely. Not verbatim, but structurally similar enough to warrant attribution

Didn't got your point on this paragraph

✅ Synchronized metadata from Issue #1421:

• Labels: enhancement, level 1, recode
• Milestone: None

✅ Synchronized metadata from Issue #1421:

• Labels: enhancement, level 1, recode
• Milestone: None

✅ Synchronized metadata from Issue #1421:

• Labels: enhancement, level 1, recode
• Milestone: None

✅ Synchronized metadata from Issue #1421:

• Labels: enhancement, level 1, recode
• Milestone: None

✅ Synchronized metadata from Issue #1421:

• Labels: enhancement, level 1, recode
• Milestone: None

✅ Synchronized metadata from Issue #1421:

• Labels: enhancement, level 1, recode
• Milestone: None

This is well written blog, i requested few backlink and image changes.

🔴 One Concern Worth Flagging The sentence structure explaining flat namespace vs. hierarchical namespace closely parallels Ken Muse's 2021 blog post, which explains that in traditional Azure Storage, a file path like "myfolder/myfile.txt" has no real folder underneath — the SDKs merely split on "/" to simulate folder existence. The core idea and even the illustrative example (path with slashes that aren't real separators) match closely. Not verbatim, but structurally similar enough to warrant attribution

I had wrote the entire section @sanjay-kv , we don't had any risk now .

@sanjay-kv thanks for all the suggestions you had given , i had looked thoroughly into all and resolved all of them . kindly take a look now . for me personally its far above better.

It's good.

thanks this is perfect