Add a/b test for home

[elie222]

Summary by CodeRabbit

• New Features

  • Introduced a feature flag mechanism for dynamic rendering of call-to-action buttons and FAQs.
  • Added a new FAQsHome component to display FAQs based on feature flags.
  • Implemented a new FeaturesHome component that adapts content based on feature flags.

• Enhancements

  • Improved rendering logic for the Hero section to enhance user engagement based on feature availability.

• Refactor

  • Renamed the Features function to FeaturesPrivacy for clarity and introduced the FeaturesHome function for better feature flag management.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
inbox-zero	🔄 Building (Inspect)	Visit Preview	Aug 19, 2024 1:46pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The recent updates enhance the flexibility and conditional rendering of various components in the landing application by incorporating feature flags. New components like FAQsHome and FeaturesHome are introduced, and existing components undergo renaming and logic modifications to support dynamic content display. This refactoring allows for more responsive user experiences based on the application's configuration, improving clarity and maintainability.

Changes

File Path	Change Summary
apps/web/app/(landing)/home/CTAButtons.tsx	Introduced feature flag mechanism to conditionally render button text based on variants.
apps/web/app/(landing)/home/FAQs.tsx	Added FAQsHome component with conditional rendering based on the feature flag.
apps/web/app/(landing)/home/Features.tsx	Renamed Features to FeaturesPrivacy, introduced FeaturesHome, and modified rendering logic.
apps/web/app/(landing)/home/HeroAB.tsx	Updated copy object structure and enhanced property access using optional chaining.
apps/web/app/(landing)/page.tsx	Consolidated component imports and cleaned up commented-out code for better readability.

Poem

🐇 In a world of flags that flutter and sway,
Buttons now dance in a vibrant array.
FAQs and features, all set to engage,
A rabbit’s delight in this code-filled stage!
With each little change, our app's heartbeats bright,
Hop along, dear friends, let’s code through the night! 🌙✨

---

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 testing code 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 testing code 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 testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.