Add links (both directions) between main website and https://kubernetes.dev/

kubernetes / website

Kubernetes website and documentation repo:

https://kubernetes.io

Creative Commons Attribution 4.0 International

4.47k stars 14.39k forks source link

Add links (both directions) between main website and https://kubernetes.dev/ #23417

Closed sftim closed 3 years ago

sftim commented 4 years ago

This is a Feature Request

What would you like to be added

Alter https://www.kubernetes.dev/docs/guide/non-code-contributions/ to link to pages within https://kubernetes.io/docs/contribute/
On https://k8s.io/, signpost Kubernetes developers to https://www.kubernetes.dev/docs/guide/

Why is this needed These links help all developers find relevant contribution guides.

Comments

/language en /kind feature

sftim commented 4 years ago

/sig contributor-experience

celestehorgan commented 4 years ago

@mrbobbytables and I had a chat about this yesterday – I think the idea is to deprecate & remove the current Community page and instead link off to kubernetes.dev?

Some thoughts:

Judging by the commit history on the community page, it's mostly LF folks who've made changes in the past year or so. @zacharysarah @idvoretskyi – are there any issues on our side if we remove/replace this page?
Personally I'd like to see an external link icon (i.e. this) sit beside this link in the top header and have the link target set to _blank , so that we're clear with people that we're linking off-site. This will require a bit of Docsy layout-wrangling, I think?

sftim commented 4 years ago

Community is more than contributors: there are also live streamed events for Kubernetes users, KubeCon / CloudNativeCon, online discussions, physical meetups†, etc. I got the impression that https://www.kubernetes.dev/ is just for people doing development on Kubernetes. Is that difference important?

† consult your physician before scheduling :wink:

sftim commented 4 years ago

BTW the Docsy layout wrangling part shouldn't be too difficult, if that's the approach taken.

celestehorgan commented 4 years ago

Per discussion in the 9/22 SIG Docs meeting:

We are going to get rid of the /community page and re-home the Events & Meetups content and Code of Conduct content.
We'll link via the top nav to kubernetes.dev

sftim commented 4 years ago

We'll link via the top nav to kubernetes.dev

Hmm, this might not be as easy as I thought it would be. I'm sure it's feasible though.

fejta-bot commented 3 years ago

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-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

sftim commented 3 years ago

/remove-lifecycle stale

fejta-bot commented 3 years ago

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

fejta-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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

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

fejta-bot commented 3 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

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

k8s-ci-robot commented 3 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes/website/issues/23417#issuecomment-862609490): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

sandipanpanda commented 2 years ago

/reopen

k8s-ci-robot commented 2 years ago

@sandipanpanda: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to [this](https://github.com/kubernetes/website/issues/23417#issuecomment-952891449): >/reopen > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

sftim commented 2 years ago

I think this is done.