---
url: 'https://dxpr.com/markdownify/taxonomy/term/15'
title: 'Match your brand | DXPR'
author:
  name: Anonymous
updated: '2026-10-23T14:31:17+00:00'
copyright: 'Copyright DXPR. All rights reserved.'
type: website
summary: "Make DXPR Builder pages look like the rest of your site, and give editors your brand's styles in place of generic ones. Most of this work happens once, in the theme or the module settings, and then every editor benefits. Use the table to find the page for what you want to do. I want to ... Use Needs offer brand text styles in the text editor's Styles list Text editor the Administer DXPR Builder configuration permission choose which text editor buttons a role sees Text editor a builder profile for that role style builder content with the site's own CSS Custom CSS access to the theme's files use brand fonts on builder pages Custom fonts access to the theme's files, or DXPR Theme add an icon set to the icon picker, or see which sets ship Icon libraries a custom module or theme for a new set list your own classes under HTML classes Utility classes access to the theme's .info.yml run the editor from a local build instead of the DXPR CDN Editor assets a local build of the editor change the module's own Twig templates Override DXPR Builder templates access to the admin theme's files Which should I use Start with the theme. Fonts, colours and the CSS behind your classes belong there, because one change updates every page. Custom CSS and Custom fonts show how. Then give editors names for that CSS. A class in the HTML classes list styles a whole element, such as a card or a section. A custom style in the text editor's Styles list styles a paragraph or a few words. Both point at the same theme CSS, so pick by what the editor selects. The last three rows are for developers. Most sites never need them. For a single element on a single page, use its settings dialog instead; see Style your elements. What's next? Visual design and branding: plan colours, spacing and layout across pages. Text editor: the most common first step, brand styles for editors."
tags:
  - 'Manage the site'
image: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
published: true
og:
  site_name: DXPR
  'image:alt': 'DXPR, powered by Drupal: AI-powered Drupal for marketers.'
---
## [Match your brand

 ](/hc/documentation/learn-dxpr-builder/customization)

Make DXPR Builder pages look like the rest of your site, and give editors your brand's styles in place of generic ones. Most of this work happens once, in the theme or the module settings, and then every editor benefits. Use the table to find the page for what you want to do.

| I want to ... | Use | Needs |
|---|---|---|
| offer brand text styles in the text editor's **Styles** list | [Text editor](/hc/documentation/learn-dxpr-builder/customization/text-editor) | the **Administer DXPR Builder configuration** permission |
| choose which text editor buttons a role sees | [Text editor](/hc/documentation/learn-dxpr-builder/customization/text-editor#toolbar-buttons-per-role) | a builder profile for that role |
| style builder content with the site's own CSS | [Custom CSS](/hc/documentation/learn-dxpr-builder/customization/custom-css) | access to the theme's files |
| use brand fonts on builder pages | [Custom fonts](/hc/documentation/learn-dxpr-builder/customization/custom-fonts) | access to the theme's files, or DXPR Theme |
| add an icon set to the icon picker, or see which sets ship | [Icon libraries](/hc/documentation/learn-dxpr-builder/customization/icon-libraries) | a custom module or theme for a new set |
| list your own classes under **HTML classes** | [Utility classes](/hc/documentation/learn-dxpr-builder/customization/utility-classes) | access to the theme's `.info.yml` |
| run the editor from a local build instead of the DXPR CDN | [Editor assets](/hc/documentation/learn-dxpr-builder/customization/editor-assets) | a local build of the editor |
| change the module's own Twig templates | [Override DXPR Builder templates](/hc/documentation/learn-dxpr-builder/customization/custom-templates) | access to the admin theme's files |

## Which should I use

Start with the theme. Fonts, colours and the CSS behind your classes belong there, because one change updates every page. [Custom CSS](/hc/documentation/learn-dxpr-builder/customization/custom-css) and [Custom fonts](/hc/documentation/learn-dxpr-builder/customization/custom-fonts) show how.

Then give editors names for that CSS. A class in the **HTML classes** list styles a whole element, such as a card or a section. A custom style in the text editor's **Styles** list styles a paragraph or a few words. Both point at the same theme CSS, so pick by what the editor selects.

The last three rows are for developers. Most sites never need them.

For a single element on a single page, use its settings dialog instead; see [Style your elements](/hc/documentation/learn-dxpr-builder/element-settings).

## What's next?

- [Visual design and branding](/hc/documentation/learn-dxpr-builder/design/overview): plan colours, spacing and layout across pages.
- [Text editor](/hc/documentation/learn-dxpr-builder/customization/text-editor): the most common first step, brand styles for editors.