The digital pattern library (DPL) is a resource created and owned by the digital communications team. Find out what the DPL does on the about page.
The DPL is used to create internal webpages and web applications as well as external pages (outside the University of St Andrews domain). It follows the design principles of the digital communications team and is platform agnostic. The code in the DPL is version controlled via GitHub.
You may not use the digital pattern library without signing a copy of these terms and conditions of use. For details contact the digital communications team via Unidesk.
This policy is supported by the digital communications take-down policy, which states that any incorrect usage of the DPL may result in a request to rollback or remove the product.
If you wish to use the DPL and you are a member of staff at the University of St Andrews, you must liaise with the digital communications team for access and training. Any member of staff using the DPL will be expected to attend the fortnightly DPL developers’ meeting on a regular basis.
External agencies or partners who wish to use the DPL must request access from the digital communications team. Access to the DPL to external partners is granted on a case by case basis.
All users of the DPL must have an understanding of user-centred design, and keep up to date with amendments to the digital communications team service manual.
New web applications and webpages designed using the digital pattern library must be approved by the digital communications team before they are deployed to a production environment.
All users who wish to use the DPL to build a product must first organise a kick-off meeting with the digital communications team. At this meeting rules and responsibilities will be explained. Once they have been introduced to and understand the DPL and want to continue to use it they will be required to sign a Memorandum of Understanding.
The Memorandum of Understanding will set out clear sign off gateways, which require users to share the information architecture (for webpages) and/or workflow (for web applications) as well as plans for content management with the digital communications team before the DPL is used to build or prototype a product. Once the IA or workflow has been agreed, the product must meet the relevant URL policy. All products using any element of the DPL must conform to the house style, content standards and corporate identity policy of the University.
A clear commitment must be given that no new product using the DPL will go live without the explicit, written sign-off by the digital communications team.
In turn, the digital communications team will provide advice and support for use of the DPL.
The following developers, outwith the digital communications team, have agreed to abide by the Memorandum of Understanding.
Developers using the DPL should not fork the code in GitHub. No patterns or elements (such as colours) in the DPL may be edited without liaising with the digital communications team. This is the case in both the DPL and in any content management system; patterns should not be modified in any manner. Do not use CSS to overrule DPL elements, patterns, fonts etc. All code written must follow the digital communications team’s code standards. Rules on all patterns must be adhered to - if in doubt, please ask.
New patterns may only be created by developers working directly alongside the digital communications team.
DPL patterns should only be added to our central CMS, T4, or to WordPress by the digital communications team.
Some patterns already exist within T4 and WordPress; developers are free to use these patterns in accordance with the rules of the patterns, and in accordance with this policy. There should be only one instance of each pattern in T4/WordPress. Do not duplicate patterns/content types. Any new pattern in T4/WordPress must follow the digital communications team's naming conventions.