Skip to content
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

[doc] API Documentation #731

Closed
gaocegege opened this issue Jul 17, 2018 · 19 comments · Fixed by kubeflow/website#521
Closed

[doc] API Documentation #731

gaocegege opened this issue Jul 17, 2018 · 19 comments · Fixed by kubeflow/website#521

Comments

@gaocegege
Copy link
Member

We need the documentation for v1alpha2 API

@richardsliu
Copy link
Contributor

Definitely need documentation and API reference for v1beta1 and stable release.

@abhi-g
Copy link
Member

abhi-g commented Oct 25, 2018

/priority p1

@netankit
Copy link

/priority p1

@carmine carmine added this to the 0.4.0 milestone Nov 6, 2018
@jlewi
Copy link
Contributor

jlewi commented Dec 3, 2018

Anyone working on this?

Any idea on how we can autogenerate docs? Is that something we can reasonable get done in time for 0.4 or should we punt to 0.5?

/cc @richardsliu

@jlewi jlewi removed the area/0.4.0 label Dec 17, 2018
@jlewi jlewi removed this from the 0.4.0 milestone Dec 17, 2018
@jlewi jlewi added this to New in 0.5.0 via automation Dec 17, 2018
@jlewi jlewi moved this from New to TFJob/PyTorch 1.0 in 0.5.0 Jan 6, 2019
@richardsliu richardsliu self-assigned this Feb 26, 2019
@richardsliu
Copy link
Contributor

We should be close to finishing the v1beta2 APIs for tf-operator. This would be a good opportunity to have API documentation ready.

@richardsliu
Copy link
Contributor

@johnugeorge
Copy link
Member

looks good. Is something else pending?

@richardsliu
Copy link
Contributor

I need to check in the tool (requires some configuration changes) and then somehow link the API reference from the kubeflow website. Then probably write the instructions on how to generate this for other operators.

@johnugeorge
Copy link
Member

SGTM

@sarahmaddox
Copy link

This looks great! Thanks @richardsliu. Some suggestions and questions:

  • The generated reference is for version v1beta2, whereas the currently available version is v1beta1. Do you know when we'll be launching v1beta2?

  • Currently, the generator pushes the output to a file called tensorflow.md in the kubeflow/tf-operator repo on GitHub. Two comments:

    • The content of the file is HTML, not Markdown, so it'd be better to use the .html extension.
    • Would it be possible to push the output directly to a doc page instead of into the kubeflow/tf-operator repo? For example, can you push the generated output to something like this: https://github.com/kubeflow/website/content/docs/reference/tfjob/v1beta2/tensorflow.html? Of course, you'd also need to change all the internal paths.
  • Similar comments for the generated file common.md - can you push the output to something like this: https://github.com/kubeflow/website/content/docs/reference/tfjob/v1beta2/common.html?

  • Does the doc generation produce just those two files (tensorflow.md and common.md)? I couldn't see any others in your forked repo, but may have missed some.

  • If you can push the generated doc directly to the kubeflow/website directory as suggested above, then I'll add a new reference section to the docs to include the TFJob reference now, and later other references.

  • As well as including the generated reference in the new reference section, I'll add a link to it from the existing TFJob guide: https://www.kubeflow.org/docs/components/tftraining/

@richardsliu
Copy link
Contributor

Thanks @sarahmaddox. We are planning to launch the v1beta2 APIs as part of 0.5.0.

So the reason for generating those two .md files in the tf-operator repo is purely out of convenience. The tool that I am using also assumes that you are generating documentation in the same repo.

I can try to generate the same content again but under kubeflow/website. Can you help create the section and navigation buttons?

@sarahmaddox
Copy link

@richardsliu
Copy link
Contributor

@sarahmaddox I've created a PR for the html files generated. Another reason for using .md is that the formatting works nicely on GitHub. But it should be simple to just add some css to style it up.

@richardsliu
Copy link
Contributor

The documentation is on the kubeflow website now: https://www.kubeflow.org/docs/reference/tfjob/v1beta1/tensorflow/

Keeping this open until the tool/instructions are also merged.

@abhi-g
Copy link
Member

abhi-g commented Mar 5, 2019 via email

@johnugeorge
Copy link
Member

@richardsliu do we need to keep docs of both versions in the website?

@richardsliu
Copy link
Contributor

We should keep docs for all the versions that we currently support (i.e. v1beta1 and v1beta2).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
0.5.0
  
Done
Development

Successfully merging a pull request may close this issue.

9 participants