AI agents: the content index is at /llms.txt. Every page is also available as Markdown — send the request header Accept: text/markdown, or append .md to the page URL.
Xperience Docs

Cookie consent

We use necessary cookies (opens in a new tab) to run our website and improve your experience while browsing. Additional cookies are only used with your consent. You may revoke your consent on the Cookies Policy (opens in a new tab) page or in your browser at any time.

Configure (opens in a new tab)
  • Documentation
    InstallationUsing the Xperience interfaceDeveloping websitesConfiguring XperienceManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresRelease notes - Xperience 13Xperience terminology glossary
  • Tutorial
    Using the Xperience interfaceDeveloper tutorialBusiness tutorialResource hub for marketers
  • API Examples
    ConfigurationContent managementDevelopmentE-commerceOn-line marketingSocial media
  • Community Questions & Answers (opens in a new tab)
  • Contact support (opens in a new tab)
  1. Home
  2. Custom development
  3. Extending the administration interface
  4. Developing web parts
  5. Customizing web parts

Customizing web parts


Was this page helpful?

Send us feedback Go back to top

Related pages

  • Creating new web parts
  • Creating inherited web parts
  • Using custom web part layouts

There are two basic ways to change or extend the functionality of existing web parts:

  • Customize the web part code – edit the markup or code behind of the user control that implements the web part.
  • Use macro expressions in web part properties – by inserting macro expressions into the values of web part properties, you can implement many types of custom functionality without modifying the web part code.

Important: We do not recommend customizing the code of the default web parts directly. Instead, create a clone of the required web part and implement the changes there. Using clones ensures that the system does not overwrite your code when applying hotfixes or upgrades to newer versions of Xperience.

Alternatively, you can create Inherited web parts – copies of existing web parts that share the code files, but allow you to modify the definitions of properties and their default values.