New here?

Our tutorials will get you up to speed with Hippo development.

Follow the Hippo Trail

Architecture

The relations between repository, CMS and delivery tier.

How it all fits together

Developer Info

Source code, forge, license, roadmap and system requirements.

Quick links

Careers

Interested? We're always on the lookout for new talent.

Have a look

What is Hippo CMS?

Hippo CMS is a little bit different from other CMS systems. We built it so you can easily integrate it into your existing architecture.

Open Platform

We are big believers in open source. We use and contribute to many open source components - and our entire core is available under the Apache License

Java Stack

What you'd expect from a Java environment: easy to integrate, testable, ready for continuous integration, and sticking to familiar Java standards such as JCR 2.0 and JAX-RS

Scalability

Highly scalable platform which supports both  clustering and  replication

Performance

Performance matters to us! Hippo CMS  scales both  horizontally and vertically and makes use of  multi-layered caching to squeeze the most out of your implementation

Integrations

Query content using REST, or import content from somewhere else into Hippo. Hook up an external application into the rendering phase via Spring. Build a Mobile app or an AngularJS app that consumes content from Hippo. Use external data systems to feed our personalisation engine

Security

Protect your content with fine grained authorizations,  LDAP support and secure  replication

The CMS Features You'd Expect

Content editing, workflow, history, version control, image library, user management, out of the box

Flexible Content Model

Fully customizable document oriented content model with built-in modelling tools. Strict separation of content from presentation. Reuse content across Websites, Mobile Websites and apps

Deployments

Deploy on-premise or in the cloud on your preferred servlet container

Extensible Components

Use or extend existing components from the Hippo Feature Library or build your own. Use JSP, Freemarker or AngularJS to render your components

Give Control To End Users

End users can manage page configurations, menus, URL structures and component mappings. Without you having to go into code

Personalisation

Deliver personalized pages to visitors with the Relevance module

Your HTML

We don't mess with your HTML output. Use whatever web framework you like; Bootstrap, AngularJS, it's up to you

Search

Out of the box querying, facetting and full text search capabilities based on Apache Lucene - or hook up Elasticsearch if you need more power

 

Can I try it out?

Yes! Download our demo. Or look under the hood if you like, we share our source code.

Gallery Media Banner

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s

Latest Blogs

Kickstart your projects with the Hippo feature library
September 25, 2014

With this feature library, you can add commonly used functionality to your project

Hippo CMS Integration Patterns
October 15, 2014

At this year's Hippo GetTogether, Senior Architect Jeroen Reijn presented examples of integration patterns used by Hippo clients in their existing application landscape.

Missing news document from Essentials
by: Karun | 31-01-15 00:25:05 (CET)

Hello, I have recently begun developing with Hippo CMS. Ive installed hippo cms and added the news feature with essentials. Currently I am using cargo to run it. I then go to the news folder and right click on it, and I see a option to create a new news folder but no option to create a news documen

Re: [hippo-community] Auto Export Docs into separate XML files
by: Olivier Bourgeois | 30-01-15 23:59:05 (CET)

Hi Jimmy,    the configuration of the auto-export is not per document type but is using paths instead: check the "Multiple content modules" section that explains how you can break down your auto-export files: http://www.onehippo.org/library/development/automatic-export-add-on.html Regards,Olivier.

Auto Export Docs into separate XML files
by: jimmy...@gmail.com | 30-01-15 23:24:01 (CET)

Is there a way to tell Hippo CMS to create separate XML files for each document type when exporting content via auto-export?  I imported the content in one massive XML file, but I would like it broken down by document type. Thanks.

Re: [hippo-community] CMS Xinha editor's table works improperly in Firefox
by: n.out | 30-01-15 18:29:27 (CET)

Hi Anton, 7.8.9 has been out since October 2nd [1], both 7.8.8 and 7.8.9 contain a few fixed related to Xinha. Please let us know if it's possible to reproduce this after updating to 7.8.9. Regards, Niels Out - Service Desk Team Lead [1] http://www.onehippo.org/7_8/library/about/release-notes/rel

Re: [hippo-community] Setting User Permissions FOR the CMS and Console
by: Dev Intern | 30-01-15 17:32:41 (CET)

So I'm playing around with different types of facet rules that could perhaps limit a user's access to only some pages. If I understand correctly you can make a facet rule of type REFERENCE which can test the UUID of a node and make a rule based on it. I'm thinking this may work if I say this rule

Re: [hippo-community] Change language of calendar widget?
by: Rick Beemsterboer | 30-01-15 15:53:28 (CET)

Screenshot added. Rick 2015-01-30 15:45 GMT+01:00 Bert Leunis <b.le...@onehippo.com>: Thanks for the follow up Rick. I added the affected version for you in the issue. Maybe add a nice screenshot that proves/supports your point? With kind regards/Met vriendelijke groet, Bert Leunis Amsterdam - O

Looking for assistance? You're welcome to ask for help. We have a very active mailing list! Please do check the tutorials and the guidelines first, though.