About

Bloomreach Content system requirements apply to on-premise deployments of Bloomreach Content and the Developer Edition.

Public hosting of Javadocs at javadoc.onehippo.org is deprecated in October 2025 and is discontinued instead of migrated to new infrastructure.

Bloomreach Content uses Semantic Versioning for all product releases in the format MAJOR.MINOR.PATCH, such as 14.1.2.

Bloomreach maintains a list of security vulnerabilities that were initially flagged and then classified as false positives for Bloomreach Content.

The Security Vulnerability Dashboard provides a centralized view of security vulnerabilities across Bloomreach CMS versions.

Bloomreach Content uses a three-tier architecture with a web tier, application tier, and database tier.

Bloomreach Content supports scaling for changing traffic demands through horizontal and vertical approaches.

Bloomreach Content is designed for high performance and integrates performance testing into product development using real-world data and scenarios.

Bloomreach Content provides configurable access control, multiple authentication methods, and integration with standard enterprise security solutions.

Bloomreach Content uses an extensible architecture with extension points across the delivery framework and Open UI.

Bloomreach Content supports high-availability web architectures and reduces the need for redeployment.

Supported product versions are eligible for helpdesk assistance under the terms of the Bloomreach service level agreement (SLA).

Content and configuration updates move through DTAP environments using different flows for code, content, and configuration.

Application release management and content management operate independently, but content creation depends on available application functionality.

A Bloomreach Content release follows three phases: preparation, execution, and finalization.

Reliable test content is required for testing Bloomreach Content releases in test environments.

Release management uses defined terms for environments, application components, and change activities in Bloomreach Content.

The Bloomreach Content Upgrade Tool is a command-line utility that automates the project-source phase of a Bloomreach Content upgrade.

Minor upgrades in Bloomreach Content move a project from one minor version to the next, such as 13.0 to 13.1.

Namespace migration in Bloomreach Content is required for backward-incompatible changes to node type definitions.

Java code formatting uses four spaces for indentation, UTF-8 encoding for all files, and a maximum line length of 120 characters.

Bloomreach Content publishes snapshot artifacts nightly to a Maven snapshot repository.

Code formatting uses shared style files for IDEs.

JSP files use two-space indentation, UTF-8 encoding, JSTL for separating logic from markup, and HST tags for Bloomreach-specific functionality.

XML files use two-space indentation, UTF-8 encoding, and a maximum line length of 120 characters.

Bloomreach Content publishes open source releases under the Apache Software License 2.0.

Bloomreach Content accepts external code contributions through Jira issues and applies them only after Engineering review.

A backport applies a bugfix, improvement, or new feature from the current version of Bloomreach Content to a maintenance branch of an older version.

Bloomreach Content developer accounts provide access to the Enterprise Maven Repository and documentation restricted to licensees.

Bloomreach customers report product issues through the Bloomreach Support Portal.

Bloomreach security issues are reported by emailing xm-security@bloomreach.com.

Bloomreach Content source code is licensed under the Apache License 2.0.

Documentation work for documentation.bloomreach.com uses five resources: CMS, Writing Documentation, Styling and Layout, Diagrams, and Naming Conventions.

Apache License Version 2.0, January 2004, grants a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license and patent license to reproduce, modify, distribute, and otherwise use the Work under specified conditions.