Coding + Development
Until version 7, Drupal was a careless entity that always had a tendency to ignore developer’s plea and patience. But now, with an innovative touch of Symphony, Drupal has started taking care of the pitiful developers. This care and concern comes with the advent of a solution called Configuration Management. Drupal developers always had problems managing config settings from Dev to Live environment. But, there was one thing that came to their rescue, called Features. But, was this a good enough solution ?
Drupal's strength as a content management framework is in its ability to effectively manage and display structured content through its Web user interface. However, the out-of-the-box system assumes all data is local (stored in the database). This can present challenges when attempting to integrate remote data stored in other systems. You cannot, by default, display non-local records as pages. While setting this up is in itself a challenge, it is an even bigger challenge to manipulate, aggregate and display this data through Views.
Drupal 8 has introduced a number of new (to Drupalists) technologies, but embedded in this mix are a handful of Drupal-centric innovations. Amongst the first of these to be introduced to Drupal 8 was the Plugin system. The Plugin system is a far reaching PHP Component that has largely replaced the old hook_info/alter pattern within Drupal and can be used outside of Drupal as well.
As the PHP renaissance continues to change how developers work with PHP, Drupal has made significant strides toward adopting PHP’s new best practices in both code and interoperability. New groups focussed on the interoperability of disparate PHP projects have begun to get traction producing such standards as PSR-0 and PSR-4 while others work to model a reusable request/response layer (yielding PSR-7).
Behat is a functional testing framework that facilitates behavior driven development in PHP. It's approach to functional testing is intuitive and powerful. Using Behat can immensely improve the stability of your projects and your development workflow.
Even though it's been around since 2010 and has earned widespread adoption in the Drupal community, many of us haven't had the time or opportunity to get started with it yet. If that's you, then it's time to level up!
Drupal’s content editing experience is key for content administrators who use it to publish information daily. But many Drupal sites suffer from either too many content types, with too many restrictions on what content can do within them — or too few content types, with too much reliance on admins having an advanced knowledge of HTML and/or a developer they can contact when iffy formatting code breaks a page.
There is very little information about remote entities available, making them a little-understood but much talked about solution for integrating external data.
For this session Dave and Colan will discuss what remote entities are, when they make sense, and how we could come together as a community to create a more mainstream solution.
Topics will include:
Managing 10, 100, 1,000+ websites for your organization? Having a hard time verifying that the look and feel of all sites is intact after an update? This session discusses how automated regression testing can be used to verify site integrity and help put an end to “deploy and pray” practices.