Skip to content

created home page and navigations#3

Merged
sreenandpk merged 1 commit into
developfrom
feat/FRO-3-glob-change
Jul 10, 2026
Merged

created home page and navigations#3
sreenandpk merged 1 commit into
developfrom
feat/FRO-3-glob-change

Conversation

@midhun123758

@midhun123758 midhun123758 commented Jul 10, 2026

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • New Features
    • Added a redesigned landing experience featuring a hero section, navigation, login entry point, and interactive globe.
    • Added animated stars, shooting comets, globe lighting, and visual effects.
    • Added enhanced globe interactions, including smart scrolling and automatic rotation.
    • Added styling for search, profile navigation, and billing-plan toggle controls.
  • Bug Fixes
    • Improved globe cleanup and interaction handling for smoother navigation and performance.

@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

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.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0a2ffef0-8d58-4910-9ab6-dec3de20d688

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

Use the checkbox below for a quick retry:

  • ✅ Review completed - (🔄 Check again to review again)
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/FRO-3-glob-change

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
src/index.css (1)

505-511: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Hero h1 at a fixed 7.5rem will overflow on narrow viewports.

There's no responsive handling, so on mobile the title spills horizontally. Consider a fluid size.

📱 Proposed fix
 .globe-hero h1 {
-  font-size: 7.5rem; /* Massively increased size */
+  font-size: clamp(2.5rem, 10vw, 7.5rem);
   font-weight: 800;
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/index.css` around lines 505 - 511, Make the .globe-hero h1 typography
responsive instead of using a fixed 7.5rem size: replace its font-size with a
fluid value such as clamp() that scales down on narrow viewports while
preserving the large desktop size, and adjust related spacing or letter-spacing
if needed to prevent horizontal overflow.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/features/globe/GlobeView.tsx`:
- Around line 74-77: Add an accessible name to the search input in the GlobeView
component by adding a descriptive aria-label or associating it with a visible
label; retain the existing placeholder as optional guidance.

In `@src/index.css`:
- Around line 538-556: Replace the global display:none radio rule with a
visually hidden but focusable technique scoped to .billing-toggle, preserving
keyboard and screen-reader access. Update the checked-state selectors to target
radios within .billing-toggle, and add a .billing-toggle radio focus-visible
rule that visibly outlines or highlights the adjacent .radio-custom control.

---

Nitpick comments:
In `@src/index.css`:
- Around line 505-511: Make the .globe-hero h1 typography responsive instead of
using a fixed 7.5rem size: replace its font-size with a fluid value such as
clamp() that scales down on narrow viewports while preserving the large desktop
size, and adjust related spacing or letter-spacing if needed to prevent
horizontal overflow.
🪄 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9e86ebf0-a024-4a32-93a2-d38cdca5c0c1

📥 Commits

Reviewing files that changed from the base of the PR and between dbc9570 and 47a30cc.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (4)
  • package.json
  • src/features/globe/GlobeView.tsx
  • src/features/globe/useGlobe.ts
  • src/index.css

Comment on lines +74 to +77
<div className="nav-search">
<span className="search-icon">🔍</span>
<input type="text" placeholder="Search (Ctrl+K)" />
</div>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Search input lacks an accessible name.

The placeholder is not a substitute for a label; screen-reader users get no name for this field. Add an aria-label (or associated <label>).

♿ Proposed fix
-            <input type="text" placeholder="Search (Ctrl+K)" />
+            <input type="text" placeholder="Search (Ctrl+K)" aria-label="Search" />
📝 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
<div className="nav-search">
<span className="search-icon">🔍</span>
<input type="text" placeholder="Search (Ctrl+K)" />
</div>
<div className="nav-search">
<span className="search-icon">🔍</span>
<input type="text" placeholder="Search (Ctrl+K)" aria-label="Search" />
</div>
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/globe/GlobeView.tsx` around lines 74 - 77, Add an accessible
name to the search input in the GlobeView component by adding a descriptive
aria-label or associating it with a visible label; retain the existing
placeholder as optional guidance.

Comment thread src/index.css
Comment on lines +538 to +556
input[type="radio"] {
display: none;
}

input[type="radio"]:checked + .radio-custom {
border-color: #fff;
}

input[type="radio"]:checked + .radio-custom::after {
content: '';
position: absolute;
top: 50%;
left: 50%;
transform: translate(-50%, -50%);
width: 10px;
height: 10px;
background: #fff;
border-radius: 50%;
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

display: none on radios breaks keyboard access, and the selector is unscoped.

Two problems:

  1. display: none removes the native radios from the tab order and accessibility tree, so keyboard users cannot select Monthly/Annually and the :checked + .radio-custom state can never be reached via keyboard.
  2. The bare input[type="radio"] selector is global — it hides every radio input across the app, not just those inside .billing-toggle.

Use a visually-hidden (screen-reader-accessible, still focusable) technique and scope it to the toggle. Add a visible :focus-visible style on .radio-custom so focus is perceivable.

♿ Proposed fix
-input[type="radio"] {
-  display: none;
-}
+.billing-toggle input[type="radio"] {
+  position: absolute;
+  width: 1px;
+  height: 1px;
+  padding: 0;
+  margin: -1px;
+  overflow: hidden;
+  clip: rect(0, 0, 0, 0);
+  white-space: nowrap;
+  border: 0;
+}
 
-input[type="radio"]:checked + .radio-custom {
+.billing-toggle input[type="radio"]:checked + .radio-custom {
   border-color: `#fff`;
 }
 
-input[type="radio"]:checked + .radio-custom::after {
+.billing-toggle input[type="radio"]:focus-visible + .radio-custom {
+  outline: 2px solid `#60a5fa`;
+  outline-offset: 2px;
+}
+
+.billing-toggle input[type="radio"]:checked + .radio-custom::after {
   content: '';
📝 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
input[type="radio"] {
display: none;
}
input[type="radio"]:checked + .radio-custom {
border-color: #fff;
}
input[type="radio"]:checked + .radio-custom::after {
content: '';
position: absolute;
top: 50%;
left: 50%;
transform: translate(-50%, -50%);
width: 10px;
height: 10px;
background: #fff;
border-radius: 50%;
}
.billing-toggle input[type="radio"] {
position: absolute;
width: 1px;
height: 1px;
padding: 0;
margin: -1px;
overflow: hidden;
clip: rect(0, 0, 0, 0);
white-space: nowrap;
border: 0;
}
.billing-toggle input[type="radio"]:checked + .radio-custom {
border-color: `#fff`;
}
.billing-toggle input[type="radio"]:focus-visible + .radio-custom {
outline: 2px solid `#60a5fa`;
outline-offset: 2px;
}
.billing-toggle input[type="radio"]:checked + .radio-custom::after {
content: '';
position: absolute;
top: 50%;
left: 50%;
transform: translate(-50%, -50%);
width: 10px;
height: 10px;
background: `#fff`;
border-radius: 50%;
}
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/index.css` around lines 538 - 556, Replace the global display:none radio
rule with a visually hidden but focusable technique scoped to .billing-toggle,
preserving keyboard and screen-reader access. Update the checked-state selectors
to target radios within .billing-toggle, and add a .billing-toggle radio
focus-visible rule that visibly outlines or highlights the adjacent
.radio-custom control.

@sreenandpk
sreenandpk merged commit 7f3f7a8 into develop Jul 10, 2026
1 of 2 checks passed
@sreenandpk
sreenandpk deleted the feat/FRO-3-glob-change branch July 16, 2026 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants