---
title: "Customization"
description: "Where to change your project's colors, logo, name, fonts, and page head."
canonical_url: "https://nuxtstart.com/docs/getting-started/customization"
---

> Index of every page on this site: [llms.txt](https://nuxtstart.com/llms.txt)

Your project has two applications and a set of layers they share. Before you change anything, decide
which one owns it:

- `apps/site` is the public website: marketing pages, blog, docs, legal pages, contact form.
- `apps/web` is the signed-in product: account settings, administration, billing, APIs.
- `packages/layer-*` holds anything both applications use, or anything you'd want to copy into
another Nuxt project.

Change a value in the application when it belongs to that application alone. Change it in a layer
when both applications should follow. [Technical details](https://nuxtstart.com/docs/getting-started/technical-details)
covers the ownership rule in full.

## Colors

Nuxt UI reads its semantic colors from an application's `app/app.config.ts`. Neither application
ships one, so create the file in whichever application you want to change:

```ts [apps/site/app/app.config.ts]
export default defineAppConfig({
  ui: {
    colors: {
      primary: 'sky',
      secondary: 'indigo',
      neutral: 'slate',
    },
  },
})
```

`packages/layer-base/app/app.config.ts` already sets shared UI defaults, and the file you just
created merges over them — write only the keys you want to differ. The
[Nuxt UI design system](https://ui.nuxt.com/docs/getting-started/theme/design-system)
lists every color and token you can set.

`primary` alone changes nothing yet. `packages/layer-base/app/assets/css/theme.css` pins
`--ui-primary` to `black` on `:root` and `white` on `.dark`, and those win over `app.config.ts`.
Delete those two lines, or set them to `var(--ui-color-primary-500)` and
`var(--ui-color-primary-400)`, and your `primary` palette takes effect.

### The brand color is separate

Two things render outside the browser and can't read Nuxt UI's theme: the fallback social image and
the buttons in transactional email. Both read one constant:

```ts [packages/layer-base/shared/utils/constants.ts]
export const BRAND_COLOR = '#00DC82'
```

Change it alongside your Nuxt UI colors, or your emails and social images drift away from your
interface.

## Name

Your product name lives in `.env.project.schema` at the root of the repository, because it names the
product and not the deployment — and because both applications read the same one:

```env [.env.project.schema]
PROJECT_DISPLAY_NAME=Acme
```

It reaches page titles, transactional email, and social images, arriving in each application as
`NUXT_PUBLIC_APP_NAME`.

The same file holds your product's one-sentence description, which becomes the website's meta
description and the summary at the top of its `llms.txt`:

```env [.env.project.schema]
PROJECT_DESCRIPTION="A CRM for small agencies, with pipelines, invoicing and client portals."
```

[Project identity](https://nuxtstart.com/docs/reference/project-identity) covers the rest of that file, what happens while
a value in it is empty, and every name derived from it.

## URLs and indexing

Each of these describes a deployment rather than the product, so they live in the value files rather
than the schema:

<table>
<thead>
  <tr>
    <th>
      Key
    </th>
    
    <th>
      Set in
    </th>
    
    <th>
      Required
    </th>
    
    <th>
      What it does
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        NUXT_PUBLIC_APP_BASE_URL
      </code>
    </td>
    
    <td>
      Both applications
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      The origin that application is served from
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        NUXT_PUBLIC_APP_WEBSITE_BASE_URL
      </code>
    </td>
    
    <td>
      <code>
        apps/web
      </code>
      
       only
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      Points the product at the public website
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        NUXT_PUBLIC_SITE_INDEXABLE
      </code>
    </td>
    
    <td>
      Both applications
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      Whether search engines may index it
    </td>
  </tr>
</tbody>
</table>

[Environment values](https://nuxtstart.com/docs/reference/environment-values) explains which file each one belongs in.
Each deployed context's origins are written at the stage that adds it:
[Deploying development](https://nuxtstart.com/docs/getting-started/deploying-development) for `development`,
[Adding pull request previews](https://nuxtstart.com/docs/getting-started/adding-pull-request-previews) for `preview`,
[Adding staging](https://nuxtstart.com/docs/getting-started/adding-staging) for `staging`, and
[Going to production](https://nuxtstart.com/docs/getting-started/going-to-production) for production.

## Logo

Each application serves its own logo from its `public/` directory:

```text
apps/site/public/logo.png
apps/web/public/logo.png
```

Replacing those two files is the whole change. `packages/layer-base` defaults `app.logo` to
`/logo.png`, and the shared `AppLogo` component renders it.

To use a different file per color mode, set `app.logo` to an object instead, in that application's
`app/app.config.ts` — creating the file if you have not already:

```ts [apps/web/app/app.config.ts]
export default defineAppConfig({
  app: {
    logo: {
      light: '/logo-light.svg',
      dark: '/logo-dark.svg',
    },
  },
})
```

`AppLogo` accepts either shape — a string renders one image, an object renders a color-mode pair —
so nothing else has to change. Put the files in that application's `public/` directory.

<tip>

Deploying both applications? The website can host the shared assets, and `apps/web` can point
`app.logo` at an absolute URL on it instead of keeping a second copy.

</tip>

## Favicon and page head

Replace `apps/site/public/favicon.ico` and `apps/web/public/favicon.ico`. Nuxt serves them without
any configuration, so there's nothing to declare unless you want a different filename or format.

The `app.head` block in an application's config is where the rest of the static head lives:

```ts [apps/site/nuxt.config.ts]
export default defineNuxtConfig({
  app: {
    head: {
      title: ENV.NUXT_PUBLIC_APP_NAME,
      htmlAttrs: {
        lang: 'en',
      },
    },
  },
})
```

Nuxt's [SEO and meta guide](https://nuxt.com/docs/4.x/getting-started/seo-meta) covers the full API.

## Fonts and design tokens

Each application's `app/assets/css/main.css` imports `packages/layer-base/app/assets/css/theme.css`
after Nuxt UI, so its Tailwind v4 theme tokens win. It already sets `--font-sans` and `--font-mono`;
change them there:

```css [packages/layer-base/app/assets/css/theme.css]
@theme {
  --font-sans: 'Inter', sans-serif;
  --font-mono: 'JetBrains Mono', monospace;
}
```

The token defines the utility. Loading the font is a separate step — the browser needs the file
before the utility means anything. Tailwind's [theme documentation](https://tailwindcss.com/docs/theme)
covers the other token groups.

## Website settings

Values that belong to the public website, rather than to either application, live in the site
layer's app config. The social links are there today:

```ts [packages/layer-site/app/app.config.ts]
export default defineAppConfig({
  socials: {
    x: 'https://x.com/your-handle',
  },
})
```

The blog and docs layers each register their own content section from their own `nuxt.config.ts`,
under `appConfig.contentSections`. A new content section of your own follows that pattern in its own
layer.

## Next steps

- [Creating a page](https://nuxtstart.com/docs/getting-started/creating-a-page) — add a page to either application
- [Technical details](https://nuxtstart.com/docs/getting-started/technical-details) — what each package owns
- [Environment values](https://nuxtstart.com/docs/reference/environment-values) — which file each value belongs in

## Sitemap

See the full [sitemap](https://nuxtstart.com/sitemap.md) for all pages.
