On 27 July 2015 at 23:22, Andrea Schweer <schw...@waikato.ac.nz> wrote:
> As a completely separate thought, might it make sense to look at > something like Mailchimp just in terms of what other places consider > reasonable to put in front of end users when it comes to creating e-mail > templates? They probably need less complex logic than may be required > for DSpace. But from my little bit of exposure to Mailchimp, they do a > pretty good job with the UX. > Email distribution services (potentially) have a quite different goal to fulfil. Typically, with MailChimp et al, you are most likely to be writing almost entirely "static" content, with tiny bits of mail merge customisation (e.g. name) if any. Whilst these services will have templates to get you started, they can afford to allow you to upload pretty much raw HTML (if they want to), with just a couple of tags for merges. We are going to want a more data driven engine than just a straightforward merge. For example, inserting details of a repository item, and potential stylistic concerns about how the citation is presented. I agree that XSLT is too heavyweight a mechanism for laying out emails, especially considering who is likely to want to amend it, and it quite possibly makes sense to tie in with how we do a new UI, if it is using a more lightweight templating engine (Freemarker, Thymeleaf, Mustache, etc.) G
------------------------------------------------------------------------------
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
