Add link to main OpsiMate website in navbar and footer

[AKRITI-ENG]

Hi! I added the link to the main OpsiMate website as requested in issue #18.

I've added the website link in two places:

• In the navbar at the top (as a "Website" link)
• In the footer at the bottom (under a new "Resources" section)

This makes it easy for users to find the main website while reading the docs, and also helps with SEO and navigation between the main site and documentation.

Fixes #18

Summary by CodeRabbit

• New Features
  • Added a "Website" link to the main navigation bar
  • Added a "Community" section in the footer with GitHub and Slack links
  • Added a "Resources" section in the footer with Main Website and Documentation links

[vercel]

@AKRITI-ENG 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]

Walkthrough

Adds a navbar item linking to https://www.opsimate.com/ and extends the footer with a "Community" HTML block (GitHub/Slack icons) and a "Resources" block containing links to the main website and documentation in the Docusaurus config.

Changes

Cohort / File(s)	Summary
Docusaurus configuration opsimate-docs/docusaurus.config.js	Added a new navbar item (Website, href https://www.opsimate.com/, positioned left). Added footer links: a "Community" block containing HTML for GitHub and Slack icons, and a "Resources" block with links to Main Website and Documentation.

Assessment against linked issues

Objective	Addressed	Explanation
Add link to main OpsiMate website in navbar, footer, or homepage [#18]	✅

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 f25b223 and 23b9d75.

📒 Files selected for processing (1)

• opsimate-docs/docusaurus.config.js (3 hunks)

🔇 Additional comments (3)

opsimate-docs/docusaurus.config.js (3)

47-51: LGTM! Previous issue resolved.

The navbar item now correctly uses href for the external link, which is the proper Docusaurus API for external URLs. The implementation aligns with the PR objective of making the main website accessible from the documentation.

---

128-151: LGTM! Duplicate section removed.

The Community section is now present only once in the footer, resolving the previous duplication issue. The HTML implementation includes proper accessibility attributes and follows good practices for external links.

---

152-164: Resources section looks good.

The new Resources section successfully adds the main website link to the footer as intended. Both links use the correct href property. The "Documentation" link pointing to / provides a quick way to return to the documentation homepage, which can be useful for users deep in the docs.

---

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

[coderabbitai]

Actionable comments posted: 2

📜 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 728f274 and f25b223.

📒 Files selected for processing (1)

• opsimate-docs/docusaurus.config.js (2 hunks)

🔇 Additional comments (1)

opsimate-docs/docusaurus.config.js (1)

174-186: Resources section looks good, verify Documentation link destination.

The Resources section correctly adds links to the main website and documentation. The implementation uses the appropriate href property for external links.

Minor consideration: The Documentation link points to '/' (root). Verify this is the intended destination. If you want to link to the docs section specifically, you might want to use '/docs' instead:

            {
              label: 'Documentation',
-              href: '/',
+              href: '/docs',
            },

[idanlodzki]

@AKRITI-ENG please add screenshot

[AKRITI-ENG]

Hi @idanlodzki! Here is the screenshot: