This document discusses using code-driven development for a Drupal site by: 1) Installing modules and settings as features to version control the site configuration. 2) Managing the site workflow through a controller module and hook updates. 3) Using Drush commands to push settings between environments like reverting features to the database or updating from the database.

1. Yuriy Gerasimov Madcap B.V. [email_address] skype yuriy_gerasimov Code Driven Development

3. No separation from content

4. Pushing changes to Staging / Production

5. No version control

7. Resolving conflicts between developers

8. Push settings between installations (to production)

9. See if client didn’t change anything

10. Keep client’s testing data on staging site

13. Content types (all CCK fields settings)

14. Views

15. Panels

16. Imagecache presets

17. Blocks visibility (context)

18. Creating feature

20. create some node, taxonomy, users space

21. create node, term

22. Step 4: Workflow hook_update_N()

23. Workflow

24. Workflow. New developer joins the team

25. Workflow. Also add changes to hook_install()

26. Features Namespace # Feature News (feature_news) Views feature_news_blocks feature_news_list feature_news_node feature_news_taxonomy Contexts feature_news_front feature_news_list CCK Fields field_news_pictures field_news_links Imagecache Presets news-s news-m news-l news-portrait

27. Drush features

31. Drush features-diff _feature_name_

33. drush updatedb – run all updates

34. drush features-revert-all – update settings from features

35. drush cc – clear caches

37. http://drupal.org/project/features

38. http://drupal.org/project/kit

40. Yuriy Gerasimov Madcap B.V. [email_address] skype yuriy_gerasimov twitter @ygerasimov Code Driven Development Thanks!