Rough example layout of potentially-imported python docs #1085
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
yeah this looks good. lets shop it |
|
Let's close this since much of the work for #1109 has been done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributes to:
@chalin @austinlparker as promised:
Preview: https://deploy-preview-1085--opentelemetry.netlify.app/docs/instrumentation/python2/
This is rough since I'm not gonna spike hard on actually porting docs over, but it stays fairly consistent with the rest of the site without dropping things that were proposed here: open-telemetry/opentelemetry-python#2319 (comment)
Relative ordering of things, subsections and sub-subsections, etc. are all up for discussion of course 🙂
As mentioned in our call, there's quite a lot of existing content, so getting this up to par with JS/Java/.NET wouldn't be too heavy of a lift.