following three sets of resources: • Drupal code files – usually managed under a VCS • Data files (i.e. sites/default/files/*) – Usually not relevant when moving from development to production, as it is full of placeholder images • Drupal database – Changes to configuration (important) – Lorem Ipsum content (irrelevant)
database are part of the development process. • Moving config should not move test content • Config should be handled in the same VCS that manages the code • It should be possible to propagate changes from development to production (specially for a live site)
for taking different site building components from modules with exportables and bundling them together in a single feature module. A feature module is like any other Drupal module except that it declares its components (e.g. views, contexts, CCK fields, etc.) in its .info file so that it can be checked, updated, or reverted programmatically.”