Glossary

A design approach where all functionality is exposed via APIs from the start, enabling any front-end or integration to consume content independently of the back-end.

The process of verifying a user's identity in Ibexa DXP, supported via username/password, API tokens, OAuth 2.0, SAML 2.0, and LDAP through the Symfony Security component.

Ibexa DXP uses tag-based HTTP caching via Varnish or Symfony's built-in HTTP cache. Published changes trigger precise invalidation of only the affected cached responses.

A Content Delivery Network caches assets and responses on globally distributed edge nodes, reducing latency for end users regardless of their geographic location.

A blueprint that defines the structure of a content item — its fields, their types, and validation rules. Similar to a class in object-oriented programming.

Digital Experience Platform. An integrated suite of tools for creating, managing, and delivering personalised digital experiences across all channels and touchpoints.

The data type of a single field within a Content Type — for example Text, Image, RichText, Date, or Relation. Ibexa ships with many built-in types and supports custom ones.

A query language for APIs that lets clients request exactly the data they need. Ibexa DXP ships a fully auto-generated GraphQL schema reflecting your content model.

A content management system where the editorial back-end is decoupled from the presentation layer. Content is delivered via APIs and rendered by any front-end framework.

A node in the Ibexa content tree that points to a content item. One content item can have multiple locations (multi-homing), each with its own URL alias.

The ability to run multiple independent websites from a single Ibexa DXP installation, each with its own domain, design, languages, and content tree root.

The visual drag-and-drop editor in Ibexa DXP used to compose landing pages by placing and configuring blocks inside layout zones.

The Ibexa Personalization engine analyses user behaviour to deliver individualised content recommendations and segment-based targeting across all channels.

A Field Type that stores structured XML content (DocBook-based) and renders it via configurable Twig templates. Powers the Online Editor in the back-office.

A named configuration context in Ibexa DXP that maps a domain or URL prefix to a specific language, design theme, and content tree root. The primary multisite mechanism.

The PHP framework on which Ibexa DXP is built. Provides the dependency injection container, routing, security layer, Twig templating, and the full Symfony ecosystem of bundles.

A human-readable URL mapped to a content location. Ibexa generates URL aliases automatically from the content name and keeps historical aliases for SEO continuity.

A configurable approval process that moves content through defined stages (e.g. Draft → Review → Published) with role-based permissions at each step.