Stack technologies

• React + Typescript
• Zustand - Small, fast, and scalable bearbones state management solution
• React Hook Form - Performant, flexible and extensible forms with
• React Query - Automatically caches data from your queries, reducing the need for redundant network requests and improving application performance.
• Tailwindcss - For styles
• Nextjs - framework for SSR

Important

This code structure was created using FSD (Feature-Sliced Design). Please read the FSD documentation before making any changes. Tailwind CSS and shadcn-ui are used for UI components. Define any CSS units such as px, rem, etc., in globals.css. React Query is used for API integration.

Basic requirements for the project

Note

Version Node +v20*

For Developers

npm i
# and
npm run dev
# or
yarn install
# and
yarn dev

Run the project at localhost:3000

To launch the project in the production environment, run the command:

npm i
npm run build
npm run dev
# or
yarn install
yarn build
yarn dev

run the project at localhost:3000

Note

You need to create .env.development following the example of .env.example so that all parameters are

Project structure (we will describe large sections separately inside the folder)

Root
├── .hasky - Prehooks for commits
│
├── public - All public files that will be included in the production build
│
├── src - Development folder
│   │
│   ├── api- Describes all back requests indicating the Endpoint for firebase
│   │
│   ├── app - Here is the entire project structure by structure
│   │
│   ├── assets - All images of the project should be in this folder
│   │
│   ├── components - Components common to the project that are not included in the ui
│   │
│   ├── constants - Common constants for the project that are used throughout the project
|   |
│   ├── helpers - Contains utility functions and code for auxiliary tasks throughout the project
│   │
│   ├── layouts - For all layouts of the project
│   │
│   ├── lib - Contains shared utility functions and reusable components.
|   |
│   ├── locales - All project language words are formed in this folder!
|   |
│   ├── pages - All page of the project, that is, all pages, the main code is created in this folder
|   |
│   ├── providers - All project providers are described and formed in this folder
│   │
│   ├── shared - Components that are used throughout the project
│   │
│   ├── stores - State management is written in this folder
│   │
│   ├── styles - For globals css
│   │
│   ├── types- General types by src
│   │
│   └── widgets- Contains reusable UI components and widget implementations
│
├── .env.example - Example of environment variables for production.
├── .eslintrc.json - Configuration for ESLint.
├── .gitignore - Specifies which files and directories to ignore in Git.
├── .npmrc - Configuration for npm, including registry settings and package behaviors.
├── .prettierignore - Specifies which files and directories to ignore for Prettier formatting.
├── tailwind.config.ts - Configuration for tailwind.
├── .prettierrc - Configuration for Prettier formatting.
├── next.config.ts - Configuration settings for Next.js.
├── package.json - List of project dependencies and scripts.
├── postcss.config.cjs - Configuration for PostCSS.
└── tsconfig.json - Configuration for TypeScript

☝️ - IMPORTANT:

1. The names of folders and files are always in notation (kebab-case), except for components that are both folders and files in notation (PascalCase)
2. From the component, everything always imports from the index.ts file
3. Styles are always in tailwindcss
4. Interfaces in types.ts
5. constants in constants.tsx

Code Review

1) If the code is not ready, then mark your PR as “Draft” with the “Mark as draft” button
2) Considers Architectural, Structural and other agreements on the design of PR to be critical and for this is not passed further than PR
3) The remaining comments are purely advisory in nature and are not a blocker for PR
4) Any controversial issue is discussed by the team and if there is no violation of points 1-2, then this dispute is not blocked!

☝️ - IMPORTANT:

• To type everything and anything that is possible is not to use ANY!
• any enemy! - always discuss exceptions with the team!
• avoid console.log if possible, in extreme cases console.error console.warn
• mutate values ​​outside the mobx store (use exclusively actions from the mobx store for such things.)