# First Steps

As a first step, it is important to understand the big picture of the brand ecosystem and select the “umbrella brand”—this will act as the base of the white-label design system.

<figure><img src="/files/RG9AHBHi8c93hVgkGsPf" alt=""><figcaption></figcaption></figure>

Then define what needs to change between brands. For instance:

* Color
* Typography
* Illustrations
* Icons
* Interactions

The choice of the token naming system is not limited to a single approach and depends on the collaboration between design and development.

<figure><img src="/files/XbvgY8G2NasE0u7SuRmg" alt=""><figcaption></figcaption></figure>

And a few things to keep in mind as you begin:

1. Think semantically trying to define universal design decisions
2. More flexibility means more complexity
3. There is not a bullet proof system
4. Meaning, you'll probably have to come back to redefine your framework


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dsplaybook.farcostudio.com/part-2-the-process/documentation-2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.