DrupalCon is an exciting time. Lots of talks, lots of sessions and topics to attend. However making sure you see everything and anything you want can be stressful as well. So what should you attend to make the most of this DrupalCon experience?
Fear not, I am back to give you some of the highlights of an amazing week packed with talks, learnings, surprises and more.
And with the quantity and high quality of the sessions this year, no matter your interests, be…
In a previous installment of Experience Express, we explored how effective core REST out of the box can be for the purposes of consuming content retrieved from Drupal and manipulating said data as well. Furthermore, with the help of Views, any content listing can be easily converted into an API resource. As these features indicate, Drupal 8 is a powerful web services provider that can expose content to any consumer application on any channel.
Nonetheless, sometimes…
As we saw in a previous installment of Experience Express, because Drupal has a HAL-compliant REST API available out of the box with minimal configuration, you can easily provision an API that can immediately be employed to consume content entities and manipulate them from other applications. Now that we have successfully exposed content entities as REST resources, used Entity Access to govern permissions, and customized the formats and authentication mechanisms in use…
Perhaps the most critical piece of any decoupled CMS architecture is the API layer which exposes data in the back end for consumption by other applications. In Drupal's case, the REST module (also known as the RESTful Web Services module) in Drupal 8 core fulfills this responsibility. The REST module contains important logic that drives the availability of data through formatted responses.
Nevertheless, in many cases, what is provided in Drupal core might not be the…
