Add enterprise page

[madhuramendis]

Purpose

Briefly describe what this pull request does.

Related Issues

Include any related issues that are resolved by this PR.

Checklist

• Updated sidebars.ts if adding a new documentation page
• Run npm run start to preview the changes locally
• Run npm run build to ensure the build passes without errors
• Verified all links are working (no broken links)

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• New Features
  • Added "Enterprise" link to the main navigation menu for quick access
  • Launched new Enterprise page featuring service offerings with detailed provider information, comprehensive feature lists, and learning resources

Walkthrough

This pull request introduces a new Enterprise page to the Docusaurus site. The changes include updating the site configuration to load a client-side module and add a navbar link, creating a new CSS module for styling the enterprise page layout with offering cards and feature lists, and implementing a React page component that renders the enterprise content using the defined styles.

Changes

Cohort / File(s)	Summary
Configuration Updates docusaurus.config.ts	Added clientModules entry to load ./src/clientModules/gtagGuard.ts and inserted a new "Enterprise" navigation link in the top navbar.
Enterprise Page Implementation src/pages/enterprise.tsx, src/pages/enterprise.module.css	Created a new Docusaurus page component with hero section, styled offering card with provider logo, tagline, and feature list. Paired with a comprehensive CSS module defining layout, card styling, feature list presentation, button styling, and responsive adjustments for mobile devices.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description contains the template structure with Purpose and Related Issues sections, but both are empty placeholders with no actual content filled in. The checklist items are present but unchecked and lack substantive information about what was done.	Fill in the Purpose section with a description of the enterprise page functionality, specify any related issues in the Related Issues section, and check off completed checklist items.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add enterprise page' directly and clearly summarizes the main change: adding a new enterprise page component with styling and configuration updates.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/pages/enterprise.module.css`:
- Around line 137-139: The current CSS rule .cButton:focus { outline: none; }
removes keyboard focus visibility and must be replaced with a visible,
accessible focus style; update the selector to use .cButton:focus-visible (or
keep :focus for broader support) and add a clear high-contrast focus indicator
(for example a 2px solid outline or visible box-shadow and outline-offset) that
uses an accessible color token (e.g., --focus-color) so keyboard users can see
focus on the CTA button; ensure you remove the outline:none rule and add the new
focus style to the .cButton ruleset.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e8738ea5-9e90-4eb6-9ed7-cd76ec8fe080

📥 Commits

Reviewing files that changed from the base of the PR and between 5225390 and bd7bae0.

📒 Files selected for processing (3)

• docusaurus.config.ts
• src/pages/enterprise.module.css
• src/pages/enterprise.tsx

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Do not remove keyboard focus visibility on the CTA button.

Line 137-Line 139 removes focus outline with no replacement, which is an accessibility regression for keyboard users.

💡 Proposed fix

-.cButton:focus {
-  outline: none;
-}
+.cButton:focus-visible {
+  outline: 2px solid var(--ifm-color-primary);
+  outline-offset: 2px;
+}

📝 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

	.cButton:focus {
	outline: none;
	}
	.cButton:focus-visible {
	outline: 2px solid var(--ifm-color-primary);
	outline-offset: 2px;
	}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/pages/enterprise.module.css` around lines 137 - 139, The current CSS rule
.cButton:focus { outline: none; } removes keyboard focus visibility and must be
replaced with a visible, accessible focus style; update the selector to use
.cButton:focus-visible (or keep :focus for broader support) and add a clear
high-contrast focus indicator (for example a 2px solid outline or visible
box-shadow and outline-offset) that uses an accessible color token (e.g.,
--focus-color) so keyboard users can see focus on the CTA button; ensure you
remove the outline:none rule and add the new focus style to the .cButton
ruleset.