Support the following field types for rendering:

• #12
• #13
• #14
• #15

All the front-end development so far was done in Jugaadu Rema. Bring it to main upstream Rema.

Add the template model schema to the documentation.

Add placeholder support for both the template and certificate APIs.
Some good placeholders could be:

• TEMPLATE_DATE
• CERTIFICATE_DATE
• CERTIFICATE_TITLE
• TEMPLATE_TITLE
• CERTIFICATE_UID

Add a new property to the certificate object (not certObj.values, certObj itself) and export it with the resulting response.

Prune unused downloaded images every once in a while.

Define the template schema.

Support generation of certificate in the following formats:

• PDF: Selectable fields must be distinguishable.
• PNG

Have both a Dockerfile and a docker-compose.yml ready for the containerization of Rema.

Define the certificate schema.

Avoid cluttering long data URIs inside the database. It's too much of an overhead.

Create the following stock templates:

• stock-award
• stock-best-award
• stock-brilliance
• stock-colourful-ornament
• stock-curly-borders
• stock-generic
• stock-ornamental

Support at least the following import/export formats:

• JSON

Not in priority but aim for possible future support of:

• YAML
• XML
• JSON5

Now that everything is being downloaded or accepted as an existing image, it is safe to assume that all images will be located at different locations in one directory (which could be a mounted object storage e. g. S3 in production).

Why use callbacks when we can use promises? Do the same for the validation method.

Hint: Pass by reference. 😎

Test SVG background and field support for rendering:

• Background
• Fields

Upon bulk certificate generation, respond with an updated CSV containing the same data with an additional column: REMA_CERT_UID, containing the UID.

Accept CSV files containing the information.

Check for the presence of the stock templates in the database and their files in the INTERNAL_STATIC_DIR.
Whichever found missing, fix using the contents from the builtins directory in Rema's root and the src/initDB.js script to fix the database.

Support at least the following specification formats:

• URL
• Filename
• Data URI

The rendering must include all rendering, including that of both templates and certificates.

Accept a background colour in the template model. Use white by default, and if provided "transparent", don't add a background colour.

Placeholders including:

• Those in the bulk CSV column-names.
• Those in certificate/template objects.

The following updates are to be done:

• #32
• #33
• #34
• #35

Minify the following outgoing:

• HTML
• CSS
• JavaScript

Could reduce image size using node:15-alpine

rema Image size

node:15-alpine3.13

node:15.0.0-buster

The following need to be implemented and tested extensively:

• Gradients in text

❌ Patterns in text (support dropped in 9c8a6c0)

• #17

Create documentation for the template API.

Scale down for sizes exceeding the capabilities of the application.

If ?force is given, delete all corresponding certificates and then modify the template.

Check for common issues right before startup.

Id est #45 .

Have better validation of image sources:

• URL
• Filename
• Data URI

Create a REST API for CRUD operations on the templates:

• Create
• Extend existing
• Get all
• Get
• Render and retrieve a preview
• Patch/Update
• Delete
• Delete all

Create an API that allows using existing templates to create certificates.

Some points need to be taken care of:

• The certificate must only store a reference to the template it extends (via its identifier)
  and the values it provides the template's fields.
• #26
• Needs to have a route that renders the certificate, supporting both PNG and PDF, in a
  similar fashion as the template API renders its preview.