We are pleased to announce that Jackrabbit Explorer, an administration tool for JCR repositories, is now available on Google Code. It's exciting to be able to contribute something back to the JCR and Jackrabbit community, and we'd welcome feedback and feature requests (and bug reports!) for Jackrabbit Explorer via the Google Code project.
This example follows a site editor making minor changes to a page in a Magnolia CMS website and a site publisher reviewing that change before publishing it for public viewing. It uses the Magnolia CMS Demo Area, hosted by Magnolia International to provide an area for exploring and practising.
Magnolia CMS's publishing mechanism revolves around the concept of a server used for creating, editing and previewing content, available only to a limited group of users and known as the authoring instance, and one or more publicly accessible servers which operate in a read-only style, serving content over the web and known as public instances. In this short tutorial, we describe the concept.
Here is the video of the seminar we gave recently at Internet World 2011 on the Content Platform we built for TUI Travel.
Now that Internet World 2011 is over, we can look back on a hugely successful week at Earl's Court in London. Read for photographs of our stand and the seminar last week.
Here are the slides from the seminar on Content Platforms given by our Principal Consultant, Matthew Skelton, at Internet World last week
This example follows a site editor making minor changes to a page in a Magnolia CMS website and then publishing that change for public viewing.
Magnolia CMS is an easy-to-use open-source content management system (CMS) with many advanced features. Here, we've collected together several articles and blog posts relating to Magnolia CMS.
Two Priocept developers, Chris and Adam, went to Basel last week to get trained up as Magnolia developers. Here's a quick report-back.
The Twitter Engineering team (@twittereng) has just achieved an impressive 3x performance improvement for Twitter search queries, largely, it seems, by replacing Ruby-on-Rails web applications with new applications built on Java, coupled with a switch from MySQL to Lucene for the data store.