Sarah,<br><br>Congrats on the good work you are doing for Jewish, Muslim and other religious organizations. Some folks coming to the CiviCRM Meetups in Toronto speak quite highly of you.<br><br>Just to echo parts of what Sami and Tim are saying: try to keep the level of integration required between the Moodle and Drupal/CiviCRM parts of the site to a minimum. Where it is necessary, try to make it as thin and standardized as possible, or as loose and distant as possible. For example, give Moodle and Drupal/CiviCRM complementary but separate branding, so you don't have to replicate changes in both environments, especially not simultaneously. It might even be good to make one application a subdomain, eg <a href="http://crm.mycongregation.org">crm.mycongregation.org</a>. Also, you might want to try to avoid developing integrated login by using LDAP for single sign-on, though of course setting that up for Moodle and Drupal / CiviCRM can be its own small kettle of fish. The objective as I see it would be to avoid having to maintain middleware code that would have to be kept in synch with two or more projects that each has its own upgrade cycle.<br>
<br>As this is starting to become fairly complex but is really useful for your vertical, you might want to make it into a SaaS offering so that the setup and maintenance costs (and expertise) can be reduced through scale and allocated to more customers.<br>
<br>Mehta,<br>Joe<br><br clear="all">Joe Murray, PhD<br>President, JMA Consulting<br><a href="mailto:joe.murray@jmaconsulting.biz">joe.murray@jmaconsulting.biz</a><br>skype JosephPMurray twitter JoeMurray<br>416.466.1281<br>
<br>Sarah wrote:<br>
<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sami - The use case that I am thinking about is a community-driven<br>
website for a religious congregation. The demographics of the<br>
congregation is that about 30% are not computer-literate and will not<br>
use the website, and another 15% are very young children who also will<br>
not be using the website. So hooking CiviCRM into Drupal is already<br>
needed so the staff can keep track of the whole congregation including<br>
family relationships.<br>
<br>
The congregation also has a religious education program for kids and<br>
parents, plus an adult education program. This is the area where<br>
Moodle is being considered.<br>
<br></blockquote></div><br>