App Router is not using layout.tsx, causing unnecessary re-renders and slower rendering performance

[ru5hikesh]

Issue:

The current App Router setup does not utilize a layout.tsx file.
This leads to repeated mounting and unmounting of common components across routes.

The application should include a centralized layout.tsx so shared components (e.g., Navbar, gradient, container) remain persistent between routes.

Proposed Fix:

Introduce a layout.tsx at the appropriate levels in the App Router to wrap global elements and prevent repetitive component mounting.

This change aligns with Next.js best practices for App Router design. Maintainability through DRY principles...

I would appreciate a thumbs-up from the maintainers so I can proceed with opening a draft pull request. This involves substantial work, as there are 12 routes along with their sub-routes. @shivankacker @sainak

[Sparshagarwal29]

This makes sense and improves usability. Once the design direction is finalized, I’d be happy to help with any smaller parts of the refactor if needed

[ru5hikesh]

This makes sense and improves usability. Once the design direction is finalized, I’d be happy to help with any smaller parts of the refactor if needed

let it be...