Nus templates new

[ccewuz]

---

name: Certificate Template Addition about: This is the workflow for requesting new certificate templates to be added to the OpenCerts repository title: "[New Template]" labels: new template assignees: ''

---

Pull Request Guidelines for Adding Certificate Templates

This document is a work in progress but here are some basic checks. As these are only basic guidelines, meeting the below doesn't indicate there will be no issues with your pull request.

Pre-merge checks

• [x] Did not modify any files outside of your organisation's template folder (e.g package-lock.json or anything else)
• [x] Ensure that your code has been rebased on top of latest OpenCerts master
• [x] Linter issues resolved (Run npm run lint:fix to see issues)
• [x] npm run test passes
• [x] npm run test:integration passes
• [x] Travis Build passes

Certificate Template

• [x] No more than 5 templates or 25 added/modified files in the pull request
• [x] Ensure that your .opencert file's data complies with the intentions of the OpenCerts' schema - e.g recipient related information is inside the recipient object, etc.
• [x] Integration test for each template that checks that the correct rendering is done given a sample certificate
• [x] Sample certificate file included for each template, located alongside the integration test for each template
• [x] Sample certificates must obviously be a sample certificate
  • [x] Obviously fictitious name
  • [x] Obviously sample signatory images
• [x] No fixed-size raster images as part of certificate layout
• [x] Mobile responsive design
• [x] Date parsing should be localised to template author's timezone
• [x] Webpack chunking code is correct
  • [x] Has chunking code
  • [x] Same chunking code as the other certificates belonging to that institute
• [x] Certificate Store Addresses have been updated
  • [x] Template Whitelist
  • [x] Registry
• [x] Template should not be using resources(images etc.) on the website outside of their own folder (e.g institute logo shouldn't be used from /static because there's no guarantee it will not change)

[lgtm-com[bot]]

This pull request introduces 2 alerts when merging 4aeb1db36334ca234f15868202053646f503bd09 into cb5936f3c7d712e099ca145e8c85a798422804cf - view on LGTM.com

new alerts:

• 2 for Assignment to constant

[ccewuz]

please help with merge. thanks

[Nebulis]

Hi, I'm sorry but this repository is not meant to accept new templates since the 1st Jan

Please reach out to ssg

[ccewuz]

This pull consists updates to existing templates as well. If cancel this and resubmit a subset of changes w/o new templates, will it be accepted?

[Nebulis]

Yes we can approve changes to exisiting templates