DrupalXray and SimpleTest are two of my favorite sites that help me respectively in doing site audits and testing out new module, set of modules.

What does a Webhook do : When some action happens ping a given URL with some relevant data about the action. In Github's case we can configure such that whenever a new release is announced it will ping the pre-defined with data about that particular release like release name, release date and download urls for the code

Github webhooks can be used to automate various workflows. Setting them up and using them can be tricky if you don't know some basics.

Most of the times you end up having more than one development sites and copying the files folder to have the images up and running can be a huge pain. So here are the two approaches you can use.

1. Use Dummy Images Module : https://www.drupal.org/project/dummyimage

Enable Dummy Images Module like any other module. Goto admin/config/development/dummyimage

It has been almost 5 years since I first encountered Drupal. I have always wondered what are the modules used by the popular sites and I have not got a satisfying answer till date.

We do have https://www.drupal.org/project/project_module which gives us a list of most installed modules and options to filter these modules based on criteria we choose. But currently there is no way we can get a listing of modules that are used in the most popular websites. Yes, we also have https://www.drupal.org/case-studies but still the number of entries are limited and they are added on a case to case basis. But the major disadvantage here is we can look at the modules used in a particular site and there is now way at-least for now where we can see the list of modules used in most popular sites.

*Reposting from my answer on Stack Exchange

These are notes from my experiences and might vary from what others experience. I predominantly use LAMP stack and have considered the same in my suggestions.

Thumb rules for caching that I generally follow.

  1. Process Once Use Multiple Times.
  2. Live with stale data when possible.
  3. Clear Caches infrequently and keep it very specific.
  4. When possible do the changes at the lowest level in the stack. LAMPDCCc : Linux, Apache, Mysql, PHP, Drupal Core, Contrib and custom module.

Drupal modules are one of those things which appear to be a boon in the beginning but becomes a challenge as the time progresses. Initial it made us feel good thinking that there are so many modules out there. But now the same thing has become a bane. There are so many of them out them we are no more sure which one to select for our use case. I am going to list down a few of the rules that we follow in selecting the modules for our projects.

For the benefit of those who don't know what Headless Drupal is, here is the definition in Webchick's words

Headless #Drupal : Sites out there using custom front-end, Drupal = content store.

Without using Drupalisms, we can say it is a decoupled version of Drupal. By decoupling the front end from the backend it increases the flexibility of the system. It also enables your team to make use of the proficiencies of a Front End Engineer who has no knowledge of Drupal theming. Drupal theming is a costly affair(I have heard of Drupal themers who charge more than 120$/hour) and Decoupled Drupal can just be a saviour. While this is a good reason, what should really motivate you isCOPE (Create Once Publish Everywhere).

What is Marketing Automation ?

In simplest terms : Marketing Automation is automation of your marketing Strategy with minimal human intervention.

Using complex jargons : The process of collecting the user analytics and deriving the marketing intelligence out of it, which in turn can be used to automate the marketing strategy of an organization which will ultimately lead to higher conversions for the organization and hyper personalized experience for the consumer.

In layman's terms : Create leads where there are none, convert your leads to customers and sell more to your existing customers :P

What is Content Strategy?

It's the process of planning your content such that you can use, reuse your content across the form-factors and across the fast changing platforms which keep on replacing each other in a short span of time. Its not limited to making your content suitable for all the existing form-factors but it should also accommodate the form-factors which might appear in the future.

Drupal 8 is around the corner. We have been hearing it many times, I know ;). But this time we are very close. As of 06:58 UTC today, September 19, there are zero Drupal 8 beta blockers. What this effectively means is we will be hearing about the Drupal 8 Beta version very soon, as in next 10-14 days, if there are no new additional blockers.

One question that everybody in Drupal community has on their minds is how do we prepare for Drupal 8. This is a question that is common to clients who are using Drupal, companies working on Drupal and Drupal developers, site builders. Here are a few of the tips that I collected over time.

Powered by Drupal