options panel appearance on click instead of hover and popup modal design fix

[myself-alif]

…ign fix

Summary by CodeRabbit

• Improvements
  • Changed the action menu in documents to open and close with a click instead of on hover, making it easier to control visibility.
  • Improved the visibility of the upgrade popup by ensuring it always appears above all other page elements.
  • Increased spacing between admin restriction icons for better visual clarity.

[coderabbitai[bot]]

Walkthrough

This update modifies the interaction for toggling the action menu in the DocActions component from hover-based to click-based. Additionally, it increases the z-index of the UpgradePopup modal container to ensure it appears above other page elements. A minor CSS gap adjustment was made in SectionArticles. No public APIs or exported entities were changed.

Changes

Cohort / File(s)	Change Summary
DocActions Interaction Update src/components/DocActions.js	Changed action menu visibility logic from hover events to click-based toggle.
UpgradePopup Z-Index Adjustment src/components/ProPreviews/common/UpgradePopup.js	Added a very high z-index to the modal container to ensure it overlays other elements.
SectionArticles CSS Update src/components/DocListing/SectionArticles.js	Increased CSS gap between flex items from 0 to 2 units for spacing adjustment.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

A rabbit clicks, no longer hovers,
Menus pop with nimble covers.
Popups leap to the highest height,
Above all else, in z-index flight.
Gaps grow wider, spacing bright—
UI hops with pure delight! 🐇✨

[!NOTE]

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 53efe36d02b247cb75b04591f01123a55adae5b6 and 1b92116d6b11afa9b5db95ca6a19909db34ccf98.

📒 Files selected for processing (1)

• src/components/DocListing/SectionArticles.js (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• src/components/DocListing/SectionArticles.js

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

🧪 Generate unit tests

• [ ] Create PR with unit tests
• [ ] Post copyable unit tests in a comment
• [ ] Commit unit tests in branch options-panel-appearence-update-and-modal-design-fix

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 generate unit tests to generate unit tests for 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.