Skip to content

feat: docs tab in main menu #642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Jun 19, 2025
Merged

feat: docs tab in main menu #642

merged 10 commits into from
Jun 19, 2025

Conversation

amhsirak
Copy link
Member

@amhsirak amhsirak commented Jun 13, 2025

Summary by CodeRabbit

  • New Features

    • Added a "Documentation" button with a new icon to the main menu, linking directly to the documentation site.
  • Refactor

    • Removed the "Docs" link from the user dropdown menu in the navigation bar.

Copy link

coderabbitai bot commented Jun 13, 2025

Walkthrough

This change updates navigation options related to documentation in the dashboard UI. The MainMenu now features a "Documentation" button linking to an external docs site, while the NavBar removes its "Docs" menu item from the user dropdown. No other functionality or exported entities were modified.

Changes

File(s) Change Summary
src/components/dashboard/MainMenu.tsx Replaced a commented-out API docs button with a new "Documentation" button linking externally.
src/components/dashboard/NavBar.tsx Removed the "Docs" menu item from the user dropdown menu.

Sequence Diagram(s)

Loading
sequenceDiagram
    participant User
    participant MainMenu
    participant ExternalDocs

    User->>MainMenu: Clicks "Documentation" button
    MainMenu->>ExternalDocs: Opens https://docs.maxun.dev in new tab

Possibly related PRs

Suggested labels

Type: Enhancement, Scope: UI/UX

Poem

A menu refreshed with a hop and a wink,
Docs moved around quicker than you’d think!
Buttons now point to knowledge anew,
While dropdowns shed a link or two.
With every click, a rabbit’s delight—
Navigation’s clearer, the docs are in sight!
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
src/components/dashboard/MainMenu.tsx (1)

7-7: Consider importing icons individually to improve tree-shaking

Importing from the root @mui/icons-material barrel can prevent dead-code elimination and pull the whole icon set into the bundle in some build setups. Switching to per-icon imports keeps the production bundle lean.

-import { AutoAwesome, FormatListBulleted, VpnKey, Usb, CloudQueue, Description } from "@mui/icons-material";
+import AutoAwesome from '@mui/icons-material/AutoAwesome';
+import FormatListBulleted from '@mui/icons-material/FormatListBulleted';
+import VpnKey from '@mui/icons-material/VpnKey';
+import Usb from '@mui/icons-material/Usb';
+import CloudQueue from '@mui/icons-material/CloudQueue';
+import Description from '@mui/icons-material/Description';
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ed6b22f and 1e66e07.

📒 Files selected for processing (2)
  • src/components/dashboard/MainMenu.tsx (2 hunks)
  • src/components/dashboard/NavBar.tsx (0 hunks)
💤 Files with no reviewable changes (1)
  • src/components/dashboard/NavBar.tsx

Comment on lines +114 to +116
<Button href='https://docs.maxun.dev' target="_blank" rel="noopener noreferrer" sx={buttonStyles} startIcon={<Description />}>
Documentation
</Button>
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Hard-coded label and URL bypass i18n & environment configuration

The new “Documentation” button is helpful, but:

• The label is not run through t(…), breaking translation consistency.
• A fixed URL forces code changes for staging/enterprise deployments.

-  <Button href='https://docs.maxun.dev' target="_blank" rel="noopener noreferrer" sx={buttonStyles} startIcon={<Description />}>
-    Documentation
-  </Button>
+  <Button
+    href={process.env.REACT_APP_DOCS_URL ?? 'https://docs.maxun.dev'}
+    target="_blank"
+    rel="noopener noreferrer"
+    sx={buttonStyles}
+    startIcon={<Description />}
+  >
+    {t('mainmenu.documentation')}
+  </Button>

Add mainmenu.documentation to your i18n resource files and expose REACT_APP_DOCS_URL (or equivalent) via CI/CD to keep the link configurable.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<Button href='https://docs.maxun.dev' target="_blank" rel="noopener noreferrer" sx={buttonStyles} startIcon={<Description />}>
Documentation
</Button>
<Button
href={process.env.REACT_APP_DOCS_URL ?? 'https://docs.maxun.dev'}
target="_blank"
rel="noopener noreferrer"
sx={buttonStyles}
startIcon={<Description />}
>
{t('mainmenu.documentation')}
</Button>
🤖 Prompt for AI Agents
In src/components/dashboard/MainMenu.tsx around lines 114 to 116, the
"Documentation" button label is hard-coded and not internationalized, and the
URL is fixed, which prevents translation and environment-specific configuration.
To fix this, replace the label string with a call to the translation function
t('mainmenu.documentation') and replace the hard-coded URL with a configurable
environment variable like process.env.REACT_APP_DOCS_URL. Ensure the environment
variable is exposed via CI/CD and add the key mainmenu.documentation to the i18n
resource files.

@amhsirak amhsirak added Type: Enhancement Improvements to existing features Scope: UI/UX Issues/PRs related to UI/UX labels Jun 13, 2025
@amhsirak amhsirak merged commit fb4d2d5 into develop Jun 19, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: UI/UX Issues/PRs related to UI/UX Type: Enhancement Improvements to existing features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant