Store and Display Content Using the Kibo eCommerce CMS and the Kibo eCommerce Database
Kibo eCommerce provides a CMS and a database (collectively referred to as custom schema) that you can access using the Kibo eCommerce API. Within these systems, you can store content or data that can then be leveraged by an application or exposed on the storefront using a theme. The following steps guide you through the process of learning about custom schema, and provide links to help topics with more details for each step.
Learn the Difference Between Documents and Entities
In general, documents are used for content management, and entities are used for data management. Documents correspond to the Kibo eCommerce CMS, and entities correspond to the Kibo eCommerce Database (MZDB).
Display Documents or Entities in Admin Using Views
If you are familiar with Admin, you've likely seen grid views throughout the modules (for example, a list of orders, or a list of customer accounts). You can use the Kibo eCommerce API to create these views for your documents and entities.
Display Document Content on Your Storefront
Documents are best suited for displaying content on your storefront. Through a combination of an application and a theme, you can expose the content you store in your documents on your storefront in order to create dynamic promotions, blogs, press releases, and other media.
Leverage Entity Data in Custom Applications
You can use the data stored in entities to augment custom logic or to provide useful information to applications that you develop in Kibo eCommerce.
Leverage the API Reference
As you can tell, you lean heavily on the Kibo eCommerce API to interact with custom schema. The relevant resources for documents can be found under the Content section of the API, and the relevant resources for entities can be found in the platform/entitylists resource. Kibo eCommerce also recommends you use one of the Kibo eCommerce SDKs to make your development easier.