Thank you all for a great year!
For all of you who have supported the Build a Module.com project, through kind words, making purchases, spreading the word, or sending positive mental vibes, thank you, thank you, thank you!!! Because of your support, more and more people are getting the chance to learn Drupal with a cutting-edge set of learning tools, innovations are being made for live training techniques that could change the face of training forever, and we have quickly become one of the biggest, highest quality single-source video tutorial libraries for Drupal.
This next year is going to be an exciting one. We're going to be covering more and more territory with our tutorials, we'll be helping groups and individuals conduct live trainings across the globe with our Mentored Trainings (including at DrupalCon), and we'll introduce some great new features that will make learning on Build a Module.com an even more enjoyable experience.
Thank you again, this has been an amazing year and here's to another one that's even better!
5 new videos on capturing everything else in code
Last week we wrapped up a series of videos on how to manage feature modules, and in this week we fill in some of the gaps by looking at how to capture those bits of content and configuration that we can't quite get directly into a feature module. We also explore how to use a central list and a set of basic rules to keep track of changes that require a little manual finagling.
If you're excited about capturing everything in code that you possibly can (if you're not excited about that, then watch some of the previous videos on why code capturing is so awesome), then this will get you that last 10% that doesn't quite fit into the other tools we've covered.
Selenium IDE - a tool we've covered a bit in the past - is a great way to capture site modifications in a way that's easy to automate in other environments. In this video we take a top-level view of how this process works.
Once you have a 'test' (a macro), the next step is to capture the test in code. To do this, we export the test and create one more test to explore some of the other options available to us with Selenium.
Automating is awesome, but sometimes it's just not possible. For those changes that require real human interaction, it's great to have a set of rules and central location for keeping track of the changes as you push them to other team members and launch them into staging and production sites. In this video we show you one way to do this.
In this video we step back into Git techniques and look at using several commits for one group of changes to make it easy to roll back and document changes from one revision to another.
New FREE video of the week
To demonstrate using Selenium IDE, we begin by recording a macro that generates a new node. You can record virtually any change with Selenium, but this would be one common use of the tool. We'll follow it up with one more test to demonstrate some additional techniques.