Drupal has been around for more than 10 years and while we've seen more and more organizations migrate to Drupal, there is also a increasing number of organisations that are running Drupal websites in the whole world and in extension in Belgium (the birth place of Drupal). A few years ago most of the requests started with : "Dear Wunderkraut, we want to build a new website and ... " - nowadays we are addressed as "Dear Wunderkraut, we have x websites in Drupal and are very happy with that, but we are now looking for a reliable partner to support & host ... ".
This blogpost tells the story of how we came to be that reliable partner.
With the overhaul of many API's in Drupal 8, one of the new kids on the block is the configuration system with its integration with the entity API. This means that we can now define configuration entities (that work much like the regular content entities) for the purpose of managing more complex configuration. For example, a View is a configuration entity and so is a field or an image style.
A customer journey map is a strategic tool that captures the entire customer experience. It provides an overview of all the interactions your customers can have with your organisation in a clear, self-explanatory format. By mapping the complete journey it becomes easier to see where the customer experience can be improved
Organisations used to communicate in a controlled and focused fashion with their end-users but this one way communication has turned into uncontrolled, networked conversations. Now the customer defines how, when and why people want to use your product or service. It has become crucial to focus on and start from the end-user’s wishes and needs and adjust your services accordingly. The question is, what do you have to change and how do you make those changes happen?
In the very recent period this new thing popped up in the Drupal community that has everybody talking: the Acquia certification for Drupal developers. I'm writing this article minutes after actually taking this exam to share with you my impressions.
Today, I will talk a bit about access control. Specifically, what options you as a module developer have for controlling access to nodes and individual fields. As I'm sure you agree, the Drupal permission system available for site builders is powerful. Yet, fringe cases occur that leave this system wanting. It's a case like this I will talk about below.
On Sunday May 25th, Belgians will vote a new regional and federal parliament for the next 5 years. Working up to the official start of the election campaigns in February, Wunderkraut Benelux expanded their client network with 3 political parties! Using Drupal we were able to deliver time sensitive qualitative solutions in response to various client needs and political objectives.
In this article we will look at how you can leverage the power of the Drupal 7 Form API states system to create dependencies between your form fields. In other words, when you programmatically write your forms, you’ll be able to make the behaviour of the elements depend on others.