REQ - Positron IDE guidance

Open Beginner friendly
#182 0 comments 0 reactions 0 assignees View on GitHub

@johannajokio is already working on this.

Since Nov 5, 2026.

  • #177 by @johannajokio — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

Start by reading the existing RStudio guidance in the repository and compare its structure with the Positron resources linked in the issue. Identify PHS-specific setup or usage considerations and draft guidance that helps users get started and understand Positron's features. Done means the repository has Positron guidance with relevant PHS details and links to Posit's documentation for standard features.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.
Posit Workbench will support multiple IDEs but the guidance that exists doesn't cover any other than RStudio. Positron is a newer IDE made available by Posit, and will likely receive some interest across the organisation, with the implementation potentially having some specific differences in the PHS infrastructure that user's should know about.

Describe what you'd like
Add guidance documents for Positron, identifying it's features and comparison with other tools to support users getting started and using the application.

Describe alternatives you've considered
Linking to Posit guidance - this should be done, especially for standard features beyond the basics. However, there are like to be PHS-specific considerations, and supporting users to get started that is better covered by a PHS-owned document.

Additional context

Dominant language
No language data
Stars
7
Forks
5
Avg merge
20h 45m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Public-Health-Scotland/technical-docs

All issues in Public-Health-Scotland/technical-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.