Documentation
Installation Using the Xperience interface Developing websites Configuring Xperience Managing users Securing websites Deploying websites Managing website content Multilingual websites Macro expressions External utilities Integrating 3rd party systems Custom development E-commerce features On-line marketing features Release notes - Xperience 13 Xperience terminology glossary
Tutorial
Using the Xperience interface Developer tutorial Business tutorial Resource hub for marketers
API Examples
Configuration Content management Development E-commerce On-line marketing Social media

Developing web parts

CoreMVC 5

Web parts are components that provide a combination of content and functionality. They are the basic building blocks of Portal Engine page templates used for the Xperience administration interface. You can use web parts to create the content of page templates in the Administration interface application, using the Page templates -> Edit -> Design interface.The term "web part" covers items on three levels:

Code files

On a technical level, web parts are user controls⁠ (opens in a new tab) (.ascx files) that inherit from an appropriate base class.

System objects

Web parts must be registered as objects in the system. The purpose of the objects is to:

Specify the path to the user control source file
Define the web part's properties and store other configuration options

Template components

Web parts placed onto templates are called web part instances. You can create any number of instances of a single web part.

Instances must be inserted into web part zones, which are defined within the layouts of page templates.

Xperience contains a number of web parts by default. You can develop your own web parts or modify existing ones.