Feature Request: Optional Template Management from Configuration

Problem/Motivation

The current module lacks an intuitive way for administrators to manage templates directly from the configuration page. Customizing templates often requires direct theme file modification, which can be cumbersome, especially for non-technical users. Enabling administrators to manage templates directly from the admin interface would simplify the process and reduce the dependency on developers for minor changes.

Steps to reproduce

1. Navigate to the module's configuration page.
2. Note that there is no option to manage or customize templates directly.
3. Attempt to modify the template, only to realize it requires direct changes to theme files.

Proposed resolution

Introduce an optional feature in the module settings that enables administrators to manage and customize templates directly from the configuration page. This feature would include the following functionalities:

• Template Selection: Administrators can select and assign templates from the module configuration interface.
• Template Editing: Administrators can edit templates without needing to modify theme files directly.
• Template Variables: Allow dynamic content variables to be passed to templates through the configuration settings.

This feature should be optional, meaning administrators can enable or disable it based on their needs.

Remaining tasks

• Design the user interface for template selection and editing in the configuration page.
• Implement the logic for dynamic template variable passing.
• Test the preview functionality to ensure it displays templates correctly before applying changes.
• Ensure compatibility with existing functionality if the feature is disabled.

User interface changes

• Add a new "Templates" section in the module configuration page.
• Include a toggle or checkbox to enable or disable template management.
• Introduce a template editor interface where administrators can edit the templates directly.

Data model changes

• No changes to the core data model are expected for this feature.
• Consider adding a new configuration table to store template customisations if necessary.