Skip to content

Who uses DXPR Builder

DXPR Builder serves three audiences. Content marketers publish pages without code. Site administrators manage permissions and settings. Developers extend the editor and connect it to Drupal. The first section shows what each audience does in the product; the second shows the kinds of organisation that use it.

The three audiences

Content marketers

Marketers work in the editor on the page itself. They:

  • drag elements from the element picker into sections, rows and columns, and edit text inline (see Editor basics)
  • start pages from page templates or their own saved user templates (see Templates)
  • generate sections, rewrite copy and create images with the AI assistant (see AI features)
  • place Drupal blocks, Views and forms inside layouts without leaving the page

Site administrators and webmasters

Administrators configure the module under DXPR Studio at /admin/dxpr_studio/dxpr_builder. They:

  • enter the product key and choose where it is stored (General Settings)
  • switch AI features on or off and set output filtering (AI)
  • create user profiles that decide which elements, blocks, views, templates and editor buttons each role sees (see User profiles)
  • manage page templates and global user templates
  • assign the Edit with DXPR Builder permission and watch the User Licenses and Content Items pages (see Licensing)
  • review outbound connections and data residency (see Firewall and data residency)

Developers

Developers work with the module's code and APIs. They:

  • add the DXPR Builder field formatter to their own content types and block types
  • expose utility classes with hook_dxpr_builder_classes_alter(), and register icon sets with *.dxpr_icon_sets.yml files (see Hooks API)
  • script content with the drush dxb:* commands (see Drush commands)
  • call the AJAX and AI routes from custom integrations (see API endpoints)
  • theme the output, which is Bootstrap 5 HTML stored in the entity field

Organisations that use DXPR Builder

Digital agencies

Agencies hand page creation to their clients while keeping Drupal's content workflow and permissions. User profiles limit what each client role can change.

Government

Government teams let non-technical staff publish pages while meeting accessibility and security requirements. The module runs on the organisation's own Drupal server and stores pages in its database. Outbound connections are limited to licence checks, editor assets, editor analytics and AI requests, and the EU model option keeps AI processing with a European provider. What works when outbound access is blocked is set out on Firewall and data residency.

Higher education

University web teams let departments publish their own pages within brand-controlled templates. User profiles restrict which elements, templates and text editor buttons each role can use.

Enterprise

Enterprise teams scale content operations across business units. User profiles, page and user templates, and Drupal's content workflow support large distributed teams.

What's next?

Something wrong or missing on this page? Report it or edit the page.