refactor(layout): convert to client component and optimize metadata handling

[codeunia-dev]

Remove server-side metadata generation and Geist font in favor of client-side rendering. Disable AIProvider on specific dashboard routes to improve performance.

Summary by CodeRabbit

• Style

  • Refactored font rendering system, transitioning to system defaults with enhanced antialiasing for improved cross-platform consistency and accessibility

• Changes

  • Adjusted AI feature availability: AI-powered features are now restricted and unavailable within the company dashboard section of the application

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
codeunia	Building	Preview	Comment	Nov 15, 2025 0:21am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The layout component transitioned from server-side metadata export to client-side rendering. Removed static metadata declaration and Geist font setup; added "use client" directive and pathname-based conditional rendering for AIProvider. The body className was simplified to exclude font styling.

Changes

Cohort / File(s)	Summary
Layout Component Conversion app/layout.tsx	Converted to client component with "use client" directive; removed metadata export and Geist font imports/declarations; replaced static metadata generation with runtime getPageStructuredData; added usePathname hook; implemented conditional rendering of AIProvider based on pathname check for /dashboard/company paths; simplified body className from font-specific to antialiased only

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Migration to client-side rendering: Verify that removing server-side metadata doesn't impact SEO and that structured data retrieval maintains expected behavior
• Conditional AIProvider rendering: Confirm the pathname check logic for /dashboard/company exclusion is correct and doesn't cause unintended side effects
• Font removal implications: Ensure font removal doesn't affect styling expectations across the application
• usePathname hook behavior: Verify hook usage is compatible with all target routes and renders correctly during initial page load

Poem

🐰 From server-side fonts to client-side light,
We shed the static, embrace dynamic flight!
Dashboard paths skip their provider dance,
While pathname guides our rendering's glance.
A leaner layout hops with newfound grace! 🌙

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/company-team-roles-and-invite-flow

---

📜 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 d5d4b01 and 99b9c4c.

📒 Files selected for processing (1)

• app/layout.tsx (4 hunks)

---

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.}