Changed layout of menu and sections (#87)

Add client redirects to support changes made to pathways

Author: hannesrudolph

.roomodes

@@ -4,7 +4,7 @@
       "slug": "docs",
       "name": "Documentation Writer",
       "roleDefinition": "You are a technical documentation writer who is a seasoned, straightforward, and technically precise expert who prioritizes clarity and efficiency. With 24 years of coding and documentation writing experience, you have a natural conversational style that values concise, no-nonsense communication. Your approach is authentic and candid, focusing relentlessly on user comprehension without overselling features or using ambiguous language. You avoid fluff, ensuring every sentence provides clear value, practical guidance, or actionable steps. The tone remains professional yet approachable, fostering immediate trust through reliability and transparency. You specialize in writing technical documentation for the Visual Studio Code extension Roo Code, using Docusaurus to structure, format, and publish content efficiently. With deep expertise in Markdown and MDX, you optimize documentation for readability, accessibility, and seamless navigation within a static-site environment built on React. It is important to ensure the content is accessible to readers with varying technical proficiencies, including those who may have learning disabilities such as ADD/ADHD, by maintaining clear structure, logical flow, and avoiding unnecessary complexity.",
-      "customInstructions": "Directness and Clarity: Each documentation entry must begin directly with what users need to know, avoiding introductory filler phrases or unnecessary context.\n\nPrecision and Brevity: Prioritize short, precise explanations and actionable steps. Users should quickly grasp concepts without needing additional clarification.\n\nAuthentic and Natural Tone: Use conversational language that reflects Roo's personality—straightforward, reliable, and trustworthy—without marketing jargon or generic phrases.\n\nPractical Examples: Include practical, realistic examples relevant to experienced developers, avoiding overly basic scenarios or clichéd tasks. Code snippets must be accurate, concise, and ready for immediate use.\n\nConsistent Formatting: Maintain a consistent format throughout, utilizing structured headings, bullet points, and brief paragraphs that facilitate quick scanning and easy comprehension.\n\nAvoid Over-explaining: Assume a reasonable level of technical competence. Do not over-explain basic coding concepts unless essential to understanding a unique Roo Code feature.\n\nProactive Anticipation: Anticipate common questions or misunderstandings proactively. Address potential issues or complexities directly within the relevant sections.\n\nMinimalism in Wording: Eliminate unnecessary adjectives, adverbs, or overly descriptive phrases. Prioritize functional language that enhances clarity and reduces cognitive load.\n\nInternal Links: Always use relative paths for internal links without including .md file extensions.\n\nCode Examples: Ensure all code snippets are clearly formatted and easy to copy-paste, maintaining consistent syntax highlighting and structure.\n\nInsert image placeholder where we need to add images, make sure to include a description of what the photo should be under the placeholder. The final version of the image in the code will always be `<img src=\"/img/installing/installing-2.png\" alt=\"VS Code's Install from VSIX dialog\" width=\"600\" />` and with the folder starting with `/img/`",
+      "customInstructions": "### Custom Instructions\n\n1. **Directness and Clarity**  \n   Begin each documentation entry with the most important information users need, avoiding introductory filler or unnecessary context.\n\n2. **Precision and Brevity**  \n   Favor short, precise explanations and actionable steps. Users should swiftly grasp concepts without requiring additional clarification.\n\n3. **Authentic and Natural Tone**  \n   Write in a conversational style that reflects Roo's straightforward, reliable, and trustworthy personality—avoiding marketing jargon or generic phrases.\n\n4. **Practical Examples**  \n   Include realistic examples aimed at experienced developers. Provide accurate, concise code snippets ready for immediate use, avoiding trivial or clichéd demos.\n\n5. **Consistent Formatting**  \n   Use structured headings, bullet points, and brief paragraphs for easy scanning and comprehension.\n\n6. **Avoid Over-explaining**  \n   Assume a reasonable level of technical competence. Do not elaborate on basic coding concepts unless it’s essential to clarify a unique Roo Code feature.\n\n7. **Proactive Anticipation**  \n   Address likely questions or pitfalls within the relevant sections. Incorporate tips or clarifications to prevent common mistakes.\n\n8. **Minimalism in Wording**  \n   Eliminate unnecessary adjectives, adverbs, or verbose descriptions. Use clear, functional language that reduces cognitive load.\n\n9. **Internal Links**  \n   Always use **relative paths** for internal links, and **omit the `.md` file extension**.  \n   Example:  \n   ```md\n   [Link to Guide](../intro/)\n\n\t10.\t@site Alias\n\t•\tFor code imports or special references that need to resolve from the project root, use the @site alias.\n\t•\tExample:\n\nimport Header from '@site/src/components/Header';\n\n\n\t•\tAvoid @site in Markdown links—use relative paths instead.\n\n\t11.\tCode Examples\nProvide clearly formatted code snippets suitable for copy-pasting. Maintain consistent syntax highlighting, indentation, and structure.\n\t12.\tImages\nInsert an image placeholder where needed. Include a brief description of the image below the placeholder. The final image element should follow this format (folder name may vary):\n\n<img src=\"/img/installing/installing-2.png\" alt=\"VS Code's Install from VSIX dialog\" width=\"600\" />\n\n(with the folder starting at /img/)",
       "groups": [
         "read",
         [

docs/advanced-usage/local-models.md

@@ -24,7 +24,6 @@ Roo Code currently supports two main local model providers:
 ## Setting Up Local Models
 
 For detailed setup instructions, see:
-
 * [Setting up Ollama](/providers/ollama)
 * [Setting up LM Studio](/providers/lmstudio)
 

docs/advanced-usage/mcp.md

@@ -8,7 +8,7 @@ Prompt engineering is the art of crafting effective instructions for AI models l
     *   **Bad:** Fix the code.
     *   **Good:** Fix the bug in the `calculateTotal` function that causes it to return incorrect results.
 
-*   **Provide Context:** Use [Context Mentions](../basic-usage/context-mentions) to refer to specific files, folders, or problems.
+*   **Provide Context:** Use [Context Mentions](/basic-usage/context-mentions) to refer to specific files, folders, or problems.
     *   **Good:** `@/src/utils.ts` Refactor the `calculateTotal` function to use async/await.
 
 *   **Break Down Tasks:** Divide complex tasks into smaller, well-defined steps.
@@ -42,7 +42,7 @@ Custom instructions are added to the system prompt, providing persistent guidanc
 *   Define project-specific conventions.
 *   Adjust Roo Code's tone or personality.
 
-See the [Custom Instructions](./custom-instructions) section for more details.
+See the [Custom Instructions](/features/custom-instructions) section for more details.
 
 ## Handling Ambiguity
 

docs/advanced-usage/prompt-engineering.md

@@ -46,6 +46,6 @@ If you set the rate limit to 10 seconds, Roo Code will wait at least 10 seconds
 *   **Use Custom Instructions:**  Provide custom instructions to guide Roo Code's behavior and reduce the need for lengthy explanations in each prompt.
 *   **Choose the Right Model:**  Some models are more cost-effective than others.  Consider using a smaller, faster model for tasks that don't require the full power of a larger model.
 *   **Use Modes:** Different modes can access different tools, for example `Architect` can't modify code, which makes it a safe choice when analyzing a complex codebase, without worrying about accidentally allowing expensive operations.
-*   **Disable MCP If Not Used:** If you're not using MCP (Model Context Protocol) features, consider [disabling it in the MCP settings](/mcp/using-mcp-in-roo#enabling-or-disabling-mcp-server-creation) to significantly reduce the size of the system prompt and save tokens.
+*   **Disable MCP If Not Used:** If you're not using MCP (Model Context Protocol) features, consider [disabling it in the MCP settings](/features/mcp/using-mcp-in-roo#enabling-or-disabling-mcp-server-creation) to significantly reduce the size of the system prompt and save tokens.
 
-By understanding and managing your API usage, you can use Roo Code effectively and efficiently.
+By understanding and managing your API usage, you can use Roo Code effectively and efficiently.

docs/advanced-usage/rate-limits-costs.md

@@ -80,4 +80,4 @@ This safety mechanism ensures you maintain control over which files are modified
 
 ## Learn More About Tools
 
-For more detailed information about each tool, including complete parameter references and advanced usage patterns, see the [Advanced Tool Reference](../advanced-usage/tool-reference) documentation.
+For more detailed information about each tool, including complete parameter references and advanced usage patterns, see the [Advanced Tool Reference](/features/tool-reference) documentation.

docs/basic-usage/how-tools-work.md

@@ -11,7 +11,7 @@ Clearly state what you want Roo Code to do.  Avoid vague or ambiguous language.
 | Strategy | Implementation |
 |----------|----------------|
 | **Be specific** | "Fix the bug in `calculateTotal` that returns incorrect results" instead of "Fix the code" |
-| **Provide context** | Use @ [Context Mentions](./context-mentions) for file and code references |
+| **Provide context** | Use @ [Context Mentions](/basic-usage/context-mentions) for file and code references |
 | **Break down tasks** | Submit complex tasks in smaller manageable steps |
 | **Include examples** | Provide sample code when you need specific formatting or style |
 

docs/basic-usage/typing-your-requests.md

@@ -73,4 +73,4 @@ Four ways to switch modes:
 
 ## Custom Modes
 
-Create your own specialized assistants by defining tool access, file permissions, and behavior instructions. Custom modes help enforce team standards or create purpose-specific assistants. See [Custom Modes documentation](../advanced-usage/custom-modes) for setup instructions.
+Create your own specialized assistants by defining tool access, file permissions, and behavior instructions. Custom modes help enforce team standards or create purpose-specific assistants. See [Custom Modes documentation](/features/custom-modes) for setup instructions.

docs/basic-usage/using-modes.md

@@ -24,7 +24,7 @@ Inspired by LangMem, this simple Rule allows you to define new rules and delete
 
 ## Custom Modes Gallery
 
-Share and discover custom modes created by the community! Learn how to create and configure custom modes in the [Custom Modes documentation](advanced-usage/custom-modes). To add your own custom mode to the gallery, create a pull request from the "Edit this page" link below.
+Share and discover custom modes created by the community! Learn how to create and configure custom modes in the [Custom Modes documentation](/features/custom-modes). To add your own custom mode to the gallery, create a pull request from the "Edit this page" link below.
 
 ### Jest Test Engineer by [@mrubens](https://github.com/mrubens)
 

docs/community.md

@@ -48,12 +48,11 @@ Roo Code is a powerful tool, and it's important to use it responsibly.  Here are
 
 ### How do I install Roo Code?
 
-See the [Installation Guide](getting-started/installing) for detailed instructions.
+See the [Installation Guide](/getting-started/installing) for detailed instructions.
 
 ### Which API providers are supported?
 
 Roo Code supports a wide range of API providers, including:
-
 *   [Anthropic (Claude)](/providers/anthropic)
 *   [OpenAI](/providers/openai)
 *   [OpenRouter](/providers/openrouter)
@@ -70,40 +69,33 @@ Roo Code supports a wide range of API providers, including:
 *   [VS Code Language Model API](/providers/vscode-lm)
 
 ### How do I get an API key?
-
 Each API provider has its own process for obtaining an API key.  See the [Setting Up Your First AI Provider](/getting-started/connecting-api-provider) for links to the relevant documentation for each provider.
 
 ### Can I use Roo Code with local models?
-
 Yes, Roo Code supports running models locally using [Ollama](/providers/ollama) and [LM Studio](/providers/lmstudio).  See [Using Local Models](/advanced-usage/local-models) for instructions.
 
 ## Usage
 
 ### How do I start a new task?
-
 Open the Roo Code panel (<Codicon name="rocket" />) and type your task in the chat box. Be clear and specific about what you want Roo Code to do. See [Typing Your Requests](/basic-usage/typing-your-requests) for best practices.
 
 ### What are modes in Roo Code?
-
 [Modes](/basic-usage/using-modes) are different personas that Roo Code can adopt, each with a specific focus and set of capabilities. The built-in modes are:
 
 *   **Code:** For general-purpose coding tasks.
 *   **Architect:** For planning and technical leadership.
 *   **Ask:** For answering questions and providing information.
 *   **Debug:** For systematic problem diagnosis.
-
-You can also create [Custom Modes](/advanced-usage/custom-modes).
+You can also create [Custom Modes](/features/custom-modes).
 
 ### How do I switch between modes?
 
 Use the dropdown menu in the chat input area to select a different mode, or use the `/` command to switch to a specific mode.
 
 ### What are tools and how do I use them?
-
 [Tools](/basic-usage/how-tools-work) are how Roo Code interacts with your system.  Roo Code automatically selects and uses the appropriate tools to complete your tasks. You don't need to call tools directly. You will be prompted to approve or reject each tool use.
 
 ### What are context mentions?
-
 [Context mentions](/basic-usage/context-mentions) are a way to provide Roo Code with specific information about your project, such as files, folders, or problems. Use the "@" symbol followed by the item you want to mention (e.g., `@/src/file.ts`, `@problems`).
 
 ### Can Roo Code access the internet?
@@ -112,7 +104,7 @@ Yes, if you are using a provider with a model that support web browsing. Be mind
 
 ### Can Roo Code run commands in my terminal?
 
-Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands. If you're experiencing issues with terminal commands, see the [Shell Integration Guide](troubleshooting/shell-integration) for troubleshooting.
+Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands. If you're experiencing issues with terminal commands, see the [Shell Integration Guide](/troubleshooting/shell-integration) for troubleshooting.
 
 ### How do I provide feedback to Roo Code?
 
@@ -128,16 +120,15 @@ Yes, you can customize Roo Code in several ways:
 *   **Settings:** Adjust various settings, such as auto-approval, diff editing, and more.
 
 ### Does Roo Code have any auto approval settings?
-Yes, Roo Code has a few settings that when enabled will automatically approve actions. Find out more [here](/advanced-usage/auto-approving-actions).
+Yes, Roo Code has a few settings that when enabled will automatically approve actions. Find out more [here](/features/auto-approving-actions).
 
 ## Advanced Features
 
 ### Can I use Roo offline?
 Yes, if you use a [local model](/advanced-usage/local-models).
 
 ### What is MCP (Model Context Protocol)?
-
-[MCP](/advanced-usage/mcp) is a protocol that allows Roo Code to communicate with external servers, extending its capabilities with custom tools and resources.
+[MCP](/features/mcp/overview) is a protocol that allows Roo Code to communicate with external servers, extending its capabilities with custom tools and resources.
 
 ### Can I create my own MCP servers?