Enterprise content-managed websites need bi-directional content transfers on a regular basis. Here we explain why, and how to achieve this, a task which involves content editors, IT operations, and software development teams.
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.
In June 2011, Priocept gave two presentations at Sitecore's DreamcoreEU 2011 event in London. We spoke about the multilingual ecommerce Sitecore website we built for Virgin Mobile in Qatar in the Middle East. Here are the videos from the two sessions: one focused on the business case and user experience, and the second covers the more technical aspects of the project.
A short article on the differences between three important and fundamental security concepts that are often confused: Authentication, Authorisation, and Access Control.
In this article, we look at the difference between a CMS and a content repository, and how and why you might decide that a content repository is the right technology for your expanding content requirements.
Priocept's Principal Consultant, Matthew Skelton, talks about Sitecore's excellent support for multi-lingual websites including Arabic.
Developing web applications can be optimised to make the Test cycle quicker and more thorough. The HTML mark up - if written with automation in mind - will make automated test vastly easier to write and maintain, allowing builds to be more robust and code to be released more frequently with a higher quality. Furthermore, adopting a defensive approach to data validation and processing will lead to much more secure applications.
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.
Testing is an often under-appreciated part of the software life cycle. Timelines will shift, there will be delays with the development and the testing phase is the part the suffers. Here we have compiled a list of tips to help increase the productivity of testing and to help avoid releasing bugs into production and keep a high level of quality in the software released.
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.