Migrate to Drupal 8
The first meeting of the Drupal User Group Bodensee (Lake Constance) in 2017 will be about migration to Drupal 8.
Blog
Avoid self-definition in taxonomy term description when using the Onomasticon module
The Drupal 8 module Onomasticon automatically displays the definition of taxonomy terms everywhere a term is used. However, you may want to avoid self-definition on the term's own page as its description is already visible without it.
Add a link to call by skype in Drupal 8
Websites can use protocol handlers to provide a convenient way for users to open default applications directly from a web page. In Drupal you can add such handlers to the list of allowed protocols, e.g. in order to create a link for your visitors to directly call you by skype.
Composer based Drupal projects can be fun
As a team that had spend time and money for years in developing best practices for staging, deployment and operations of many Drupal sites on version 5 to 7, the all new Drupal 8 came with some surprises and challenges in 2015, when first alpha and then beta releases started to see the light. Where all of Drupal core up to Drupal 7 had been exposed in the main project folder, all the contributed code from the Drupal community and third parties was located deep down in the code tree with custom code for the specific project sometimes was hard to separate from other contributions.
Configure Drush for Drupal 8 to work from project root
Drupal 8 projects are in most cases controlled by Composer and following best practices, the directory structure of a Drupal project looks similar to this (more details have already been covered here):
Testing Drupal projects with Behat in PhpStorm
Developers are known for their most famous topics to be testing and doumentation - not. And I'm no different. However, the bigger my projects tend to get and the longer they last, the more this becomes a real issue so that even the developer in me starts to promote the idea of proper testing and documentation.
Performing DRD actions from Drush
Drupal Remote Dashboard (DRD) fully supports Drush and it does this in two ways: DRD provides all its actions as Drush commands and DRD can trigger the execution of Drush commands on remote domains. This blog post is part of a series (see part 1 of 4) that describes all the possibilities around these two powerful tools. This is part 2 which describes on how to trigger any of DRD's actions from the command line by utilizing Drush.
DRD and Drush
Almost 5 years ago I've started working on DRD - a.k.a. Drupal Remote Dashboard. The idea behind this module which is published on drupal.org has been and still is to provide a central place in a web browser for Drupal shops and system administrators or DevOps to get all the essential data and statuses about any number of Drupal installations.
Development environment prepared for later migration to live site
Although so many articles have been written about this issue already, the approach I'm using successfully hasn't been mentioned yet - or I missed the appropriate post. Hence I'm writing another one and hope people may find this useful.
