Drupal - Code Driven Development

I think most of my sites have 2 versions...LOCAL and LIVE to allow testing of various changes as well as developing new themes and modules. Some sites have 3 versions, LOCAL, USER TEST, and LIVE.

I like having a local version so that I can polish it first. Also, I use tools like NetBeans for coding and debugging.

I use "Code driven development" for all my Drupal sites. Remember, the changes you are making through the GUI in your Drupal site are being saved to the database.  To use code-driven development, you need to get those changes out of the DB and into code.  This is where Features comes in.  My process:

1. Develop code or theme; make your config changes in Drupal
2. Export as much as possible using Features and Strongarm - This puts the DB changes into code
3. Checkin the code to your version control system
4. On the server - pull code from your repo
5. Enable the various Features

Once you have your systems and procedures in place, this can actually be a time saver.  It's actually quite fun!!!! :)