This started out as a very modest project, and then it grew. Like Drupal 8 itself (to a much lesser extent, of course).
Mike Booth, Senior Cloud Software Engineer at Acquia, on tackling concrete problems, file systems, real world Drupal -- and the value of incremental improvement. Part 1 in a series.
With the official release of Drupal 8.0.0 on the horizon, "real world" Drupal 8 stories are becoming more valuable.
Now that the train is actually approaching the station, we all want to know what it will be like to get on.
Mediacurrent, a leading Drupal design firm, got their Drupal 8 ticket punched early. They partnered with Acquia to launch a Drupal 8 site for Manhattan Associates, a supply chain management software provider, back in August, 2015, when Drupal 8 was in beta. The site has been on the Drupal 8 frontier ever since.
So what has the experience been like?
A "real world Drupal 8" series from Mediacurrent and Acquia has been telling some backstories.
One of the most difficult parts of executing a successful round of usability testing can be recruiting participants.
The landscape of Drupal theme development has drastically changed in recent years. Cutting-edge front-end development tools are now considered standard within Drupal enterprise builds.
In our last post, we looked at why Manhattan Associates was happy with Drupal 8 from a front-end perspective. What sealed the deal for them, though, were the powerful ways they could extend and develop Drupal 8 with improved configuration management, a new Web services API, and easy internationalization.
In my last post, we discussed the advantages to getting a headstart on Drupal 8 before its official release.
This is the second and final installment in our series covering Acquia Global Support Team’s third-party API integration with Zendesk (part one covered Five Ways to Leverage Third-Party APIs: The Drupal-Zendesk Integration).
Security is very hard to bolt on to any software or product after it has been built. Building it into the core of the code helps to avoid mistakes, and thus the upcoming release of Drupal 8 tries to build in more security by default, while still being usable for developers and site builders. This list of 10 security improvements is not exhaustive - some are just a line or two to handle an edge case, and there are others I may have overlooked. I've contributed to a number of these improvements, but they reflect overall the community consensus as well as reactions to problems that required security releases for Drupal core or contributed modules in the past. For each point I've tried to include a link or two, such as the Drupal core change record, a documentation page, or a presentation that provides more information. Some of these may also be possible to back-port to Drupal 7, to benefit you even sooner. A "7.x back-port" link indicates that.
For context on why these 10 improvements are important, I looked at past security advisories (SAs) as well as considering the kind of questions we get here at Acquia from companies considering adopting Drupal. In terms of past SAs, cross-site scripting (XSS) is the most commonly found vulnerability in Drupal core and contributed modules and themes.