Grzegorz Pietrzak

Soon, we will be celebrating the first anniversary of the day Droopler – our open Drupal distribution for corporate websites – was released. It is a perfect time for some summaries and plans for the future. In this article, I’m going to show you how Droopler works and what awaits its users in the upcoming release. Why Droopler? Where did the idea of creating a new distribution come from?

What to do with an old, outdated website that you would like to keep online? The perfect solution is to archive it to pure HTML code. We will demonstrate it on the example of a drupalcamp.pl website created in Droopler, based on Drupal. Why archive pages at all? Sometimes websites have their expiration date. It may result from the life cycle of the technology used to build it or simply because the website was created for an event or some special occasion.

An event website can be a big challenge. Usually, you will have to do it quickly and cheaply, while ensuring its high quality. After all, the prestige of the event and, consequently, the high turnout of guests and visitors, depends directly on its quality. How to reconcile a tight budget with great quality? If you are looking for a good solution to this conundrum, you can go with Droopler, Droptica’s distribution based on Drupal. The event industry is characterised by many contradictions.

Projects implemented by Droptica often require a large amount of coding in PHP. Taking advantage of various tool and configurations allows us to streamline the process and make it far more convenient and pleasant. In this post, we wanted to share our experiences and describe an ideal software configuration for coding in PHP (mainly in Drupal, since we are a Drupal agency). The base software that we use includes Linux (most people use Ubuntu) and PHPStorm as IDE.

Everyone who does Drupal development will sooner or later encounter the need to define tighter control of access to content. The standard mechanisms of roles and permissions are very flexible, but they may be insufficient in complex projects. When access to nodes starts to depend on, for example, fields assigned to a given user, then you have to take advantage of more advanced solutions.