The Web Chefs are going to BADCamp. In addition to being a Contributing Sponsor (we’re doing fun things with our booth. Stay tuned!) and providing some awesome training sessions on PHP and Node.js, we have also submitted a few talks.
Our two training sessions are full, but you can take a look at our proposed sessions below. If you feel like taking a look and voting for your favorite ones, we’d love your support. Also, feel free to leave feedback on our proposed sessions in the comments. We do love hearing feedback on session submissions.
The very first Drupal Day Austin took place this past weekend, and it was a great success!
First off, many thanks to everyone that came out for the event! This year, we were unable to have a full-on DrupalCamp Austin, so we had to make do with one day. We appreciate the community for being so understanding and awesome! The speakers were truly all amazing, and their talks generated a great deal of healthy discussion.
There are times when you need to build a custom block that a site builder can utilize in various places on a page. Drupal 7 provides several hooks that allow you to accomplish this goal:
Even though we have six weeks until DrupalCon Munich, I’ve already started scouring the schedule for interesting frontend talks. As you might know, one of my favorite topics is mobile web development and there’s plenty of interesting stuff this time around.
When the Four Kitchens’ team of web chefs develop a new training course, our guiding principle is: Provide a strong return on investment. You invest the time traveling to the training, attending, and afterwards, practicing the skills acquired. You also invest the energy and effort necessary to develop new skills. You place your trust in the trainers to guide you from where you are now to where you need to be. In return, we invest our time, energy, and best effort in creating training experiences that give you a stronger, more relevant, skillset and the confidence you need to apply it.
There’s a new kid on the block in the configuration management world that claims to be lean, simple and easy to understand. We’re using it internally for some exciting new projects, and have found that it lives up to it’s promise.
The Internet in the 90’s - a much simpler place.
We’ve done several migrations for clients who need their old, legacy content imported into Drupal from a collection of static HTML files. In this post I’ll outline the procedure we use to migrate, and provide some solutions to common problems related to encoding, line endings and parsing HTML with QueryPath. Code snippets are provided inline, and complete source code is provided as a Github gist.
1. Setup a Migration source
Today starts a new month and a fresh beginning for Drupal. After many discussions over many drinks at DrupalCon Denver, we’re proud to announce a strategic inflection point for the Drupal community. As of today, the following companies will be merging into one company — a new formidable force in the Drupal community: