Orchard Core Content Types - Prompt Templates

Create a Content Type

You are an Orchard Core expert. Generate code and configuration for creating a content type.

Guidelines

• Content type technical names must be PascalCase with no spaces.
• Always include a TitlePart unless the content type uses a custom title strategy.
• Add AutoroutePart for routable content types with a URL pattern.
• Use CommonPart conventions (owner, created/modified dates) where appropriate.
• Attach ListPart if the content type should act as a container.
• Use content part and field settings to configure editors and display modes.
• Use the asynchronous IContentDefinitionManager APIs such as AlterTypeDefinitionAsync and AlterPartDefinitionAsync.
• Define fields on a content part, then attach that part to a content type. Fields cannot be attached directly to a type definition.
• To inject a part into types programmatically at build time, or to make a type, part, or field system-defined (undeletable through the UI or recipes), use IContentDefinitionHandler — see the orchardcore-content-definition-handlers skill.

Migration Pattern

public sealed class Migrations : DataMigration
{
    private readonly IContentDefinitionManager _contentDefinitionManager;

    public Migrations(IContentDefinitionManager contentDefinitionManager)
    {
        _contentDefinitionManager = contentDefinitionManager;
    }

    public async Task<int> CreateAsync()
    {
        await _contentDefinitionManager.AlterTypeDefinitionAsync("{{ContentTypeName}}", type => type
            .DisplayedAs("{{DisplayName}}")
            .Creatable()
            .Listable()
            .Draftable()
            .Versionable()
            .WithPart("TitlePart", part => part
                .WithPosition("0")
            )
            .WithPart("AutoroutePart", part => part
                .WithPosition("1")
                .WithSettings(new AutoroutePartSettings
                {
                    AllowCustomPath = true,
                    Pattern = "{{ ContentItem | display_text | slugify }}"
                })
            )
        );

        return 1;
    }
}

Content Definition Service

IContentDefinitionService is in the OrchardCore.ContentTypes namespace and is provided by OrchardCore.ContentTypes.Abstractions. It contains reusable content definition operations and accepts AlterFieldContext and AlterTypePartContext for targeted settings changes. It does not expose public loading helpers. Use IContentDefinitionManager when a definition must be loaded or listed.

await contentDefinitionService.AlterFieldAsync(new AlterFieldContext
{
    PartName = "ArticlePart",
    FieldName = "Summary",
    DisplayName = "Summary",
    Editor = "Wysiwyg",
    DisplayMode = "Detail"
});

await contentDefinitionService.AlterTypePartAsync(new AlterTypePartContext
{
    TypeName = "Article",
    PartDefinition = await contentDefinitionManager.GetPartDefinitionAsync("ArticlePart"),
    PartName = "ArticlePart",
    DisplayName = "Article details",
    Description = "Article-specific settings",
    Editor = "Default",
    DisplayMode = "Detail"
});

Content Field Configuration

When adding fields to a content part:

await _contentDefinitionManager.AlterPartDefinitionAsync("{{PartName}}", part => part
    .WithField("{{FieldName}}", field => field
        .OfType("{{FieldType}}")
        .WithDisplayName("{{FieldDisplayName}}")
        .WithPosition("{{Position}}")
    )
);

Common field types include:

• TextField - simple text input
• HtmlField - rich HTML editor
• NumericField - numeric values
• BooleanField - true/false
• DateField / DateTimeField - date pickers
• ContentPickerField - reference to other content items
• MediaField - media library attachment
• LinkField - URL with optional text
• TaxonomyField - taxonomy term selection