On Friday September 26th, the largest Drupal training worldwide was held in Amsterdam. Over 250 students, teachers and professionals from Belgium and The Netherlands participated in a curriculum of 5 different tracks introducing them with Drupal.
At our company LimoenGroen we use Drupal on a daily base. To improve the quality of our development process, we implemented a continuous integration workflow based on Jenkins.
Continuous Integration builds, updates & tests the full website automatically after every change in the code, which results in increasing the overall quality of the development process.
After an anxious year waiting and preparing for DrupalCon, the moment is finally there. Tomorrow the whole LimoenGroen gang and i will fly to Prague to attend this year’s DrupalCon. It will be my 5th DrupalCon and it’s gonna be a busy one. I’ve been to every EU DrupalCon since Paris and as each year I’m excited as a little kid to pack my bags and go.
Within our company we use Drush and Drush alias files a lot. Recently I wrote a company blog post (in Dutch) about the workflow we’ve set-up and this post is its English translation. For those of you not familiar with Drush, I’ll start with a short introduction. If you are already familiar with Drush and Drush alias files, you can skip to the interesting part.
There are already many Drupal modules to display or import Tweets on your website, but most of them come with limitations: they just display the tweets instead of importing them. This makes it hard to filter, especially when you display a specific hashtag. In some cases, it’s pretty handy if you can quickly unpublish an unwanted tweet. The modules that do import tweets have other limitations.