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.
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.
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.
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.
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
In Part 1 of this two part post, we looked at the basics of international software, and how to plan your project to best support the demands of international applications. In this second post, we look at using local market knowledge to speed up localisation efforts, the pros and cons of a translation management system, and some ways to avoid mobile app "sprawl".
Web and mobile applications today should be designed and built from the ground up to support international markets, unless there is a strong business case to restrict them to a single market. The availability of tools and frameworks to provide your application with international support (including multiple languages, currencies, locales, etc.) lowers the barrier for application development teams, but the technology build is only part of the challenge of supporting international markets. In Part 1 of this two part post, we look at the basics if international software, and how to plan your project to best support the demands of international applications.