website

Implement a set of Drupal modules called CiviCRM. It is an Open
Source thing, and in theory, the major benefit is that we would have a
single platform for management of content and of customers. The drawback
is that it there is not a lot of support available for that piece of
software, and there is not a lot of understanding of what it does and
what it doesn't. We would have to hire professional services from day
one to help us scope the project, and then more for implementation,

This issue is being discussed here: http://cms.can.org.nz/article/need-your-advice-regarding-email-notificat... If everyone is OK with it, the solution will be as follows: The problems we have been experiencing with people complaining about email notifications have been identified as associated with groups that have too many messages. There is just one group in this category: the CAN group. (The CAN Exec Group could be in this category, but let's re-evaluate again after sorting out the CAN Group) Ideally, what we would like to have is the following behavior: - By default, a

Just can't find out how to change the footer of the e.CAN newsletter.

The roles and permissions are apparently right, but the outcome is not. This ws flagged by Axel and Adrian on the page http://cms.can.org.nz/joinfull .

To sort this out we need to provide more HTML training to André! :-)