Skip to content

Conversation

@Nexvyn
Copy link
Contributor

@Nexvyn Nexvyn commented Oct 31, 2025

Issue Reference

Fixes GitHub button links to point to the main OpsiMate repository instead of the documentation repository #41


What Was Changed

Updated all GitHub links across the documentation site to point to the main OpsiMate repository (https://github.com/OpsiMate/OpsiMate) instead of the documentation repository.

Specifically updated:

  • Header "GitHub" nav item
  • Footer "GitHub" link
  • All other "GitHub" CTAs across the docs site

Why Was It Changed

The "GitHub" button currently redirects users to the documentation repository. It should link to the main OpsiMate repository as per the bug report.

These changes ensure:

  1. All "GitHub" buttons/links across the docs site point to https://github.com/OpsiMate/OpsiMate
  2. Consistent user experience across all GitHub links
  3. Proper redirection to the main project repository

Before:

After:


Summary by CodeRabbit

  • Documentation

    • Updated repository links in the site navigation and footer
  • Style

    • Non-functional CSS cleanup (minor whitespace/formatting adjustments)

…erts

- Defined dark mode base styles for admonitions with consistent background, border, and text colors
- Customized tip, info, caution, and danger admonitions with harmonious dark color schemes
- Ensured proper styling of admonition content including paragraphs and links in dark mode
- Added alert styles for both light and dark themes with distinct color palettes per alert type
- Applied consistent alert content styling for text and links in all themes
- Included root-level CSS variable override for alert background in dark mode
- Enhanced specificity for dark mode alert content to maintain color inheritance and link decoration
@vercel
Copy link

vercel bot commented Oct 31, 2025

@Nexvyn is attempting to deploy a commit to the idan lodzki's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link

coderabbitai bot commented Oct 31, 2025

Walkthrough

Updated two GitHub repository URLs in the Docusaurus configuration and made a trivial whitespace-only edit in the custom CSS; no functional behavior or exported/public declarations were changed.

Changes

Cohort / File(s) Change Summary
Configuration updates
opsimate-docs/docusaurus.config.js
Replaced two GitHub repository hrefs in navbar/footer HTML blocks from OpsiMate/documentation to OpsiMate/OpsiMate (URL string changes only).
Whitespace-only CSS edit
opsimate-docs/src/css/custom.css
Inserted two additional blank lines after the .admonitionContent_pbrs p a:hover rule; no selector/property/behavior changes.

Possibly related PRs

Suggested labels

hacktoberfest, hacktoberfest-accepted

Suggested reviewers

  • idanlodzki

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bfb9190 and 65a600e.

📒 Files selected for processing (1)
  • opsimate-docs/src/css/custom.css (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • opsimate-docs/src/css/custom.css

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

Comment @coderabbitai help to get the list of available commands and usage tips.

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)
opsimate-docs/src/css/custom.css (1)

1067-1104: Consider consolidating duplicate alert styles.

The alert styles defined here (lines 1067-1104) duplicate the styles already defined at lines 974-1042. While the comment at line 1059 suggests this is for specificity, this duplication:

  • Increases CSS file size unnecessarily
  • Creates maintenance burden (changes must be made in two places)
  • Could be consolidated using higher-specificity selectors or CSS custom properties

Consider consolidating to a single definition:

-/* ===== DARK MODE SPECIFIC OVERRIDES (if needed) ===== */
-
-/* Dark mode alert background */
-[data-theme="dark"]:root {
-  --ifm-alert-background-color: #121212 !important;
-}
-
-/* Alternative approach - direct styling for alerts in dark mode */
-html[data-theme="dark"] .alert,
-[data-theme="dark"] .alert {
-  background-color: #121212 !important;
-  border: 1px solid #333333 !important;
-  color: #e6eef6 !important;
-}
-
-/* Tip alert (Our Mission block) - Dark mode */
-html[data-theme="dark"] .alert--tip,
-[data-theme="dark"] .alert--tip {
-  background-color: #121212 !important;
-  border: 1px solid #3949ab !important; /* Primary indigo color */
-  color: #e3f2fd !important;
-}
-
-/* Info alert - Dark mode */
-html[data-theme="dark"] .alert--info,
-[data-theme="dark"] .alert--info {
-  background-color: #121212 !important;
-  border: 1px solid #303f9f !important; /* Indigo blue */
-  color: #e3f2fd !important;
-}
-
-/* Caution alert - Dark mode */
-html[data-theme="dark"] .alert--caution,
-[data-theme="dark"] .alert--caution {
-  background-color: #121212 !important;
-  border: 1px solid #5d4037 !important; /* Brownish amber */
-  color: #ffecb3 !important;
-}
-
-/* Danger alert - Dark mode */
-html[data-theme="dark"] .alert--danger,
-[data-theme="dark"] .alert--danger {
-  background-color: #121212 !important;
-  border: 1px solid #6d4c41 !important; /* Brownish red */
-  color: #ffcdd2 !important;
-}

If the duplication was added to resolve specificity issues, please add a comment explaining why both sections are necessary.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bc0983f and bfb9190.

📒 Files selected for processing (2)
  • opsimate-docs/docusaurus.config.js (2 hunks)
  • opsimate-docs/src/css/custom.css (1 hunks)
🔇 Additional comments (2)
opsimate-docs/docusaurus.config.js (2)

61-61: LGTM! GitHub link correctly updated.

The navbar GitHub link now correctly points to the main OpsiMate repository instead of the documentation repository, aligning with the PR objectives.


137-137: LGTM! Footer GitHub link correctly updated.

The footer GitHub link now correctly points to the main OpsiMate repository, maintaining consistency with the navbar change.

@idanlodzki idanlodzki merged commit 016bd8d into OpsiMate:main Nov 5, 2025
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants