website: Add GSoC 2026 logo to navbar

[Ishan-AI-coder]

Fixes #4351

What this PR does

Adds the GSoC 2026 logo, label, and "Ongoing" status badge to the top navbar,
using the same pattern previously used for GSoC 2025 (which was already
present in config.toml as a commented-out template).

• Uncommented and updated the [[menu.main]] entry in config.toml to point
  to GSoC 2026 (logo, label, badge).
• Added a stable url front-matter field to
  content/en/events/upcoming-events/gsoc-2026.md, matching the convention
  used in the 2024/2025 GSoC event pages, so the link won't break once this
  page moves to /past-events/.

Testing

Built and previewed locally with hugo server and verified the navbar
renders the logo, label, and badge correctly, linking to /events/gsoc-2026/
without a 404. Also confirmed hugo --gc --minify completes cleanly.

Notes

I'd asked on the issue whether this was still wanted but hadn't gotten a
response yet — opening this PR now so there's concrete code to review.
Happy to close or rework if this turns out to be unnecessary.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign juliusvonkohout for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[google-oss-prow]

Hi @Ishan-AI-coder. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[github-actions]

🚫 This command cannot be processed. Only organization members or owners can use the commands.

[Arhell]

/ok-to-test

[Ishan-AI-coder]

Thanks for the ok-to-test, @Arhell! 🙏
Tagging you all for visibility since this touches the navbar config and the OWNERS approval flow — @andreyvelich @juliusvonkohout @thesuperzapper.
This PR adds the GSoC 2026 logo/label/badge to the top navbar (same pattern as GSoC 2025), and adds a stable url front-matter field to the event page so the link survives the move to /past-events/ later. Verified locally with hugo server and hugo --gc --minify.
Would appreciate a look when you have a chance — happy to adjust anything per feedback.

[Copilot]

Pull request overview

Adds GSoC 2026 branding and status to the main navbar.

Changes:

• Adds the GSoC logo, label, and ongoing badge.
• Links the navbar entry to the GSoC 2026 event page.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Ishan-AI-coder]

Thanks for catching those issues @juliusvonkohout !

It turns out the stable URL front matter wasn't included in the earlier diff, and the navbar was linking to the directory-derived path instead of the stable URL, so the two didn't match.

I have pushed a commit which addresses all of the feedback by:

• Adding url = "/events/gsoc-2026/" to the front matter of gsoc-2026.md, matching the existing GSoC 2025 convention.
• Updating the navbar entry in config.toml to point to the same stable path (/events/gsoc-2026/) instead of the directory-derived path (/events/upcoming-events/gsoc-2026/).
• Setting alt="" for the decorative GSoC logo image, as suggested.

Testing

Verified locally by running:

hugo server -D

All changes render correctly, and the navbar now points to the stable URL.

[juliusvonkohout]

@thesuperzapper

[thesuperzapper]

I am not sure there is a lot of benefit to have a link which has no action possible right now (as GSOC is already in progress, not accepting applications)?

[Ishan-AI-coder]

That's a fair point @thesuperzapper — since applications aren't open, a navbar link without a clear next step probably isn't worth adding right now. Happy to close this PR, or hold it and reopen closer to a phase where the link would actually be actionable (e.g. results announcement or the next application window). Let me know what you'd prefer, or I can just close it.