Issue 210 - October, 8th 2015

News

Drupal 8.0.0-RC1 Released

The first Drupal 8 release candidate was released this week!

Drupal Association Board Meeting: September 23, 2015

There were some cool announcements at this meeting last month including that Drupal 8 Accelerate was fully funded.

Rogue Wave Software Acquires Enterprise PHP Leader Zend

In PHP news Zend was acquired.

Submit Your Session for DrupalCon Asia

From Our Sponsor

Articles

Drupal's Recent Twitter Vulnerability Underscores Importance of Continuous Monitoring

Headless Drupal & Node.js | Part 2/3: Node.js

Part two of the series “Headless Drupal & Node.js” where Joris Snoek shows us "Hello Node".

Understanding Drupal Security Advisories: Vulnerability Type

"This is the second in a series of articles about how to better understand all the information in a security advisory, so that you know how to take the appropriate action for your site!"

Drupal 8

Change: Libraries Can Now Be Overridden and Extended by Themes

Change: Move Vendor Directory to the Project Root

Change: Page Title Is Now a Block

Drupal 8 "RC Target" Versus "RC Deadline" Issue Tags

"A quick note for core contributors regarding Drupal 8 issue tags related to the upcoming release candidate phase."

Drupal 8 Hall of Fame

A very cool floor decal celebrating the top 1000 contributors to Drupal 8. Paul also has made a PDF version available.

Drupal 8 Has a Stable Base Theme

The purpose of this theme in Drupal 8 is to provide a stable base theme with 8.0.0 markup, CSS, JavaScript. This will prevent breakage of themes from Drupal 8 upgrades.

What Is BigPipe and What Does It Mean for Future Drupal Performance?

A discussion of Drupal 8 caching and Drupal performance.

Tutorials

Custom Image Search with Solr, Filefield Sources, and Ctools - Part 1

How to Get a Views & Panels Site to Work with Workbench Moderation

Projects

How Can We Know if a Page in Drupal 8 Has Changed?

With CacheTag Notify module! This module offers a simple settings page where an endpoint URL can be added. Then every time a cache tag is invalidated it gets POSTed to the endpoint as a JSON string.