Goal
Create Separate Layouts for Auth, Dashboard, and Home Routes
Description
We need to create three separate layouts for different route groups to ensure proper layout separation and future scalability. This is a beginner-friendly issue focused only on routing and layouts.
No UI components like navbar, footer, or sidebar should be added.
Layout Requirements
- Auth Layout
Applies to routes:
/login
/register
Expected behavior:
Should not add any UI wrapper.
Should only render children directly.
No navbar, footer, sidebar, or additional markup.
- Dashboard Layout
Applies to routes:
/dashboard
All nested routes under /dashboard (e.g., /dashboard/settings)
Expected behavior:
Display only a simple text:
Dashboard layout
This is only to verify that all dashboard routes share the same layout.
Do not add a sidebar yet.
- Home Layout
Applies to route:
/
Expected behavior:
Create a separate layout only for the home page.
No navbar, footer, or additional UI components.
Acceptance Criteria
Only three layouts must be created:
Auth
Dashboard
Home
No UI components should be added:
No navbar
No footer
No sidebar
No extra UI elements
Must follow existing ESLint team rules:
Use normal function declarations
Destructure props
Do not use arrow functions for components
All existing routes must continue to work correctly.
Code must be clean, readable, and follow best practices.
Task Checklist
[ ] Create Auth layout for /login and /register
[ ] Create Dashboard layout for /dashboard and nested routes
[ ] Create Home layout for /
[ ] Verify ESLint rules are followed
[ ] Test that routes still work as expected
Goal
Create Separate Layouts for Auth, Dashboard, and Home Routes
Description
We need to create three separate layouts for different route groups to ensure proper layout separation and future scalability. This is a beginner-friendly issue focused only on routing and layouts.
No UI components like navbar, footer, or sidebar should be added.
Layout Requirements
Applies to routes:
/login
/register
Expected behavior:
Should not add any UI wrapper.
Should only render children directly.
No navbar, footer, sidebar, or additional markup.
Applies to routes:
/dashboard
All nested routes under /dashboard (e.g., /dashboard/settings)
Expected behavior:
Display only a simple text:
Dashboard layout
This is only to verify that all dashboard routes share the same layout.
Do not add a sidebar yet.
Applies to route:
/
Expected behavior:
Create a separate layout only for the home page.
No navbar, footer, or additional UI components.
Acceptance Criteria
Only three layouts must be created:
Auth
Dashboard
Home
No UI components should be added:
No navbar
No footer
No sidebar
No extra UI elements
Must follow existing ESLint team rules:
Use normal function declarations
Destructure props
Do not use arrow functions for components
All existing routes must continue to work correctly.
Code must be clean, readable, and follow best practices.
Task Checklist
[ ] Create Auth layout for /login and /register
[ ] Create Dashboard layout for /dashboard and nested routes
[ ] Create Home layout for /
[ ] Verify ESLint rules are followed
[ ] Test that routes still work as expected