> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: The wix.config.json File

## Article: The wix.config.json File

## Article Link: https://dev.wix.com/docs/go-headless/wix-managed-headless/other-frameworks/the-wix-config-json-file.md

## Article Content:

# The wix.config.json File

`wix.config.json` links your local project to your Wix-managed headless project. Wix creates it for you when you initialize a project from your terminal, upload a site, or send a Claude Design.

This article covers the fields you set when you build with a framework other than Astro. For the file's role in the wider CLI project structure, see [CLI Project Structure](https://dev.wix.com/docs/wix-cli/guides/project-structure/project-structure.md).

## Example

```json
{
  "projectType": "Site",
  "appId": "<YOUR_APP_ID>",
  "siteId": "<YOUR_SITE_ID>",
  "site": {
    "outputDirectory": "./dist"
  }
}
```

## appId

Your project's OAuth client ID. Wix creates a client for you and stores its ID here, so you don't need to create one in the dashboard.

Use this value as the `clientId` when you create a Wix client. See [Create an SDK Client with OAuth](https://dev.wix.com/docs/go-headless/authentication/setup/create-an-sdk-client-with-oauth.md).

## outputDirectory

Tells Wix which folder to deploy. Releasing doesn't build your project, it uploads what's already in this folder, so build with your framework's own tooling first.

### Client files only

By default, `wix.config.json` expects your build output in `./dist`:

```json
"site": {
  "outputDirectory": "./dist"
}
```

If your framework builds to a different folder, update the path before you release. For a static site with no build step, where `index.html` sits at the root of your project, use `"."`.

### Client and server files

To deploy server code as well, set `outputDirectory` to an object with `client` and `server` paths instead of a single string. You can provide either or both:

```json
"site": {
  "outputDirectory": {
    "client": "./dist/client",
    "server": "./dist/server"
  }
}
```

Wix deploys and runs the server files as long as they're built for the Cloudflare Workers runtime. Inside that constraint, you can deploy:

- **A backend on its own.** A single JavaScript worker file, or a server framework such as [Hono](https://hono.dev/).
- **A client and a backend side by side.** One directory for each, a single `wix.config.json`, and relative `fetch` calls from the client to the backend.
- **A full-stack project.** Any framework with a Cloudflare adapter.

Frameworks whose server output can't run on Cloudflare Workers aren't supported. For more information, see [About Supported Frameworks](https://dev.wix.com/docs/go-headless/wix-managed-headless/about-supported-frameworks.md).

> **Note:** Server code is only available when you initialize your project from your terminal. Uploaded sites and Claude Designs are static, so they use the single-string form.

## See also

- [About Supported Frameworks](https://dev.wix.com/docs/go-headless/wix-managed-headless/about-supported-frameworks.md)
- [Create an SDK Client with OAuth](https://dev.wix.com/docs/go-headless/authentication/setup/create-an-sdk-client-with-oauth.md)
- [CLI Project Structure](https://dev.wix.com/docs/wix-cli/guides/project-structure/project-structure.md)