Blog posts archive

October 2017

WCMS update for October 2017

In this issue:

  • Working with files in the WCMS
  • Accessibility webinars
  • Survey and voting tools

WCMS Web Dev Rev wrap-up for October 27, 2017

WCMS Web Dev Rev

At this week's Web Dev Rev, we started by looking at: Mainspring, a component-driven prototyping tool using Pattern Lab; a TWIG filter for Drupal 8 to show date ranges in as short a format as possible; the plan for contrib modules for Media now that Media Entity API is in Drupal 8 core; a call for help with Media source plugin porting; a note that timestamp fields in Drupal 8 now universally use ISO timestamps; a look at JavaScript-related changes in Drupal 8.4 and beyond; notes on effective use of the drupal.org issue queue (link no longer available); Drupalize.me's full set of Acquia certification exam guides; find conferences using Conference Radar; a collection of design resource sites; a guide to essential image optimization; a look at the fundamentals of responsive images; EFF's Certbot for Let's Encrypt; and finally, some code review etiquette.

WCMS Web Dev Rev wrap-up for October 13, 2017

WCMS Web Dev Rev

This week, regular Web Dev Rev host Kevin Paxman was on vacation, so in his place, guest host Eric Bremner from the WCMS dev team had these Web Dev Rev notes: Microsoft Edge bugs can be reported by Tweet; Microsoft Edge announced for iOS and Android, and what that really is underneath; how to port commands to Drush 9; a closer look at the Drupal out of the box initiative; what eBay's web font loading strategy (link no longer available) looks like; Drupal's new Creative Commons image library; and finally, how to use Drupal's Queue API.

WCMS Web Dev Rev wrap-up for October 6, 2017

WCMS Web Dev Rev

This week, Web Dev Rev guest host Tyler Struyk brought forward the following Drupal-related Web Dev Rev notes: Drupal 8.4.0 was released and there are release notes; some notes on how to use the new Media features in Drupal 8.4.0; Dries posts on Drupal looking to adopt React; the proposal to use React for Drupal's administrative UIs; the Drupal business survey results; and finally, the Drupal Community Governance survey results and call to action.