Highlight contributor site from Community page

[sftim]

This is a Feature Request

What would you like to be added
Update the page at https://kubernetes.io/community/ to hyperlink, prominently, to https://k8s.dev/

Why is this needed
kubernetes/contributor-site#202 calls for making the contributor site more findable.

Comments
/language en
/good-first-issue

per SIG Docs fortnightly meeting:
/assign @occase

[k8s-ci-robot]

@sftim:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

This is a Feature Request

What would you like to be added
Update the page at https://kubernetes.io/community/ to hyperlink, prominently, to https://k8s.dev/

Why is this needed
kubernetes/contributor-site#202 calls for making the contributor site more findable.

Comments
/language en
/good-first-issue

per SIG Docs fortnightly meeting:
/assign @occase

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.

[k8s-ci-robot]

@sftim: GitHub didn't allow me to assign the following users: occase.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

This is a Feature Request

What would you like to be added
Update the page at https://kubernetes.io/community/ to hyperlink, prominently, to https://k8s.dev/

Why is this needed
kubernetes/contributor-site#202 calls for making the contributor site more findable.

Comments
/language en
/good-first-issue

per SIG Docs fortnightly meeting:
/assign @occase

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.

[sftim]

The file to change is https://github.com/kubernetes/website/blob/main/content/en/community/_index.html

Unlike most of this site, that page is in HTML. https://kubernetes.io/docs/contribute/new-content/open-a-pr/ has some general tips on what to do.
It's OK to ask questions for more advice.

[sftim]

/triage accepted
/priority backlog

[ashish-jaiswar]

/assign

[ashish-jaiswar]

@sftim somebody updated the community page before assigning this issue. I was working on same issues.

[sftim]

@ashish-jaiswar I'm afraid you're not right about the timeline. As discussed in the fortnightly SIG Docs call, I highlighted this issue to @occase in #30515 (comment). Their PR came in first too, and I was happy to approve it.

I hope that this wasn't too much of an inconvenience for you. This SIG is usually happy to pick the first PR for an issue; if someone is already likely to be working on an issue, it's polite to sync with them first before you start your own work on it.

This issue is, however, now done (by #30521).
/close

[k8s-ci-robot]

@sftim: Closing this issue.

In response to this:

@ashish-jaiswar I'm afraid you're not right about the timeline. As discussed in the fortnightly SIG Docs call, I highlighted this issue to @occase in #30515 (comment). Their PR came in first too, and I was happy to approve it.

I hope that this wasn't too much of an inconvenience for you. This SIG is usually happy to pick the first PR for an issue; if someone is already likely to be working on an issue, it's polite to sync with them first before you start your own work on it.

This issue is, however, now done (by #30521).
/close

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.