Hippo is now Bloomreach


#1

hippo_bloomreach

In case you missed it

In October 2016 BloomReach acquired Hippo - and we’ve been busy combining BloomReach’s leading machine learning and big data technologies with Hippo’s agile, open-source CMS to bring you BloomReach Experience - the first truly open and intelligent digital experience platform. This powerful combination is poised to drive best-in-class digital experiences across all industries, organisations, and digital devices.

What this means

The developer community will, of course, remain a core part of the business. The Hippo Community Edition, formerly known as “Hippo CMS” is now available as “ Bloomreach Experience Manager - Developer Edition ” and will be developed under its current Apache software license. The software will continue to be open source and Bloomreach remains committed to contributing to open source projects, particularly to the Apache Software Foundation.

Onehippo.org is now documentation.bloomreach.com

Bloomreach will also continue to maintain the former website onehippo.org which is now available at documentation.bloomreach.com .

What does this mean for you as a Hippo customer, partner, or developer? When it comes to day-to-day interactions, integrations, and agreements, not much changes. In the bigger picture, the Hippo brand will fold under the BloomReach brand.

You’ll continue to work with your favorite Hippo people - now equipped with new BloomReach business cards and an updated website.

If you have any questions about the transition from onehippo.org to documentation.bloomreach.com, please don’t hesitate and shoot me an email at niklas.winkels@bloomreach.com.


pinned #2

#3

Tied to these changes in our XM documentation, I’d like to inform you that we are taking offline the documentation of the out-of-maintenance versions 7.6 through 7.9. All but 7.9 have already been hidden behind a login. We keep the version 10 documentation live, but since brXM v10 is no longer maintained, so is its documentation.

If you have a compelling need to access the old documentation, please get in contact with our support department.

regards

Tobi