-
Notifications
You must be signed in to change notification settings - Fork 4
docs(core): rework of documentation #1558
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
Conversation
f681950 to
c7a1676
Compare
5da7a27 to
3f4ca8b
Compare
Zaggy21
left a comment
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.
Nice, the navigation is convenient. The links are broken for me, so I added suggestions for all of them. Also fixed some typos and yamls. Plugin doc is missing the reconcile annotation.
uwe-mayer
left a comment
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.
One comment, thx @Zaggy21 for checking all the links !
|
@Zaggy21 thanks actually we need to remove the md everywhere. |
This PR aims to rework the documetation structure. getting-started/core-concepts should not contain technical details but give a brief overview. How to configure the API resources should be shown under reference/components. This is a more detailed documentation and may contain some additional info on how to use the API. Next to the generated api docs. user-guides should only contain examples/tutorials that guide the user to complete a specific task. to make the navigation and finding related resources easier the refactored docs pages will now have a 'Next steps' section at the bottom of the page
Co-authored-by: Krzysztof Zagorski <[email protected]>
436d23e to
76d463c
Compare
On-behalf-of: @SAP [email protected]
Zaggy21
left a comment
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.
Just two suggestions left to resolve. Other than that looks great.
bd0a99b to
a2ec344
Compare
Description
This PR aims to rework the documetation structure.
getting-started/core-concepts should not contain
technical details but give a brief overview.
How to configure the API resources should be shown
under reference/components. This is a more detailed
documentation and may contain some additional info
on how to use the API. Next to the generated api docs.
user-guides should only contain examples/tutorials
that guide the user to complete a specific task.
to make the navigation and finding related resources
easier the refactored docs pages will now have a
'Next steps' section at the bottom of the page
fixes all the broken links
What type of PR is this? (check all applicable)
Related Tickets & Documents
Added tests?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
Checklist