Website: Add sig-docs contributor guide to Community project

[sftim]

This is a Feature Request _that targets https://github.com/kubernetes/community/_

Kubernetes as a project has an overall guide for contributors, and a section:
https://github.com/kubernetes/community/blob/master/contributors/guide/README.md#sig-specific-contributing-guidelines
about SIG-specific contributions.

How about we represent sig-docs there as well?
At the moment several SIGs are represented, but not documentation.

What would you like to be added

Eg, we add a page at https://github.com/kubernetes/community/blob/master/sig-docs/CONTRIBUTING.md that signposts people to the website repo, as that's where the main part of sig-docs effort goes.
and we get the main contributor guide to link to this (maybe it's automatic, I haven't checked).

We might also need to make small tweaks to other pages in this (website) repo, moving things round for a smoother experience.

Why is this needed
I'm logging this here so that it's visible as an issue in the repo that sig-docs contributors are most likely to look at.

Comments
This is a low-priority change aimed at smoothing the experience for potential and actual new contributors.

[sftim]

/sig docs

[zhangqx2010]

How about this page?
https://kubernetes.io/docs/contribute/

[irvifa]

Is this different from this one https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet ? @sftim

[sftim]

This is about signposting. We can link to all those pages to make them more discoverable.

[sftim]

/priority backlog

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

[fejta-bot]

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

[irvifa]

/remove-lifecycle rotten

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

[sftim]

/remove-lifecycle stale

[sftim]

/help
(if anyone would like to - it's a very low priority)

[k8s-ci-robot]

@sftim:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

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

In response to this:

/help
(if anyone would like to - it's a very low priority)

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.

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

[sftim]

/remove-lifecycle stale

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

[sftim]

/remove-lifecycle stale

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

[irvifa]

/remove-lifecycle stale

[sftim]

Since this was logged, we gained https://www.kubernetes.dev/

[sftim]

/priority awaiting-more-evidence
/remove-priority backlog
/close

[k8s-ci-robot]

@sftim: Closing this issue.

In response to this:

/priority awaiting-more-evidence
/remove-priority backlog
/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.