[Bug] Fix Folder Structure for Frontend
Opened this issue · 1 comments
Abhi0049k commented
Is there an existing issue for this?
- I have searched the existing issues
Bug Description?
The current folder structure for the frontend is inconsistent and may cause difficulty in maintaining and scaling the project. We need to reorganize the folders for better clarity, ease of use, and adherence to best practices.
Tasks:
-
Audit the existing folder structure:
- Identify any inconsistencies or redundancy in folder names or locations.
-
Propose and implement a new folder structure:
- Group related components, pages, and assets logically.
- Follow a clear and scalable naming convention (e.g., components/, pages/, hooks/, styles/, assets/).
- Ensure separation of concerns between UI components, utility functions, and business logic.
-
Update imports:
- Ensure all import paths are updated to reflect the new folder structure.
- Use relative imports where necessary to avoid deep folder references.
Acceptance Criteria:
The folder structure follows a clean and consistent organization.
All features and routes remain functional after the changes.
Documentation is updated to reflect the new structure.
Priority: High
Add Screenshots
No response
What browsers are you seeing the problem on?
No response
Record
- I agree to follow this project's Code of Conduct
- I'm a GSSOC contributor
- I want to work on this issue (Optional)
- I'm willing to provide further clarification or assistance if needed.