Get Started > Positron #1692
Merged
Get Started > Positron #1692
Conversation
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
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1692.quarto.org 🔄 Modified Documents |
|
Howdy @cwickham -- would this be OK to rollout by the start of July? Any review of revisions we can help with? |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1692.quarto.org 🔄 Modified Documents |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1692.quarto.org 🔄 Modified Documents |
|
@mine-cetinkaya-rundel and @juliasilge, I made some changes to the language picker. How do you feel about it here: https://deploy-preview-1692.quarto.org/docs/get-started/hello/positron.html ? Thanks for all the feedback, I think I've addressed it all now. I still need to do a full round of screenshots (light and dark, no yellow tint) before merging. |
|
That looks great to me! |
cscheid
approved these changes
Jul 16, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Jul 17, 2025
(cherry picked from commit 1715f6e)
|
Successfully created backport PR for |
5 tasks
cwickham
added a commit
that referenced
this pull request
Jul 17, 2025
(cherry picked from commit 1715f6e) Co-authored-by: Charlotte Wickham <[email protected]>
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.
Audience
For Positron users, assume these are people who work with data (as opposed to VS Code flow, where readers might be software developers, or more scientific computing types).
Assume no prior knowledge of similar systems, e.g. RMarkdown.
Summary
This is mostly a reuse and blend of the RStudio and VS Code flows with the following big modifications:
computations/positron.qmd- it felt like there was too much material in this one so I trimmed heavily. Added a "Cell Workflow" section.Thoughts and questions
Can we add some CSS to minimize the appearance of the tabsets? I.e. I want to keep the tab headers (although maybe they could move to right), but would like to have tab content inline with other content (i.e. not indented). Done
The example doc doesn't show computational output in the initial screenshot. Should we re-write to move a code cell earlier? A bit more like: https://quarto.org/index.html#python-tab. Yes, it removes dependency on an external image, and helps cement the purpose of computational cells.
It might be nice to include more advanced features in the example doc like a cross-reference, or a caption. Now includes cross-reference.
Would Python users be put off by using
plotnineas opposed to something likematplotlib? (I personally like that the two example documents look identical despite the language used to create them). Verdict is, no, this is fine.Currently, this is mostly a "look at this tutorial". Should it involve more doing? I.e. "Edit the heading and re-render". No problems with first page being mostly "look at this". Next steps, could be more "do this".