Skip to content

docs: add installing guide with correct Open VSX and VSCodium guidance - #2

Open
ghost wants to merge 2 commits into
mainfrom
docs/installing-guide-vscodium
Open

docs: add installing guide with correct Open VSX and VSCodium guidance#2
ghost wants to merge 2 commits into
mainfrom
docs/installing-guide-vscodium

Conversation

@ghost

@ghost ghost commented Apr 11, 2026

Copy link
Copy Markdown

Opened by @roomote-v0 on behalf of David Duatis

Adds a new docs/getting-started/installing.mdx page with tabbed installation instructions for VS Code, VSCodium/Open VSX, and JetBrains. Key additions:

  • VSCodium / Open VSX tab with steps for installing from the Open VSX Registry (search or manual VSIX), plus an info callout noting the panel looks different from VS Code Marketplace
  • VSCodium troubleshooting section with a platform-specific table of product.json paths (Linux system/Flatpak, macOS, Windows), the correct Open VSX gallery URL, and a warning about VS Code Marketplace URLs not working
  • Navigation update in docs.json to include the new page under IDE Extensions > Getting Started

References draft PR: dduatis-star/Roo-Code-Docs#1


View task on Roo Code Cloud

@ghost

ghost commented Apr 11, 2026

Copy link
Copy Markdown
Author

Rooviewer Clock   See task

Re-review complete. The previously noted MDX rendering pitfalls are still present in the current diff.

  • Move <Info> out from inside <Step> to avoid Mintlify <Steps> child rendering issues
  • Avoid <username> in Windows path (MDX may treat as HTML tag); use {username} or escape
Previous reviews

Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.

<Step title="Install from Open VSX">
Visit the [Continue page on Open VSX](https://open-vsx.org/extension/Continue/continue) and click `Download` to get the `.vsix` file, or search for "Continue" directly in your editor's extension panel.

<Info>

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<Info> is nested inside a <Step> here; Mintlify's <Steps> component often expects only <Step> children (and the existing install page keeps <Info> outside <Steps>), so this may render incorrectly. Consider moving this callout below </Steps>.

Fix it with Roo Code or mention @roomote and request a fix.

| **Linux** (system install) | `/usr/share/codium/resources/app/product.json` |
| **Linux** (Flatpak) | `/var/lib/flatpak/app/com.vscodium.codium/current/active/files/share/codium/resources/app/product.json` |
| **macOS** | `/Applications/VSCodium.app/Contents/Resources/app/product.json` |
| **Windows** | `C:\Users\<username>\AppData\Local\Programs\VSCodium\resources\app\product.json` |

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Windows path uses C:\Users\<username>..., but in MDX the <username> can be parsed as an HTML tag and disappear in the rendered output. Using {username} or escaping the angle brackets avoids that.

Fix it with Roo Code or mention @roomote and request a fix.

@ghost

ghost commented Apr 11, 2026

Copy link
Copy Markdown
Author

Pushed a follow-up commit with three fixes:

  1. Removed duplicate nav entry -- docs.json had both ide-extensions/install and getting-started/installing in the Getting Started group. Removed the old one so only the new page appears.
  2. Added YouTube embed -- The original install page includes a YouTube iframe; the new page was missing it.
  3. Aligned punctuation style -- Removed trailing periods from step text to match the existing convention used in ide-extensions/install.mdx (Mintlify docs in this repo omit sentence-ending periods in step descriptions and info callouts).

@dduatis-star
dduatis-star marked this pull request as ready for review May 31, 2026 11:19
Repository owner locked and limited conversation to collaborators Jun 2, 2026
Repository owner unlocked this conversation Jun 2, 2026
Repository owner locked and limited conversation to collaborators Jun 2, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants