Refactoring Redux and the Context

[MuhammadKhalilzadeh]

Note: Considering all the diverse levels of skills and applying all details, each of these issues will only take 30-60 mins to develop

Currently what we're using more state management is good; but, we can make it much better, more efficient, cleaner, and encapsulated in a better.

Here are the purposes we'll be using Redux and Context API for:

• Redux for global state management, especially when you have complex state logic, middleware needs (e.g., logging, thunks, sagas, authentication), or when you need to share state across many components.
• Context API for simpler state management or when you want to avoid prop drilling for localized state (e.g., component props, etc.).

Here are the things we'll consider to organize our state management in a better way:

• Separate Concerns: Dividing our states into logical domains (e.g., auth, user, theme). We'll use Redux for global state and Context API for localized or component-specific state.
• Modularize Redux: We'll use Redux Toolkit slices to organize our Redux code into modular, reusable pieces.
• Provide a complete and strong documentation that covers all the details

---

Here are the modules to work on according to above descriptions:

• Redux (Please use the naming convention VWRedux for the new folder) #638
• Context API (Please use the naming convention VWContext for the new folder) #639