fix the layout

[Aditya30ag]

Before

After

center the container for better ui

Summary by CodeRabbit

• Style
  • Refined landing page layout container styling to optimize responsive design and content presentation across different screen sizes.

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[coderabbitai]

Walkthrough

The container CSS utility class was removed from the main content wrapper in the landing page, while preserving all other styling properties including padding and positioning values.

Changes

Cohort / File(s)	Summary
CSS class removal landing-page/src/Pages/pictopy-landing.tsx	Removed container class from the main content wrapper's className; padding and z-index remain unchanged

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A class was removed, clean and neat,
The container class faced defeat,
Padding stayed put, styling intact,
A minimal change, a simple fact,
The landing page hops on with grace! 🌟

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The pull request title "fix the layout" is related to the changeset, which involves removing the container class from the main content wrapper in the landing page component. However, the title is vague and lacks specificity about what was actually changed and why. While it conveys that a layout modification was made, a teammate scanning the commit history would not understand the specific change (removal of the container class) or the concrete improvement (centering the container). The title uses a generic term that could refer to many different types of layout modifications, making it unclear and overly broad.	Consider revising the title to be more specific and descriptive. A clearer title might be "Remove container class from landing page main wrapper to center content" or "Center landing page layout by removing container constraint." This would help teammates quickly understand the specific change that was made and its purpose without requiring additional context.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

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

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 589d71f and 2751ff5.

📒 Files selected for processing (1)

• landing-page/src/Pages/pictopy-landing.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Backend Tests

[coderabbitai]

🛠️ Refactor suggestion | 🟠 Major

🧩 Analysis chain

Clean up trailing whitespace in className.

The removal of the container class aligns with the PR objective. However, there's a trailing space at the end of the className string.

Apply this diff to remove the trailing whitespace:

-      <div className="px-4 md:px-6 relative z-10 ">
+      <div className="px-4 md:px-6 relative z-10">

Additionally, verify that the layout displays correctly across all breakpoints (mobile, tablet, desktop) since removing the container class changes how the content width is constrained.

---

I'll verify the concerns in the review comment by examining the actual file content.

</script>

---

🏁 Script executed:

#!/bin/bash
# Verify the current state of the file and check for trailing whitespace
if [ -f "landing-page/src/Pages/pictopy-landing.tsx" ]; then
  echo "=== File exists ==="
  echo "=== Line 50 (with visible whitespace): ==="
  sed -n '50p' "landing-page/src/Pages/pictopy-landing.tsx" | cat -A
  echo ""
  echo "=== Lines 48-52 for context: ==="
  sed -n '48,52p' "landing-page/src/Pages/pictopy-landing.tsx"
  echo ""
  echo "=== Check for className with trailing space pattern: ==="
  rg -n 'className="[^"]*\s"' "landing-page/src/Pages/pictopy-landing.tsx"
else
  echo "File not found at landing-page/src/Pages/pictopy-landing.tsx"
fi

Length of output: 456

---

I've confirmed the trailing whitespace. Now let me verify if the container class was actually removed as claimed in the review comment.

</script>

---

🏁 Script executed:

#!/bin/bash
# Check git diff to see what changed on line 50
echo "=== Git diff for the file (if available): ==="
git diff HEAD^ -- landing-page/src/Pages/pictopy-landing.tsx 2>/dev/null | head -80 || echo "No git history available"
echo ""
echo "=== Check if 'container' class appears elsewhere in file: ==="
rg -n 'container' landing-page/src/Pages/pictopy-landing.tsx

Length of output: 738

---

Remove trailing whitespace from className.

The removal of the container class intentionally allows full-width content layout, aligning with the PR objective. However, line 50 contains a trailing space after z-10.

Apply this diff:

-      <div className="px-4 md:px-6 relative z-10 ">
+      <div className="px-4 md:px-6 relative z-10">

Verify that the layout renders correctly across all breakpoints (mobile, tablet, desktop) without the container constraint.

📝 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="px-4 md:px-6 relative z-10 ">
	<div className="px-4 md:px-6 relative z-10">

🤖 Prompt for AI Agents

In landing-page/src/Pages/pictopy-landing.tsx around line 50, the className
string "px-4 md:px-6 relative z-10 " contains a trailing space; remove the
trailing whitespace so it becomes "px-4 md:px-6 relative z-10" and ensure no
other stray spaces remain in className attributes, then run the app and verify
the layout at mobile, tablet, and desktop breakpoints renders correctly without
the removed container constraint.