Standard Header Component + Responsivenss Fixes

[saadiqbal-dev]

Resolves #141

Summary by CodeRabbit

• New Features

  • Introduced a reusable hero section component with customizable titles, descriptions, and optional action buttons for improved consistency across pages.

• Refactor

  • Replaced multiple individual hero components with the new reusable hero component throughout the app.
  • Updated layouts and containers for better responsiveness and visual alignment on various screen sizes.

• Style

  • Adjusted grid layouts and padding to enhance the appearance and usability on large screens and different devices.

• Chores

  • Removed unused hero components to streamline the codebase.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
curatedotfun-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 13, 2025 11:41am

[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 reusable HeroComponent for grid banner headers, replacing duplicated hero sections across multiple pages. The new component standardizes the hero UI, accepts props for title, description, and buttons, and is now used in the Explore, Leaderboard, Submissions, and Create Feed pages. Related redundant components are removed.

Changes

File(s)	Change Summary
frontend/src/components/CreateFeedHero.tsx, frontend/src/components/SubmissionsHero.tsx	Deleted redundant hero components previously used in Create Feed and Submissions pages.
frontend/src/components/HeroComponent.tsx	Added a new reusable, prop-driven HeroComponent for grid banner headers.
frontend/src/components/Leaderboard.tsx	Replaced inline hero section with HeroComponent; updated layout classes for consistency.
frontend/src/components/SubmissionList.tsx	Adjusted grid layout on large screens from 3 to 2 columns.
frontend/src/routes/_layout.tsx	Removed horizontal and vertical padding on main layout for medium and larger screens.
frontend/src/routes/_layout/create/feed.tsx	Swapped CreateFeedHero for HeroComponent with explicit props in the Create Feed page.
frontend/src/routes/_layout/feed/$feedId.tsx	Added max-width and overflow-y-hidden to tab navigation container for layout consistency.
frontend/src/routes/_layout/index.tsx	Replaced inline hero markup with HeroComponent in Explore page; adjusted container padding.
frontend/src/routes/_layout/submissions/_layout.tsx	Replaced SubmissionsHero with HeroComponent in Submissions layout.

Sequence Diagram(s)

sequenceDiagram
    participant Page as Any Page (Explore, Leaderboard, Submissions, Create Feed)
    participant HeroComponent
    participant UI

    Page->>HeroComponent: Render with title, description, [buttons]
    HeroComponent->>UI: Display grid banner header (end-to-end, no padding)
    UI-->>Page: Standardized hero section shown

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Common component for grid banner header (#141)	✅
End-to-end, no padding for header (considering layout) (#141)	✅
Standardize header across explore, leaderboard, submissions, create feed pages (#141)	✅

Poem

A banner stretches, edge to edge,
No padding left to hedge.
One hero now, both bold and neat,
Makes every page feel more complete.
Explore, submit, create, or lead,
Consistency’s the rabbit’s creed! 🐇✨

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

[saadiqbal-dev]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

frontend/src/components/HeroComponent.tsx (2)

9-14: Consider removing commented code.

The commented descriptionWithBreak property suggests an incomplete feature or implementation consideration that was not completed. It's generally better to remove commented code that isn't being used.

interface HeroComponentProps {
  title: string;
  description: string;
  buttons?: ButtonProps[];
-  //   descriptionWithBreak?: boolean;
}

---

40-47: Consider simplifying the variant mapping logic.

The nested ternary operators for button variant mapping can be difficult to read and maintain. Consider using a mapping object or a more explicit approach.

<Button
-  variant={
-    button.variant === "primary"
-      ? "filled"
-      : button.variant === "secondary"
-        ? "secondary"
-        : "default"
-  }
+  variant={
+    {
+      "primary": "filled",
+      "secondary": "secondary"
+    }[button.variant] || "default"
+  }
>

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1f77f1d and 49e62e7.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (10)

• frontend/src/components/CreateFeedHero.tsx (0 hunks)
• frontend/src/components/HeroComponent.tsx (1 hunks)
• frontend/src/components/Leaderboard.tsx (5 hunks)
• frontend/src/components/SubmissionList.tsx (1 hunks)
• frontend/src/components/SubmissionsHero.tsx (0 hunks)
• frontend/src/routes/_layout.tsx (1 hunks)
• frontend/src/routes/_layout/create/feed.tsx (2 hunks)
• frontend/src/routes/_layout/feed/$feedId.tsx (1 hunks)
• frontend/src/routes/_layout/index.tsx (2 hunks)
• frontend/src/routes/_layout/submissions/_layout.tsx (2 hunks)

💤 Files with no reviewable changes (2)

• frontend/src/components/SubmissionsHero.tsx
• frontend/src/components/CreateFeedHero.tsx

🧰 Additional context used

🧬 Code Graph Analysis (5)

frontend/src/routes/_layout/index.tsx (1)

frontend/src/components/HeroComponent.tsx (1)

• HeroComponent (16-57)

frontend/src/components/Leaderboard.tsx (1)

frontend/src/components/HeroComponent.tsx (1)

• HeroComponent (16-57)

frontend/src/routes/_layout/submissions/_layout.tsx (1)

frontend/src/components/HeroComponent.tsx (1)

• HeroComponent (16-57)

frontend/src/components/HeroComponent.tsx (1)

frontend/src/components/ui/button.tsx (2)

• ButtonProps (42-46)
• Button (62-62)

frontend/src/routes/_layout/create/feed.tsx (1)

frontend/src/components/HeroComponent.tsx (1)

• HeroComponent (16-57)

🔇 Additional comments (17)

frontend/src/routes/_layout.tsx (1)

17-17: Improved responsive padding for better layout

This change removes horizontal padding on medium and large screens while maintaining bottom padding. This allows content to use the full container width on larger screens, which is consistent with the broader layout refinements across the application.

frontend/src/routes/_layout/feed/$feedId.tsx (1)

128-128: Enhanced tab navigation responsiveness

Adding overflow-y-hidden and max-width constraints improves the tab navigation's responsive behavior. The 380px limit on small screens prevents layout issues, while allowing full width on medium+ screens maintains proper spacing.

frontend/src/components/SubmissionList.tsx (1)

56-56: Improved grid layout for large screens

Reducing columns from 3 to 2 on large screens creates a more consistent experience between medium and large viewports. This change provides more horizontal space for each item, improving readability and visual balance.

frontend/src/routes/_layout/create/feed.tsx (1)

3-3: Good implementation of reusable HeroComponent

Replacing the specific CreateFeedHero with the reusable HeroComponent follows the DRY principle and improves maintainability. The implementation correctly provides title and description as props, matching the component's expected interface.

Also applies to: 12-15

frontend/src/routes/_layout/submissions/_layout.tsx (2)

6-6: Well-structured import of the new reusable component.

The import for the new HeroComponent is correctly placed at the top of the file with the other imports, maintaining good code organization.

---

25-28: Good implementation of the standardized hero component.

Replacing the specific SubmissionsHero with the reusable HeroComponent improves consistency across the application. The title and description props are clearly defined with appropriate content.

frontend/src/routes/_layout/index.tsx (3)

15-15: Clean import of the reusable component.

The import for the new HeroComponent is correctly placed with the other imports.

---

142-157: Excellent implementation of the standardized hero component with button options.

The implementation effectively showcases the flexibility of the new HeroComponent by including both title, description, and multiple buttons with different variants. This demonstrates good use of the component's capabilities.

---

158-191: Improved layout organization with container wrapper.

The addition of a flex container with appropriate padding around the FeedSection components improves the structure and maintainability of the layout. The explicit comments for each section also enhance code readability.

frontend/src/components/Leaderboard.tsx (4)

5-5: Clean import of the standardized hero component.

The import for the new HeroComponent is correctly placed with the other imports.

---

112-116: Good implementation of the standardized hero component.

Replacing the custom hero section with the reusable HeroComponent improves consistency across the application and simplifies the code in this component.

---

218-218: Improved responsive design for mobile support.

Adding the max-w-[400px] constraint for smaller screens while maintaining full width on medium screens (md:max-w-full) enhances the responsiveness of the table container.

---

243-243: Enhanced overflow handling for table content.

Adding overflow-x-auto to the table body improves the user experience by ensuring that all content is accessible on smaller screens.

frontend/src/components/HeroComponent.tsx (4)

3-7: Well-structured button props interface.

The ButtonProps interface is clear and concise, providing a good abstraction for configuring buttons in the hero component with appropriate typing.

---

22-29: Good styling practices with Tailwind and inline styles.

The component effectively combines Tailwind CSS classes for layout and spacing with inline styles for background image properties. This is a clean approach that separates concerns appropriately.

---

31-34: Responsive typography implementation.

The component properly implements responsive text sizing with the Tailwind md: prefix, ensuring proper display on different screen sizes.

---

36-54: Well-implemented conditional rendering for buttons.

The component smartly checks for the existence and length of the buttons array before rendering, and properly maps through each button with appropriate styling variants. This ensures the component is flexible enough to handle various use cases.