We often get asked whether Magnolia's Standard Templating Kit is the best way to go when planning out a new Magnolia project. In this article we discuss some of the pros and cons associated with the STK to help you decide whether it fits the requirements of your Magnolia project.
Our Magnolia Services
Priocept has been working with Magnolia since 2009, and is one of only a handful of Magnolia partners in the UK. We have worked extensively with the Magnolia product suite, providing both development and consultancy services to a wide range of clients. Priocept also has considerable expertise in the Java Content Repository (JCR) and Apache Jackrabbit technologies which underpin Magnolia, having been working with JCR and Jackrabbit since 2008.
We work with clients on everything from one day of Magnolia consultancy to provide technical advice or user training, through to large implementation programmes and long term support and operation of Magnolia based websites against a formal service level agreement.
More on Magnolia…
ITW (Illinois Tool Works) is a diversified manufacturer of industrial technologies that employs 60,000 people worldwide and has annual revenues in excess of $15 billion. This case study describes how Priocept assisted ITW with the development of a Magnolia CMS platform and its integration with an inRiver Product Information Management (PIM) system.
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 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 has been appointed by Sheffield City Council to assist in the training and roll-out of their new Magnolia based website and content management platform.
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.
Priocept, the internet technology consulting firm, and Magnolia International, the creator of the open source content management system Magnolia CMS, have announced a strategic partnership in the UK.
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.
In September 2010 Priocept started working with a major automotive manufacturer to streamline management of their UK website. In this case study we look at how Priocept integrated Magnolia CMS with the Grails framework to create an effective content management solution.