# Docs ## Docs - [Frequently Asked Questions (FAQ)](/docs/faq): `useEffect` excels at responding to prop/state changes, but it doesn’t encode the idea of a sequential flow with typed payloads or single-line navigation. Relay stores each step in a typed store, tracks its status, and exposes helpers like `start`, `retry`, and `next`. That means you can declaratively rerun the second step without coupling it to every state variable that the first step mutates. - [Getting Started](/docs/getting-started): Before starting, note that `Relay` is typed from the ground up. The `createRelay` factory defined in `libraries/relay/src/relay.ts` lets you parametrize the configuration, step metadata, success payload, and error payload types before you register any steps. Type every shape first, then rely on `StepSuccess` and `StepError` to keep the runtime results discriminated so the compiler knows exactly when a step succeeded or failed. The rest of this guide walks you through that flow. - [Installation](/docs/installation): Relay is published as `@0xhq/relay` and ships as ESM. - [Why Relay](/docs/introduction): `React` makes building event-driven UIs easy, but `coordinating` multi-step `flows—forms`, `payments`, `blockchain transactions` or anything async, quickly turns into tangled `useEffect` chains, manual timers, or duplicated state. - [Node.js example](/docs/examples/nodejs): Relay runs just as well in CLI scripts as it does inside React. This example uses `createRelay` in a Node process to initialize three sequential steps, starts the flow, and polls the store so the script can log the current status of every step as it resolves. - [Simple example](/docs/examples/simple-example): The simple example shows how to wire up a basic Relay layout with a header, sidebar, and footer so you can see how the pieces fit together before customizing anything. It pulls in the sample `SimpleExample` component along with the related layout fragments below, which together demonstrate the standard structure for a Relay application page.