This is a Feature Request

What would you like to be added
Either:

• Change https://kubernetes.io/docs/reference/kubectl/generated/ so that a “search within page” finds any subcommand; for example, I should be able to search within page for kubectl config view and find a match.
• Make a one-page version of https://kubernetes.io/docs/reference/kubectl/generated/, building the combined page during static site generation.
  • and make the one-page version easy to discover

When we do that, we can redirect https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands to the page that does include all subcommands on one page; we can do this whichever approach we picked.

Why is this needed
We want https://kubernetes.io/docs/reference/kubectl/generated/ to supersede https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands, but: the one-page legacy version is much easier to use for some tasks.

What we lose with the one page legacy version is the navigation to the rest of our docs, and a little bit of branding / UX.

Comments
The mechanism for this could use something a <details> element for revealing extra context, keeping the overall page small and readable. If we do that, we should think about how to enable a useful way to search for subcommands.