10.0.1 release notes

HIPPO CMS 10.0.1 FCS release notes

May 12, 2015

 

Hello everyone,

We are excited to announce the FCS release of Hippo CMS 10 (starting with version 10.0.1). In this release announcement you find more information about the new functionality and improvements in this major release.

If you have any questions, don’t hesitate to contact us at info@onehippo.com.

On behalf of everyone that made this release a reality,

 

Mark Peerdeman
Product manager

 

Highlights

Hippo CMS 10 is a major new release. Many new features and improvements will be available, ramping the system up in the direction towards a full digital experience platform for the enterprise that matches our future vision.

  • For the business and marketing user we offer the new experiments feature, integrating A/B and multivariate testing directly in the CMS. New is also the ‘Trends’ page, providing insights in the performance of content. The new ‘switch template’ functionality enables the marketing or business user to quickly rotate between alternative rendering methods for components, giving them a radical different look or even functionality.

  • For developers we have increased the agility by offering the option to synchronize content between the repository and disk. Together with the switch template functionality, you can deploy new templates, CSS and Javascript files without having to rebuild.

  • For system administrators we offer a new synchronization mechanism (sometimes referred to as ‘Blue/Green deployment’), minimising the downtime required when executing upgrades.

  • We have restyled the full user interface, resulting in a great new look and even more fun to use CMS.

In this new release of Hippo, we introduce a new versioning scheme. As a result of this, the Hippo release will be referred to as ‘Hippo CMS 10’.

 

Features

UI/UX track

Refreshed user interface

Hippo CMS 10 has a completely new visual style. We refreshed the complete user interface of the CMS. The interface is very clear and a joy to work with. Besides a new look, we have introduced some small smart changes in the user interaction as well, improving the efficiency of your interaction with the system and making it much more fun to use:

  • a much more efficient placement and control of the document tabs and,

  • an improved page and menu management user interface,

  • drag-and-drop and multi file capabilities for uploading files,

  • multi-layered icons that can display multiple states.

Agility track

Switch template

Inside Hippo, ‘rendering templates’ take care of how a component eventually ‘looks’ on a web page. A rendering template contains Freemarker code that determines what and how content is rendered to HTML. For the Hippo user, changing these looks used to be not one of the easiest tasks to perform. Selecting a different template involved manual handling of code and a rebuild of the CMS, resulting in redeploy as well. With the new ‘Switch template’ functionality, available in the community and enterprise editions, choosing an alternative rendering template for your component is much more convenient. Documentation for switch template can be found here.

Web Files

Furthermore, these Freemarker templates do not have to reside on the file system anymore, but Hippo can store these inside the repository. This means that you can dynamically add and remove templates, even in a system that is running, without the need of having to rebuild. This does not apply to Freemarker files only, but to all web resource files you use in your project. This web files feature is available in both community and enterprise versions. Web files is currently available as a developer tool, but we will extend this with remote deployment capabilities in upcoming releases.

Furthermore, for the developer, we provide an automatic synchronization mechanism between the files on local disk and in the repository. When you as a developer change a file, it will be automatically updated and synchronized with the repository. This means you can keep using your own favorite IDE to write your code, Hippo takes care of syncing your edits automatically.

Documentation about web files can be found here.

Setup and feature library

  • Hippo Setup and Feature library now has the ‘selections plugin’ moved to the tools section of the feature and setup library as an integrated, built-in tool instead of as a feature plugin.

  • Hippo Setup and Feature library now provides more control of where features end up in the repository, improving the usability for existing projects besides the current support for new projects.

  • Hippo Setup and Feature library now contains a Google Maps component. After installing this plugin, a drag and drop Google Maps component is added to component library in the CMS editor.

  • Hippo Setup and Feature library makes full use of web files.

  • Most Hippo Setup and Feature library CMS components are shipped with several alternative rendering  templates.

  • Our getting started trail is fully utilising the Setup and Feature library.

Data track

Experiments

Hippo Experiments, part of the Enterprise Edition, will find out which of the available component alternatives are performing best on the site. With Hippo Experiments, the marketer can perform two types of experiments:

  • Content experiment: Hippo tests and reports which of the alternative configurations of a component converts better. This experiment can be used to test two variants, but includes a more sophisticated multi variance test, up to 25 variants per component, as well. This type of experiment is very powerful, besides content, you can use it to test all kinds of aspects of your component, including even the presentation in the channel by combining it with Switch Template to test completely different rendering templates for the component to be analysed.

Examples of use:

  1. do a content test and discover which content performs best.
  2. do a rendering / experience test (use e.g. “switch template”) and discover the best way to display your content in this channel.
  3. Do a multivariate test and see which of a set of four banners performs best.
     
  • Audience experiment: Hippo tests and reports whether an alternative configuration converts better for a specified targeting audience or for the general visitor. This powerful type of experiment is currently unique for Hippo and combines the Hippo Relevance engine with the new Experiments capability.

Example use cases:

  • do an audience test and discover if your content works better for new or for recurring visitors, or converts better for people in the USA compared to Europe.

  • find out if a certain rendering template works better for a specified audience. Do developers like a dark layout better than other visitors?

You can find more information about Hippo Experiments here.

Trends

Trends, part of the Enterprise Edition, provides a tabular overview of the peak performing content categories or other metadata fields connected to your content for your selected data set. ‘Peak Performing’ means that data that is outperforming (very well or very bad) for the selected dataset compared to all visitors is displayed in a table. Trends can integrate with your marketing automation system, using the lists in this system as filter for reporting.

The Trends feature augments the current ‘real time visitor analysis’ capabilities of the CMS. Trends uses the same characteristics and data, but presents these in an aggregated and very flexible way, providing interactive viewing angles on the data you collect. It is an excellent tool to gain insights on personas and segments to create and apply personalisation to.

You can read more about Trends here.

Enterprise Features

Two-factor authentication option

Optionally for enterprise users, a two-factor authentication option for the CMS is available. This security feature provides an extra step in the login process, relying on a second verification mechanism like an authenticator mobile app or SMS on a mobile phone. Documentation can be found here.

Repository synchronization add-on

Maximizing the availability of your cluster while doing an upgrade is very important for many of our customers that utilize Hippo as a mission critical tool. With new extended functionality to the Hippo replication and synchronization capabilities in the enterprise edition you have powerful tooling to upgrade or update your entire cluster while minimizing the downtime. This deployment method is sometimes referred to as ‘Blue/Green’ deployment. Documentation can be found here.

Upgrade Verifier

The upgrade verifier is a powerful utility tool (separate web application) to support projects and developers during the upgrade between major Hippo Enterprise editions. It is available for Hippo Enterprise customers and partners and will be available together with the GA release of Hippo 10.

The tool provides several reports of possible configuration conflicts between the current project and the targeted next major Hippo Enterprise edition, and, where feasible, also provides upgrade instructions and relevant online documentation links.

LDAP support

LDAP support has been moved into the enterprise version.

User interface improvement programme

At Hippo we want our users to have an excellent user experience. It is therefore important for us to know how they interact with the system. As of version 10, we’re starting to collect usage statistics in the CMS. This allows us to better understand how the system is being used - and what we should work on. We’ll be using Lean methodologies to improve our user interface as we want to make absolutely sure that we’re going into the right direction. The data collected contains metrics on which perspectives have been opened, which buttons have been clicked, etc. No content or configuration of the customer will be transmitted to our data centers. We will not use this info for any other purposes than improving our products and services. However, if for some reason you don’t want to participate in our user interface improvement programme, you can disable the usage statistics functionality as explained in the documentation.

New version numbering scheme and end-of-life policy

From this release of Hippo, a new versioning scheme will be introduced. Together with this new versioning scheme, we will adapt our end-of-life policy as well so it reflects this change as well. The new versioning scheme applies to both the community edition of Hippo CMS, as well as the  Enterprise edition.

Version numbers

In the Semantic Versioning scheme, software releases have the format of three numbers, separated by dots, with an optional label added, e.g.:

10.0.2 GA

In general, this takes the form of

MAJOR.MINOR.PATCH <label>

  • The MAJOR version number is issued to introduce new functionality or changes in the system and/or architecture that could break backwards compatibility with previous versions or might introduce incompatible API changes.

  • In a MINOR version, we introduce new functionality in a less invasive way; backwards compatibility with the major version is not affected.

  • A PATCH version is mainly intended for small changes or bug fixes only. This is done in a backwards compatible way with the major version.

  • An additional <label> can be used to add meta data like labels for pre-release or release, i.e. ‘FCS’ or ‘GA’.

End-of-life policy

Together with the new version numbering, we will introduce a new and transparent end-of-life policy, as depicted in the image below. It means that the life of the final minor version is extended with two GA periods and the major GA version with one GA period. All other releases will be marked EOL when a succeeding release becomes available.

 

//onehippo-prod.global.ssl.fastly.net/binaries/ninecolumn/content/gallery/versions-and-eol-periods.png

 

Please note that micro versions (patches) have no influences on the product lifetime. As long as a version is not EOL, patches will be distributed for this version.

 

Feature overview table - Community vs. Enterprise Editions

Feature

Community availability

Enterprise availability

Restyled UI

yes

yes

Drag-and-drop multi-file upload

yes

yes

Improved page and menu management UI

yes

yes

Experiments

 

yes

Trends

 

yes

Two-factor authentication for the CMS

 

yes

Repository synchronization and replication

 

yes

Upgrade verifier

 

yes

LDAP support

 

yes

Switch template

yes

yes

Web files

yes

yes

Improved ‘selections’ tool in the Setup and Feature library

yes

yes

Improved configuration options in the Setup and Feature library

yes

yes

Google maps component in the Setup and Feature library

yes

yes

Switch template support and variants of many features in the Setup and Feature library

yes

yes

 

Known issues

  • The restyling of the document type editor will be improved for the 10.0 GA release.

  • A Firefox bug can cause a rendering issue within Essentials within CMS 10.0 if the browser session has previously visited Essentials in CMS 7.9 or earlier. To resolve this issue either clear the cache on the browsing session or install the Firefbug Firefox plugin and disable caching while the tool is open using the NET tab.

Availability

The Hippo CMS 10.0.1 Community Edition is available from today onwards. The Enterprise edition will be rolled out in two phases:

  • May 2015: First Customer Shipment (FCS) - Selected customers and partners can start a new project or upgrade an existing project to the 10.0 release under close involvement of Hippo B.V.. For these selected projects, the FCS release is supported for use in production environments. Projects in which Hippo is not closely involved are kindly asked to wait until the GA release or request Hippo assistance.

  • August 2015: General Availability (GA) including Migration Pack for previous installations - All aspects of the Hippo Enterprise Edition are generally available for implementation by Hippo Customers and Hippo Certified Partners. Customers upgrading from previous releases are advised to wait for this GA release in order to benefit from the Migration Pack.