Web Parts allow for greater flexibility in designing pages by enabling editors to modify content, appearance and behavior directly in a browser. They are similar to Dynamic Content but can also contain Dynamic Content. The presentation is separated from the Web Part markup to allow for uneven zone widths. Properties and names can be translated. Static Web Parts are useful for template functionality.

1. Web Parts in EPiServer [email_address]

3. Dictionary Web Part Controls for creating Web sites that enable end users(editors) to modify the content, appearance, and behavior of Web pages directly in a browser. Zone Container for Web Parts. Dynamic Web Part A Web Part dynamically added by editor. Not to be mistaken with EPiServers dynamic properties nor DynamicContent. Static Web Part A static WebPart or UserControl inside a zone. Much like a UserControl inside a Page. Shared Scope The most commonly used scope in EPiServer context. Editors edit Web Parts which are visible to all users, thus shared. User Scope Fully supported, but rarely used. Provides user personalization capabilities much like igoogle and bbc.co.uk . Web Part Provider Data layer between Web Application and WebPart repository. Flexigrid Free EPiCode module allowing editors to create dynamic Web Part Zones.

4. Demo – Web Part concepts

16. Web Parts Dynamic Content Exposes on EPiServer property types X X Preview view X - Soft links (warning on deleting referenced content) X Drag & drop support X - Indexed values (searchable content) X Multilanguage support X X Follow page on copy & paste, export & import X X Editable from View mode (dope) X Can host corresponding Web Part / Dynamic Content X Support IsRequired properties X Resides in WebPartZone PropertyXhtmlString