Minor note: Looks like those docs were auto-generated with cobra: https://github.com/spf13/cobra/blob/master/doc/md_docs.md which even has an example for kubectl.

Update: helm has a hidden command helm docs that will do just that.

Originally, we removed this section from the documentation as it was a massive blocker for users wishing to contribute documentation to Helm.

In order to re-build the CLI reference, you required the ability to build the helm CLI from source, which for many users is a major blocker for contributing to the docs... There very few users who are comfortable with Go, and even fewer comfortable with Go and Hugo.

How do we reconcile those concerns?

The only way I can imagine we address that is by setting up a netlify script that pulls the latest version of Helm down and re-generates the CLI reference every build. Perhaps that's an option here?

The only way I can imagine we address that is by setting up a netlify script that pulls the latest version of Helm down and re-generates the CLI reference every build. Perhaps that's an option here?

That would be a good option, I think, though there would need to be some minor massaging before it'd be good to go, namely: the header information (title and description) need to be grabbed from the first three lines of the generated docs, and the SEE ALSO links at the bottom need to be redirected to ../ and have the .md extension removed.

helm docs has an option to be rendered as HTML (via --output html). Hugo accepts both markdown as well as raw HTML. That could be used to work around that.

html output would be good, though I didn't see that as an option when I ran helm docs --help:

Generate documentation files for Helm.

This command can generate documentation for Helm in the following formats:

- Markdown
- Man pages

It can also generate bash autocompletions.

Usage:
  helm docs [flags]

Flags:
      --dir string    directory to which documentation is written (default "./")
  -h, --help          help for docs
      --type string   the type of documentation to generate (markdown, man, bash) (default "markdown")

The links would still need to be adjusted.

I stand corrected. Either way, we were able to work around it in Helm 2's documentation; I'm sure we can take a similar approach here as well.

@flynnduism where does this stand? I see one final task in the checkboxes.

@mattfarina this PR reinstates that section to the site, updates menus etc. However the uncertain part is extracting the latest helm cmd help content from main project repo itself. The content here in this PR is still based on v2.

In v2, mkdocs exported markdown for this and we rendered this within the docs website. The script that published it is no longer in place. I need help figuring out how to export the most-up-to-date help text to publish it here.

Actually I can do this with the info @bacongobbler provided - running helm docs --type markdown generates the content I need to complete this PR.

Ok the latest help text content has been imported and indexed. This is ready for review:
https://5e1cdeae86b7440007fd1286--helm-merge.netlify.com/docs/helm/helm/

I noted that two of the CLI commands from v2 are not documented here.

helm get notes
helm inspect readme

Assuming these are depreciated?

they weren't ported over I think. I believe they're open issues for Helm 3 to bring back

We can add them to the CLI reference once they've been reintroduced

Hey @flynnduism! Is this PR ready for another review? Let me know and I can take another look. Thanks!

@bacongobbler yep this is good to review.

I was unsure about the missing content - we can follow up separately with the docs for helm get notes andhelm inspect readme once those are reinstated in the main project.

@bacongobbler thanks, I've updated the readme

The links from the see also pages don't line up with the paths on the site. e.g.
helm home on the index goes to /docs/helm/helm/helm_home.md rather than /docs/helm/helm_home/ where it exists.

Good catch @StephenBrown2. I added a fix to correct those see also links.
Preview here. If that looks 👍 I will merge this.

LGTM, should there also be a step in the README to fix them on update?

LGTM, should there also be a step in the README to fix them on update?

Yep, this PR updates the Readme to do so here.

Yes, that's what I linked[1], but there isn't a step to fix the SEE ALSO links.

[1] the README: https://github.com/helm/helm-www/pull/401/files#diff-04c6e90faac2675aa89e2176d2eec7d8R46-R53

Yes, that's what I linked[1], but there isn't a step to fix the SEE ALSO links.

D'oh, I'm sorry. That makes total sense @StephenBrown2. I will amend with a follow up PR.