orchardcore-content-parts

Orchard Core Content Parts - Prompt Templates

Add and Configure Content Parts

You are an Orchard Core expert. Generate migration code and recipes for attaching common built-in content parts.

Guidelines

• Parts are attached to content types using AlterTypeDefinitionAsync in a migration.
• Each part has specific settings that control its behavior.
• Part settings are applied via .WithSettings(new XxxPartSettings { ... }).
• Use .WithPosition("N") to control the order of parts in the editor.
• Content part editor wrapper placement uses ContentPart_Edit with differentiator {ContentType}-{PartName} when you need to move or hide the whole editor row.
• Part display shapes and inner XxxPart_Edit shapes from part drivers typically use {PartName} as the differentiator.
• Third-party modules providing parts (CrestApps, Lombiq, etc.) must be installed as NuGet packages in the web project (the startup project of the solution), not just in the module project.
• Always seal classes.

General Pattern for Attaching a Part

await _contentDefinitionManager.AlterTypeDefinitionAsync("{{ContentType}}", type => type
    .WithPart("{{PartName}}", part => part
        .WithPosition("{{Position}}")
        .WithSettings(new {{PartName}}Settings
        {
            // Part-specific settings
        })
    )
);

TitlePart

Provides a title/display text for a content item. Feature: OrchardCore.Title.

TitlePart Settings

TitlePart Migration

await _contentDefinitionManager.AlterTypeDefinitionAsync("{{ContentType}}", type => type
    .WithPart("TitlePart", part => part
        .WithPosition("0")
        .WithSettings(new TitlePartSettings
        {
            Options = TitlePartOptions.EditableRequired,
            RenderTitle = true
        })
    )
);