#1 - Boilerplate Folder Structure

[ThunderNaka]

Folder Structure Proposal

This issue aims to establish a well-organized folder structure for our project. Below are the key areas we need to address:

Some tips for you:

Keep it simple. Avoid overly complex hierarchies and file structures. Deeply nested folders can make it difficult to find files and can become unwieldy.

Consistency. Establishing and adhering to a consistent naming convention part of core file and folder structure best practices. Be logical, grouping based on factors such as category or functionality.

Accessibility and sharing. Based on goals for sharing and collaborating on files, ensure the computer file structure organization allows for ease of use among team members.

Top-Level Structure

• Define the primary directories and their purposes.

Categorization

• Determine how to categorize different types of files and components.

Components

• Structure: Outline how components, their tests, styles, hooks, and subcomponents should be organized.
• Regular vs Reusable: Specify the colocation of regular components and reusable components.

Hooks

• Define the colocation and structure for hooks.

Constants

• Establish where constants should be located.

Data Layer

• Outline the structure for everything related to API calls.

Utils

• Define the colocation for utility functions.

Styles

• Determine if there should be a dedicated styles directory and its structure.

Pages/Screens

• Colocation: Define where pages/screens should be located.
• Naming: Establish naming conventions for pages/screens.
• Structure: Specify how a screen should be organized.