Mack Hardy presenting "Everything in Code" on the drupal development tools of Features, make files and drush. Presented at the 2nd Pacific Northwest Drupal Summit http://pnwdrupalsummit.org/2010/sessions/everything-code
Mack is the founder of Affinity Bridge http://affinitybridge.com
Content and config are separated. Config is version-ed in source control. Code can be diffed, so we can tell what changed. Building from code has PREDICTABLE, REPEATABLE results. easy to hand off a project to someone else Time is saved.
the initial act of building a drupal site (drush_make) choosing all these useful contrib modules that work together (install profile) the couple of hours of config you just did (feature).
The basics version control to save your stuff drush manage your stuff features to hold your stuff
If you change the sandwich in the UI, you can run the update -> code If you want your old sandwich back the way it was, revert drush features-update feature-name and drush features-revert feature-name
If you change the sandwich in the UI, you can run the update -> code If you want your old sandwich back the way it was, revert drush features-update feature-name and drush features-revert feature-name
If you change the sandwich in the UI, you can run the update -> code If you want your old sandwich back the way it was, revert drush features-update feature-name and drush features-revert feature-name
If you change the sandwich in the UI, you can run the update -> code If you want your old sandwich back the way it was, revert drush features-update feature-name and drush features-revert feature-name
If you change the sandwich in the UI, you can run the update -> code If you want your old sandwich back the way it was, revert drush features-update feature-name and drush features-revert feature-name
If you change the sandwich in the UI, you can run the update -> code If you want your old sandwich back the way it was, revert drush features-update feature-name and drush features-revert feature-name
If you change the sandwich in the UI, you can run the update -> code If you want your old sandwich back the way it was, revert drush features-update feature-name and drush features-revert feature-name
If you change the sandwich in the UI, you can run the update -> code If you want your old sandwich back the way it was, revert drush features-update feature-name and drush features-revert feature-name
If you change the sandwich in the UI, you can run the update -> code If you want your old sandwich back the way it was, revert drush features-update feature-name and drush features-revert feature-name
Knowing is half the battle
Post commit hooks
input formats taxonomy is newly node_queue block settings machine names for everything features_extra module
get a make file, or make one wget http://gist.github.com/raw/441422/063be9a1c41d9a45b1f127464ba528175ba42138/simplecontext.build Show the build file http://skitch.com/mackhardy/d3tey/terminal-bash-96x24 run a build file http://skitch.com/mackhardy/d3t85/terminal-gzip-96x24 talk about drush features-update feature-name and drush features-revert feature-name
As a Team - what should the language say here? the message is that we take small steps to build out the framework as a team. collaborate? just "team" - talk about how to automate a process you do it manually - drush will immediatly save you time - build from examples Tips Next easy component: get a feel for features. Source control - ONLY version-control the code you create yourself - your makefile, install profile, custom theme probably, and your custom modules, including features. A good learning aid with drush_make is to build with the --debug flag.
On Thursday, Young Hahn from Dev Seed announced that the Everything-in-Code workflow - the whole drush_make, install profile, and Features stack - can now be used on Drupal 7. To help us all get started with that, Dev Seed has also created, for your utility and education, a D7 install profile called Build Kit . Build Kit is specifically designed to make it easier to develop using this technique. It comes with Everything-in-Code-tastic build tools including Features, Strongarm, Views, Panels/Ctools, Admin, Context, Diff, and Devel. Build Kit is also designed to keep track of the ongoing developments in exportables for Drupal 7, which has been a road not without bumps D7 support for the Everything-in-Code approach is moving fast: exportability for taxonomy vocabularies was committed to D7 HEAD on Friday. Hooray! Hopefully, text formats will also be totally exportable soon. Basically Everything-in-Code is the way of the future.