Skip to content

Fix Contact section heading overlap beneath sticky navbar#367

Open
RiddhiBose wants to merge 4 commits into
Darshan3690:mainfrom
RiddhiBose:main
Open

Fix Contact section heading overlap beneath sticky navbar#367
RiddhiBose wants to merge 4 commits into
Darshan3690:mainfrom
RiddhiBose:main

Conversation

@RiddhiBose

@RiddhiBose RiddhiBose commented Jun 18, 2026

Copy link
Copy Markdown

Description

Fixes the layout overlapping issue where the sticky floating navigation bar obstructs the top portion of the Contact page layout, as reported in #363. The container's top spacing has been adjusted to provide an appropriate layout offset.

Changes Made

-Modified the outermost container div inside the Contact component.
-Swapped py-16 for pt-32, which explicitly sets a 128px top padding offset to clear the sticky navbar while preserving the existing bottom layout spacing.

Related Issues

Closes #363

Verification

Before: The "Get In Touch" heading text was partially cut off and layered directly underneath the floating navbar container.

Screenshot 2026-06-18 123433

After: The full heading and description text render completely visible with clean breathing room beneath the navigation menu.

Screenshot 2026-06-18 124416

Summary by CodeRabbit

  • Style
    • Updated the contact page layout wrapper to use a simpler container element, removing the previous main-content identifier.
    • Adjusted the inner section’s vertical spacing so the content starts lower (increased top padding) while keeping horizontal padding unchanged.
    • No changes to the form’s behavior, validation, or submit flow.

@vercel

vercel Bot commented Jun 18, 2026

Copy link
Copy Markdown

@RiddhiBose is attempting to deploy a commit to the Darshan Rajput's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b2f95aa5-6a36-4509-90dc-cc33835ee323

📥 Commits

Reviewing files that changed from the base of the PR and between 951b4dd and a230b82.

📒 Files selected for processing (1)
  • app/contact/page.tsx
✅ Files skipped from review due to trivial changes (1)
  • app/contact/page.tsx

📝 Walkthrough

Walkthrough

The Contact page outer wrapper is changed from a <main id="main-content"> element to a plain <div> with the same background and gradient styling. The inner container's vertical padding is updated from py-16 to pt-32, increasing top spacing to prevent the sticky navbar from overlapping the "Get In Touch" heading. No form logic, validation, or other layout elements are modified.

Changes

Contact Page Navbar Overlap Fix

Layer / File(s) Summary
Contact page wrapper and top padding adjustment
app/contact/page.tsx
Outer wrapper changed from <main id="main-content"> to <div>, and inner container padding updated from py-16 to pt-32 (keeping px-4), providing sufficient top offset to clear the sticky navbar. Closing tag updated to match.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 The navbar once hid the greeting so tall,
A header obscured, nearly lost to the wall.
With pt-32 I hopped to the fix,
Just one tiny class in the Tailwind bag of tricks.
Now "Get In Touch" shines clear for all! 🌟

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title 'Fix Contact section heading overlap beneath sticky navbar' directly summarizes the main change: fixing a layout overlap issue between the sticky navbar and Contact heading.
Linked Issues check ✅ Passed The code changes (changing py-16 to pt-32 padding and removing main id) directly address issue #363 by providing the required offset to prevent navbar overlap of the Contact section heading.
Out of Scope Changes check ✅ Passed The changes (padding adjustment from py-16 to pt-32 and markup structure modification) are within scope of fixing the navbar overlap issue, though removing the main id appears tangential to the primary spacing fix.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@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: 1

🤖 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 `@app/contact/page.tsx`:
- Around line 62-63: The ContactPage component contains a semantic HTML
violation with a nested <main id="main-content"> element that conflicts with the
layout's own main container. Remove the outer <main> wrapper element from the
return statement, and transfer any styling classes (such as the gradient
background classes like bg-gradient-to-br from-gray-50 via-blue-50/30
to-purple-50/30 and dark mode variants) to the inner container div on line 64
instead. This ensures only one <main> element exists in the document hierarchy
while preserving all visual styling on the appropriate inner container.
🪄 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: 42a9283a-4656-4b4f-8e04-853f9ca79b15

📥 Commits

Reviewing files that changed from the base of the PR and between ea88b72 and 2a0c37a.

📒 Files selected for processing (1)
  • app/contact/page.tsx

Comment thread app/contact/page.tsx Outdated
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

@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: 1

🤖 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 `@app/contact/page.tsx`:
- Line 63: The opening tag on line 63 uses a `<div>` element with the gradient
background styling, but the closing tag on line 272 incorrectly uses `</main>`
instead of `</div>`. This JSX tag mismatch will cause a parse error and break
the page. Replace the closing `</main>` tag on line 272 with `</div>` to
properly close the opening `<div>` wrapper.
🪄 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: 49713845-3fc9-4b15-bd3b-bc062e812833

📥 Commits

Reviewing files that changed from the base of the PR and between 2a0c37a and 951b4dd.

📒 Files selected for processing (1)
  • app/contact/page.tsx

Comment thread app/contact/page.tsx
@RiddhiBose

Copy link
Copy Markdown
Author

Hi! I believe the CodeRabbit comment is unrelated to the changes in this PR, as I only updated a style element. @Darshan3690 please verify whether the warning can be ignored or if any action is required from me? Thanks.

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.

[Bug]: Sticky Navbar overlaps Contact section heading on scroll/navigation

1 participant