The amount of user-configurable templates is becoming hard to manage

[sergei-maertens]

Open Form allows admins/form designers to configure a number of templates that are rendered at certain stages of a form submission, such as (but not limited to):

• confirmation email (global config / form-specific overrides)
• cosign request email
• confirmation page content
• cosign confirmation page content
• introduction page
• start page body text

It's becoming hard to keep the overview of which templates are available and in which cases they get rendered, and there's now also branching being added for templates for forms with/without cosign. If we follow this pattern e.g. for submissions with/without payment requirement, the possible combinations explode (with/without cosign + with/without payment -> 4 template fields, each localized in 2 languages -> 8 DB columns (!))

Additionally, loading a WYSIWYG editor in the admin for each template field adds quite some overhead to the page (in terms of memory and CPU footprint).

A better solution to manage user templates should be investigated.

See also thoughts in comment

[joeribekker]

This is good to pick up when we add yet another template...