Drupal

Alondra de la parra. Photo by Deutsche Welle.

I'm not intended to push until I get that new Composerizing verb to be into the dictionary, but I wan't to leave track of my experience about how to implement Composer on our old Drupal projects where it wasn't used before, and why move to this new work schema so maybe some developers who were habituated to work with older versions of Drupal, and I'm talking about Drupal 7 and early versions of 8, can find here a useful reference to guide them through their way to truth and happiness. (!)

Demonstration code as shown by Symfony's VarDump

Every Drupal 7 developer in ways of expanding its knowledge to work now with Drupal 8 will find out a not so pleasing surprise when working with the Devel module, this essential and powerful tool that simplifies a lot the debugging work of custom modules and themes. That's because in Drupal 7 we got the almighty dsm and dpm functions to query the values on variables, arrays and objects in a single line of code.

Old typewriting machine

I have decided to write this entry because in the past few days I exploring the RESTful module of Drupal 8 to publish some contents from an outer source and I found myself on a confusing situation, even when there are already many tutorials and documentation about it, which however may have become already obsolete in certain way as the RESTful module has transformed since the beginning (as the one and only Dries Buytaert explained in his website).

Lego construction blocks

Drupal has the ability to mount multiple websites within one single Drupal instance. How is convenient to use this feature? It's a great idea to consider when we have several sites which shares similar features. For instance, if we have several websites where we must implement the same modules or share one same visual theme, it could be convenient to integrate them as part of a Drupal multisite. The advantage of doing that is the maintenance tasks become easier when updating the Drupal core and its modules.