Redirect from Home Page on Session

[nikitadrokin]

Description

If a user has a valid session, visiting / will now redirect to /mail/inbox. To see the home page with a valid session, you will need to navigate to /home.

---

Type of Change

• 🎨 UI/UX improvement

Areas Affected

• 🏠 Home page

Checklist

• I have read the CONTRIBUTING document
• My code follows the project's style guidelines
• I have performed a self-review of my code
• My changes generate no new warnings

---

By submitting this pull request, I confirm that my contribution is made under the terms of the project's license.

Summary by CodeRabbit

• New Features

  • Introduced a new landing page experience with dynamic title content based on feature flags.
  • The landing page now displays a responsive layout with a blurred gradient background, improved navigation, and adaptive content for different screen sizes.
  • Users are redirected to their inbox if already signed in.

• Style

  • Enhanced visual design with updated backgrounds and dark mode support.

[vercel]

@nikitadrokin is attempting to deploy a commit to the Zero Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This change introduces a new HomeContent component that encapsulates the landing page layout and logic, including feature flag-based title rendering and responsive design elements. The main home page (apps/mail/app/page.tsx) is refactored to simplify its structure: it now checks for user session and redirects authenticated users to the inbox, while unauthenticated users see the new HomeContent. A new route file (apps/mail/app/home/page.tsx) is added to export a wrapper component for HomeContent. The previous direct rendering of UI elements and feature flag logic in the main home page is now delegated to HomeContent.

Changes

File(s)	Change Summary
apps/mail/components/home/HomeContent.tsx	Added new HomeContent component with feature flag logic, responsive layout, and UI composition.
apps/mail/app/page.tsx	Refactored to render HomeContent or redirect based on session; removed previous UI/layout logic.
apps/mail/app/home/page.tsx	Added new route file exporting a wrapper that renders HomeContent.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HomePage
    participant Session
    participant HomeContent

    User->>HomePage: Visit "/"
    HomePage->>Session: getSession()
    alt Session exists
        HomePage->>User: Redirect to "/mail/inbox"
    else No session
        HomePage->>HomeContent: Render HomeContent
        HomeContent->>FeatureGate: Check "landing_title"
        HomeContent->>User: Render landing page with conditional title and layout
    end

Loading

Possibly related PRs

• Staging #655: Modifies filtering logic inside DemoMailLayout, which is now included in the new HomeContent component.
• update home navigation menu on homepage + add login link #607: Updates the Navbar component, which is used within the new HomeContent component.

Poem

In the warren of code, a new path we see,
HomeContent now hops with simplicity.
Session checks guide where users will go,
To inbox or landing, the logic’s in flow.
With Navbar and Hero, the page feels just right—
A rabbit’s delight in the soft morning light!
🐇✨

---

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

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

apps/mail/components/home/HomeContent.tsx (1)

40-43: Consider removing or documenting commented code.

These commented lines for the "CASA Certified" section are not being used. If this is planned for future implementation, consider adding a TODO comment explaining its purpose. Otherwise, it might be cleaner to remove it.

apps/mail/app/page.tsx (1)

2-2: Remove unused import.

The DemoMailLayout component is imported but not used in this file. It should be removed to keep the imports clean.

- import { DemoMailLayout } from '@/components/mail/mail';

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ab4f90d and 32b4478.

📒 Files selected for processing (3)

• apps/mail/app/home/page.tsx (1 hunks)
• apps/mail/app/page.tsx (1 hunks)
• apps/mail/components/home/HomeContent.tsx (1 hunks)

🔇 Additional comments (4)

apps/mail/components/home/HomeContent.tsx (1)

1-48: Well-structured component with good separation of concerns.

The new HomeContent component encapsulates all landing page UI logic that was previously in the main page file. This is a good architectural decision that improves maintainability and follows the single responsibility principle.

The component correctly implements:

• Conditional rendering based on a feature flag
• Responsive design with different layouts for mobile/desktop
• Proper Suspense boundaries with fallbacks for asynchronous components

apps/mail/app/home/page.tsx (1)

1-5: Clean implementation of the explicit home route.

This simple wrapper component correctly implements the PR objective of allowing users with valid sessions to explicitly access the home page content by navigating to /home. The component is concise and follows good separation of concerns by delegating the actual content rendering to the HomeContent component.

apps/mail/app/page.tsx (2)

7-10: Session check and redirect logic implemented correctly.

The session check and redirect logic properly implements the PR objective of redirecting authenticated users from the root URL to their inbox. This improves the user experience by taking users directly to their content when they're already logged in.

---

12-12: Clean fallback to HomeContent.

For unauthenticated users, rendering the HomeContent component maintains the landing page experience while keeping the code clean and maintainable through good separation of concerns.

[MrgSub]

Let's not move the pages and just redirect them to /mail if they have a session

[nikitadrokin]

Let's not move the pages and just redirect them to /mail if they have a session

We actually need to do this. Otherwise, importing the component exported from the page would include the check for redirecting if a valid session is found. Making the page uncontrolled and adding a check outside it allows normal use.

[atharvadeosthale]

was just reading the PRs and wanted to chime in - can't we just check if the session cookie exists in the middleware and redirect immediately to /mail if it does? Would be much cleaner and will not have to move things around.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
0	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 22, 2025 6:12pm