> ## Documentation Index
> Fetch the complete documentation index at: https://weaverse.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Weaverse component configuration uses `settings`. `inspector` is deprecated; never generate it.
> Weaverse Hydrogen themes use React Router v7: import from `react-router`, never `react-router-dom` or `@remix-run/*`.
> Before using any code sample, read `@weaverse/hydrogen` in the project's `package.json`: 6.x and 5.x import from different entries and use different type names, so code for one does not build on the other.
> `@weaverse/hydrogen` 6 (Shopify Hydrogen 2026.10 and later, the version these docs show) imports from `@weaverse/hydrogen/react-router` and uses `Weaverse*` types such as `WeaverseComponentProps`, `WeaverseComponentLoaderArgs` and `WeaverseComponentSchema`; the root `@weaverse/hydrogen` entry only exports `createSchema()`, data helpers and types.
> `@weaverse/hydrogen` 5.x (Hydrogen 2026.4 and earlier) imports everything from `@weaverse/hydrogen` and uses `HydrogenComponentProps`, `ComponentLoaderArgs` and `HydrogenComponentSchema`. On a 5.x project, convert samples to these names. Upgrade to 6 only when asked (`npx @weaverse/cli@latest migrate v6`, plus the Hydrogen 2026.10 upgrade). Do not mix major versions.
> Next.js themes use `@weaverse/hydrogen` 6.2.0 or later: import client and shared code from `@weaverse/hydrogen/next` and server-only code from `@weaverse/hydrogen/next/server`. `@weaverse/next` is deprecated; never install or import it.
> For live project data (pages, theme settings, translations), use the Weaverse MCP server: https://weaverse.io/docs/developer-tools/weaverse-mcp

# Forward - Next.js Starter Theme

> Forward is the Weaverse starter theme for Next.js: an App Router storefront on @weaverse/hydrogen/next with Shopify data, Studio editing, markets and translations.

Meet [Forward](https://forward-sandy.vercel.app/), the Weaverse starter theme for **Next.js**. Forward plays the same role for Next.js storefronts that [Pilot](https://weaverse.io/docs/hydrogen-themes/pilot-theme-overview.md) plays for React Router storefronts: a complete, open-source storefront you can run, edit in Weaverse Studio, and make your own.

Forward is built on the Next.js App Router and [`@weaverse/hydrogen/next`](https://weaverse.io/docs/nextjs/overview). It reads products, collections, pages and articles from the Shopify Storefront API through Shopify's framework-agnostic Hydrogen SDK (preview), and it is styled with Tailwind CSS v4.

## Key Features

***

* **Composed pages:** The home page, product, collection, all products, article, page and custom pages are Weaverse pages that merchants build and rearrange in Studio.
* **Live Studio editing:** Edits appear instantly in the preview. Changing a product or collection picker re-runs only that section's loader, with no full-page reload ([per-item revalidation](https://weaverse.io/docs/nextjs/studio.md)).
* **Theme settings:** Header, footer, layout (such as page width) and editorial imagery are configured through Weaverse theme settings, not as page sections.
* **Markets and translations:** Each market gets its own URL prefix, the theme's own copy can be translated in Studio's Translation Manager, and prices and dates format per market. See [Markets & Translations](https://weaverse.io/docs/nextjs/markets-translations.md).
* **Declared theme routes:** Forward serves collections at `/shop/:handle` and articles at `/journal/:handle`. It declares these routes in its theme schema, so Studio's page selector and URL picker open the right paths.
* **Store-driven catalog:** Categories, filters and sort options come from your store's data and the Storefront API's own filters, so Forward runs on any Shopify store without theme-side product lists.
* **Shopify Cart and Customer Account:** The cart is the server-owned Shopify Cart API with Shopify checkout, and account pages use the Shopify Customer Account API.

## Getting Started

***

Forward is open source on [GitHub](https://github.com/Weaverse/forward). It needs [Bun](https://bun.sh) and Node.js 22.18 or later.

```bash theme={null}
npx @weaverse/cli@latest create --template forward --project-id YOUR_PROJECT_ID --project-name my-storefront
```

The CLI downloads Forward, writes `.env` with your Weaverse project ID, and installs dependencies with Bun (offering to install Bun if it is missing). Add your Shopify store and Storefront API keys to `.env`, then start the dev server:

```bash theme={null}
cd my-storefront
bun run dev
```

Open [http://localhost:3333](http://localhost:3333). Forward always runs against a real Shopify store, so it refuses to start until the Shopify variables are set.

For a step-by-step setup, including connecting Weaverse Studio, see the **[Next.js Quickstart](https://weaverse.io/docs/nextjs/quickstart.md)**. When you're ready to go live, see **[Deploy to Vercel](https://weaverse.io/docs/guides/deployment/vercel.md)**.

## Available Sections

***

Forward's sections are grouped by the page they are built for, but any section can be added to any page in Studio.

**Shared elements**

* Heading, Subheading, Paragraph, Button and Buttons
* Section content (a container for grouping elements inside a section)

**Home**

* Home hero
* Hero slideshow (with slides)
* Featured products
* Collection index
* Product spotlight
* Material standard
* Kit callout
* Repair and journal

**Product**

* Main product, split into composable parts: product media, product info, breadcrumb, meta row, title, prices, summary, variant selector, buy buttons and collapsible details
* Related products

**Collection**

* Collection hero
* Main collection, with toolbar, filters and product grid
* System manifest
* Field practice

**All products**

* All products, with toolbar and product grid

**Article**

* Article header
* Article body

**Pages and editorial**

* Page hero, page premise, page values and page origin
* Editorial hero, editorial overlay hero and editorial callout
* Standard statement, stat band and principle grid
* Product strip, product tiles and product case study
* Numbered sequence

Browse the full, up-to-date list in [`src/sections`](https://github.com/Weaverse/forward/tree/main/src/sections) on GitHub.

## Project Structure

***

| Path | What lives there |
| - | - |
| `src/app/[locale]/` | App Router routes, one segment per market. The default market has no URL prefix. |
| `src/app/api/weaverse/revalidate/` | The route Studio calls to re-run a section's loader after an edit. |
| `src/sections/` | Weaverse sections. Each one exports its component and its `schema`, and some have a server `loader`. |
| `src/lib/weaverse/` | The Weaverse wiring: server client, component registries, root provider and theme schema. |
| `src/lib/weaverse/settings/` | Theme settings, one group per file (layout, header, footer, editorial imagery). |

The Weaverse integration in `src/lib/weaverse/` is a good reference when you add `@weaverse/hydrogen/next` to your own app. See [Rendering Pages](https://weaverse.io/docs/nextjs/rendering-pages.md) and [Studio Integration](https://weaverse.io/docs/nextjs/studio.md) for how each piece fits.

## Learn More

***

> [card] [@weaverse/hydrogen/next Overview](https://weaverse.io/docs/nextjs/overview.md)
>
> How Weaverse works in a Next.js App Router storefront.

> [card] [Next.js Quickstart](https://weaverse.io/docs/nextjs/quickstart.md)
>
> Run Forward locally and connect it to Weaverse Studio.

> [card] [Studio Integration](https://weaverse.io/docs/nextjs/studio.md)
>
> Studio connector, live revalidation and theme routes.

> [card] [Deploy to Vercel](https://weaverse.io/docs/guides/deployment/vercel.md)
>
> Take your Forward storefront live.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.