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,106 @@
+---
+title: combine
+description:
+nav: 200
+---
+
+# combine
+
+`combine` 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 do not 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)
+ - [`destroy` function](#destroy-function)
+ - [`storeApi`](#storeapi)
+- [Usage](#usage)
+ - TBD
+- [Troubleshooting](#troubleshooting)
+ - TBD
+
+## Reference
+
+### `combine` Signature
+
+```ts [TypeScript]
+combine<T, U>(initialState: T, additionalStateCreator: StateCreator<T, [], [], U>): 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.
+- `additionalStateCreator`: A function that should take [`setState`](#setstate-function) function,
+ [`getState`](#getstate-function) function and [`api`](#api) as arguments. It should returns an
+ additional state based on the initial state.
+
+#### Returns
+
+`combine` returns a new state that is the result of merging the initial state and the additional
+state.
+
+### `setState` function
+
+The `setState` function lets you update the state to a different value and trigger a 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 async operations.
+
+### `subscribe` function
+
+The `subscribe` function lets you subscribe to state updates. It should take current state and
+previous state as arguments.
+
+#### Parameters
+
+- `currentState`: It's the current state.
+- `previousState`: It's the previous state.
+
+#### Returns
+
+`subscribe` returns a function that lets you unsubscribe.
+
+### `destroy` function
+
+The `destroy` function lets you clear all the listeners. This function is **deprecated** and would
+be removed in the future.
+
+### `storeApi`
+
+The `storeApi` lets you access to the store api functions like [`setState`](#setstate-function)
+function, [`getState`](#getstate-function) function, [`subscribe`](#subscribe-function) function,
+and [`destroy`](#destroy-function) function.
+
+## Usage
+
+## Troubleshooting

docs/reference/create-context.md

@@ -0,0 +1,24 @@
+---
+title: createContext
+description:
+nav: 201
+---
+
+# createContext
+
+`createContext` lets you create a context that components can provider or read. Lorem ipsum dolor,
+sit amet consectetur adipisicing elit. Voluptate a ipsum in accusamus adipisci consectetur
+aspernatur pariatur excepturi nam quod architecto id doloremque repellat nisi minus deserunt, quae
+aperiam quasi.
+
+```js
+createContext()
+```
+
+## Reference
+
+### `createContext` Signature
+
+```ts
+createContext<StoreApi<T>>(): { Provider: (props: any) => JSX.Element, useStore: () => T, useStoreApi: () => StoreApi<T> }
+```

docs/reference/create-store.md

@@ -0,0 +1,141 @@
+---
+title: createStore
+description:
+nav: 202
+---
+
+# createStore
+
+`createStore` lets you create a vanilla store. You can use a vanilla store in React with
+[`useStore`](./use-store) hook.
+
+```js [JavaScript]
+createStore(initializer)
+```
+
+- [Reference](#reference)
+ - [Signature](#createstore-signature)
+ - [`setState` function](#setstate-function)
+ - [`getState` function](#getstate-function)
+ - [`subscribe` function](#subscribe-function)
+ - [`destroy` function](#destroy-function)
+ - [`storeApi`](#storeapi)
+- [Usage](#usage)
+ - [Updating state based on previous state](#updating-state-base-on-a-previous-state)
+ - [Updating objects and non-objects in state](#updating-objects-and-non-objects-in-state)
+ - [Subscribing to state updates](#subscribing-to-state-updates)
+ - [Split state in multiple slices](#split-state-in-multiple-slices)
+- [Troubleshooting](#troubleshooting)
+ - [I’ve updated the state, but the screen doesn’t update](#ive-updated-the-state-but-the-screen-doesnt-update)
+
+## Reference
+
+### `createStore` Signature
+
+```ts
+createStore<T>()(initializer: StateCreator<T, [], []>): StoreApi<T>
+```
+
+#### Parameters
+
+- `initializer`: The value you want the state to be initially. It can be a value of any type, but
+ when you pass a function should take [`setState`](#setstate-function) function,
+ [`getState`](#getstate-function) function and [`storeApi`](#storeapi) as arguments.
+
+#### Returns
+
+`createStore` returns a vanilla store, that expose [`setState`](#setstate-function) function,
+[`getState`](#getstate-function) function, [`subscribe`](#subscribe-function) function, and
+[`destroy`](#destroy-function) function.
+
+### `setState` function
+
+The `setState` function lets you update the state to a different value and trigger a 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 async operations.
+
+### `subscribe` function
+
+The `subscribe` function lets you subscribe to state updates. It should take current state and
+previous state as arguments.
+
+#### Parameters
+
+- `currentState`: It's the current state.
+- `previousState`: It's the previous state.
+
+#### Returns
+
+`subscribe` returns a function that lets you unsubscribe.
+
+### `destroy` function
+
+The `destroy` function lets you clear all the listeners. This function is **deprecated** and would
+be removed in the future.
+
+### `storeApi`
+
+The `storeApi` lets you access to the store api functions like [`setState`](#setstate-function)
+function, [`getState`](#getstate-function) function, [`subscribe`](#subscribe-function) function,
+and [`destroy`](#destroy-function) function.
+
+## Usage
+
+### Updating state base on a previous state
+
+Lorem ipsum dolor sit amet consectetur adipisicing elit. Nam in provident eius eaque modi,
+architecto consequuntur nihil soluta, dolore ratione, deleniti voluptatum unde. Qui veritatis,
+deleniti error vero ducimus sunt.
+
+### Updating objects and non-objects in state
+
+Lorem, ipsum dolor sit amet consectetur adipisicing elit. Cupiditate consectetur sequi repellendus
+culpa nesciunt dolores aut. Voluptas corrupti expedita temporibus doloribus, maxime dolor iure
+suscipit adipisci hic cumque quasi officia?
+
+### Subscribing to state updates
+
+Lorem ipsum dolor sit amet, consectetur adipisicing elit. Aut quidem est neque consequuntur,
+dolorem eius, explicabo ullam voluptatibus ex corporis qui, quasi eum reprehenderit maxime! Magni
+magnam dignissimos eos dicta!
+
+### Split state in multiple slices
+
+Lorem ipsum dolor sit amet consectetur adipisicing elit. Repellat, sint doloremque incidunt beatae
+asperiores tempore amet quam ipsa commodi adipisci nobis quis fugiat aliquam? Facere repellendus
+asperiores incidunt maxime facilis?
+
+## Troubleshooting
+
+Lorem, ipsum dolor sit amet consectetur adipisicing elit. Aut illo, earum beatae voluptate corporis
+saepe ipsa? Placeat animi commodi qui odit debitis eveniet enim maiores, illum tempora repellendus
+sint non?
+
+### I’ve updated the state, but the screen doesn’t update
+
+Lorem ipsum dolor sit amet consectetur adipisicing elit. Modi facere vel minus saepe inventore hic
+tenetur aspernatur officia ipsam accusantium illum, neque consectetur placeat doloremque pariatur
+voluptatum amet odio quos!