> For the complete documentation index, see [llms.txt](https://docs.frase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frase.io/troubleshooting-and-faqs/theme-your-blog-automatically.md).

# Theme Your Blog Automatically

### What Brand Hub DNA does

When you host your blog on [Frase CMS](https://docs.frase.io/integrations/cms-publishing/frase-cms), you want it to look like the rest of your site, not a generic template. Brand Hub DNA handles that for you.

Frase analyzes your website's visual style, including your colors, fonts, and layout, and builds a matching theme for your Frase-hosted blog. You get a snapshot preview of how it will look, a one-click way to apply it, and live controls to fine-tune anything you want to change.

{% hint style="success" %}
**Your blog is themed from your brand automatically.** Frase reads the visuals captured in [**Brand Hub**](https://docs.frase.io/feature-reference/brand-hub) and applies them to your Frase-hosted blog. In **Settings**, click **Preview** to see how your page will look, then switch to **edit mode** and select any card to fine-tune the styling—margins and padding, corner radius, borders, shadow, and card colors.&#x20;
{% endhint %}

### How to Preview Your Brand Style

1. Open *Brand Hub* and go to **Profile**.
2. Pick the site you want to review.
3. Click **Assets** to open the style gallery.

The gallery shows how Frase has read your brand: your colors, typography, messaging, images, and more. This is the look Frase will use as the starting point for your blog and can be edited at any time.

### How to Apply Your Brand Look

1. On the left sidebar, open the *Frase CMS* section.
2. Click **Settings**.
3. Open the *Style*, *Layout*, and *Connections* tabs to review your blog's appearance.
4. Click **Use brand defaults** or **Re-sync from brand** to apply the theme Frase built from your site.
5. Click **Save**.

<figure><img src="/files/91Z0WXyiZR12iX3uootT" alt=""><figcaption></figcaption></figure>

Your live blog reflects the change within seconds. There's no rebuild and no waiting, so you can adjust and check your blog in real time.

{% hint style="success" %}
Apply the brand defaults first, then fine-tune from there. It's faster than building a theme from scratch, and you can override any color, font, or layout choice you don't like.&#x20;
{% endhint %}

### Refreshing Your Brand Analysis

If you update your website's design, you can have Frase re-analyze it to pick up the new look. Re-analysis is limited to a few runs per hour per user to keep things responsive, so if you hit the limit, wait a bit and try again.

{% hint style="info" %}
If your blog doesn't reflect a change right away, give it a few seconds and refresh. Theme edits apply almost immediately, but your browser may be holding an older cached version of the page.&#x20;
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.frase.io/troubleshooting-and-faqs/theme-your-blog-automatically.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
