User Story

As a:

Programmer

I want:

to have a templating engine in the backend

so that:

I can easier and cleaner create and maintain templates for e.g. (html) mails

Storypoints:

Acceptance criteria:

[ ] templates stored under e.g. api/src/templates/mail/ can be rendered
[ ] variables can be passed to the value
- [ ] object-values from a passed value can be accessed (nested)
[ ] a wrapper template can be defined in the render-function (this may be useful to create a tempalte file for the message and a wrapper-file to define some kind of html markup stuff)

Additional info:

The module mini-template-engine looks pretty good for this task.

Some kind of example code may be this:

class Templating {
  private $wrapper = '<div>add here some cool styled css/html stuff<div class="content">[[CONTENT]]</div></div>';
  private $activation = 'Hi {user.name}, please click {activationlink}. CU';

  public static function render($template, $html = false, array $attributes) {
    // todo check if template exists
    $input = $template_content; // MAGIC: this is the content of eg $activation for $template = 'activation'
    if ($html) {
      strreplace('[[CONTENT]]', $wrapper, $input);
    }
    $output = TinyTmpl.render($input, $attributes);
    return $output;
  }
}

but instead of getting the content from the variables we should read them from the template-files.

geli-lms / geli

Introduce a (mail-) templating #78