Fix bronze sponsor anchor navigation and align Sponsors page with community submodule

[Surajiitmjnu]

### fixed Silver sponsor section does not scroll on click

Describe the bug

When clicking on the Silver Sponsor section link (or accessing the page with a Silver sponsor anchor link), the page loads successfully but does not scroll or navigate to the Silver Sponsor section. Instead, it stays at the top of the page.

Issue

#2277

Kind of Change

• Bug fix

What Changed

• Added id="bronze-sponsors" to the Bronze Sponsors heading on the homepage to enable anchor-based navigation.
• Updated pages/overview/sponsors/index.page.tsx to load content directly from:
  _includes/community/programs/sponsors/sponsors.md
  instead of reading from pages/overview/sponsors/_index.md.

Why This Change

• Fixes anchor navigation so #bronze-sponsors scrolls correctly.

Demo

suaj_json.mp4

[github-actions]

Hi @Surajiitmjnu! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

Hi @Surajiitmjnu! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

Hi @Surajiitmjnu! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

Hi @Surajiitmjnu! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

Hi @Surajiitmjnu! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[Utkarsh-123github]

Hi @Surajiitmjnu,
The issue you mentioned is not showing up in the issues list.
Could you please tag the correct issue in your PR?
Also your PR is failing checks.
Thanks!

[github-actions]

Hi @Surajiitmjnu! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
website	✅ Ready (View Log)	Visit Preview	4af8ed0

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (dbfaf31) to head (4af8ed0).
⚠️ Report is 92 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #2288   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           30        30           
  Lines          633       672   +39     
  Branches       196       211   +15     
=========================================
+ Hits           633       672   +39     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Hi @Surajiitmjnu! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

Hi @Surajiitmjnu! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

Hi @Surajiitmjnu! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[Surajiitmjnu]

Hi @Utkarsh-123github sir

While working on this issue, I noticed that the file
_includes/community/programs/sponsors/sponsors.md
belongs to the json-schema-org/community submodule.

When I modify this .md file locally, the changes are not directly visible in the website repository PR comparison, since it only updates the submodule reference.

Before proceeding further, I would like to confirm the correct workflow:

1. Should I create a separate PR in the json-schema-org/community repository for the markdown changes, and then update the submodule reference here?
2. Or should this issue be resolved only within the website repository (without modifying the submodule)?

I want to make sure I follow the project’s contribution guidelines correctly.