Integrate Python examples into Great Docs - #285
Closed
uriahf wants to merge 10 commits into
Closed
Conversation
Contributor
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
Examplesblog section to the Great Docs configuration.Why
The goal is to make the Python documentation and Python examples one coherent rtichoke experience while preserving the existing R/Python examples identity. Users can move between guides, examples, and API reference without being sent to a visibly separate Python blog site.
Validation
This repository already has a pull-request documentation workflow. The PR should build Great Docs and deploy a rendered preview to the repository's GitHub Pages
pr-previewarea. Please use that rendered preview as the acceptance check before merging.Scope
This is intentionally a draft. The existing
rtichoke_blog_pythonsite is not removed or redirected in this PR, so the current public site remains untouched while the integrated version is reviewed.