Xcellerator.Components 1.0.132

id: xcellerator-docs title: Xcellerator product documentation summary: Canonical documentation for using, integrating, extending, and maintaining Xcellerator. audiences:

• editor
• administrator
• nuget-consumer
• maintainer status: stable source_paths:
• Xcellerator.Core/
• Xcellerator.Admin/
• Xcellerator.Components/ last_verified: 2026-09-28

Xcellerator product documentation

This is the canonical documentation for Xcellerator as represented by the current repository working tree. It explains what the product provides, how editors and administrators use it, how a Kentico application consumes it, and how maintainers extend it safely.

Xcellerator is a reusable Kentico Xperience product delivered through three NuGet packages:

• Xcellerator.Core contains the generated content model and small cross-cutting utilities.
• Xcellerator.Admin contains the Xcellerator administration module, Channel Configuration application, and shared admin form controls.
• Xcellerator.Components contains the Page Builder components, rendering services, configuration catalogs, public assets, and deployment payload.

Xcellerator.Web is a local development harness. It demonstrates integration patterns, but it is not a production application or a fourth product package.

Start by role

• Content editors: choose and configure widgets, sections, templates, content, and release windows.
• Administrators: configure channels, brands, assets, styles, catalogs, and integrations.
• NuGet consumers: install and configure the packages in a Kentico web application.
• Product maintainers: change product code, metadata, assets, generated models, and documentation.

Product map

• Product philosophy and boundaries
• Architecture and runtime flow
• Page Builder
  • Widgets
  • Sections
  • Page templates
• Content model
• Administration and configuration
• Layouts and site chrome
• Services and modules
• Extension points
• Development and operations
• Reference

Current product surface

The source currently registers:

• 10 widgets
• 7 sections
• 2 page templates
• 3 page content types
• 15 reusable content types
• 7 reusable field-schema interfaces

XContentFilter is included because it exists in the working tree. Its documentation is marked in-flight; do not treat that surface as release-stable until its implementation and design records are reconciled.

How to use these documents

Each page starts with machine-readable metadata:

• id: stable document identifier.
• summary: one-sentence retrieval summary.
• audiences: intended readers.
• packages: relevant packages when applicable.
• status: stable, in-flight, deprecated, or reference.
• source_paths: implementation sources used to verify the page.
• last_verified: date the page was checked against source.

Follow Documentation conventions when changing behavior or documentation. Use the manifest for machine discovery and the glossary for product terminology.

Source-of-truth boundaries

• Kentico Admin is authoritative for Kentico classes, fields, alternative forms, and module metadata.
• kxp-codegen output is authoritative for generated C# only after regeneration from the Admin model.
• Xcellerator.Components/PageBuilderAssets is authoritative for packaged Page Builder assets and JSON defaults.
• Channel Configuration data in Kentico is authoritative for channel-level database overrides.
• Client applications own their layouts, branding, site CSS, endpoints, and business-specific integrations.
• This directory is authoritative for Xcellerator product documentation.

Generated Kentico reference documentation, code-review records, technical-debt records, WIP notes, and historical session notes remain outside this directory and are not canonical product behavior.