Docs Refactor

[mikesplain]

We've had a number of attempts to refactor our docs into a docs site over the past few years and I'm hoping we can finally get this done soon. This issue will represent the core refactor, started in #5085.

The major refactor and movement is currently taking place in #7593

Outstanding issues I would like to address once that merges:

• [] Getting an actual site live on github pages
• Getting the site live on netlify: https://kops.sigs.k8s.io/
• Reduce spread and duplication of docs
  • There are quite a few docs that are similar and spread out, many were also not include in the mkdocs site yet out of sheer quantity. In order to keep Docs cleanup / mkdocs migration #7593 manageable I decided not to be too aggressive on the cleanup. I think smaller PRs will help us solve this as we go.
  • Feel free to propose changes in the form of PRs and assign them to me, ideas always welcome!
• Breaking down the kops README.md to be smaller with links to subpages in docs.
• Convert docs/index.md and docs/README.md to sym link of README.md.
• Maybe eventually turn strict checking back on, disabling strict check in mkdocs allows docs to exist in the docs folder without being on the github site while we figure out where to organize them.
• Update video and architecture diagrams

[mikesplain]

Based on kubernetes/community#3454, we can request a netlify site setup and work with Sig-docs to setup. This is likely the best bet for us!

[mrbobbytables]

/assign

[mrbobbytables]

/unassign

woops, meant to assign the k/org issue...too many tabs open

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

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]

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

[mikesplain]

/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

[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

[fejta-bot]

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]

@fejta-bot: Closing this issue.

In response to this:

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

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.