Update docs content

docs/community/docs-contributors.md

@@ -0,0 +1,5 @@
+---
+title: Docs Contributors
+description:
+nav: 301
+---

docs/community/third-party-libraries.md

@@ -0,0 +1,5 @@
+---
+title: Third-party Libraries
+description:
+nav: 302
+---

docs/community/versioning-policy.md

@@ -0,0 +1,5 @@
+---
+title: Versioning Policy
+description:
+nav: 303
+---

docs/community/zustand-videos.md

@@ -0,0 +1,5 @@
+---
+title: Zustand Videos
+description:
+nav: 300
+---

docs/learn/async-data-and-data-fetching.md

@@ -0,0 +1,5 @@
+---
+title: Async Data and Data Fetching
+description:
+nav: 106
+---

docs/learn/choosing-the-state-structure.md

@@ -0,0 +1,5 @@
+---
+title: Choosing the State Structure
+description: One store, multiple stores, and multiple slices
+nav: 104
+---

docs/learn/colocation-actions.md

@@ -0,0 +1,5 @@
+---
+title: Colocating Actions
+description:
+nav: 105
+---

docs/learn/extracting-state-logic-into-a-reducer-with-redux-and-devtools-middlewares.md

@@ -0,0 +1,5 @@
+---
+title: Extracting State Logic into a Reducer with Redux and Devtools Middlewares
+description:
+nav: 112
+---

docs/learn/isolating-state-between-components.md

@@ -0,0 +1,5 @@
+---
+title: Isolating State Between Components
+description:
+nav: 108
+---

docs/learn/listening-to-selected-data-with-subscribe-with-selector-middleware.md

@@ -0,0 +1,5 @@
+---
+title: Listening to Selected Data with SubscribeWithSelector Middleware
+description:
+nav: 113
+---

docs/learn/middleware-use-cases.md

@@ -0,0 +1,5 @@
+---
+title: Middleware Use Cases
+description:
+nav: 114
+---

docs/learn/persisting-state-with-persist-middleware.md

@@ -0,0 +1,5 @@
+---
+title: Persisting State with Persist Middleware
+description:
+nav: 111
+---

docs/learn/selecting-data-and-preventing-re-renders-with-selectors-and-equality-function.md

@@ -0,0 +1,5 @@
+---
+title: Selecting Data and Preventing Re-renders with selectors and equality function
+description:
+nav: 107
+---

docs/learn/start-new-project.md

@@ -0,0 +1,5 @@
+---
+title: Start a new project
+description: Vanilla, React, and React Native
+nav: 102
+---

docs/learn/thinking-in-zustand.md

@@ -0,0 +1,5 @@
+---
+title: Thinking in Zustand
+description: Motivation, principles, and glossary
+nav: 101
+---

docs/learn/tutorial-tic-tac-toe.md

@@ -0,0 +1,5 @@
+---
+title: 'Tutorial: Tic-Tac-Toe'
+description:
+nav: 100
+---

docs/learn/using-middlewares.md

@@ -0,0 +1,5 @@
+---
+title: Using Middlewares
+description:
+nav: 109
+---

docs/learn/using-typescript.md

@@ -0,0 +1,5 @@
+---
+title: Using TypeScript
+description:
+nav: 103
+---

docs/learn/writing-immutable-update-with-immer-middleware.md

@@ -0,0 +1,5 @@
+---
+title: Writing Immutable Updates with Immer Middleware
+description:
+nav: 110
+---

docs/reference/combine.md

@@ -0,0 +1,98 @@
+---
+title: combine
+description:
+nav: 201
+---
+
+# combine
+
+`combine` middleware lets you create a new state by combining an initial state with additional
+state created by a function. This middleware is particularly useful due to infers the state, so you
+don't need to type it.
+
+```js
+combine(initialState, additionalStateCreator)
+```
+
+- [Reference](#reference)
+  - [Signature](#combine-signature)
+  - [`setState` function](#setstate-function)
+  - [`getState` function](#getstate-function)
+  - [`subscribe` function](#subscribe-function)
+  - [`storeApi`](#storeapi)
+- [Usage](#usage)
+- [Troubleshooting](#troubleshooting)
+
+## Reference
+
+### `combine` Signature
+
+```ts
+combine<T, U>(initialState: T, additionalStateCreatorFn: StateCreator<T, [], [], U>): StateCreator<Omit<T, keyof U> & U, [], []>
+```
+
+#### Parameters
+
+- `initialState`: The value you want the state to be initially. It can be a value of any type,
+  except a function.
+- `additionalStateCreatorFn`: The state creator function that specifies how the state gets
+  initialized and updated. It must be pure, should take `setState` function, `getState` function
+  and `storeApi` as arguments.
+
+#### Returns
+
+`combine` returns a state creator function.
+
+### `setState` function
+
+The `setState` function lets you update the state to a different value and trigger re-render. You
+can pass the next state directly, a next partial state, a function that calculates it from the
+previous state, or replace it completely.
+
+#### Parameters
+
+- `nextState`: The value that you want the state to be. It can be a value of any type, but there is
+  a special behavior for functions.
+  - If you pass an object as a `nextState`. It will shallow merge `nextState` with the current
+    state. You can pass only the properties you want to update, this allows for selective state
+    updates without modifying other properties.
+  - If you pass a non-object as a `nextState`, make sure you use `replace` as `true` to avoid
+    unexpected behaviors.
+  - If you pass a function as a `nextState`. It must be pure, should take current state as its
+    only argument, and should return the next state. The next state returned by the updater
+    function face the same restrictions of any next state.
+- `replace`: This optional boolean flag controls whether to replace the entire state or merge the
+  update with the current state.
+
+#### Returns
+
+`setState` function do not have a return value.
+
+### `getState` function
+
+The `getState` function lets you access to the current state. It can be stale on asynchronous
+operations.
+
+### `subscribe` function
+
+The `subscribe` function lets you subscribe to state updates. It should take current state and
+previous state as arguments.
+
+#### Parameters
+
+- `currentState`: The current state.
+- `previousState`: The previous state.
+
+#### Returns
+
+`subscribe` returns a function that lets you unsubscribe.
+
+### `storeApi`
+
+The `storeApi` lets you access to the store API functions like
+[`setState` function](#setstate-function), [`getState` function](#getstate-function), and
+[`subscribe` function](#subscribe-function).
+
+## Usage
+
+## Troubleshooting

docs/reference/core-concepts.md

@@ -0,0 +1,71 @@
+---
+title: Core Concepts
+description:
+nav: 200
+---
+
+# Core Concepts
+
+## Store
+
+The Store lets you access to the store API utilities.
+
+## API Utilities
+
+These store API utilities are: `setState` function, `getState` function, and `subscribe` function.
+
+### `setState` function
+
+The `setState` function lets you update the state to a different value and trigger re-render. You
+can pass the next state directly, a next partial state, a function that calculates it from the
+previous state, or replace it completely.
+
+#### Parameters
+
+- `nextState`: The value that you want the state to be. It can be a value of any type, but there is
+  a special behavior for functions.
+  - If you pass an object as a `nextState`. It will shallow merge `nextState` with the current
+    state. You can pass only the properties you want to update, this allows for selective state
+    updates without modifying other properties.
+  - If you pass a non-object as a `nextState`, make sure you use `replace` as `true` to avoid
+    unexpected behaviors.
+  - If you pass a function as a `nextState`. It must be pure, should take current state as its
+    only argument, and should return the next state. The next state returned by the updater
+    function face the same restrictions of any next state.
+- `replace`: This optional boolean flag controls whether the state is completely replaced or only
+  shallow updated, through a shallow merge.
+
+#### Returns
+
+`setState` function do not have a return value.
+
+### `getState` function
+
+The `getState` function lets you access to the current state. It can be stale on asynchronous
+operations.
+
+### `subscribe` function
+
+The `subscribe` function lets you subscribe to state updates. It should take current state, and
+its previous state as arguments.
+
+#### Parameters
+
+- `currentState`: The current state.
+- `previousState`: The previous state.
+
+#### Returns
+
+`subscribe` returns a function that lets you unsubscribe from itself.
+
+### Selector
+
+Lorem, ipsum dolor sit amet consectetur adipisicing elit. Vel veritatis alias saepe vitae placeat
+blanditiis laborum, asperiores architecto explicabo unde. Cum sint vero veritatis. Hic ipsum quis
+saepe voluptates temporibus!
+
+### Bound Hook
+
+Lorem, ipsum dolor sit amet consectetur adipisicing elit. Minus quas sequi, similique corrupti iure
+incidunt autem. Voluptas eum atque harum! Assumenda natus, animi doloribus facilis maiores dicta
+iusto ipsa earum.