London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
Navigation [hide]
[expand]
- Architecture
- Business Foundation
- Exporting and importing meta models
- Extending meta models
- Filtering and sorting
- Generating typed business foundation classes
- SQL Meta Model
- Working with entity objects
- Working with SQL Records
- Business Meta Model
- Caching
- Catalogs
- Product associations
- Catalog data sources
- Catalog database partitioning
- Event-driven catalog indexing
- Catalog object model and database diagram
- Catalog product search
- Defining package items
- Displaying products
- Guidelines for working with catalogs
- Importing catalog data
- Configuration
- Content
- Bundles and packages
- Categorizations
- Catalog content provider
- Product variants
- Related entries
- Using a CMS-style rendering template
- Working with the Catalog as IContent
- Assets and media
- Customers
- Deployment
- Globalization
- Initialization
- Logging
- Marketing
- Creating a volume discount promotion
- Custom promotion development
- Promotions
- Using calculate discount activity
- Markets
- Meta Data Plus
- Notifications
- Orders
- EPiServer.Commerce.Sample guideline
- Changing order number sequence
- Checkout process
- Extending order classes
- Order addresses
- Order management classes
- Order notifications
- Order object model and database diagram
- Recurring orders
- Searching for orders
- Shopping cart
- Taxes
- Payments
- Pricing
- Reports
- Routing
- Scheduled Jobs
- Search
- Configuring facets and filters
- Configuring EPiServer Find search provider
- Configuring Solr search provider
- Confirming SQL Server Full-text index
- Creating a search provider
- Customizing search
- Security
- Shipping
- Warehouses and inventories
- Workflows
Content
This document provides an introduction to working with content in EPiServer and EPiServer Commerce in particular. Commerce uses the same content type model as EPiServer CMS, providing a flexible way to implement your own content types based on existing type model classes in EPiServer.
Content in EPiServer can be pages, blocks, media files and folders in CMS. It can also be catalog content in EPiServer Commerce. The content type defines a set of properties that an item, for instance a page, consists of.
Refer to the Content section in the EPiServer CMS SDK for more information about the EPiServer content model, and pages blocks and media. In this part of the Commerce SDK we will describe how the EPiServer content model is applied in EPiServer Commerce, for instance to work with catalog content.
See also
- Catalog content provider section of the EPiServer Commerce SDK.
- Assets and media section of the EPiServer Commerce SDK.
- Content section in the EPiServer CMS SDK.
Last updated: Mar 31, 2014
