This is Part 3 of an interview with Will Eisner, Senior Director, Product at Acquia.
Drupal is one of the most flexible content management systems in existence.
If there's anyone who has command of the command line, it's Dave Myburgh, a senior engineer at Acquia.
So we asked him to share how he works with the CLI -- to help us all improve the way we work. Here are the top ten command line tips that Dave suggested. Check them out, and increase your speed of development.
When you spin up sites for a living, velocity is important. The developers at Acquia understand this, which is why we’re always looking for ways to make website development simpler and easier.
Drupal 7 out the box offers a good implementation for uploading media, but it has three significant challenges.
In this 3-part Drupal How-To series, I'm going to show you how various options for configuring images on your site.
It all started at DrupalCon Barcelona, when Shailesh Gogate, VP at Faichi Solutions, met Johanna Boel Bergmann, the Account Manager, Drupal Businesses at the Drupal Association.
Johanna had never heard of Faichi; she had never seen it in the Drupal.org Marketplace. This even though our company has been working with big enterprise clients for the past five years, as well as contributing to Drupal.org.
That was an eye-opener for Shailesh. When he returned to India, he shared his findings with Faichi’s engineers and senior management. They took the feedback very seriously. They decided to create a plan to show their presence: not only in the Drupal Marketplace, but to the whole Drupal community.
Recently I had a customer ask me how to tell Drupal 8 to display certain blocks conditionally, based on whether or not the node page being viewed referenced certain taxonomy terms. In Drupal 7 I would have recommended the Context module for this, but as it’s not yet ready for Drupal 8 I had to go looking for other options.
My search led me fairly quickly to the brand-new Block Visibility Groups module, which aims to provide the same sort of conditional block visibility functionality that Context provides, but in a manner that integrates more closely with the core Block UI. It works well, but doesn’t natively provide support for basing visibility off of node field data (such as taxonomy term references). However, since Block Visibility Groups uses the core D8 Condition plugin type to define its conditions, all that’s needed is to implement a custom plugin to get the desired behavior. Here’s how it works, from start to finish: