Make contributor site findable

[jberkus]

I've lost the URL for the contributor site, and found that there was no way to get to it if you don't already have the URL. There's no link to it from kubernetes.io that I can find, and its google rank is apparently 0.

We need to work on findability for the site if we expect it do do any good. This would include:

1. Linking from home page or community page of kubernetes.io
2. Linking from CNCF contributor page
3. Developing pattern for contributor comms that works as (1) add page to contributor site (2) make announcement that links to contributor site instead of putting content elsewhere

[sftim]

https://kubernetes.io/docs/contribute/ is a guide to contributing to Kubernetes documentation.

I'd like to redirect https://kubernetes.io/docs/contribute/ to https://www.kubernetes.dev/docs/guide/ but there's a problem: localization. https://kubernetes.io/docs/contribute/ is localized; https://www.kubernetes.dev/docs/guide/ is not. If we take the naive approach, we discard all the downstream localizations of https://kubernetes.io/docs/contribute/ and we don't have a good home for them afterwards.

I welcome suggestions on ways forward, without requiring that https://www.kubernetes.dev/ adopts localization. I'm all for localizing https://www.kubernetes.dev/, but that's going to need a lot of interest from people with the skills and the time to help out.

[mrbobbytables]

I welcome suggestions on ways forward, without requiring that https://www.kubernetes.dev/ adopts localization. I'm all for localizing https://www.kubernetes.dev/, but that's going to need a lot of interest from people with the skills and the time to help out.

Multiple groups have shown interest in localizing that content - The first real step will be to migrate the repo to the kubernetes org so we can reuse teams. There are a few other reason for that migration, but easier localization is a big one.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[jberkus]

/remove-lifecycle stale

This is still an issue.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[jberkus]

/remove-lifecycle stale

This is still unfixed

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sandipanpanda]

/remove-lifecycle stale
This is still an issue.

[jberkus]

tag @mrbobbytables

So ... this has been stuck on the localization issue for quite a while; we either need a plan for this or an acceptable workaround.

[sftim]

https://kubernetes.io/docs/contribute/ does already signpost to https://k8s.dev/

How about updating https://kubernetes.io/community/ to link there too?

[Debanitrkl]

I can help with this, we had a discussion on this in the sig-contribex upstream marketing team meeting and a few folks from the team will be guiding me about this
/assign

[chris-short]

@jberkus Do you know if we at least have 1 and 2 done?

1. Linking from home page or community page of kubernetes.io
2. Linking from CNCF contributor page

I can't find the links is why I'm asking and I'm wondering if links ended up on some other page(s)?

If not, I can work on at least these two items.

[chris-short]

@parispittman Can you share access to the Google Search Console for kubernetes.dev? I need to figure out if what we're doing is helping or not and that's usually the best place.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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.

[sftim]

I'm OK with seeing this issue reopened.

[chris-short]

Without additional data from the search engine webmaster tools I'm not sure we can assess what we've done to date has worked or not. I'm fine putting on my SEO hat if I can get access to the tools that help measure change. More specifically..

https://search.google.com/search-console

https://www.bing.com/webmasters/

There is a Google Site Verification DNS TXT record that exists for k8s.dev which leads me to believe there's already a registration there. Access can be shared with other goog accounts I believe here: https://search.google.com/search-console/users