-
Notifications
You must be signed in to change notification settings - Fork 154
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
API docs generated by reference-docs #550
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: lingyu.hou <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @greensong! It looks like this is your first PR to kubeedge/website 🎉 |
Signed-off-by: lingyu.hou <[email protected]>
@@ -0,0 +1,20 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems actually no APIs in other resources dir, we can remove this directory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Processed
@@ -0,0 +1,800 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
operations still have another API: nodeUpgradeJob Ref: https://github.com/kubeedge/kubeedge/blob/master/pkg/apis/operations/v1alpha1/type.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we added this API(nodeUpgradeJob):https://github.com/greensong/website/blob/master/docs/reference/kubeedge-api/operations-resources/node-upgrade-job-v1alpha1.md
We can add a category file under every directory like https://github.com/kubeedge/website/blob/master/docs/architecture/edge/_category_.json, name this directory with |
Sorry, I cannot find where are the common parameters from, could you help figure it out? Another optimization idea about common parameters: Now metadata details are described in every API file, autually these all seem to be the same, we can put metadata under common parameters. |
Could you please introduce how these API files auto-generated step-by-step? including, but not limited to, the reference repository (now is your personal repo), what modified you have did in the repo, and how to use it. And we can also explore how to generate the Chinese version of the API documentation in the future. |
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
Signed-off-by: guolinsheng <[email protected]>
We've made changes to the revisions,If there are areas for improvement, we will continue to make changes. |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Add API documents.
If you want to generate API documents, you can do like this:
api
andconfig
directories withinreference-docs
, create folders named with version numbers to store the new versions ofswagger.json
andtoc.yaml
files respectively.