Docs: Migration from RStudio

[jmcphers]

Outline:

• Overview
  • Graphic overview of panes in RStudio and how they map to Positron
  • Guide for deciding if you should switch from RStudio to Positron (reference Key Differences)
  • Emphatic promise that RStudio is not going away
• Key feature differences
  • Features included in Positron but not RStudio
    • Remote sessions
    • Multiple R versions & consoles
    • Integrated data explorer, AI assistant, etc.
    • VS Code extensions
  • Features included in RStudio but not Positron
    • Quarto inline output
    • Profiling
    • Build & packages panes
    • Data import
    • RStudio Add-ins
    • Saving/loading workspace state
• Migration guide
  • Navigation
    • Replacing Cmd + .
    • Navigating symbols, going to definitions, etc. 
  • Keyboard shortcuts
  • Mapping between shortcuts you’re used to in RStudio and equivalents in Positron
  • Enabling RStudio shortcuts; list of supported RStudio shortcuts
  • Creating your own shortcuts
  • Code writing and formatting
    • Formatting
    • Philosophical differences, configurability (or lack thereof)
    • Snippets
  • Workspace management
    • Saving/loading tools (or lack thereof)
    • Package tools
    • Testing, building, etc.
  • Recommended settings
    • I.e. configuring Positron to act more like RStudio in various ways
  • Add-ins and Extensions
    • Recommended extensions
    • Creating Positron extensions
    • Using the RStudio API in Positron - supported/unsupported methods, etc.

[jennybc]

We already had #4157, so we should consolidate these.

[jennybc]

I don't see "command palette" above, but that definitely needs to come up.

[dhruvisompura]

Edit (07/102025) - We've added a standalone page for the command palette. We can link to that in the migration guides as needed. I have updated the suggestion below to encompass these changes.

I'm working on the content we'd want for command palette related docs. The current plan is to tailor the information for the command palette in each migration guide. The. VS Code guide needs less than the RStudio guide. See #7541 for the overall plan for command palette content.

I wanted to drop this draft here on how we can talk about the command palette for this migration guide with a focus on why/how the command palette is useful for workflows:

### Command Palette
In RStudio, many actions, such as running code, knitting a document, or opening a new script, are just a click away. In Positron, you can still access buttons and menus for these tasks, but the Command Palette offers a faster and more flexible way to perform the same actions.

The Command Palette helps you stay focused by reducing distractions. Instead of navigating menus or looking for buttons, simply search for the command you need. This feature is especially useful when you need to stay immersed in writing code, analyzing data, or editing documents.

For details on how to use the Command Palette, see the [Command Palette guide](command-palette.qmd).

#### Discovering Commands
The Command Palette brings all available commands into one searchable interface.

You no longer need to remember the exact location of every command. When you open the Command Palette, start typing a keyword or command name, and Positron will instantly show matching results. This makes it easy to discover features that might not be immediately visible in the UI.

If you don’t see an action from the RStudio toolbar, menu, or panes in the Positron IDE, try the Command Palette. The functionality is most likely available through the Command Palette.

#### Custom Commands
As you extend Positron with custom keybindings or extensions, the Command Palette makes them available just like built-in features. 

Once an extension or custom command is added, you can quickly access it from the Command Palette by typing the command name.

I think we'll need to update the custom commands section to tie in with the keybindings/custom shortcuts section of the guide.