Restructure events section, and add GSoC 2025 page

[thesuperzapper]

closes #3614

This PR updates the events section of the website in the following ways:

1. Adds youtube links to recordings of past summits
2. adds a new GSoC 2025 page, to reduce the number of people contacting potential mentors
3. splits the events page into "future events" and "past events"

It also adds a GSoC banner to the top of all pages, similar to our existing summit banner.

Screenshot

[thesuperzapper]

@varodrig @jbottum @rareddy please review so we can get info about GSoC 2025 on the website

[terrytangyuan]

Should we refrain from creating GSOC 2025 page given that it hasn't started and we haven't been accepted yet?

[thesuperzapper]

Should we refrain from creating GSOC 2025 page given that it hasn't started and we haven't been accepted yet?

It's pretty much certain that we participate in some capacity, so I think there is benefit to having the page. It also says "we plan to participate", not that we are formally accepted yet.

Also, last year's mentors are getting a lot of contact from people who plan to apply this year, and I would like to have a place to point them.

[varodrig]

@thesuperzapper I think it looks fantastic really! thank you for the hard work. one suggestion is to list the future events directly on the events page. so moving the content /events/upcoming-events/ to /events/ and keep the past events as it is. let me know what you think.

[thesuperzapper]

@thesuperzapper I think it looks fantastic really! thank you for the hard work. one suggestion is to list the future events directly on the events page. so moving the content /events/upcoming-events/ to /events/ and keep the past events as it is. let me know what you think.

@varodrig I tried that, and it did not look as good, because the names of the future events were not clearly events.

Also, I'm using a hard-coded URL for the event pages so that when we move them to past events, the URL doesn't change so we don't get 404s.

[varodrig]

/lgtm

[varodrig]

Should we refrain from creating GSOC 2025 page given that it hasn't started and we haven't been accepted yet?

It's pretty much certain that we participate in some capacity, so I think there is benefit to having the page. It also says "we plan to participate", not that we are formally accepted yet.

Also, last year's mentors are getting a lot of contact from people who plan to apply this year, and I would like to have a place to point them.
in our event's detail page mentions as @thesuperzapper said:
"The Kubeflow Community plans to participate in Google Summer of Code 2025. This page aims to help you participate in GSoC 2025 with Kubeflow." @terrytangyuan let us know if you are ok with this.

[terrytangyuan]

Why not make it a GSoC page and remove “2025” from it? You can still use it to point to past events.

[thesuperzapper]

Why not make it a GSoC page and remove “2025” from it? You can still use it to point to past events.

We already have a 2024 page, which had information specific to that year (different dates, different projects, etc), and acts had a history for the project, like other "past events".

Also, it's best for SEO if we are the top result for "GSoC 2025", and have a new page for it.

It don't see the harm in having the page up.

[terrytangyuan]

Also, it's best for SEO if we are the top result for "GSoC 2025", and have a new page for it.

Nothing stops us from creating the new page later once we finalize the plan. Personally I would prefer not to over-promise anything.

Not an expert but I feel like a single GSoC page that will serve as the main entry to other past pages and get reused/revisited every year would have much better results than GSoC 2025.

[varodrig]

Also, it's best for SEO if we are the top result for "GSoC 2025", and have a new page for it.

Nothing stops us from creating the new page later once we finalize the plan. Personally I would prefer not to over-promise anything.

Not an expert but I feel like a single GSoC page that will serve as the main entry to other past pages and get reused/revisited every year would have much better results than GSoC 2025.

@thesuperzapper can we remove GSoC 2025 for now?

[rareddy]

I like the page /lgtm Great work @thesuperzapper Thank you.

I do not see any harm in having a page to show our intention to participate. It will certainly help prospective students visiting the site with timelines and project ideas at this early stage. We have seen a lot of students reaching out to project maintainers last year directly, we hopefully avoid that. How about drop down on "Events" menu? That said I do like the idea of a separate GSoc page, on the banner or not.

[thesuperzapper]

@terrytangyuan to address your concerns, I have added a specific warning to the top of the page that we have not been formally accepted yet.

I think with this change, it's worth merging the PR, as I will reduce the number of contacts past mentors/maintainers are getting (I am getting multiple a day).

[terrytangyuan]

/lgtm

[terrytangyuan]

/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: terrytangyuan

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [terrytangyuan]

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