fix: remove Team and Partners section

[inclinedadarsh]

Add conditional logic for displaying CTA in navbar
remove CTA from the navbar
remove Team section
remove Team from the navbar

Summary by CodeRabbit

• Refactor
  • Updated the Navbar to conditionally render the CTA link, ensuring it only displays when applicable.
  • Removed the cta prop from the Layout component affecting the Navbar and Partner component display.
  • Temporarily disabled the 'Team' section on the HomePage for future updates.

[coderabbitai]

Walkthrough

The recent updates focus on refining the user interface by adjusting visibility and relevance of components. Specifically, the changes involve conditional rendering of a Call to Action (CTA) in the Navbar based on the availability of cta data, and simplifying the HomePage by commenting out the 'Team' component and its related content. These adjustments aim to enhance user experience by ensuring content relevance and clarity.

Changes

Files	Change Summary
.../Navbar/index.jsx .../layout/index.jsx	Updated CTA rendering in Navbar; removed cta prop from Navbar and Partner.
HomePage.jsx content.js	Commented out 'Team' component and related section in HomePage content.

🐇✨

In the realm of code, where changes abound,
A rabbit hopped, leaving traces profound.
"No more clutter, no more fuss," it said,
"Only the essential, let the rest be shed."
With every leap, a cleaner path it weaves,
Celebrating change, like leaves in autumn eves.
🌟🐾

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit-tests for this file.
  • 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 generate unit tests for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between c63687b and 5f31261.

Files selected for processing (4)

• src/components/layout/Navbar/index.jsx (1 hunks)
• src/components/layout/index.jsx (1 hunks)
• src/pages/HomePage.jsx (2 hunks)
• src/pages/content.js (1 hunks)

Additional Context Used

Additional comments not posted (6)

src/pages/HomePage.jsx (2)

8-8: Commenting out code can lead to clutter. If the removal of the Team component is permanent, consider removing the line entirely.

---

22-22: Commenting out code can lead to clutter. If the removal of the Team component usage is permanent, consider removing the line entirely.

src/components/layout/index.jsx (2)

28-29: Commenting out code can lead to clutter. If the removal of the cta prop from Navbar is permanent, consider removing the commented line entirely.

---

34-34: Commenting out code can lead to clutter. If the removal of the Partner component is permanent, consider removing the commented line entirely.

src/components/layout/Navbar/index.jsx (1)

95-104: The conditional rendering of the CTA link aligns well with the PR objectives and is implemented correctly.

src/pages/content.js (1)

53-56: Commenting out code can lead to clutter. If the removal of the 'Team' section is permanent, consider removing the commented lines entirely.