orchardcore-content-items

To manage Orchard Core content items, use IContentManager to handle CRUD operations including creating, retrieving, updating, and publishing. It serves as the primary API for executing content item lifecycle workflows accurately.

YesSql querying in Orchard Core indexes content items to enable fast retrieval. You write queries against these indexes to filter and retrieve content without loading entire content trees into memory.

You need ContentHandlers in Orchard Core when responding to content item lifecycle events. They allow you to execute custom logic during specific phases like creating, publishing, or removing content items.

Yes, you can use recipes for content import and export in Orchard Core. Recipes facilitate content item lifecycle workflows by defining structured data packages that automate deployment and migration.

The best way to access Orchard Core content parts and fields is by using strongly-typed helpers. This approach simplifies retrieving data from content items and ensures compile-time safety when interacting with content structures.

Yes, Orchard Core content item versioning requires IContentManager. It handles the underlying logic for creating, publishing, and managing different versions of content items throughout their lifecycle.