Note: Dynamic content is deprecated. Use blocks instead. While existing solutions will continue to work, you should not build new solutions on this API. It will be phased out in the future.
The dynamic content function in Episerver lets developers create functionality in code which an editor can use in the HTML editor.
A Dynamic Content class does not define a whole page rather just a small section of it, making it suitable for smaller functionality which will be inserted inline into texts on the site by the editor. A user control (such as a .NET UserControl) implements the user interface part of a dynamic content object.
Dynamic Content has the following advantages:
The Dynamic Content concept was introduced in Episerver CMS before blocks became available. Blocks and dynamic content are somewhat overlapping concepts and we generally recommend blocks where possible. Since Episerver CMS 7.5, it is possible to drag and drop a block into a rich text area which makes it possible to use the block as a "dynamic content" in the text. The main limitation with blocks in rich text is that this is always treated as a block level element. Dynamic content can be treated as either an inline or block element.
Dynamic Content has functionality to auto-generate an editor for the settings for dynamic content. This still uses the editing system that was used in Episerver CMS 6; this system has some limitations that you should be aware of if you want to use the automatic editing functionality:
These limitations are only valid when you are using the auto-generated user interface. You can always create your own editorial user interface for your dynamic content to overcome most of these limitations.
When you develop dynamic content, consider the following:
Last updated: Dec 09, 2016