-
Notifications
You must be signed in to change notification settings - Fork 802
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move katib docs to website #72
Comments
/assign |
Waiting on #105. |
Should we move the Katib documentation to "Guides -> Components" or should it be part of the "Getting Started" section? |
@amsaha @jlewi My 2c is that the Katib docs should be part of "Guides -> Components". Currently the Katib guide is quite short, but we may expand it later so that it becomes more than just a getting-started guide for Katib. My thinking is that the "Getting Started" section should focus on getting started with Kubeflow as a whole, rather than on getting started with components of it. So, I think it's OK for the Minikube and gke quickstarts to be in the getting-started section, but the quickstarts for each component belong rather in the "Guides" section. An added advantage of this thinking is that we can keep the getting-started section short, which makes it simpler for new users. |
I agree with @sarahmaddox. Katib should be its own section "Hyperparameter Tuning" @amsaha If you want to take a stab at moving the existing Katib docs over that would be great. |
Thanks @sarahmaddox and @jlewi for the comments. I will work on this (thats why I assigned it to myself). So I will put it in Guides->Components->Hyperparameter Tuning. Wondering whether Katib should be part of the name (Guides->Components->Hyperparameter Tuning (Katib)) so that users who know of Katib (instead of the general area of hyperparameter tuning) can also easily locate the doc. |
/close |
Docs were added in kubeflow/kubeflow#989; we should move them to our webiste.
The text was updated successfully, but these errors were encountered: