From b5677735b09b162776307a5197d0ae6be7b7db98 Mon Sep 17 00:00:00 2001
From: Sivaprasath <121082414+sivaprasath2004@users.noreply.github.com>
Date: Sat, 27 Jul 2024 08:21:24 +0530
Subject: [PATCH 1/4] Add 255 lc solution
---
...Preorder-Sequence-in-Binary-Search-Tree.md | 367 ++++++++++++++++++
1 file changed, 367 insertions(+)
create mode 100644 dsa-solutions/lc-solutions/0200-0299/0255-Verify-Preorder-Sequence-in-Binary-Search-Tree.md
diff --git a/dsa-solutions/lc-solutions/0200-0299/0255-Verify-Preorder-Sequence-in-Binary-Search-Tree.md b/dsa-solutions/lc-solutions/0200-0299/0255-Verify-Preorder-Sequence-in-Binary-Search-Tree.md
new file mode 100644
index 000000000..a53382081
--- /dev/null
+++ b/dsa-solutions/lc-solutions/0200-0299/0255-Verify-Preorder-Sequence-in-Binary-Search-Tree.md
@@ -0,0 +1,367 @@
+---
+id: verify-preorder-sequence-in-binary-search-tree
+title: Verify Preorder Sequence in Binary Search Tree
+sidebar_label: 0255-Verify Preorder Sequence in Binary Search Tree
+tags: [Hash Map, Two Pointers,Binary Search Tree]
+description: Solution to finding and Verify Preorder Sequence in Binary Search Tree.
+---
+
+### Description
+
+Given an array of numbers, verify whether it is the correct preorder traversal sequence of a binary search tree.
+
+You may assume each number in the sequence is unique.
+
+Consider the following binary search tree:
+
+```bash
+ 5
+ / \
+ 2 6
+ / \
+ 1 3
+```
+
+### Example:
+
+**Example 1:**
+```bash
+Input: [5,2,6,1,3]
+Output: false
+```
+
+
+**Example 2:**
+```bash
+Input: [5,2,1,3,6]
+Output: true
+```
+### Solution
+
+#### **Approach**
+
+- Use a stack to simulate the traversal.
+- Maintain a variable `low` which represents the lowest value that the next node can take. Initially, set `low` to negative infinity.
+- Iterate through the array:
+ - If we encounter a value less than `low`, it means the sequence is invalid.
+ - If the current value is greater than the top of the stack, keep popping from the stack and update `low` to the value of the last popped element. This ensures that we are correctly moving to the right subtree.
+ - Push the current value onto the stack.
+
+
+
+
+
+
+```javascript
+function verifyPreorder(preorder) {
+ let stack = [];
+ let low = -Infinity;
+
+ for (let value of preorder) {
+ if (value < low) {
+ return false;
+ }
+ while (stack.length > 0 && value > stack[stack.length - 1]) {
+ low = stack.pop();
+ }
+ stack.push(value);
+ }
+ return true;
+}
+
+// Example usage:
+const preorder1 = [5, 2, 6, 1, 3];
+console.log(verifyPreorder(preorder1)); // Output: false
+
+const preorder2 = [5, 2, 1, 3, 6];
+console.log(verifyPreorder(preorder2)); // Output: true
+```
+
+
+
+
+
+
+```typescript
+function verifyPreorder(preorder: number[]): boolean {
+ let stack: number[] = [];
+ let low: number = -Infinity;
+
+ for (let value of preorder) {
+ if (value < low) {
+ return false;
+ }
+ while (stack.length > 0 && value > stack[stack.length - 1]) {
+ low = stack.pop()!;
+ }
+ stack.push(value);
+ }
+ return true;
+}
+
+// Example usage:
+const preorder1: number[] = [5, 2, 6, 1, 3];
+console.log(verifyPreorder(preorder1)); // Output: false
+
+const preorder2: number[] = [5, 2, 1, 3, 6];
+console.log(verifyPreorder(preorder2)); // Output: true
+```
+
+
+
+
+
+
+```python
+def verifyPreorder(preorder):
+ stack = []
+ low = float('-inf')
+
+ for value in preorder:
+ if value < low:
+ return False
+ while stack and value > stack[-1]:
+ low = stack.pop()
+ stack.append(value)
+
+ return True
+
+# Example usage:
+preorder1 = [5, 2, 6, 1, 3]
+print(verifyPreorder(preorder1)) # Output: False
+
+preorder2 = [5, 2, 1, 3, 6]
+print(verifyPreorder(preorder2)) # Output: True
+```
+
+
+
+
+
+```java
+import java.util.Stack;
+
+public class Solution {
+ public boolean verifyPreorder(int[] preorder) {
+ Stack stack = new Stack<>();
+ int low = Integer.MIN_VALUE;
+
+ for (int value : preorder) {
+ if (value < low) {
+ return false;
+ }
+ while (!stack.isEmpty() && value > stack.peek()) {
+ low = stack.pop();
+ }
+ stack.push(value);
+ }
+ return true;
+ }
+
+ public static void main(String[] args) {
+ Solution solution = new Solution();
+
+ int[] preorder1 = {5, 2, 6, 1, 3};
+ System.out.println(solution.verifyPreorder(preorder1)); // Output: false
+
+ int[] preorder2 = {5, 2, 1, 3, 6};
+ System.out.println(solution.verifyPreorder(preorder2)); // Output: true
+ }
+}
+```
+
+
+
+
+```cpp
+#include
+#include
+#include
+#include
+
+using namespace std;
+
+class Solution {
+public:
+ bool verifyPreorder(vector& preorder) {
+ stack stk;
+ int low = INT_MIN;
+
+ for (int value : preorder) {
+ if (value < low) {
+ return false;
+ }
+ while (!stk.empty() && value > stk.top()) {
+ low = stk.top();
+ stk.pop();
+ }
+ stk.push(value);
+ }
+
+ return true;
+ }
+};
+
+int main() {
+ Solution solution;
+
+ vector preorder1 = {5, 2, 6, 1, 3};
+ cout << (solution.verifyPreorder(preorder1) ? "true" : "false") << endl; // Output: false
+
+ vector preorder2 = {5, 2, 1, 3, 6};
+ cout << (solution.verifyPreorder(preorder2) ? "true" : "false") << endl; // Output: true
+
+ return 0;
+}
+```
+
+
+
+
+
+### Explanation:
+
+
+
+
+
+
+1. **Initialization**:
+ - A stack is used to keep track of the nodes.
+ - `low` is initialized to `-Infinity` to represent the smallest possible value initially.
+
+2. **Iteration**:
+ - For each value in the `preorder` array:
+ - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `false`.
+ - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
+ - Push the current value onto the stack.
+
+3. **Return**:
+ - If we successfully iterate through the entire array without finding any violations, return `true`.
+
+
+
+
+
+
+1. **Initialization**:
+ - A stack is used to keep track of the nodes.
+ - `low` is initialized to `-Infinity` to represent the smallest possible value initially.
+
+2. **Iteration**:
+ - For each value in the `preorder` array:
+ - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `false`.
+ - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
+ - Push the current value onto the stack.
+
+3. **Return**:
+ - If we successfully iterate through the entire array without finding any violations, return `true`.
+
+
+
+
+
+1. **Initialization**:
+ - A stack is used to keep track of the nodes.
+ - `low` is initialized to negative infinity to represent the smallest possible value initially.
+
+2. **Iteration**:
+ - For each value in the `preorder` array:
+ - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `False`.
+ - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
+ - Push the current value onto the stack.
+
+3. **Return**:
+ - If we successfully iterate through the entire array without finding any violations, return `True`.
+
+
+
+
+
+1. **Initialization**:
+ - A stack is used to keep track of the nodes.
+ - `low` is initialized to `Integer.MIN_VALUE` to represent the smallest possible value initially.
+
+2. **Iteration**:
+ - For each value in the `preorder` array:
+ - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `false`.
+ - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
+ - Push the current value onto the stack.
+
+3. **Return**:
+ - If we successfully iterate through the entire array without finding any violations, return `true`.
+
+
+
+
+
+1. **Initialization**:
+ - A stack is used to keep track of the nodes.
+ - `low` is initialized to `INT_MIN` to represent the smallest possible value initially.
+
+2. **Iteration**:
+ - For each value in the `preorder` array:
+ - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `false`.
+ - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
+ - Push the current value onto the stack.
+
+3. **Return**:
+ - If we successfully iterate through the entire array without finding any violations, return `true`.
+
+
+
+
+
+### Complexity:
+
+
+
+
+
+
+- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
+- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
+
+
+
+
+
+- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
+- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
+
+
+
+
+
+
+- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
+- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
+
+
+
+
+
+- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
+- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
+
+
+
+- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
+- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
+
+
+
+
+
+
+## References
+
+- **LeetCode Problem:** [Binary Search Tree](https://leetcode.com/problems/verify-preorder-sequence-in-binary-search-tree/)
+
+
Author:
+
+
+{['sivaprasath2004'].map(username => (
+
+))}
+
From 16a0988c98535b721e900a399659cf1e6d308150 Mon Sep 17 00:00:00 2001
From: Sivaprasath <121082414+sivaprasath2004@users.noreply.github.com>
Date: Sat, 27 Jul 2024 08:22:11 +0530
Subject: [PATCH 2/4] wrong Attempt
---
...Preorder-Sequence-in-Binary-Search-Tree.md | 367 ------------------
1 file changed, 367 deletions(-)
delete mode 100644 dsa-solutions/lc-solutions/0200-0299/0255-Verify-Preorder-Sequence-in-Binary-Search-Tree.md
diff --git a/dsa-solutions/lc-solutions/0200-0299/0255-Verify-Preorder-Sequence-in-Binary-Search-Tree.md b/dsa-solutions/lc-solutions/0200-0299/0255-Verify-Preorder-Sequence-in-Binary-Search-Tree.md
deleted file mode 100644
index a53382081..000000000
--- a/dsa-solutions/lc-solutions/0200-0299/0255-Verify-Preorder-Sequence-in-Binary-Search-Tree.md
+++ /dev/null
@@ -1,367 +0,0 @@
----
-id: verify-preorder-sequence-in-binary-search-tree
-title: Verify Preorder Sequence in Binary Search Tree
-sidebar_label: 0255-Verify Preorder Sequence in Binary Search Tree
-tags: [Hash Map, Two Pointers,Binary Search Tree]
-description: Solution to finding and Verify Preorder Sequence in Binary Search Tree.
----
-
-### Description
-
-Given an array of numbers, verify whether it is the correct preorder traversal sequence of a binary search tree.
-
-You may assume each number in the sequence is unique.
-
-Consider the following binary search tree:
-
-```bash
- 5
- / \
- 2 6
- / \
- 1 3
-```
-
-### Example:
-
-**Example 1:**
-```bash
-Input: [5,2,6,1,3]
-Output: false
-```
-
-
-**Example 2:**
-```bash
-Input: [5,2,1,3,6]
-Output: true
-```
-### Solution
-
-#### **Approach**
-
-- Use a stack to simulate the traversal.
-- Maintain a variable `low` which represents the lowest value that the next node can take. Initially, set `low` to negative infinity.
-- Iterate through the array:
- - If we encounter a value less than `low`, it means the sequence is invalid.
- - If the current value is greater than the top of the stack, keep popping from the stack and update `low` to the value of the last popped element. This ensures that we are correctly moving to the right subtree.
- - Push the current value onto the stack.
-
-
-
-
-
-
-```javascript
-function verifyPreorder(preorder) {
- let stack = [];
- let low = -Infinity;
-
- for (let value of preorder) {
- if (value < low) {
- return false;
- }
- while (stack.length > 0 && value > stack[stack.length - 1]) {
- low = stack.pop();
- }
- stack.push(value);
- }
- return true;
-}
-
-// Example usage:
-const preorder1 = [5, 2, 6, 1, 3];
-console.log(verifyPreorder(preorder1)); // Output: false
-
-const preorder2 = [5, 2, 1, 3, 6];
-console.log(verifyPreorder(preorder2)); // Output: true
-```
-
-
-
-
-
-
-```typescript
-function verifyPreorder(preorder: number[]): boolean {
- let stack: number[] = [];
- let low: number = -Infinity;
-
- for (let value of preorder) {
- if (value < low) {
- return false;
- }
- while (stack.length > 0 && value > stack[stack.length - 1]) {
- low = stack.pop()!;
- }
- stack.push(value);
- }
- return true;
-}
-
-// Example usage:
-const preorder1: number[] = [5, 2, 6, 1, 3];
-console.log(verifyPreorder(preorder1)); // Output: false
-
-const preorder2: number[] = [5, 2, 1, 3, 6];
-console.log(verifyPreorder(preorder2)); // Output: true
-```
-
-
-
-
-
-
-```python
-def verifyPreorder(preorder):
- stack = []
- low = float('-inf')
-
- for value in preorder:
- if value < low:
- return False
- while stack and value > stack[-1]:
- low = stack.pop()
- stack.append(value)
-
- return True
-
-# Example usage:
-preorder1 = [5, 2, 6, 1, 3]
-print(verifyPreorder(preorder1)) # Output: False
-
-preorder2 = [5, 2, 1, 3, 6]
-print(verifyPreorder(preorder2)) # Output: True
-```
-
-
-
-
-
-```java
-import java.util.Stack;
-
-public class Solution {
- public boolean verifyPreorder(int[] preorder) {
- Stack stack = new Stack<>();
- int low = Integer.MIN_VALUE;
-
- for (int value : preorder) {
- if (value < low) {
- return false;
- }
- while (!stack.isEmpty() && value > stack.peek()) {
- low = stack.pop();
- }
- stack.push(value);
- }
- return true;
- }
-
- public static void main(String[] args) {
- Solution solution = new Solution();
-
- int[] preorder1 = {5, 2, 6, 1, 3};
- System.out.println(solution.verifyPreorder(preorder1)); // Output: false
-
- int[] preorder2 = {5, 2, 1, 3, 6};
- System.out.println(solution.verifyPreorder(preorder2)); // Output: true
- }
-}
-```
-
-
-
-
-```cpp
-#include
-#include
-#include
-#include
-
-using namespace std;
-
-class Solution {
-public:
- bool verifyPreorder(vector& preorder) {
- stack stk;
- int low = INT_MIN;
-
- for (int value : preorder) {
- if (value < low) {
- return false;
- }
- while (!stk.empty() && value > stk.top()) {
- low = stk.top();
- stk.pop();
- }
- stk.push(value);
- }
-
- return true;
- }
-};
-
-int main() {
- Solution solution;
-
- vector preorder1 = {5, 2, 6, 1, 3};
- cout << (solution.verifyPreorder(preorder1) ? "true" : "false") << endl; // Output: false
-
- vector preorder2 = {5, 2, 1, 3, 6};
- cout << (solution.verifyPreorder(preorder2) ? "true" : "false") << endl; // Output: true
-
- return 0;
-}
-```
-
-
-
-
-
-### Explanation:
-
-
-
-
-
-
-1. **Initialization**:
- - A stack is used to keep track of the nodes.
- - `low` is initialized to `-Infinity` to represent the smallest possible value initially.
-
-2. **Iteration**:
- - For each value in the `preorder` array:
- - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `false`.
- - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
- - Push the current value onto the stack.
-
-3. **Return**:
- - If we successfully iterate through the entire array without finding any violations, return `true`.
-
-
-
-
-
-
-1. **Initialization**:
- - A stack is used to keep track of the nodes.
- - `low` is initialized to `-Infinity` to represent the smallest possible value initially.
-
-2. **Iteration**:
- - For each value in the `preorder` array:
- - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `false`.
- - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
- - Push the current value onto the stack.
-
-3. **Return**:
- - If we successfully iterate through the entire array without finding any violations, return `true`.
-
-
-
-
-
-1. **Initialization**:
- - A stack is used to keep track of the nodes.
- - `low` is initialized to negative infinity to represent the smallest possible value initially.
-
-2. **Iteration**:
- - For each value in the `preorder` array:
- - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `False`.
- - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
- - Push the current value onto the stack.
-
-3. **Return**:
- - If we successfully iterate through the entire array without finding any violations, return `True`.
-
-
-
-
-
-1. **Initialization**:
- - A stack is used to keep track of the nodes.
- - `low` is initialized to `Integer.MIN_VALUE` to represent the smallest possible value initially.
-
-2. **Iteration**:
- - For each value in the `preorder` array:
- - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `false`.
- - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
- - Push the current value onto the stack.
-
-3. **Return**:
- - If we successfully iterate through the entire array without finding any violations, return `true`.
-
-
-
-
-
-1. **Initialization**:
- - A stack is used to keep track of the nodes.
- - `low` is initialized to `INT_MIN` to represent the smallest possible value initially.
-
-2. **Iteration**:
- - For each value in the `preorder` array:
- - If the value is less than `low`, it means we are visiting a node in the right subtree that violates the BST property, hence return `false`.
- - If the current value is greater than the top of the stack, it means we are transitioning from the left subtree to the right subtree. We keep popping the stack and update `low` to ensure that subsequent nodes in the right subtree are greater than this value.
- - Push the current value onto the stack.
-
-3. **Return**:
- - If we successfully iterate through the entire array without finding any violations, return `true`.
-
-
-
-
-
-### Complexity:
-
-
-
-
-
-
-- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
-- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
-
-
-
-
-
-- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
-- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
-
-
-
-
-
-
-- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
-- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
-
-
-
-
-
-- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
-- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
-
-
-
-- **Time Complexity**: `O(n)`, where `n` is the length of the preorder array. Each element is pushed and popped from the stack at most once.
-- **Space Complexity**: `O(n)`, where `n` is the length of the preorder array, which is the worst-case space complexity for the stack.
-
-
-
-
-
-
-## References
-
-- **LeetCode Problem:** [Binary Search Tree](https://leetcode.com/problems/verify-preorder-sequence-in-binary-search-tree/)
-
-
Author:
-
-
-{['sivaprasath2004'].map(username => (
-
-))}
-
From c4b6eb007d925f6a1b8e6717a405caf4fe152be3 Mon Sep 17 00:00:00 2001
From: Sivaprasath <121082414+sivaprasath2004@users.noreply.github.com>
Date: Sat, 27 Jul 2024 13:33:00 +0530
Subject: [PATCH 3/4] remodify
---
docs/react/_category_.json | 8 -
docs/react/advanced-usage/_category_.json | 8 -
.../advanced-usage/advanced-configuration.md | 134 -------
.../alternatives-to-ejecting.md | 51 ---
.../advanced-usage/can-i-use-decorators.md | 151 --------
docs/react/advanced-usage/custom-templates.md | 301 ---------------
.../pre-rendering-into-static-html-files.md | 92 -----
docs/react/assets/Frontend-Roadmap.pdf | Bin 13765701 -> 0 bytes
docs/react/assets/ReactJS-Guide.pdf | Bin 29461530 -> 0 bytes
docs/react/assets/audio.mp3 | Bin 310169 -> 0 bytes
.../back-end-integration/DataFetcher.jsx | 32 --
.../FetchDataComponent.jsx | 38 --
.../back-end-integration/_category_.json | 8 -
.../fetching-data-with-ajax-requests.md | 189 ---------
.../integrating-with-an-api-backend.md | 154 --------
.../proxying-api-requests-in-development.md | 236 ------------
.../title-and-meta-tags.md | 67 ----
docs/react/building-your-app/_category_.json | 8 -
.../building-your-app/adding-a-router.md | 102 -----
.../building-your-app/adding-bootstrap.md | 195 ----------
.../adding-custom-environment-variables.md | 132 -------
docs/react/building-your-app/adding-flow.md | 197 ----------
docs/react/building-your-app/adding-relay.md | 211 ----------
.../building-your-app/adding-typescript.md | 72 ----
.../importing-a-component.md | 96 -----
.../installing-a-dependency.md | 106 -----
.../making-a-progressive-web-app.md | 120 ------
.../measuring-performance.md | 138 -------
.../building-your-app/production-build.md | 127 ------
docs/react/building-your-app/style.css | 136 -------
.../using-global-variables.md | 225 -----------
docs/react/create-react-app.md | 65 ----
docs/react/css/style.css | 20 -
docs/react/deployment/_category_.json | 8 -
docs/react/deployment/deployment.md | 103 -----
docs/react/development/_category_.json | 8 -
.../development/analyzing-the-bundle-size.md | 63 ---
.../developing-components-in-isolation.md | 83 ----
.../development/setting-up-your-editor.md | 166 --------
.../development/using-https-in-development.md | 82 ----
docs/react/getting-started/_category_.json | 8 -
.../getting-started/available-scripts.md | 45 ---
.../react/getting-started/folder-structure.md | 70 ----
docs/react/getting-started/forms-in-react.md | 362 ------------------
docs/react/getting-started/getting-started.md | 194 ----------
.../supported-browsers-features.md | 47 ---
.../updating-to-new-releases.md | 44 ---
docs/react/hooks/_category_.json | 8 -
docs/react/hooks/useCallback.md | 37 --
docs/react/hooks/useContext.md | 31 --
docs/react/hooks/useEffect-hook.md | 42 --
docs/react/hooks/useMemo.md | 42 --
docs/react/hooks/useReducer.md | 50 ---
docs/react/hooks/useRef.md | 42 --
docs/react/hooks/useState-hook.md | 37 --
docs/react/img/getting-started-react.svg | 1 -
docs/react/img/local-host-2.gif | Bin 4434146 -> 0 bytes
docs/react/img/logo.svg | 1 -
docs/react/img/react.svg | 1 -
docs/react/intro-react.md | 52 ---
docs/react/styles-and-assets/_category_.json | 8 -
.../adding-a-css-modules-stylesheet.md | 202 ----------
.../adding-a-sass-stylesheet.md | 132 -------
.../styles-and-assets/adding-a-stylesheet.md | 113 ------
.../styles-and-assets/adding-css-reset.md | 77 ----
.../adding-images-fonts-and-files.md | 198 ----------
.../react/styles-and-assets/code-splitting.md | 74 ----
.../loading-graphql-files.md | 130 -------
.../styles-and-assets/post-processing-css.md | 152 --------
.../using-the-public-folder.md | 63 ---
docs/react/support/troubleshooting.md | 56 ---
docs/react/testing/_category_.json | 8 -
docs/react/testing/debugging-tests.md | 114 ------
docs/react/testing/running-tests.md | 134 -------
74 files changed, 6507 deletions(-)
delete mode 100644 docs/react/_category_.json
delete mode 100644 docs/react/advanced-usage/_category_.json
delete mode 100644 docs/react/advanced-usage/advanced-configuration.md
delete mode 100644 docs/react/advanced-usage/alternatives-to-ejecting.md
delete mode 100644 docs/react/advanced-usage/can-i-use-decorators.md
delete mode 100644 docs/react/advanced-usage/custom-templates.md
delete mode 100644 docs/react/advanced-usage/pre-rendering-into-static-html-files.md
delete mode 100644 docs/react/assets/Frontend-Roadmap.pdf
delete mode 100644 docs/react/assets/ReactJS-Guide.pdf
delete mode 100644 docs/react/assets/audio.mp3
delete mode 100644 docs/react/back-end-integration/DataFetcher.jsx
delete mode 100644 docs/react/back-end-integration/FetchDataComponent.jsx
delete mode 100644 docs/react/back-end-integration/_category_.json
delete mode 100644 docs/react/back-end-integration/fetching-data-with-ajax-requests.md
delete mode 100644 docs/react/back-end-integration/integrating-with-an-api-backend.md
delete mode 100644 docs/react/back-end-integration/proxying-api-requests-in-development.md
delete mode 100644 docs/react/back-end-integration/title-and-meta-tags.md
delete mode 100644 docs/react/building-your-app/_category_.json
delete mode 100644 docs/react/building-your-app/adding-a-router.md
delete mode 100644 docs/react/building-your-app/adding-bootstrap.md
delete mode 100644 docs/react/building-your-app/adding-custom-environment-variables.md
delete mode 100644 docs/react/building-your-app/adding-flow.md
delete mode 100644 docs/react/building-your-app/adding-relay.md
delete mode 100644 docs/react/building-your-app/adding-typescript.md
delete mode 100644 docs/react/building-your-app/importing-a-component.md
delete mode 100644 docs/react/building-your-app/installing-a-dependency.md
delete mode 100644 docs/react/building-your-app/making-a-progressive-web-app.md
delete mode 100644 docs/react/building-your-app/measuring-performance.md
delete mode 100644 docs/react/building-your-app/production-build.md
delete mode 100644 docs/react/building-your-app/style.css
delete mode 100644 docs/react/building-your-app/using-global-variables.md
delete mode 100644 docs/react/create-react-app.md
delete mode 100644 docs/react/css/style.css
delete mode 100644 docs/react/deployment/_category_.json
delete mode 100644 docs/react/deployment/deployment.md
delete mode 100644 docs/react/development/_category_.json
delete mode 100644 docs/react/development/analyzing-the-bundle-size.md
delete mode 100644 docs/react/development/developing-components-in-isolation.md
delete mode 100644 docs/react/development/setting-up-your-editor.md
delete mode 100644 docs/react/development/using-https-in-development.md
delete mode 100644 docs/react/getting-started/_category_.json
delete mode 100644 docs/react/getting-started/available-scripts.md
delete mode 100644 docs/react/getting-started/folder-structure.md
delete mode 100644 docs/react/getting-started/forms-in-react.md
delete mode 100644 docs/react/getting-started/getting-started.md
delete mode 100644 docs/react/getting-started/supported-browsers-features.md
delete mode 100644 docs/react/getting-started/updating-to-new-releases.md
delete mode 100644 docs/react/hooks/_category_.json
delete mode 100644 docs/react/hooks/useCallback.md
delete mode 100644 docs/react/hooks/useContext.md
delete mode 100644 docs/react/hooks/useEffect-hook.md
delete mode 100644 docs/react/hooks/useMemo.md
delete mode 100644 docs/react/hooks/useReducer.md
delete mode 100644 docs/react/hooks/useRef.md
delete mode 100644 docs/react/hooks/useState-hook.md
delete mode 100644 docs/react/img/getting-started-react.svg
delete mode 100644 docs/react/img/local-host-2.gif
delete mode 100644 docs/react/img/logo.svg
delete mode 100644 docs/react/img/react.svg
delete mode 100644 docs/react/intro-react.md
delete mode 100644 docs/react/styles-and-assets/_category_.json
delete mode 100644 docs/react/styles-and-assets/adding-a-css-modules-stylesheet.md
delete mode 100644 docs/react/styles-and-assets/adding-a-sass-stylesheet.md
delete mode 100644 docs/react/styles-and-assets/adding-a-stylesheet.md
delete mode 100644 docs/react/styles-and-assets/adding-css-reset.md
delete mode 100644 docs/react/styles-and-assets/adding-images-fonts-and-files.md
delete mode 100644 docs/react/styles-and-assets/code-splitting.md
delete mode 100644 docs/react/styles-and-assets/loading-graphql-files.md
delete mode 100644 docs/react/styles-and-assets/post-processing-css.md
delete mode 100644 docs/react/styles-and-assets/using-the-public-folder.md
delete mode 100644 docs/react/support/troubleshooting.md
delete mode 100644 docs/react/testing/_category_.json
delete mode 100644 docs/react/testing/debugging-tests.md
delete mode 100644 docs/react/testing/running-tests.md
diff --git a/docs/react/_category_.json b/docs/react/_category_.json
deleted file mode 100644
index 6f7bf7453..000000000
--- a/docs/react/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
- "label": "React",
- "position": 22,
- "link": {
- "type": "generated-index",
- "description": "React is a JavaScript library for building user interfaces. It is maintained by Facebook and a community of individual developers and companies."
- }
- }
\ No newline at end of file
diff --git a/docs/react/advanced-usage/_category_.json b/docs/react/advanced-usage/_category_.json
deleted file mode 100644
index 3628975e8..000000000
--- a/docs/react/advanced-usage/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
- "label": "Advanced Usage",
- "position": 10,
- "link": {
- "type": "generated-index",
- "description": "5 minutes to learn the most important RoadMap for React Mastery."
- }
- }
\ No newline at end of file
diff --git a/docs/react/advanced-usage/advanced-configuration.md b/docs/react/advanced-usage/advanced-configuration.md
deleted file mode 100644
index f15ab9223..000000000
--- a/docs/react/advanced-usage/advanced-configuration.md
+++ /dev/null
@@ -1,134 +0,0 @@
----
-id: advanced-configuration
-title: Advanced Configuration
-sidebar_label: Advanced Configuration
-sidebar_position: 4
-tags: [Create React App, Advanced Configuration, Environment Variables, Webpack, Babel, CRACO, react-scripts, Custom Scripts, Ejectify, Custom Templates]
-keywords: [create react app, advanced configuration, environment variables, webpack, babel, craco, react-scripts, custom scripts, ejectify, custom templates]
-description: Learn how to customize and fine-tune your React projects with advanced configuration options in Create React App. Discover powerful features and alternatives to ejecting that will help you take control of your development environment.
----
-In Create React App, you have the power to customize various development and production settings using environment variables. These options allow you to control the behavior of your React application without diving into complex configurations. Let's take a closer look at each setting in a handy table format:
-
-| Variable | Development | Production | Usage |
-| :------------------------ | :---------: | :--------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| BROWSER | ✅ Used | 🚫 Ignored | Override the default system browser that Create React App opens during development. You can specify a specific browser or set it to `none` to disable browser opening. You can even use a custom Node.js script for launching the browser with additional arguments from `npm start`. |
-| BROWSER_ARGS | ✅ Used | 🚫 Ignored | Pass additional arguments to the browser instance when `BROWSER` is specified. Multiple arguments are supported, separated by spaces. |
-| HOST | ✅ Used | 🚫 Ignored | Specify a custom host for the development web server. By default, it binds to all available hostnames on the device. |
-| PORT | ✅ Used | 🚫 Ignored | Set a custom port for the development web server. By default, it listens on port 3000 or finds the next available port if 3000 is in use. |
-| HTTPS | ✅ Used | 🚫 Ignored | Run the development server in `https` mode by setting this variable to `true`. |
-| WDS_SOCKET_HOST | ✅ Used | 🚫 Ignored | Specify a custom WebSocket hostname for hot module reloading in the development server. Useful when working on multiple Create React App projects simultaneously. |
-| WDS_SOCKET_PATH | ✅ Used | 🚫 Ignored | Set a custom WebSocket path for hot module reloading in the development server. Helpful when working on multiple Create React App projects simultaneously. |
-| WDS_SOCKET_PORT | ✅ Used | 🚫 Ignored | Use a custom WebSocket port for hot module reloading in the development server. Useful for working on multiple Create React App projects simultaneously. |
-| PUBLIC_URL | ✅ Used | ✅ Used | Force assets to be referenced verbatim to the provided URL (including hostname). Useful when using a CDN to host your application. This variable overrides the default assumption of your app's hosting location specified in `package.json` (`homepage`). |
-| BUILD_PATH | 🚫 Ignored | ✅ Used | Specify a new path for Create React App to output compiled assets during the production build. By default, assets are output to `/build` directory adjacent to your `/src`. |
-| CI | ✅ Used | ✅ Used | Treat warnings as build failures and make the test runner non-watching when `true`. Most Continuous Integration (CI) environments set this flag by default. |
-| REACT_EDITOR | ✅ Used | 🚫 Ignored | Override the automatic editor detection in development. When your app crashes, you'll see an error overlay with a clickable stack trace. Clicking it opens the relevant source file based on running processes. You can set this variable to your editor's bin folder's path or `none` to disable it. |
-| CHOKIDAR_USEPOLLING | ✅ Used | 🚫 Ignored | Run the watcher in polling mode (`true`) if `npm start` isn't detecting changes. Useful inside virtual machines (VMs). |
-| GENERATE_SOURCEMAP | 🚫 Ignored | ✅ Used | Enable (`true`) or disable (`false`) source maps generation during production build. Disabling source maps can resolve Out of Memory (OOM) issues on some smaller machines. |
-| INLINE_RUNTIME_CHUNK | 🚫 Ignored | ✅ Used | Embed (`true`) or import as usual (`false`) the runtime script into `index.html` during production build. Use this when dealing with Content Security Policy (CSP) restrictions. |
-| IMAGE_INLINE_SIZE_LIMIT | ✅ Used | ✅ Used | Control the size limit (in bytes) for images that will be inlined in the CSS or JS build artifact as data URI in base64. Set to `0` to disable image inlining. |
-| FAST_REFRESH | ✅ Used | 🚫 Ignored | Enable (`true`) or disable (`false`) experimental Fast Refresh support. Fast Refresh allows tweaking components in real-time without reloading the page. |
-| TSC_COMPILE_ON_ERROR | ✅ Used | ✅ Used | Allow running and building TypeScript projects even with TypeScript type check errors. Errors are displayed as warnings in the terminal and/or browser console. |
-| ESLINT_NO_DEV_ERRORS | ✅ Used | 🚫 Ignored | Convert ESLint errors to warnings during development, hiding them from the error overlay. |
-| DISABLE_ESLINT_PLUGIN | ✅ Used | ✅ Used | Completely disable the [eslint-webpack-plugin](https://github.com/webpack-contrib/eslint-webpack-plugin). |
-| DISABLE_NEW_JSX_TRANSFORM | ✅ Used | ✅ Used | Disable (`true`) the new JSX transform introduced in React 17 and backported to React 16.14.0, 15.7.0, and 0.14.10. New projects have this enabled by default, but you may need to disable it in existing projects if you can't upgrade React. |
-
-Remember to experiment with these configurations, as it allows you to tailor your React application according to your specific requirements.
-
-## Advanced Configuration in Create React App
-
-Welcome to the world of advanced configurations in Create React App! 🚀 In this guide, we'll dive deeper into the powerful features and options available to fine-tune your React projects. Don't worry; we'll make sure it's easy to understand, even for beginners!
-
-## What is Create React App?
-
-For those who are new to Create React App (CRA), it's a fantastic tool that helps you kickstart your React projects without getting bogged down in complex setup processes. CRA abstracts away the configuration, allowing you to focus on building amazing React applications right from the get-go.
-
-## Customizing the Configuration
-
-CRA provides a way to customize its configuration without ejecting your project. Ejecting means you'd have to deal with all the build tools and configurations yourself, which can be overwhelming for beginners. So, let's look at how to customize the configuration while staying within the comfort zone of CRA.
-
-### Environment Variables
-
-Environment variables are super handy for managing various settings in your app. By default, CRA supports `.env` files, but you can create environment-specific files like `.env.development`, `.env.production`, etc.
-
-```bash
-# .env.development
-REACT_APP_API_URL="https://api.dev.example.com"
-```
-
-Now, you can access the variable like this:
-
-```javascript
-const apiUrl = process.env.REACT_APP_API_URL;
-```
-
-### Adding Webpack Plugins
-
-Webpack is the magic behind CRA, and you can extend it with plugins. For example, let's add the "Bundle Analyzer" plugin to visualize your bundle's size:
-
-```javascript
-// In your react-scripts version 5.0.0+ or higher, you can use the following syntax in the 'webpack.config.js'
-const { BundleAnalyzerPlugin } = require("webpack-bundle-analyzer");
-
-// Inside your 'webpack.config.js' module.exports object, add this plugin to the 'plugins' array
-module.exports = {
- // ... other config options ...
- plugins: [
- // ... other plugins ...
- new BundleAnalyzerPlugin(),
- ],
-};
-```
-
-### Rewriting the Webpack Config
-
-Need more control over the Webpack configuration? CRA offers a simple way to extend the config directly:
-
-```javascript
-// In your react-scripts version 4.0.0+ or higher, you can use the following syntax in the 'craco.config.js'
-module.exports = {
- webpack: {
- configure: (webpackConfig) => {
- // Add your custom webpack config here
- webpackConfig.optimization.minimize = true;
- return webpackConfig;
- },
- },
-};
-```
-
-### Adding Babel Plugins
-
-To further enhance your app's capabilities, you can add Babel plugins to transform your code. For example, let's add the "transform-class-properties" plugin:
-
-```bash
-npm install --save-dev @babel/plugin-proposal-class-properties
-```
-
-Then, create a `.babelrc` file in the root of your project:
-
-```json
-{
- "plugins": ["@babel/plugin-proposal-class-properties"]
-}
-```
-
-Now you can use class properties in your components:
-
-```javascript
-class MyClassComponent extends React.Component {
- state = {
- count: 0,
- };
-
- handleClick = () => {
- this.setState((prevState) => ({ count: prevState.count + 1 }));
- };
-}
-```
-
-## Conclusion
-
-Congratulations! You've taken your first steps into the exciting world of advanced configuration in Create React App. Now you can customize your projects, add plugins, and take control of your development environment with confidence.
-
-Remember, the power of customization comes with great responsibility. Always experiment with caution and keep an eye on the official documentation for the latest updates and best practices. Happy coding! 🎉
\ No newline at end of file
diff --git a/docs/react/advanced-usage/alternatives-to-ejecting.md b/docs/react/advanced-usage/alternatives-to-ejecting.md
deleted file mode 100644
index dbc65760f..000000000
--- a/docs/react/advanced-usage/alternatives-to-ejecting.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-id: alternatives-to-ejecting
-title: Alternatives to Ejecting
-sidebar_label: Alternatives to Ejecting
-sidebar_position: 5
-tags: [React, Create React App, Advanced Usage]
-keywords: [alternatives to ejecting, create react app, react-scripts, craco, custom scripts, package.json, ejectify, custom templates, boilerplates]
-description: Learn about alternatives to ejecting from Create React App and how to customize your project without ejecting.
----
-
-## Introduction
-
-Create React App (CRA) is an awesome tool that provides a quick and easy way to set up a React project with no build configuration. However, sometimes you might find yourself needing more control over the build process or wanting to add custom configurations. The traditional way to achieve this is by ejecting from Create React App, but it can be a bit intimidating for beginners and can lead to maintenance headaches. Fear not, for there are some fantastic alternatives that will let you customize your project without the need to eject! 🚀
-
-## 1. **Customize with react-scripts**
-
-Instead of ejecting, you can use the `react-scripts` package that comes with Create React App under the hood. It offers hidden features that you can use to tweak your project's settings without ejecting. Create a file in the root of your project called `.env`, and you can add custom environment variables like this:
-
-```plaintext
-REACT_APP_MY_VARIABLE=hello-coders
-```
-
-Now you can access this variable in your code using `process.env.REACT_APP_MY_VARIABLE`.
-
-## 2. **CRACO - Create React App Configuration Override**
-
-CRACO is like magic for your Create React App projects. It stands for Create React App Configuration Override and lets you easily modify CRA's configuration without ejecting. You can add custom webpack configurations, Babel plugins, and much more, all from a single configuration file. It's like wielding a powerful wand to control your project's build process! 🧙♂️
-
-## 3. **Custom Scripts in `package.json`**
-
-For simpler customizations, you can add your own scripts directly to the `package.json` file. For example, you can create a script to run a pre-build task or automate some setup steps. Just add something like this:
-
-```json
-"scripts": {
- "custom-script": "node scripts/customScript.js"
-}
-```
-
-Then, you can run your custom script using `npm run custom-script`.
-
-## 4. **Ejectify - The Un-Ejecting Tool**
-
-Ejectify is a fun and clever tool that reverses the eject process. Instead of ejecting, you can use Ejectify to "un-eject" your Create React App project. This means you can revert to a state similar to a pre-eject status while keeping all your customizations intact! It's like traveling back in time to undo a decision without any regrets! ⏰
-
-## 5. **Custom Templates and Boilerplates**
-
-If you have specific project requirements, you can create your own custom templates or boilerplates with all the necessary configurations pre-set. Tools like `degit` allow you to easily scaffold a new project based on your custom template, saving you time and effort. It's like having your own personalized React project starter kit! 🎁
-
-## Conclusion
-
-As you can see, there's no need to fear the eject button anymore! With these amazing alternatives, you can confidently customize your Create React App projects without the complexity and drawbacks of ejecting. So go ahead, unleash your creativity, and build incredible React applications while keeping the magic of Create React App alive! Happy coding! 😄🚀
diff --git a/docs/react/advanced-usage/can-i-use-decorators.md b/docs/react/advanced-usage/can-i-use-decorators.md
deleted file mode 100644
index 06538237d..000000000
--- a/docs/react/advanced-usage/can-i-use-decorators.md
+++ /dev/null
@@ -1,151 +0,0 @@
----
-id: can-i-use-decorators
-title: The Power of Decorators in CRA
-sidebar_label: Use Decorators
-sidebar_position: 2
-tags: [decorators, create react app, decorators in create react app, decorators in react, decorators in javascript, decorators in typescript]
-keywords: [decorators, create react app, decorators in create react app, decorators in react, decorators in javascript, decorators in typescript]
-description: Learn how to use decorators in Create React App to enhance and extend the functionality of your components.
----
-
-
-## Introduction to Decorators
-
-Decorators are an amazing feature in JavaScript that allows us to enhance and extend the functionality of classes and their properties. They are essentially special functions that wrap around components and add magic to our code. Create React App (CRA) supports decorators out of the box, making it super easy for us to level up our React components! In this guide, we'll delve into decorators, how to set up CRA for using them, and explore some cool examples.
-
-## Understanding Decorators
-
-In simple terms, decorators are like cool stickers that you put on your React components to make them extra special. They start with the `@` symbol, and you can think of them as powerful modifiers that can change the behavior of classes, methods, or properties.
-
-## Setting Up CRA for Decorators
-
-Before we can start using decorators in our CRA project, we need to set up the right environment. Don't worry; it's a breeze! Here's what you need to do:
-
-1. First, let's create your CRA project:
-
- ```bash
- npx create-react-app my-app
- cd my-app
- ```
-
-2. Now, let's install the magical `babel-plugin-transform-decorators-legacy` package:
-
- ```bash
- npm install babel-plugin-transform-decorators-legacy --save-dev
- ```
-
-3. Finally, let's configure Babel to recognize decorators by adding the plugin in your `package.json` file:
-
- ```json title="package.json"
- {
- "name": "my-app",
- "version": "0.1.0",
- "babel": {
- "plugins": [
- "babel-plugin-transform-decorators-legacy"
- ]
- }
- }
- ```
-
-## Using Decorators in CRA
-
-Now comes the fun part! Let's see how we can use decorators to make our components shine:
-
-### Class Decorators
-
-Imagine class decorators as superhero capes you put on your entire component class. They can change the class's behavior or even add cool superpowers! Check this out:
-
-```jsx title="MyComponent.jsx"
-import React from 'react';
-
-function withHoverStyle(WrappedComponent) {
- return class extends React.Component {
- state = { isHovered: false };
-
- handleMouseEnter = () => this.setState({ isHovered: true });
- handleMouseLeave = () => this.setState({ isHovered: false });
-
- render() {
- return (
-
- );
- }
-}
-```
-
-In this example, the `withHoverStyle` decorator adds a nice hover effect to our component, all without modifying the original component code!
-
-### Method Decorators
-
-Method decorators are like little wizards that cast spells on specific methods in your component. Let's create a decorator to throttle an expensive method:
-
-```jsx title="MyComponent.jsx"
-function throttle(wait) {
- return function (target, key, descriptor) {
- let timeout;
-
- descriptor.value = function (...args) {
- clearTimeout(timeout);
- timeout = setTimeout(() => {
- target.apply(this, args);
- }, wait);
- };
-
- return descriptor;
- };
-}
-
-class MyComponent extends React.Component {
- @throttle(500)
- handleScroll() {
- // Expensive operation
- }
-}
-```
-
-Here, the `throttle` decorator makes sure that the `handleScroll` method is only called every 500 milliseconds, preventing performance bottlenecks!
-
-### Property Decorators
-
-Property decorators are like the secret agents that guard your component properties. They can enforce rules or do other behind-the-scenes stuff. Let's make a property read-only:
-
-```jsx title="MyComponent.jsx"
-function readonly(target, key, descriptor) {
- descriptor.writable = false;
- return descriptor;
-}
-
-class MyComponent extends React.Component {
- @readonly
- title = 'My Component';
-}
-```
-
-Now, the `title` property cannot be changed from outside the component, keeping your data safe and sound.
-
-## Conclusion
-
-Decorators are a superpower in Create React App, and now you know how to use them to make your components even more awesome! By leveraging class, method, and property decorators, you can add exciting features, enhance behavior, and make your codebase cleaner and more organized.
-
-Remember, with great power comes great responsibility. Use decorators wisely and sparingly, and you'll become a true React pro in no time! Happy coding!
\ No newline at end of file
diff --git a/docs/react/advanced-usage/custom-templates.md b/docs/react/advanced-usage/custom-templates.md
deleted file mode 100644
index c3c0a2031..000000000
--- a/docs/react/advanced-usage/custom-templates.md
+++ /dev/null
@@ -1,301 +0,0 @@
----
-id: custom-templates
-title: Custom Templates
-sidebar_label: Importing a Component
-sidebar_position: 1
-tags: [create react app, custom templates, custom template, react project, project setup, project configuration, project dependencies, project folder structure, react app, react project setup, react project configuration, react project dependencies, react project folder structure, react project template, react project scaffolding, react project boilerplate, react project starter kit, react project setup template, react project configuration template, react project dependencies template, react project folder structure template, react project scaffolding template, react project boilerplate template, react project starter kit template, react project setup boilerplate, react project configuration boilerplate, react project dependencies boilerplate, react project folder structure boilerplate, react project scaffolding boilerplate, react project starter kit boilerplate]
-keywords: [create react app, custom templates, custom template, react project, project setup, project configuration, project dependencies, project folder structure, react app, react project setup, react project configuration, react project dependencies, react project folder structure, react project template, react project scaffolding, react project boilerplate, react project starter kit, react project setup template, react project configuration template, react project dependencies template, react project folder structure template, react project scaffolding template, react project boilerplate template, react project starter kit template, react project setup boilerplate, react project configuration boilerplate, react project dependencies boilerplate, react project folder structure boilerplate, react project scaffolding boilerplate, react project starter kit boilerplate]
-description: Learn how to create and use custom templates in Create React App to quickly start new projects with specific configurations, dependencies, and folder structures.
----
-
-## Introduction to Custom Templates
-
-Custom templates in Create React App (CRA) are pre-configured project setups that allow developers to scaffold new projects with specific configurations, dependencies, and folder structures. They enable you to avoid repetitive manual setup and quickly start your projects with your preferred settings. In this guide, we'll create a custom template that includes a popular UI library, sets up a state management system, and adds some custom scripts for building an engaging React app.
-
-:::note
-This feature is available with `react-scripts@3.3.0` and higher.
-:::
-
-Custom Templates in Create React App empower you to select a specialized project template while retaining all the benefits of Create React App's features.
-
-Custom Templates follow the naming convention `cra-template-[template-name]`, but you only need to provide `[template-name]` when creating a new project.
-
-Scoped templates are also supported using the format `@[scope-name]/cra-template` or `@[scope-name]/cra-template-[template-name]`, which can be installed via `@[scope]` and `@[scope]/[template-name]` respectively.
-
-To create a new project using a custom template, use the following command:
-
-```sh
-npx create-react-app my-app --template [template-name]
-```
-
-## Finding Custom Templates
-
-Create React App ships with two default templates:
-
-- [`cra-template`](https://github.com/facebook/create-react-app/tree/main/packages/cra-template)
-- [`cra-template-typescript`](https://github.com/facebook/create-react-app/tree/main/packages/cra-template-typescript)
-
-However, the community offers a wide range of great custom templates. You can find them by searching for ["cra-template-\*"](https://www.npmjs.com/search?q=cra-template-*) on npm.
-
-## Building a Custom Template
-
-If you're interested in creating your custom template, start by exploring how the default [`cra-template`](https://github.com/facebook/create-react-app/tree/main/packages/cra-template) is built.
-
-A custom template must adhere to the following structure:
-
-```
-cra-template-[template-name]
- ├── README.md (for npm)
- ├── template.json
- ├── package.json
- ├── template
- | ├──README.md (for projects created from this template)
- | ├──gitignore
- | ├──public
- | | ├──index.html
- | | └── ...
- | ├──src
- | ├── index.js (or index.tsx)
- | └── ...
- └── ...
-```
-
-### Testing a Custom Template
-
-To test a custom template locally, use the `file:` prefix followed by the file path to your template source.
-
-```sh
-npx create-react-app my-app --template file:../path/to/your/template/cra-template-[template-name]
-```
-
-### The `template` Folder
-
-The `template` folder is copied to the user's app directory when Create React App installs. During this process, the file `gitignore` is renamed to `.gitignore`.
-
-Feel free to add any additional files you want in this folder, but ensure you have at least the files specified above.
-
-### The `template.json` File
-
-The `template.json` file is the configuration file for your custom template. As this feature evolves, more options will be added. For now, only the `package` key is supported.
-
-The `package` key allows you to provide any keys/values you want to add to the new project's `package.json`. You can include dependencies and any custom scripts your template relies on.
-
-Below is an example `template.json` file:
-
-```json title="template.json"
-{
- "package": {
- "dependencies": {
- "eslint-plugin-jsx-a11y": "^6.2.3",
- "serve": "^11.2.0"
- },
- "scripts": {
- "serve": "serve -s build",
- "build-and-serve": "npm run build && npm run serve"
- },
- "eslintConfig": {
- "extends": ["react-app", "plugin:jsx-a11y/recommended"],
- "plugins": ["jsx-a11y"]
- }
- }
-}
-```
-
-Any values you add for `"dependencies"` and `"scripts"` will merge with the Create React App defaults. For other keys, the values will be used as-is, replacing any matching Create React App defaults.
-
-As a convenience, we automatically replace `npm run` with `yarn` in your custom `"scripts"`, as well as in your `README` when projects are initialized with yarn.
-
-
-## Step-by-Step Guide to Creating Custom Templates in Create React App
-
-### Step 1: Setting Up the Initial CRA Project
-
-Before creating our custom template, we need to set up a basic Create React App project. If you haven't installed CRA, do it using npm (Node Package Manager):
-
-```bash
-npm install -g create-react-app
-```
-
-Once installed, create a new React app with the following command:
-
-```bash
-npx create-react-app my-custom-template-app
-```
-
-Replace `my-custom-template-app` with your preferred project name.
-
-### Step 2: Customize Your CRA Project
-
-In the newly created `my-custom-template-app` directory, you'll find the basic CRA project structure. We'll now add some customizations to our template.
-
-#### Example Customization 1: Adding a UI Library
-
-For our example, let's use the popular UI library `Material-UI`. Install it using npm:
-
-```bash
-npm install @mui/material @emotion/react @emotion/styled
-```
-
-Next, create a new file `CustomButton.js` in the `src` folder with the following code:
-
-```jsx title="CustomButton.js"
-// CustomButton.js
-import React from 'react';
-import Button from '@mui/material/Button';
-
-const CustomButton = ({ text }) => {
- return ;
-};
-
-export default CustomButton;
-```
-
-In the `src/App.js` file, import and use the `CustomButton` component:
-
-```jsx title="App.js"
-// App.js
-import React from 'react';
-import CustomButton from './CustomButton';
-
-function App() {
- return (
-
-
Hello, Custom Template!
-
-
- );
-}
-
-export default App;
-```
-
-#### Example Customization 2: Setting Up State Management (using Redux)
-
-For state management, we'll integrate Redux into our custom template. Install the required packages:
-
-```bash
-npm install redux react-redux
-```
-
-Now, create a new folder named `store` in the `src` directory. Inside this folder, create a file `counterSlice.js` with the following code:
-
-```jsx title="src/store/counterSlice.js"
-// src/store/counterSlice.js
-import { createSlice } from '@reduxjs/toolkit';
-
-const counterSlice = createSlice({
- name: 'counter',
- initialState: { value: 0 },
- reducers: {
- increment(state) {
- state.value += 1;
- },
- decrement(state) {
- state.value -= 1;
- },
- },
-});
-
-export const { increment, decrement } = counterSlice.actions;
-export default counterSlice.reducer;
-```
-
-In the `src/store` folder, create a file named `store.js` to set up the Redux store:
-
-```jsx title="src/store/store.js"
-// src/store/store.js
-import { configureStore } from '@reduxjs/toolkit';
-import counterReducer from './counterSlice';
-
-export default configureStore({
- reducer: {
- counter: counterReducer,
- },
-});
-```
-
-Finally, update `src/index.js` to wrap the `App` component with the Redux Provider and pass the store:
-
-```jsx title="src/index.js"
-// src/index.js
-import React from 'react';
-import ReactDOM from 'react-dom';
-import { Provider } from 'react-redux';
-import store from './store/store';
-import App from './App';
-
-ReactDOM.render(
-
-
- ,
- document.getElementById('root')
-);
-```
-
-### Step 3: Create the Custom Template
-
-Now that we've customized our CRA project, let's turn it into a reusable template.
-
-**1. Template Folder Structure**
-
-Create a new folder named `template` in the root directory of your CRA project. Move all the files and folders (except the `node_modules` folder) from the root to this `template` folder.
-
-**2. Custom Template Package.json**
-
-In the `template` folder, create a new `package.json` file. Add the following:
-
-```json title="package.json"
-{
- "name": "my-custom-react-template",
- "version": "0.1.0",
- "dependencies": {
- "@mui/material": "^5.0.0",
- "@emotion/react": "^11.4.1",
- "@emotion/styled": "^11.3.0",
- "redux": "^4.1.1",
- "react-redux": "^7.2.5",
- "react-scripts": "4.0.3"
- }
-}
-```
-
-Note: The dependencies listed here should match the ones used in your CRA project. Additionally, update the version numbers if needed.
-
-**3. README.md**
-
-Create a `README.md` file in the `template` folder and add documentation for your custom template. Describe the purpose of the template, its features, and any additional setup or configuration instructions.
-
-### Step 4: Test Your Custom Template Locally
-
-Before publishing your template, test it locally to ensure everything works as expected.
-
-**1. Link Your Custom Template**
-
-In the root directory of your CRA project, run the following command to create a symlink for your custom template:
-
-```bash
-npm link
-```
-
-**2. Create a New Project**
-
-Now, create a new directory outside your custom template project and use the following command to generate a new CRA project using your custom template:
-
-```bash
-npx create-react-app my-custom-app --template file:../path/to/my-custom-template-app/template
-```
-
-Replace `../path/to/my-custom-template-app/template` with the actual path to your custom template.
-
-**3. Start the New Project**
-
-Move into the newly created `my-custom-app` directory and start the app:
-
-```bash
-cd my-custom-app
-npm start
-```
-
-### Conclusion
-
-Congratulations! You've successfully created your custom template in Create React App. Now you can reuse it or share it with others, making it easier to kickstart future React projects with your preferred configurations, dependencies, and folder structures. Happy coding!
\ No newline at end of file
diff --git a/docs/react/advanced-usage/pre-rendering-into-static-html-files.md b/docs/react/advanced-usage/pre-rendering-into-static-html-files.md
deleted file mode 100644
index 043c9dad5..000000000
--- a/docs/react/advanced-usage/pre-rendering-into-static-html-files.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-id: pre-rendering-into-static-html-files
-title: Pre-Rendering into Static HTML Files
-sidebar_label: Pre-Rendering Static HTML
-sidebar_position: 3
-tags: [React, Pre-Rendering, Static HTML, SEO, Performance]
-keywords: [pre-rendering, static html, react pre-rendering, react static html, pre-rendering in react, static html in react, react performance, react seo]
-description: Learn how to pre-render your React application into static HTML files to improve performance and SEO.
----
-
-If you're hosting your React application using a static hosting provider, you have a fantastic opportunity to enhance its performance and SEO by pre-rendering it into static HTML files. Pre-rendering involves generating HTML pages for each route or link in your application, making them readily available to users even before the JavaScript bundle loads. This seamless process not only improves loading times but also boosts your website's visibility on search engines.
-
-## What is Pre-Rendering and Why Use It?
-
-Pre-rendering, also known as "snapshotting," is a technique that produces static HTML versions of your dynamic React app during the build process. This means that instead of waiting for the JavaScript to load and render the content, users receive the pre-rendered HTML instantly. It greatly improves the initial loading speed, which is crucial for providing a smooth and delightful user experience.
-
-### Benefits of Pre-Rendering:
-
-1. **Faster Initial Page Load**: Users see the core content of each page even before the JavaScript bundle finishes downloading, resulting in quicker load times and reduced bounce rates.
-
-2. **Improved SEO**: Search engines can easily crawl and index static HTML pages, which enhances your website's visibility and ranking in search results.
-
-3. **Server Load Reduction**: Pre-rendering shifts the burden of generating and caching routes from the server to the build process, optimizing server performance.
-
-## How to Pre-Render with `react-snapshot` or `react-snap`
-
-Two popular libraries, `react-snapshot` and `react-snap`, can help you achieve pre-rendering in your React application:
-
-1. **react-snapshot** (Link: [npm](https://www.npmjs.com/package/react-snapshot))
-
- This library allows you to pre-render your app into static HTML pages for each route. The pages become active or "hydrated" once the JavaScript bundle loads.
-
-2. **react-snap** (Link: [npm](https://www.npmjs.com/package/react-snap))
-
- Similar to `react-snapshot`, `react-snap` also generates static HTML pages for each route or relative link in your application.
-
-## Setting Up Pre-Rendering
-
-To get started with pre-rendering using either of these libraries, follow these general steps:
-
-1. **Create a React App**:
-
- If you haven't already, create a new React app using Create React App or your preferred method.
-
-2. **Install the Chosen Library**:
-
- For `react-snapshot`, use the following command:
-
- ```bash
- npm install react-snapshot
- ```
-
- For `react-snap`, use:
-
- ```bash
- npm install react-snap
- ```
-
-3. **Configure the Build Scripts**:
-
- Open your project's `package.json` file and modify the scripts section to include the pre-rendering library's command. For example:
-
- ```json
- "scripts": {
- "prebuild": "react-snapshot", // or "react-snap" for react-snap
- "build": "react-scripts build"
- }
- ```
-
-4. **Pre-Render Your App**:
-
- Run the following command to generate static HTML pages:
-
- ```bash
- npm run build
- ```
-
-5. **Test Your Pre-Rendered App**:
-
- After the build process completes, you can serve your pre-rendered app locally to test it:
-
- ```bash
- npx serve -s build
- ```
-
- Your pre-rendered app should now be accessible at `http://localhost:5000`.
-
-## Conclusion
-
-Pre-rendering your React app into static HTML files is a game-changer in terms of performance and SEO. By serving pre-rendered content to users, you significantly improve the initial loading speed, leading to higher user satisfaction and engagement. Moreover, search engines will have an easier time indexing your pages, potentially boosting your website's visibility.
-
-So go ahead, give pre-rendering a try, and experience the remarkable benefits it brings to your React applications!
\ No newline at end of file
diff --git a/docs/react/assets/Frontend-Roadmap.pdf b/docs/react/assets/Frontend-Roadmap.pdf
deleted file mode 100644
index 7c40f8acf0131ad71ccceb60525d9dbbd1220903..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001
literal 13765701
zcmeFZ2{_bW+Xw!Xn6gbJBx^~s4u-Lltff%d$x;}yW|u*XB~d7nom7O7y{u#3mlWBJ
zeK+>O;6H|b_5R5FJn#SizSnd8AFk{By}q4upZmVg{rQ~x+~;t`q$DN7!Oh7}NXX5=
z#b9~w0U-l}hzJAdhM@)2)|i0@+jyHnOpMUR*4j|toREtX!pnvI!8UVoa`E$Qe{x{I
zxCC&GoO}@Q&Ig1C*J8j;NN8wbusa(2wQYfLTkDP~KJM*qTqF3e#^3Do9&Dd~#~Aj#
z^T7w%^#cOt+iuz4{I=3v^IU(K=liSiH}jCa=J_EwQ@H8l%wwm|v)#5G5eRs9`T~O6
zVfuspZLNEz&;M8BZ}tWD*cbfGJ`c_qF8tg(_67NN?ep{CTK1p+w$?rN1^;UN%|7=w
z(Ek;GKE54W+X3L)jW&1(Y%We-zFkDP4~jod>mC5O_az|rUIy}U*pWNf(6!^I$`F7IeA3WHXjXe9Zk!LR(d3b;2Wys$>;1C8L?|^n}EA9*jW$1Elt6nsq(;$38!^WS_1FOMesgc+=coV3fp_rPs@C~
zyURg<`+%((r*;n)!TWL%yqAl=!>}g^+&_2c19LM@>)s&jOGWTrD)RCE+MmF?ux|r{
z+n@Qkc38s64?bXj#A)5@!M;=k@1-J`e`gckhG9<(z`Q$~7q(P5phCfE-Rr@=ROJ0T
z6|rT=Z>f2ojPNrrLJrCZIJJ9-z`HLOdG~Vhzm$o)+3*(({}d5$TK5EjcV8;`%KBPVHVI?8`;Iyvl5PqFTf1aBDI=yoKJjQVTte!Z3vgBv>{I#S1Y{71(yHy6~&s~P|XR`mL
z`RA(tCHz;*&*k`=@OF;cX5Y^W>X)sb`HS->c{qO_JAMtvRXW?l|I*C2!{WPtoogZ6
zYi|d%-wt+=?X~m!!44#OP3oG3i7f+2$=dS%9Yb3NBNGb)YeO4LJL~&~4EGG7CKiO)
zW0Qf&ecRoC;o9z->st|S55D7MV{2%B&BDl%aNEvp>;UYk--+R}j0x0SAA8Hdg1uQ_
z04Z7<7+RZHK>yx;$Ii;i%+TD>!j^%HP)v-$z|aV*_NKm-g1)&S14x47Du?8+Mr9`}
zL+stewh;G@H}@?K3~j9R?;Bd{TR;s7MYy=c7(`@b#J1z`x4zvG_l)iv>s#+ia&bYf
z;$(MQ|1QIg)yBoeFL;m)4^D=U{~#Igjvl^)WO#8hJW>bA@Zn@2;Dcl!J2H@iWcYVv
zcn^{h*pWHVA3>Z9Ki5HeBzE*j9wc)WC&PE3KaxAPcn;DdwPQ=*AQ@?#43`vk0ZJSs
zC$ppLAnduf*~Z1ibI|;`cQ^z&h#%ZL9D+z6;1Bl>hjj=v7OES
z$~yP$tgW#L377J4xoA7#m{=J8l@+Zlt+w;a&*yKqoVXmjlX<``8
zD+Ame)*rgL7;qPjf9SK5cj)>**jim_h0n>&s;HvyT
zn8t#EE5ZNN&BuVNkN?z-RldJx*xz^HmKR9c0$V$5S1a2k4X)_;t7)Ir29h!{GQwsD
zi~EK)4A?>xyNtIVZtTN@eZbg<7yIyG9|-p0$36nsM-cm90mQzxC9!J```VVp1{V9;
zmc}w3``VVrCIakhdjytj*cVRs_6Te!u&?bASPEia+as`S!@dL9D_i|r
zo3mS+F$-?(-{h-%P@pfJZTs)QSGOssC*p>c=xOuA(TYaXs;PJKV>N?>Gzo}&rgx=TSPvTui$QA)vGuk
z^wR~21t|L$(|6=(FE8#(qY@^J4(ZP)JTjwH6Ghg$nw#&<5Y7y|1T2lrXpmS^4t+8l
zJ6|*aYsOId&1jn7yXx!v*ElJ4R@0`$f9W?%AZKmbgz#p)&iBYi4@ne$c2+Ix!gn&G
zdh{esfS%W_@=d;~rn|2C+56UX!H~l#9isF*@tj7oO3DbkC`Qa|-b%E&=)U0*?G!Al
zc(x3758u@L+?cAZkOp-5dTWH9^mMUWFDH2y;Cn+@D>s^
zPK&IV6W!yf
z1{I#gO5BHQRQcwr8@99fnQKRRJ*B>yxYvYV01q$`Lf)3{0VJ94mO}d|sl}#A4*D
z;18JodZo=OOMjzh=A#pz=Z^D0&#D%8#k^J-u6{8&z;15Sj5)8tAKBtGxO~;)eQS69
zJDc>?(&cBP^LI+3PC%DVTMwQxXyi(9%@yZPt_@;puh8fmiCvYq}sGRmXb~E8~
znEa^Tg4Z;4({RFLVY0>vrlCs4>PUU{4GXt>sv(T>seYMR4H64J20d0XqtCjCPJ}Di
zfI}M*BSc;N(RGSP94X--$MS1msST5XReBXBu*t-CI^r
zQfwrQ2=G1*-pIJMrEq;o4Jr-L5uso1IUI5rv41$p4G`S>Py!N
zqg54eKi9C4%0aNHIpz^#73esUKjk+eUK?E&?L+C~9i2Cf@~!TLxz)p;BE3wPNhU)&
z^p|Wtwsg;S-s?~E;zXYS_(F^7iV`>Drv#^*93L8w`D&5IJeg`(sS-Ifa~QP$U8Zf~
zkYIc_iP1eeK@^~efHUKAi(ihY#&;w0pbMT66{~FX+tdD56=1zRn)NHG+X_ye;qf=VSsGi;s^?j9+KdTG?
z%G|XCiu(TMMJd1T=dp$rOLeX+ZQ`U}FfZ*Z)sFGOxX^UeaSAgVsNH4-$utU4H?=sI
zzHA}fFAvR5e2Z#O<9xKRK}|u-K?zS!O8+#2=VKMZFwI~2@CCiCQ9F&&@2yh4TL9!n|Xy~M*)^LZU7q;tL8-T
z(&h0e`PU8k$6U>qy-ais1}L4yY%n!JPTtV+M5rgv*SMVfxLN`v#KDp1%?@
z6utgv^t90er@L;1i+(3%7`h_5shizflh8sKC@yWs-=)##{=P*}NZc`EBNxpY5&up>
zBj82vXU~oT`Tlkz-Pg;~ms~%Mg8BX8UU_simMPxqX|Qi|h&8c&-U#e9+Ttjx9WnlJ
zr!D@i1E)S@_B1-XgYvygkgx94YJJ1K#CQEU3#dEF4w+F)w8rP6;uqk#9d3SU8G?t?
z`42;jgBZODicI{h2kIVI>=m@jPmg4NY|~K}
z*|1g6h54va6s=^j60|&(x4#^ba;Djbyt1rRK>YQW3bP|0&%I&@j3T4_ueo%tM&Nr3ZmlcH-b}|0M$4ty^~Jg#OnX(d
zDvmBzI5-+2ofVVso&1<*;FD2v{fLXYz6iVj0{nwkJwx(D_sb?`(GWGYOefdJEe!@KQe0U`sUz_4TE)`LN8XCf_7k^x=DS&~
zr}-@+Chw-a2OBSZ4l*NkBAiD%e0)zO;gYMS*NQ4$HHm45*xZhBup%%m?Gex0XqR5=
zU*c44rOI0EmV@|+;5%XRRa^aIi@Mm-P0)RqtR~Y4!4FNs0&qU$41M?Jw#R$o050TBg$tH*4|5Nx=#ZBS&<5?P2%rBdjXCh<__3>Hy45y!s)Xh2)f>`_3
z!qcv}7kk*EgAJFXANnd91-YY$AC!etCEfK}@OtJ5`H{$;!Z4hlQrH4prBy^q4{PZz
zkY7fr1(L>O)c1lp=W5t_PDV?ZtAi!8ldX!oqRIJWoKqng5u!N_Ym%
zCg-E5VKhq>iZ-C2I^GluNePSVR1whq@dOHgR$EGVyQr>{x*@c0?u?Fd(Gs7o`%yRi
zaTH74l<45;nEDHNNUCq%d|>5#!cijXIkWUz8tM|Y4jRt!tMkIqrGB-!MI&rV{b>xe
zVuoRbQ0;-28U_p^@XmB2?+0o~m_B1P351o1O>ULb)RI@%wd#)Jt<|=67(O9}{B2nR
zd*+J2JdDSW*b}Nm-BzzO%^C?h1m&Lur8sB6y9F^erzd2_Bq3x|R^H(6omy6~9s++V
zx$2qjBjay$5+Hy!{M0282lUaAooWouv5nKyK^Ol
z+=BIUgUtR%+_LFuZ-KT35^e7rubVh>ASLSniuN*Iu^9r@gU61-Lou=DQtB?n3qoHD
zA{jf_^K|M@O|gyR(P{){f5^OjPDdWyJdb!8b?ba0JL$ZDdr3c&xH0u9)xOz+=e(d%
zIS5fIrOmPR>uXnJDGbafQi8qPPm5*2PzF%tdQFfI)!&==rDBuXJj}=@40cg6w?cX6;Muz=lQW8KlZ%D^9qX#Bp{y9g}IH`a<;FoKE^yKW7HRNr9s)8k~9GDfv;ULU5m#
ztI`-aA7e+0#E)+a*FGu(7}Fgc-(^p7tqfFEIU_dV`PCj*`j2-*KliKZc9-N&5Ys7)
zP|g9{{0(FQ`gfX`vv1S-mkc07+EUB9{pjgu@z;Sf7l@9!Gg`$AduX{l#G6e5I|_v9
zmW!){U(nKe-V}}bcHNHasGpCTW1Tth%U6mhCgJ*oAi5j*dO=|)vlKjU0@X%lMTJx9zgPzmqe`FR3%X7L
zi+B!)97gQlhcE*%1D;<6c^AHAWQ23{=gUN$x##B-(@V`5?GI0sZDrr^gN#pgQ#M(+
zx~Q*5kc&6LD}9pOx*MV-!HOJg$sI?FOut<_pW}!gFXSGm5qR>5x8ZBC@yo_Wm$|8t
zcAxBGjkyI8V_4!^RZsV!nZuy{?=vlDr0!e>aC0KpX$&|L6Y>NSbN?J-Ic0tN5d;6}
zSv`&+dJ;~OC^X`GPfOKSGx}Dq=w_!4G6k&Sgih`oiQ6LDN|DN1rD;8$1MRVF$NL=Q
z2rxarWo%_KRt`*^c`ml;QyDNnGuIwX1daMoTc*1K0dDA`p-gWYMqkUMi%z=c(^Wq!
z7gi@)m4(YoGP_#YIV{eJ^STB*1Qai83ryZnp~E@1RVvPQ%3Q39*JD~^rEBSm#l>EP
zX0`Y^?Q=qN@Z|jXfUUT>_yT84_GqaFG-)2CR@@-DMY*ZrYrG)%{*+nMm%dbhHRBv<
z+ttmM{;$ox^x8eNE*Ri5`r)3zG*QY%p*tZy#cSqtYsILh>rxR-+|Tr!+cxY)1F3x-
z(kbQx2tvITF#QuVV}owSn9H+tZquKw+QO1VFyAc~nzy{%R4;VGo|_!&%ACoabnlic
zfM*A~@#gW`4gk~~Wa+mg2W6dB(56jZnT^WB$TZgopG^=Z^K{FI%?-vM(RRgmfkQF_
zv?*Sgc*MInGV#1G!fR;ybK}9W{{w*F`(n9Mt=9uu!TsyI7*I*Ea`I7{z^Ify+hEYkiozP^-L&iWN@9jn5(ei
zbN7uwf)f*RmlljANYg0l-(;SDaVD{U^jPoa;EN*1w8qBqN&NE>aLaEsy!3s2Xs>be
z#$ls#{BlaNJYlj#){fbF6j3BWZ?E8sGozO2Ll-NY?d%nFLB~62VDSp?SJ9i5pc|Gp
zocyhM5*|V?YD6>x%aZXk$IPBw#Aihdy60}?y#@6qXWFbilBgc(r?%s1s9NE7)qfOW
z^Es@NCki&Im|W&`qM};ciLOEbeTgqk#EOdNh+4ZM
z>l%110%M;W@B~l{p&lUEg{UuFb0>6F=${tn9QRw9n2IdYIhi4dmWjHtFt_nc_jT`x
zw#EC0@MCrtUpi$m_^1&XwRD`kMyQOkIcmA}@S1Lc8gz7V$s@11jqiB3g>l3t2w0Y8L&2-?G!s$Dxf~B~7tUm^TGK!zkng+mWtAUbiGg}k|yQ1D*#%Zc7
zDFGiR
zl?rANUMLEMMkIMsOu;QI*UyMpx+K0P%t6Cj?r;`SbVv$E3RrPa(-z>@k*T-KITLW4
zYK&7kIaessrOcG2M{n!gmC)}rDOsVMUP134Z9SJ=P1lJmcQ@@A>*r99F8LzU2{!h%
zBK_#`WOlgYJ!>5PdTdvh7=Du$J?nc9j!nJAV81l!;SgxpCuL*NUS4ha_
zYl}4meUX?q_LA;6;lxO509PNGLYapgqZGXxA*x&8q9k%ZcxyNt1nE_5BrXS$3Uv<8
zn>_zU@h^C
z4W;lfysxyW+ap*TGWvxugyM$4D)K#hcr$wicj5F?nN>8ZBQTz!AX>&Kw!S$Cl&2E{
z`*cSP&4H=skgGAYNljKVL3qBTx2Sz{qTx18YgejqZ~!odM3As_^3cp-(EhKOrYe1#
z$<;uFQoGIgl~HhAy+X3jg4-u%#{dV{o7L5ripd4Lc7?Yh)f>eFQ$)gk3N!`_Z7ToV
zkj;03>!pov$N(J$b|K2X^i)mwp?u-*sD^nmTPKhh-Ki73gHgIr47RHnURUi=lZFvM*>@v&K@g{qwSvl^|}ROx(?G)weTt3
z@J!GYyU@eH1}(K~A?TnvZ7Yp
z98Tr`f2i0#zcDl}LXzsBqR%3WHsDZzN94z^KVHSC1CEHFGJp8JX0Xf@#5qfqPu2uW
zQU|_Q`A{F|D-xA}SW0DOA3h$FQek3c<6ukA6+=JC(9isaBUQ)=<~Ut3EPCHzAWV^b
z5|PCkLd6r5u)v$wtK#*J2Kh2ufW%_v`3&C3!hPCf7^$oZ73Kh7T47!RbV@;F;ln-A
z*Q)P$Brna|MiaE>C#457!ZIil5Dh&oE+sJ66!_zqCpmc&LvzS%%Fq@69$%=KN(!Jg
zN!h4cD!Q??|B)K`D{D{1wgKL}&%$4TubTqwPNK+KDAb}v#0r)N=A%Ce&($Y9UDDGG
zsU;4pZgo1RJ)2Z|`#GvcGm?PcL3ZWH!s;i|qplY^2a;Y^`Lye3_k!)2qgRzb(cMVC
z9d@3~Nk|bsc~?cf_LP{0Uu*x!%$S&-n0T8+iK3L2w%t4$)#+E~Tscz?j$v(so2amY
z4K65-nphPk6UqygGMhd;*WFFq1E?RZ5;~6dHTFwZprhAue(2QnBg%2)PQ@dxkJk;o
z4?+1CK{1?WiwFUyD+!iG5UW5YXaI`JZzFwE249efn+#j^haT?~Hy*w@7i)3e)Q8F0
zG>}e|?8iGyP(v-1dSWE+MFVwud#|F6kr>n?a^E0R=16@nu}COw?e%@6%v#kezl0lKCSIDdx1qI^bgg3*9#kgXwew
zOOmhg(4+am;u#u(ctj!Kf*K{m_{N7QDe2mZ8P?#T$B|^Rf^&s9v14H$PR9**8Jb=tMa|GL0%GYS*u|$P&=0EVt&`hyjV7t8Jw6
z%WVvzk1nOluQDFO^FM({4QcHf8aKjM@2z=GyBI)-5x!}OziB9>P-(5x2}|!CWINU{
z^~?#cF&r4KVdDE@o=2huAdC!kQ*AGB?@*G5Pp({XcS{)mSVI5pAUhf4CrPRj;s0?Rai>@};_rB)uPg#u(
z3wd>!1w?knC7sN56>8T&{hB13H_sJ#2JH~uONf!6Wxg*6G8a>yog?=!TCOZO0&M^^
zq-055a|(+cgGZt2#FI^XOUx4AA(otDONv_;Rr`Sx0#tQQCJTs10cj_BGxKO+V$SyQy(^fxt+TgCw;N4}UZ2eeO{=rK%eBM)?R}n={NSHms1_vP5G+
z0?fv7>$c9N%WHbfnE9rOaDFc82PRet=0Hb!yRdtXbn);ZmkwMt(tGdnM&Wu)2kjyBO`+@0*r{?XhlMd1t-LfoQW3&e|a-9OngkR?&4QI(`*+!%PI-O<6H
z{)W?X@-+Yz?6z`|rH-qX+n8p{8P2mAtCQvBR2%M8@G*)663s>-Rj;cy-o$y8`S&q;
zwVAp%g{u2szL|GfnD1JXY=8RR3K7_#%Y3PE3|N0wDp$a~*}Cl$>zQz{K?z?k?I7Sz
z^u~j)5(F`4LS`dE``YNgsPcLdd7EttaX*xC)2n3oQegsrmHAvHt~v5NUh3S;S@GBN
zQ)(|sdC+eYVSNRdoXzI!H!Rv*1`F-JzTh=HFhL840(DlTT?(Ps2r-q_GlwcPA{bg6
zZX1YTmL6Uo8O~kuNj-$*pMb=6y%rGjaQw9XvR;*V^Sbxr)%R1E&WRbC=9(#BrXctE
zoKST-c@Nbxx{sV{Iu0a!RCX-NH+Ovi%z5`hJ>3)<@Tl)3S6^_CR9S-A^s5Hnm>#2)
zOF-8SBL11{uY?%}sE`s8mak*MbN0Hh%6Iaf9dO#ME3?!`M7BxJUidT0Ea@@##%oYM#C$6O>!V0Y}vNMbUwwIIx{_7R`L
zMbL(z?mRY)na59{o&fwpeUHZSE|)o~P|j0EKzj^cq2=+{mbDgdkau$I>qg3(EWoNS
z0mV~Z)DBE_v?u5MQL(Z7H=4s7^Fd;RUztj$5YOFWS4fU5-0Zl?3#)Cj=!isjm{&fS
z?+-1s8ca3#jCUdW6y2Fc?-N2~mMaxd?JrWVMSsiz7mLp86|v;|dMkExazv1c=QpU|
zq{C!TT6Bl7J6tITm%=@Ixg?+i(?w{1`OxE;0O3vdUjAeC{D%B3C>E`JLz@9;E>&_3
zTz9$jS^kS*(kG5Gj!Mncm&R@s^iUpx^FIKGIu|Jy?U)tq(xL}PYQ2&ZNv(dqys8-(
zRLXq4?S#|XfcHYESSM(VfxCkhRTzAZUQ_p@R~n;6zIs!UaXJFUA%Brh%|Lb?#!)SY
zBx9QN6mfZ2wkl6QO=%nW+Ke2nbNw0cV_I8jdr->V6sRum4?XlNrqcmz8SySf6b5fm
zzAx;qMi=EFG4BGFiG<{CPvJh#zO
zHA3eVb-S%Lzsj!T(_Xx!gHNdk1REa94`U|BOLdS*~bVXd|vTWyfQ`@VMyz2>7I
z3hKdUH1kWA&>2)~0#wX8k)+NXiHUv&jJb4bgjllJ@k@ZD;5Zu?$b;r3c2zT-)N6wU
z%Gy)fD|opXqFP9LX)0w1h;KH7vu7I8}?9Ej6QWIVFl9%XKf(;#Jj`c34SQl!bI}
zuH4-;CAM6gpd`*?qI;Byq_M~u1>1a@_i}BW_pg;4KEb?sVf?Is5k;dn8!KJv&~owY
zyzYI+c(r1^5{|j%2$E5&OwpJyzYx%3#4D&W9jl_i9ObpD67EbZi1w{HE2i8nm(Zah_;?n+KD}lFJ`vNa_1Y=0xV|ir_<1F#Qr}`ZA%f>&UYW?JPkq=vZ_MUn+Ryfm
zeFvSjk{4MtDiiEBYl4p48z$O#KTH+kQ%k0Rk^ahURnHztqNXgOT{G?0H(Xqal1Xz#
zJk}bB6{D?-^(wAzXCg>D-z_~1s9~T@tZeC>OsZJ^<rHe?ND@_pWq>hu^YbvS3RjU#F_6qBt@VRqK?2PeZPtt06r3tGZ48g
zILXG5C+$5oYaz6LLQ&`Ldt@djt#LEqJ-=>4{-DTehUC+1c_j#5dL4{J0KnH@mKEyq
z4nMa#aHHoYR2*58T*nJ*dxuA&DPb0rKXvH^8I^&`J$y=m*CS`(ZG_CxIJNkNT
zm&u|FzT7B--W6(&B`>G=TxW4XFi1j`N!7|7ZX#BIhSTkWas3dC1Hlk;925;o!q&Sm_N{P9JlfE2{d$!aCSgBA`J1AO>@9);E8!tgdOmW+9ElPA9z+
zPA$3S-h-LbNQ4FV$e%=4tkYG!PxKeZ8x$~4beZ=nWS)5r1d01KH55a>IUybZEr`bf
z_6t?excOW5Ac=m;S!bGvH$0of{)1U@%Qc|o=saPu0t~wt|5m5cD1NeN9`{@N9}V;|
zUbV6vg~!}=3uYghJ*`E9xt_OrcQP0Ma2}XJqvkWw-G>wS|1|=BzO-R#Y!6661~$5M
zvqY4;qwT1CI+Z4A#Hb3s_$^R%j5H#X+|fS@7n8Bjgj~f|c~gxZ4Gw
zB4ek-Jkd!W((Jf4K^Tvt9pxxEqams+x6ttiTfR-aCxrukpQH45l-WJm5#&=%$#;&r
zu$FnHht6$=G!G;{+Mo?k6P%4ug9u?COXs&wWqy|2#|
zq2CP04J@bB34HU`97Waif4>{qR1I+;?OPtuPn&9dc3QKW95zUb$p$`*DvKx^v5y|-iF+t`tG)2=DWjY;E)J$15IRld7>R@46#m6#j3xV%_zzoM7LZ!(|tLv;x2+;=N6wx#E&4Syf?f3B0k7M{EIM4?-NXf*6VlWdIHLEM
z$O7@<=%X6e#ro@18YgpN<}l20op_gnSF4_QxedHqz2jEZu1$DjvMl!_Y}1<;fTwLm
zq(I&*uNntct*!P*-|!z5Kk=RJN?g6T3_FGl)DW{KTr_f9Pm{jLe0YKXt>D>y4=t;t
z$2u8=qM5g4C_Ja3B3suIm;XU%xXFDF8RKZO`K@n`FZ5{Z8p@n4rucjV;vbaV9(V8;
zU#N_Qh45rBn28UrDqhV7C|zC%I7PHoF29hl`8@6Onb&PTmRhSA5))E_ync#E*4WUL
zt4%4vLHPRXR84NDlSCh14RiBXM>Fe$i!V9A8s3#;iNU&RM=j-SxJvMI`<0Ir8jwFS
zdgsr6ysOD^^QF@Cku$ZJ`{kwLb6+tZiU&rm2*;R`o55^`
z1``0t@O
zZ|?aHFGb^WWBR=+U+Bj3XUk;?b%fDIgG%q+P^v|r=t~Ia%4!`r&s`)9bv@n4e{(5&
zUQ%7CB;0F&n9V-Yv2FH;u{i8YO1}w&)Nl=8IZVBNB;}-d3T*U^#DLW}GZNOStji{T
zXyh4_yQ;v%zR
zHlmG;x|-%%_Jeii<6EGnomC&;88A2OuB{rWn)TY0Af1J**oKfi(kmr<`a4NdKN0wd
z!@V{{2g~9FzyHU9-s{_jR$LAZ9ft1zj12cQs5VE$?l>}4oJc@wxuSIFC;GgkjKLWu
z#-U=e#H7
zf)Ui^%df8I(jJN*M&|zo32GO``#;fF-{_b9>^bakI{}sldi?FA>*pm~^^P*DhpycD
za>xxwF(S3)^Awo`>cW@N#r<(HHHY&5ZG5(>nAnS73JsUJ9C_=Fs{5EwR!isYx8T>HG9A(jdeI~_gM6FDb+JA79D7Ax=
zZTyBD@lp3ddh~5juA)uMomwP*L5^%I(|pSNKY4(J$2uNAph{&cb8<68zm
zJ-k!zLwJn*8Zqb$p(SF&|JG&hC$gY^)$}#JEmNL5I<6K5qug3Fs$sJJ>On<$A!mjj
zJ1J4Kt1Q@Di$Qu}&E&;!6EYFZjp26_s?txn-88DLYkD>%V&qrGy71%_+gHlm7alZR
zzz6Vm4_rCN!39c}3-DLKGI8Y$bcK(#5EJl?w3-`EtDl3Ss>~j$8`5##lU^H8y&Z@*
zB4M7c+|b12;!R2DmD}%Hc{%uOc|4^Ro4QN-7GD?(NSr@o;WY&(`8oZhd7l#As_eCx+X#T
z8jy{+%_knZNTqZ6Os~f}RlL%@lL0yv-`*#grAjVAFH`;?oMA4-yEb3RnBVGeNyhFbbXV`3arpohTCg
z^NMB5!9L=GWG+NVwZhl5GmN7h+*4|$zDm>I9vAY{!zx9;3I{Zmvfb6`sk=p86vr@R
z@*{d4#SDF8c^;EQnOWvCBqHp+ab4h4Qq;Nhl@WMTp6sL1ISt2mb;-_x56bw@c#4p8
z-J#nYy0OUNsk?N~J})2=T9vMQg86Fp9lYgU7>a5|ZdOE$D9zT%4kT-i_Vx%&(08sa
zi;46t@9z7Bscq{&876JCw>o@N2MSzlVC
zC{26BE!-{Jn0fz4n&%-H|0Ec__3)xnTD@nA&^Mx{GW|xJRcTX16FU3=aD#$HdHfs&
z$tA(==alJOB0>^gRIgD=h`Qj=V{3#CkNL!+e3w(G+#^2I6lZ`EoqK5Nd4)fp3aHfL
zeLZ9)tW#2o8aqaAq*p4554xjsdW^06NE_PrQfH>oF^dsvOl?u@jGYZv>(r2p$T`av
zy%%NEjz@^f;>na>yPp7(7u;~V7Mo@TP#BfP#`f!6gx86wfe|`{88%!;y*iNI}DA?Qc;*=$kZc?~TR#v~Ox}zF1F9
zB8;apKOfi_{@#kZ<3oaCT@$IA)5V$&8jU$X-}D=GH
z=T(L%zMDu$#vR3&S247y^KvgT1v3VKMP1T{KVTxJExvI9bUN!ctMW7XNv!@xSzcF!
zOv6jf4HBZoIK+juhl4IcZ44^tVYz;_>8p-yZ^$I+MGKZk=R><4R8-D37!$eMw()v(
zRV#?PXu8_x)iPdd9I1XPj<%o-(O;NLk!JQ5d*nFXGz|JYo0P;A-a>J7JjH}CHz?}S
zS{7!?Dn#~0WJ3_S8>)wswQOWi!%uSa)r=p_I8_#j6Wpd7;l}=EK{Mo
zW(|>5#ULE=6Nw`Npd3Qni!EiQZk%p4E@~=XE&e$t<)An3q8S{ndZZxl4FwTHIoj3F6#jln?`BLP#d5@QwVmB66@beN3!bIXF$gg8qkmoIr(aB_NOfD*H5GsGg7Sy;@CJ}NkB3f4
z^oF16UD$kjC7QC5O1rZL(T}>|Y@mfHq0u2;k8-RH6q>i;I7=CKy{FyG74hQK;?d