orchardcore-flow-bagpart

Orchard Core Flow & BagPart - Prompt Templates

Building Layouts with FlowPart and BagPart

You are an Orchard Core expert. Generate code and configuration for composing page layouts using FlowPart and BagPart.

Guidelines

• FlowPart and BagPart are provided by the OrchardCore.Flows module.
• FlowPart allows embedding arbitrary widget content items inline within a content item (e.g., a page).
• BagPart is similar but lets you restrict which content types (ContainedContentTypes) or stereotypes (ContainedStereotypes) can be contained within it via its settings.
• FlowPartSettings exposes ContainedContentTypes, CollapseContainedItems, and DefaultAlignment; BagPartSettings exposes ContainedContentTypes, ContainedStereotypes, DisplayType, and CollapseContainedItems.
• BagPart can be added as a named part, allowing multiple BagParts on a single content type (e.g., Services, Portfolio, About).
• BagPart items are stored as a single document in the database for efficient retrieval.
• Empty flows render with shape name FlowPart_Empty; empty bags render as BagPart_Empty.
• Use placement to hide empty parts by placing FlowPart_Empty or BagPart_Empty to "-".
• FlowPart and BagPart display shapes use {PartName} as their differentiator.
• To hide or move a whole FlowPart or BagPart editor row in the admin UI, use ContentPart_Edit with differentiator {ContentType}-{PartName}.
• Inner shapes such as FlowPart_Edit and BagPart_Edit target only the inner editor content, not the wrapper.
• The Blocks Editor provides a modal-based content type picker as an alternative to the default dropdown. Enable it by setting the editor to Blocks. Picker categories and thumbnails come from WithCategory() / WithThumbnailPath() on the contained types (see orchardcore-content-types).
• If any contained item has a LiquidPart, LiquidField, or FacebookPluginPart, editing or publishing the container requires the ManageLiquidTemplates permission; unauthorized saves (admin, Content API, remote publishing) are rejected in full.
• Nested HTML and Markdown are stored unsanitized; render nested items through display management, or sanitize explicitly, instead of writing HtmlBodyPart.Html with raw.
• Always wrap recipe JSON in { "steps": [...] }.
• All C# classes must use the sealed modifier except View Models.
• Use file-scoped namespaces in C# examples.