Skip to content
NuxtBase logo NuxtBase Docs

Branding

The safest branding changes start in shared config, not in scattered page components.

Primary Brand Source

Section titled “Primary Brand Source”

For the shipped template, the main shared brand default source is:

shared/config/site.ts

This file controls shared values such as:

  • appName
  • logoPath
  • siteUrl
  • legal entity name and address
  • contact and support email
  • repository URL
  • SEO title and description defaults
  • default Resend sender
  • two-factor issuer

If you only change brand text in one page and ignore site.ts, the product will drift.

Runtime Override You Should Not Miss

Section titled “Runtime Override You Should Not Miss”

siteConfig.appName is not the only brand name source at runtime.

The environment layer can override it through:

Terminal window
NUXT_PUBLIC_APP_NAME=Your App Name

In the current template, NUXT_PUBLIC_APP_NAME falls back to siteConfig.appName only when the env value is missing or empty.

That matters because many auth and email flows read the resolved env value, not siteConfig.appName directly.

What Depends On siteConfig

Section titled “What Depends On siteConfig”

The following surfaces already read from shared site config:

  • app header and footer branding
  • dashboard sidebar brand block
  • docs layout brand block
  • SEO defaults on the homepage
  • email sender fallback behavior

What Depends On The Resolved Env App Name

Section titled “What Depends On The Resolved Env App Name”

Many runtime auth and email messages use the resolved app name from env-backed configuration, including flows such as:

  • reset password
  • verify email
  • magic links
  • verification codes
  • other transactional email builders that pass appName

So if you want brand naming to stay consistent, update both:

  • shared/config/site.ts
  • NUXT_PUBLIC_APP_NAME in your real environment

Visual Brand Entry Points

Section titled “Visual Brand Entry Points”

The minimum brand assets to revisit are:

  • shared/config/site.ts
  • your logo file path, usually under public/
  • app/app.config.ts for global UI color choices

In the current template, app.config.ts still sets the UI primary color to green. If you are rebranding, that is one of the first places to normalize.

Section titled “Legal And Contact Details”

Do not forget the operational values:

  • legalEntityName
  • legalAddress
  • contactEmail
  • supportEmail

These values tend to surface later in legal pages, emails, and support flows.