---
title: Overview
description: Configure your brand identity and connect shared brand data to your guidelines.
---

Your `brandtree.config.ts` is the source of truth for reusable brand data.
Start with the complete config in the example site, replace its values, and
keep required sections intact. The [configuration reference](/configuration)
lists the supported fields.

## Configure your identity

**[Brand identity](/brand-identity)**

Set the brand name, description, and guidelines metadata.

**[Colors](/colors)**

Define palette families, shades, and approved swatches.

**[Themes](/themes)**

Map your palette to light and dark interface roles.

**[Typography](/typography)**

Define font roles, weights, and the type scale.

**[Fonts](/fonts)**

Register local or hosted fonts and connect their CSS variables.

**[Logos](/logos)**

Configure artwork, colorways, clearspace, and minimum sizes.

**[Brand assets](/brand-assets)**

Reference shared resources and register downloadable packages.

**[Contact and social profiles](/contact)**

Provide the contacts and accounts readers need.

## Connect the config to your pages

A config describes the brand; an MDX page explains its use. Add a component to
show that shared data within your explanation:

```mdx
## Approved colors

Use the primary palette for our most recognizable applications.

<ColorPalette category="primary" />
```

The runtime supplies the resolved brand, interface strings, and direction for
the active locale to built-in MDX components automatically. Pass an explicit
prop to override a value for one component. See [Components](/components) for
examples, previews, and prop definitions.

**Some tasks cross config sections**

Fonts are registered at `config.fonts` and referenced by `brand.typography`.
Brand translations live at `brand.localeOverrides` and require root `i18n`
settings. [Localization](/localization) walks through both together.
[Social cards and SEO](/social-cards) explains how generated cards inherit brand
values and where to override them.

> **Keep editorial guidance in your pages**
>
> Voice, values, photography direction, iconography, and layout principles are
> written in MDX with the relevant components. They do not have dedicated fields
> in the current brand schema. Start with [Pages and MDX](/authoring).