New here?

Our Getting Started tutorial 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.

Developer Info

Careers

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

Have a look

What is Hippo CMS?

Hippo CMS is an open source Java CMS. 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 configuration s, 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! Try the online demo of  Hippo Enterprise Edition or create your own  project with Hippo Community Edition.

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

How to: Integrate Hippo CMS with an ElasticSearch enterprise search engine
January 28, 2015

Our most recent Hippo Lab focuses on integrating an open source Web Content Management System with an ElasticSearch enterprise search engine.

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

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

Re: Make fields read only for certain groups
by: Rick Beemsterboer | 30-03-15 07:54:21 (CEST)

Anyone? If this is still the way to go, that's an acceptable answer too ;-) Rick Op donderdag 26 maart 2015 09:25:59 UTC+1 schreef Rick Beemsterboer: > > Hi Hippo's, > > What is the suggested way of making cms fields read only (greyed out) for > certain user groups? At a previous project we solve

Setting specific rights on editing a channel.
by: Nils Zonneveld | 27-03-15 16:16:24 (CET)

Is there a way I can create a group or a role that allows an editor to only edit the menus in a channel, without any right to change Channel Settings and/or Components?

Re: [hippo-community] Working with maven-release plugin
by: leo.geof...@gmail.com | 27-03-15 15:45:16 (CET)

Thanks for the answer! I didn't know about the preparationGoals , i'll try to add the dist profile in there and see how it goes! I ll keep you up to date with that. cheers, Leo G. Le vendredi 27 mars 2015 12:01:08 UTC+1, j.reijn a écrit : > > I'm not sure if this is possible in a nice way. You ca

Re: Persist session when using sendRedirect
by: gigi...@gmail.com | 27-03-15 12:33:55 (CET)

Hi, We managed to get it working but I still have an issue: On the first request we have the following Response header: *Set-Cookie:JSESSIONID=8A5573F2D05770930DBAE4A9F19CD4D3; Path=/; HttpOnly* On the second request it's there in "Request headers" : *JSESSIONID=8A5573F2D05770930DBAE4A9F19CD4D3*

Re: Persist session when using sendRedirect
by: gigi...@gmail.com | 27-03-15 12:05:50 (CET)

Hi, Simple solution but somehow a hell to implement in nginx. Do you know of a solution implemented that works? So far we only got nginx to set the cookie path to double slash : "//" 1. Set-Cookie: JSESSIONID=401C20196A1F6023CAA89B272C459FD3; Path=//; HttpOnly Regards, Alex

Re: [hippo-community] Working with maven-release plugin
by: j.reijn | 27-03-15 12:01:08 (CET)

I'm not sure if this is possible in a nice way. You can do it by doing the normal release perform and checking out the tag of the project and then peform the -Pdist. With the release plugin you can configure also preparationGoals (by default clean install in the Hippo project pom) after which th

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.