-
Notifications
You must be signed in to change notification settings - Fork 30
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
Adding best practices section #836
Adding best practices section #836
Conversation
@emanuelhaine I see additional changes listed. I think you need to sync your fork/branch with the latest in meta:main |
I resolved the conflicts. Let me know if it is good now. |
docs/_sidebar.md
Outdated
@@ -9,6 +9,8 @@ | |||
- [Newly Released Packages](/newly_released.md) | |||
- [Package Vulnerabilities](/Vulnerabilities.md) | |||
- [Current Status](/Progress.md) | |||
- [Best Practices](/Guides/section.md) | |||
- zopen |
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.
Are you able to create a stub page for these?
de35f31
to
4f343b0
Compare
It is done. Let me know if you need anything else. |
Thanks, next step would be adding the content but I'm ok with this for now. Perhaps add "(coming soon)" or or similar in the content for now? |
44dec27
to
a892f4b
Compare
@IgorTodorovskiIBM , I added the "(coming soon)" to new pages that I created |
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.
LGTM
As I talked to Igor, I am opening this PR so I can start helping on the issus below:
#830
#831
This PR introduces the Best Practics section to the zopen docs