Platform, Implementation Project, and Production Instance
When working with Hippo CMS, it's essential to understand the difference between the platform, an implementation project, and a production instance. They represent different aspects of the Hippo CMS ecosystem and they differ from each other in two important ways:
- What each provides in terms of application code, application configuration, and application data.
- Who is responsible for the development, maintenance, and support of each.
The Hippo CMS platform provides the CMS and Repository applications and the HST delivery tier framework.
The platform includes standard plugins which provide additional functionality.
A Hippo CMS implementation project is a software project built on top of the platform.
An implementation project provides:
- A content model, including document types, defined in the CMS and Repository application configuration.
- One or more custom-built channels (for example, a website) delivering content, based on the HST delivery tier framework, including core page templates and components.
- Custom integrations and/or extensions.
A Hippo CMS implementation project is developed, maintained and supported by a BloomReach customer or partner.
A Hippo CMS production instance is an implementation project deployed in a production server environment.
A production instance provides:
- Content such as documents, images, and assets.
- User accounts, groups, security domains, and permissions.
- Channel configuration including page template configurations and component configurations.
- Visitor data collected by the Relevance Module.
A Hippo CMS production instance is managed by end users (such as authors, editors, and administrators).
Support for a production instance depends on agreements between BloomReach, partner and/or customer, and on whether the instance runs on-premise or on BloomReach Cloud.