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

Multi-lingual, Multi-site, Multi-channel

Out of the box support for multi-language, multi-site and multi-channel implementations. Cross-domain, cross-site, cross-language and cross-channel linking between documents are resolved automatically.

Separate Content from Presentation

Break free from page oriented development. Redesign your website without modifying content and reuse your content across websites, mobile  apps, etc. Use Hippo's  fully customizable document oriented model and built-in modelling tools to separate content from presentation.

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! 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

Did you see this?

Meet Hippo CMS 10 for Developers
May 27, 2015

Last week, we announced the release of Hippo CMS 10. Now we want to take the time to truly introduce this new release.

Simplify Upgrades with Hippo's Synchronization Add-on
June 15, 2015

Use the Synchronization Add-on you to smoothen the process of continuous delivery.

Re: [hippo-community] Template composer issues
by: t.jeger | 29-06-15 20:51:40 (CEST)

I'd have to try it out, but hope somebody else can jump in... On Mon, Jun 29, 2015 at 5:16 PM, Mathijs den Burger <m.den...@onehippo.com> wrote: > The styling of the page is scoped to the iframe in which the channel is > rendered, while the dialog is part of the DOM outside the iframe. So that

Re: hst.link hippbean
by: m.acharya | 29-06-15 17:53:49 (CEST)

You will get HST links as configured in the sitemap for for a specific item. for example: you can configure something like this for a sitemap 'brands' brands _any_ as opposed to brands _any_.html Hope this helps On Monday, June 29, 2015 at 11:46:04 AM UTC-4, ashilp...@gmail.com wrote: >

hst.link hippbean
by: ashilp...@gmail.com | 29-06-15 17:46:04 (CEST)

Hi Is it possible the remove the '.html' that appears at the end of the url by default when using <@hst.link hippobean=xxx /> ? e.g. *<@hst.link hippobean=brand />* is outputting /site/collect/brands/ *brandname.html* when we want this to be /site/collect/brands/ *brandname*Thanks Ashil

Fwd: Hiring Pega Developer (Pega CSSA) at Virignia Beach, VA
by: Chandra Lakkii | 29-06-15 17:33:43 (CEST)

Hi Folks, This is Chandra from Lakki, LLC. trying to reach you regarding a job opening with us. If you would be interested in the below job description let us know your interest in the same with your consultant resume. Please help me out below position. *Role: Pega Developer (Pega CSSA)* *Locat

Re: [hippo-community] Template composer issues
by: m.denburger | 29-06-15 17:16:29 (CEST)

The styling of the page is scoped to the iframe in which the channel is rendered, while the dialog is part of the DOM outside the iframe. So that cannot be it. @Tobias: can it be the combination of a document picker field with a dropdown field right after it? Mathijs On Mon, Jun 29, 2015 at

Re: [hippo-community] Re: Documentation conflicts regarding to production deployment
by: n.vankampenhout | 29-06-15 16:47:39 (CEST)

Hi Dávid, Thanks for your feedback, we appreciate it very much! We have a long wish list of documentation improvements but our priority has so far been with tutorials and training material aimed at web developers. It is clear from feedback we receive (from you and from others) that our deploy

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.