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 elsewhere 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 modeling 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.

Help, I'm Lost!  This seems a bit technical. Take me to the business site.

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?

Synchronization Add-on
June 15, 2015

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

Hippo CMS Videos
November 28, 2016

Watch some instructional videos on working with Hippo CMS as content editor.

Re: [hippo-community] Portlet support
by: marijan milicevic | 29-03-17 13:45:42 (CEST)

On Wed, Mar 29, 2017 at 1:29 PM, <phillip...@gmail.com> wrote: > That is a pity. Any reason why ? > I am not sure but I believe due to no demand.... (I myself can't remember when was the last time someone asked about it.) cheers, marijan > > > On Wednesday, March 29, 2017 at 1:22:52 PM

Re: [hippo-community] Portlet support
by: Phillip Krüger | 29-03-17 13:29:11 (CEST)

That is a pity. Any reason why ? On Wednesday, March 29, 2017 at 1:22:52 PM UTC+2, marijan milicevic wrote: > > Hi, > > > On Wed, Mar 29, 2017 at 1:02 PM, <phillip...@gmail.com> wrote: > >> Hi All. >> Does hippo 11 support portlets (JSR286 and even better JSR362) ? >> If so, is there any documenta

Re: [hippo-community] Portlet support
by: marijan milicevic | 29-03-17 13:22:52 (CEST)

Hi, On Wed, Mar 29, 2017 at 1:02 PM, <phillip...@gmail.com> wrote: > Hi All. > Does hippo 11 support portlets (JSR286 and even better JSR362) ? > If so, is there any documentation on how to get started ? > If not, is there any plan to add support for this ? > unfortunately we removed portlet

Portlet support
by: Phillip Krüger | 29-03-17 13:15:24 (CEST)

Hi All. Does hippo 11 support portlets (JSR286 and even better JSR362) ? If so, is there any documentation on how to get started ? If not, is there any plan to add support for this ? Thanks

Re: [hippo-community] Spring Managed HST Components support & @Autowired in PageErrorHandler causes several warnings
by: dennis.nijssen | 29-03-17 09:05:39 (CEST)

I've just created a new archetype project, and added a Component, PageErrorHandler and a FooService aswell. When I run mvn clean package and mvn -P cargo.run I still get the following warning on startup: 29.03.2017 08:55:53 WARN localhost-startStop-1 [AbstractBeanFactory. getTypeForFactoryBean:1

Re: [hippo-community] Spring Managed HST Components support & @Autowired in PageErrorHandler causes several warnings
by: woonsan.ko | 29-03-17 00:00:23 (CEST)

On Tue, Mar 28, 2017 at 12:36 PM, 'dennis.nijssen' via Hippo Community < hippo-c...@googlegroups.com> wrote: > Hello Woonsan, > > This setup seems to be almost identical. What you are missing when trying > to reproduce my problem is: You doesn't seem to have added a custom > PageErrorHandler or

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.