Forked from
Documentation / Docs / Developer Documentation
3276 commits behind the upstream repository.
-
Sean Madsen authored
perl -0777 -i -pe 's|^(.*)\n-{3,}$|## $1|gm' `find . -name '*.md'` perl -0777 -i -pe 's|^(.*)\n={3,}$|# $1|gm' `find . -name '*.md'`Sean Madsen authoredperl -0777 -i -pe 's|^(.*)\n-{3,}$|## $1|gm' `find . -name '*.md'` perl -0777 -i -pe 's|^(.*)\n={3,}$|# $1|gm' `find . -name '*.md'`
develop.md 1.43 KiB
Developing CiviCRM
Repositories
CiviCRM is divided into a few repositories. This allows developers to work with different components, allows different teams to manage each component, and will allow all the pieces to be remixed using different tools (civibuild, shell scripts, Drush & Drush make, or composer). The repositories are:
- civicrm-core - Core application which can be embedded in different systems (Drupal, Joomla, etc).
- civicrm-drupal - Drupal integration modules, with branches for each CiviCRM release & Drupal major version (e.g. 7.x-4.6, 7.x-4.7, 6.x-4.4, 6.x-4.6).
- civicrm-joomla - Joomla integration modules.
- civicrm-wordpress - WordPress integration modules.
- civicrm-packages - External dependencies required by CiviCRM.
- civicrm-l10n - Localization data.
Obtaining a development build of CiviCRM
The recommended method is to use CiviCRM Buildkit to build a CiviCRM codebase to develop with.
Deprecated instructions
Previous methods for obtaining a CiviCRM source build are documented at Deprecated Developer Processes.