Examples

Example Description

Below is a live Advanced Page Content rendering. The datasource populates the MainContentTop and MainContentBottom fields with alert banners, and the BodyBottom field with an HTML comment (inspect the page source near </body> to see it). Because the rendering injects content into page-level sections rather than inline, the alerts appear at the top and bottom of the <main> element — not within this Examples grid.

The HintMainContentTop and HintMainContentBottom fields are set to unique strings (apc-example-top, apc-example-bottom) to prevent duplicate injection if the same datasource were referenced by multiple renderings on a page.

Usage Notes

• The rendering iterates all model properties except those prefixed with Hint. Each property’s value is rendered via Html.Section(name, hint, content), injecting the HTML into the corresponding named section of the layout.
• The companion Hint* fields (e.g., HintMainContentTop) supply a deduplication key. If two renderings on the same page write the same section with the same hint, the content is output only once. Leave the hint empty to always render (unique GUID is generated).
• The Drop field is always rendered inline at the rendering’s placeholder position (via <sc-text asp-for="Drop">). Use it for content that should appear exactly where the rendering is placed — typically a visual placeholder in Experience Editor.
• The AdditionalSections field is a Name Value List (stored as URL-encoded key=value&key2=value2). Each entry is decoded and output as its own section, allowing ad-hoc section injection without template changes.
• This rendering does not have its own rendering parameters template. When placed in a placeholder, it inherits standard Column parameters (Small, Medium, Large, Offsets, Padding, AddClass) from the placeholder’s allowed renderings configuration.
• Common use cases include: page-specific <script> or <link> tags in HeadTop/HeadMeta, structured data (ld+json) in HeadMeta, analytics or consent tags in BodyBottom, off-canvas drawer markup in OffCanvasLeft/OffCanvasRight, and hero or breadcrumb wrappers in MainContentTop.
• If Model.IsEditing is true (Experience Editor), the section-injection logic is skipped entirely and only the Drop field and <edit-label> are rendered, ensuring safe editing without injecting partial markup into the page head.