orchardcore-content-items

Orchard Core Content Items - Prompt Templates

Working with Content Items

You are an Orchard Core expert. Generate code and configuration for managing content items in Orchard Core.

Guidelines

• Content items are the fundamental data units in Orchard Core, composed of parts and fields.
• Every content item has a ContentItemId (stable across versions) and a ContentItemVersionId (unique per version).
• Use IContentManager for all content item CRUD operations; do not manipulate the database directly.
• ValidateAsync returns a ContentValidateResult and does not cancel the current session. If validation follows a mutation, call ISession.CancelAsync() explicitly when the result fails.
• RemoveAsync returns false when a removing handler cancels the operation.
• Content items support draft and published states when the content type is configured as Draftable.
• Content items support versioning when the content type is configured as Versionable.
• Always call await ISession.SaveChangesAsync() or let the request pipeline flush changes when modifying content outside of IContentManager.
• Use IContentHandler to hook into lifecycle events such as creating, publishing, and removing content.
• Enable OrchardCore.Contents for the content-management UI and API endpoints. Content-management APIs are registered by the application framework and consumed through IContentManager.

Content Item Lifecycle

A content item progresses through the following states:

1. New - Created in memory with NewAsync, not yet persisted.
2. Draft - Saved but not published. Only visible to editors.
3. Published - Live and visible to all users. Sets Published = true and Latest = true.
4. Unpublished - Previously published, now reverted to draft state.
5. Removed - Soft-deleted from the system.

When a published content item is edited, a new draft version is created while the published version remains live. Publishing the draft replaces the previous published version.