---
url: 'https://dxpr.com/hc/documentation/learn-dxpr-builder/integrations/content-types'
title: 'Content types | DXPR'
author:
  name: docs-sync
  url: 'https://dxpr.com/users/docs-sync'
date: '2026-10-23T14:31:17+00:00'
copyright: 'Copyright DXPR. All rights reserved.'
type: article
summary: 'Adding DXPR Builder to any content type'
tags:
  - 'Connect Drupal features'
image: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
published: true
og:
  site_name: DXPR
  updated_time: '2026-10-23T14:31:17+0000'
  'image:alt': 'DXPR, powered by Drupal: AI-powered Drupal for marketers.'
schema:
  '@context': 'https://schema.org'
  '@graph':
    -
      mainEntity: {  }
    -
      '@type': TechArticle
      headline: 'Content types'
      description: 'Adding DXPR Builder to any content type'
      image:
        '@type': ImageObject
        url: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
        width: '1200'
        height: '630'
      datePublished: '2026-10-23T14:31:17+0000'
      dateModified: '2026-10-23T14:31:17+0000'
      author:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
        url: 'https://dxpr.com/'
        logo:
          '@type': ImageObject
          url: 'https://dxpr.com/themes/custom/dxpr_com/dxpr-logo-dark.svg'
          width: '1348'
          height: '501'
      publisher:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
        url: 'https://dxpr.com/'
        logo:
          '@type': ImageObject
          url: 'https://dxpr.com/themes/custom/dxpr_com/dxpr-logo-dark.svg'
          width: '1348'
          height: '501'
      mainEntityOfPage: 'https://dxpr.com/hc/documentation/learn-dxpr-builder/integrations/content-types'
      articleSection: 'Connect Drupal features'
    -
      '@type': WebPage
      '@id': 'https://dxpr.com/hc/documentation/learn-dxpr-builder/integrations/content-types'
      description: 'Adding DXPR Builder to any content type'
      breadcrumb:
        '@type': BreadcrumbList
        itemListElement:
          -
            '@type': ListItem
            position: 1
            name: Home
            item: 'https://dxpr.com/'
      publisher:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
      inLanguage: en
---
[Help Center](/hc)/[Documentation](/hc/documentation) /[Learn DXPR Builder](/hc/documentation/learn-dxpr-builder) /[Manage the site](/hc/documentation/learn-dxpr-builder/manage) /[Connect Drupal features](/hc/documentation/learn-dxpr-builder/integrations) # Content types.

Adding DXPR Builder to any content type

 Learn DXPR BuilderManage the siteConnect Drupal features

   ## In this guide

 Related guides

- [Your first page](/hc/documentation/learn-dxpr-builder/getting-started/first-page)

DXPR Builder works on any content type, block type or other entity type with a text field. This page helps you choose the field and the profile. The step-by-step switch is on [Installing on existing content types](/hc/documentation/learn-dxpr-builder/getting-started/installing-on-existing-content-types).

## Which fields work

DXPR Builder is a format you choose for a field on the **Manage display** page. It is offered for these field types:

| Field type | Shown under **Formatted text** as |
|---|---|
| `text_with_summary` | **Long text with summary**, such as the default **Body** |
| `text_long` | **Long text** |
| `text` | **Short text** |

Editors see the builder on the page itself, not on the edit form. They need the **Edit with DXPR Builder** permission and the right to edit that content item.

## Which field to use

Most sites switch the **Body** field. Add a separate **Long text** field when you also want a plain body, such as a product summary. A content type can have more than one DXPR Builder field. Each becomes its own editable area on the page.

| Content type | Field | Why |
|---|---|---|
| Landing page | **Body** | the whole page is built with DXPR Builder |
| Blog post | **Body** | other fields, such as tags, stay as they are |
| Event | a separate field | date and location stay in their own fields |
| Product | a separate field | the plain description stays reusable elsewhere |

## The Editing Profile setting

The settings of the DXPR Builder format have one option, **Editing Profile**. Keep **Default (Role-based Profile)** to let each editor's role pick the profile. Choose a profile to apply it to everyone who edits this field, whatever their role. Profiles are set up under [User profiles](/hc/documentation/learn-dxpr-builder/admin/user-profiles-admin).

## If you don't see the builder

- **The content shows without a toolbar.** You lack the **Edit with DXPR Builder** permission or the right to edit this item. Grant both under **People** > **Permissions**(`/admin/people/permissions`).
- **DXPR Builder is not in the Format list.** The field is not a formatted text field, for example a plain text field. Use a **Long text** field from the **Formatted text** group instead.
- **The builder does not load on an old revision.**DXPR Builder stays off on revision pages. Open the current version of the content to edit it.

## What's next?

[Build your first page on your enabled content type](/hc/documentation/learn-dxpr-builder/getting-started/first-page) to continue exploring DXPR Builder.