Spike: explore documentation solutions

[jpmcb]

Type of feature

🍕 Feature

Current behavior

There aren't really great docs around the CLI

Suggested solution

1. We should generate man pages for the CLI

2. We should explore documentation solutions for the CLI: an easy quick win would be using a GitHub wiki. But we may integrate latter into the open-sauced docs or deploy our own docusaurus site.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[jpmcb]

cc @BekahHW - do you have any thoughts on this? The docs should be pretty lite and relatively structured. A good example is some of the kubectl docs:

https://kubernetes.io/docs/reference/kubectl/

[BekahHW]

I think it should go in our main docs repo.

The goal is to move away from contributor resources that aren't necessary for using our product and focus on the product.

[jpmcb]

Cool cool, I can look at adding those soon