Changes between Version 2 and Version 3 of DrupalIntegration
- Timestamp:
- Oct 21, 2013, 1:57:49 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DrupalIntegration
v2 v3 2 2 3 3 = Overview = 4 5 4 BOINC-Drupal integration harnesses many powerful functions of the Drupal development framework and content management system, both simplifying the management of BOINC projects and improving the end user experience on project websites. 6 5 7 See further documentation on how to InstallDrupal. 6 == Benefits of Drupal == 7 Drupal offers a number of benefits to project maintainers: 8 8 9 == Benefits of Drupal == 10 11 Drupal offers a number of benefits to project maintainers: 12 * CMS: Create and manage site content without knowledge of HTML 13 * Theming: Full CSS support, complete with template overrides in custom themes 14 * Change management: Site configuration can be exported to code for versioning, minimizing manual changes 15 * Powerful deployment: Changes can be deployed across development and production systems with minimal effort 16 * Extensibility: Designed to be modular and extendible to balance simplicity and functionality 17 * Distributed maintenance: Most code owned by active members of the community, simple update process 9 * CMS: Create and manage site content without knowledge of HTML 10 * Theming: Full CSS support, complete with template overrides in custom themes 11 * Change management: Site configuration can be exported to code for versioning, minimizing manual changes 12 * Powerful deployment: Changes can be deployed across development and production systems with minimal effort 13 * Extensibility: Designed to be modular and extendible to balance simplicity and functionality 14 * Distributed maintenance: Most code owned by active members of the community, simple update process 18 15 19 16 Simplified management for project maintainers allows more time to be spent on content, site features, and presentation, improving the end user experience by extension. 20 17 21 18 Current BOINC projects that make use of Drupal integration: 22 * [http://albert.phys.uwm.edu/drupal Albert@home] (test project for @Einstein@home) 19 20 * [http://albert.phys.uwm.edu/drupal Albert@home] (test project for @Einstein@home) 23 21 24 22 == Drupal Module Organization == 25 26 23 The structure of any Drupal site revolves around the core functions of Drupal, third party enhancements to that core, and custom code that provides any required functionality not otherwise available by either of those established channels. This organization could be described as some combination of core, contrib, and custom modules working together to provide high level site features: 27 24 28 25 [[Image(BOINC-Drupal_module_organization.png, 800px)]] 29 26 30 Modules generally build on other modules, so a custom module to enhance part of the system may work in conjunction with half a dozen other modules in order to provide a given function. 27 Modules generally build on other modules, so a custom module to enhance part of the system may work in conjunction with half a dozen other modules in order to provide a given function. 31 28 32 29 == Database Integration == 33 34 30 The Drupal system ties into the BOINC database in order to display information for users, hosts, and teams. Most of this involves reading data only, though user profile data and preferences operate in a shared state, allowing changes to be made to the relevant BOINC table records from either the standard BOINC or Drupal enhanced web interfaces. There is also an import module that offers an interface for importing data when it is not feasible to rely on shared or read-only access, as is the case for discussion forums and private messages. The following diagram details how the BOINC database is used by the Drupal system: 35 31 36 32 [[Image(BOINC-Drupal_dataflow.png, 800px)]] 33 34 == How to Install == 35 See further documentation at InstallDrupal.
