🐞[Bug]: Homepage Contains Potentially Unreachable Modal Logic and Duplicate Hero Component Rendering

[Krishnx21]

Related Area

Frontend

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

While reviewing web/src/app/page.tsx, I noticed that the homepage renders the HeroAndDownload component multiple times with different prop values. The file also contains an inline comment:

fix-unreachable-launching-soon-modal

This suggests that part of the modal flow may be unreachable or not functioning as intended.

Having multiple render paths for the same component alongside a comment indicating unresolved modal behavior can lead to inconsistent UI states, unexpected modal triggering, or code paths that are no longer used but still remain in the codebase.

Expected behavior

Homepage UI logic should have a clear rendering flow.
Modal-related functionality should be reachable when intended.
Duplicate component renders should not create conflicting UI states.

Actual behavior:-

Multiple HeroAndDownload renders exist with different configurations.
An inline comment suggests unresolved or unreachable modal logic.
The intended modal flow is unclear from the current implementation.

Add ScreenShots

No response

What browsers are you seeing the problem on?

Chrome

Record

• I have read the Contributing Guidelines
• I'm a GSSOC'24 contributor
• I'm a GSSOC'26 contributor
• I'm a IEEE IGDTUW contributor
• I want to work on this issue

[github-actions]

Thank you for creating this issue! We'll look into it as soon as possible. Your contributions are highly appreciated! 😊

[akshayad2006-cmd]

@SB2318 I would like to contribute under GSSoC
/assign

[CodexCasper]

Hi @SB2318 , I would like to work on this issue.

My approach will be:

1. Inspect the homepage component structure and identify where the Hero section is rendered.
2. Verify whether the Hero component is being rendered multiple times directly or through nested components.
3. Trace the modal-related state, handlers, and rendering conditions to determine whether the modal logic is currently unreachable or unused.
4. Remove redundant Hero rendering while preserving the intended page layout.
5. Refactor or reconnect the modal logic depending on the intended behavior, ensuring no dead or inaccessible code remains.
6. Test the homepage thoroughly to confirm that the UI renders correctly and that any modal functionality behaves as expected.
7. Run project quality checks and submit a focused PR with screenshots and a clear explanation of the changes.

Could you please assign this issue to me?

[github-actions]

This issue has been triaged as a frontend task (level:intermediate).

Expected Effect & Scope: The issue clearly describes a problem with duplicate component rendering and potentially unreachable modal logic on the homepage, providing sufficient details for a frontend-web investigation. It is in scope and not a duplicate. The complexity of resolving inconsistent UI states and modal flows suggests an intermediate difficulty level, and it does not meet the criteria for maintainer escalation.

Hi @Krishnx21! Since you opened this issue and have no other active assignments, I have automatically assigned it to you. Happy coding!

[github-actions]

Hello @Krishnx21! Your issue #1338 has been closed. Thank you for your contribution!