restructure

Author: Surjit Kumar Sahoo

docs/1.architecture/6.state-management/3.global-state-redux.mdx

@@ -0,0 +1,16 @@
+---
+sidebar_position: 5
+slug: api-caching
+title: Caching API Calls
+---
+
+# Why?
+
+If the user is frequently navigation between pages, and on every page visit if we are triggering API calls to fetch the data for the page, the user will see a loading screen every single time.
+
+While it can be deemed acceptable user-experience. It can still be improved. If the data from API calls are cached. And the user frequently navigates between the pages, there's no need to call the API again, we can just return the same existing cached data.
+User will see the results instantly, no more loading screen.
+
+Only fetch the data when you really need to fetch. E.g. on the first time page visit, when the parameters change such as filters or IDs etc
+
+[API caching methods and best practices are documented here →](../1.architecture/6.state-management/4.api-and-caching.md)

docs/4.performance/5.api-caching.md

@@ -1,7 +1,7 @@
 {
   "label": "Misc Structural Guidelines",
   "collapsed": true,
-  "position": 7,
+  "position": 6,
   "link": {
     "type": "generated-index",
     "description": "Guidelines for choosing naming-conventions, avoiding nested if-checks and other structural best practices in React applications. These guidelines help maintain code readability, consistency, and ease of maintenance across your React projects."