Move mungedocs

[artasparks]

Now that the docs are in kubernetes.github.io, I think it makes sense to move the mungedocs program and fix it up: (found here: https://github.com/kubernetes/kubernetes/tree/master/cmd/mungedocs)

Thoughts about where it should go?

• New repo (kubernetes/mungedocs)
• Into kubernetes.github.io directly
• Into kubernetes/contrib. This is my least favorite of the options since contrib is currently a general purpose dumping ground.

[bgrant0607]

@Kashomon

Yes, both kubernetes and contrib repos are dumping grounds.

I was thinking we should create a "github-tools" repo for mungedocs, mungegithub, etc.

The process @philips proposed on kubernetes-dev suggested emailing the proposal to kubernetes-dev.

cc @kubernetes/docs @kubernetes/contributor-experience

[bgrant0607]

Note that the docs in kubernetes.github.io have different formatting rules/needs than docs in other repos. The reason is that the kubernetes.github.io docs are converted to html and rendered with CSS+JS, whereas the other docs are viewed directly as markdown. One example is TOC generation, which is done dynamically for kubernetes.io and statically for markdown. Link-checking rules are different, too.

I think the previous attempt by @pwittrock was in kubernetes-retired/contrib#590

[bgrant0607]

Proposed kubernetes.github.io checks:
kubernetes/website#731
kubernetes/website#732
kubernetes/website#733
kubernetes/website#734
kubernetes/website#735
kubernetes/website#736
kubernetes/website#737
kubernetes/website#738

[spiffxp]

@david-mcmahon is cmd/mungedocs even used anymore? I looked through community, contrib, kubernetes, kubernetes.github.io, release, and test-infra and couldn't find an actual call.

ref: #38309

I think it's been replaced by https://github.com/kubernetes/md-check

[spiffxp]

I take that back, pinged on #sig-release in slack, apparently it's still used via travis for kubernetes.github.io

https://github.com/kubernetes/kubernetes.github.io/blob/2f82ff8a96bcf009fed4507100a1ade55de7fdc5/.travis.yml#L29

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

[spiffxp]

/close
This was done
kubernetes/website#5178 - moved it to kubernetes/website
kubernetes/website#5191 - removed it from kubernetes/website