The current version of CiviCRM is based on Drupal 4.5 (soon to be Drupal 4.6). We have made a strong attempt to integrate well with Drupal. At the same time, we've tried to be cautious with the amount of code we share with Drupal. We'd like to avoid getting into the situation where an install of CiviCRM requires an install of Drupal. We'd also like to run under other open source CMS frameworks like Mambo and Plone.

Drupal Dependencies

We currently rely on Drupal (or the host CMS) for the following functionality:

• The menuing system. This basically ties the menu structure displayed to parts of the CiviCRM code

• The user login and permissioning system. The host CMS is responsible for the roles/rights/permissions on various actions provided by CiviCRM. Note that we have not yet done any significant development with regard to permissions

• The templating system. The host CMS is responsible for building the page and displaying it. CiviCRM is one component of the entire page. In the Drupal context, we provide the main content and also have created various blocks to enhance functionality

• Themeing. We've tried to make sure our code is as themable as possible.

• CiviCRM uses PEAR libraries for a large part of the framework. More information can be found at http://objectledge.org/confluence/pages/viewpage.action?pageId=1928

• Feel free to download and look at the code. Instructions are at: http://objectledge.org/confluence/display/CRM/Installation+Guide+for+Developers

• Note that most of the drupal specific code is under modules and themes. CiviCRM uses Smarty as a templating engine and the relevant code to integrate Smarty with Drupal is in this folder (it is also in the drupal cvs contributions)