Zoom API

New Drupal Modules - 19 April 2017 - 7:35pm

Integration with the Zoom Video Conferencing Service.

Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-defined conference room solution into one easy-to-use platform. Our solution offers the best video, audio, and wireless screen-sharing experience across Windows, Mac, Linux, Chrome OS, iOS, Android, Blackberry, Zoom Rooms, and H.323/SIP room systems. Founded in 2011, Zoom's mission is to make video and web conferencing frictionless.

Categories: Drupal Re-activating Vote Up/Down

Planet Drupal - 19 April 2017 - 7:27pm

Vote Up/Down is a drupal module that uses Voting API to provide a way to vote.
These notes are about part of the history of the module, and the recent news about it, including a couple of releases!

A long time ago...

The project itself is really ancient, it started in 2006 by frjo, in Drupal 4.7, and the same code has evolved until Drupal 7.
I took co-maintainership of the project around 2009-2010, when I met with lut4rp, at the time the one maintainer of the project; who made a rewrite to modularize it at the start of 6.x-2.x.
At that time we were still using CVS officially (and some of us git locally), and we were thrilled to receive and integrate a patch from merlinofchaos, that extended the module a lot, and make it more maintainable.
With the past of the time, I became the only active maintainer of the module.

At the start I was pretty active as a maintainer there; but over the years, I have not been responsive enough, especially around the D7 port.
During that time the community provided several patches and finally amitaibu created a sandbox, that I end up integrating into the project.
Also, I managed to write another submodule, vud_field, in that process.
For me it was clear, I advocated to remove vud_node, vud_term, and vud_comment form the project in favour of vud_field.
From my perspective it was more beneficial: (a) vud_field provided mostly the same functionality on nodes, taxonomy terms, and comments; but also (b) provided voting on any entity, embracing D7 new APIs; and also (c) made things more maintainable.
Sadly, the removal did not happened at that time, and that was one of the reasons why D7 version was never out of alpha status.

Recent news

After quite some time of inactivity in vote_up_down, this January, I started to port the module to D8, but I only started: only 4 porting commits got into the new 8.x-1.x branch.

Then, I decided to add a GSoC project as student's suggestion to port Vote Up/Down to D8 for this year.

In preparation, this week I have branched out D7 into two different versions 7.x-1.x and 7.x-2.x, adding respective releases to make things more clear:

  • 7.x.1-x (with 7.x-1.0-beta1 release): It still keeps all submodules, but it is not planned to be maintained for much longer anymore. I applied there all related code pending about vud_node, vud_comment, and vud_term.
  • 7.x-2.x (with 7.x-2.0 release): Instead, it only contains vud and vud_field, and it is planned to be maintained as the stable branch. Sadly there in not a complete upgrade path neither from 6.x-2.x nor from 7.x-1.x, but I added some starting code to do that on the related issue #1363928, and maybe someone would like to continue that.

Hopefully one of the students proposing the port to Vote Up/Down to D8 gets accepted.
It will be great to see the module active again!

Categories: Drupal

Mediacurrent: Debug Drupal PHP in Vim with Vdebug

Planet Drupal - 19 April 2017 - 3:51pm

I know quite a few developers that love Vim but think they have to use an IDE to be able to debug their applications. In this post I will show you how to set up Vim as a Xdebug client.

The Vdebug plugin for Vim provides a way to do debugging inside Vim using the tools that Vim provides to great advantage. As the project page says,


Categories: Drupal

Aten Design Group: Radios, Checkboxes, and Drupal’s Admin Interface

Planet Drupal - 19 April 2017 - 3:09pm

Custom styled form elements are a common thing to see in a design. That’s because default form styles vary visually from browser to browser and OS to OS. It makes sense that we’d want these elements styled consistently. Styling them is pretty straightforward, with the exception of select dropdowns which can be more complex. Recently, I ran into an unexpected problem when working on a site that needed a branded admin experience.

Styling Radio and Checkbox Buttons

There’s a simple method of styling radio buttons and checkboxes I’ve been using for a while. I first saw it from the people at Tuts+, and they provided this Pen demoing the technique. Briefly explained, we visually hide the input for our radios/checkboxes and draw a new one using :before and :after pseudo elements on the label element. CSS’ :checked selector allows us to toggle our styles based on if the input is checked or not. This technique relies on appropriately marked up inputs and labels, for example:

<div class=”form-element”> <input type=”checkbox” id=”click-me”> <label for=”click-me”>Click Me</label> </div>

Clicking the label (containing the fake checkbox styling) will toggle the state of the real checkbox that’s visually hidden.

Drupal’s Admin Interface

One thing I learned while working with some of Drupal’s admin interfaces is that they only supply the input, and not an accompanying label. This seemed especially true in tabled interfaces, where you’d check off rows of content and perform some action on the selected items. Since we’re hiding an input that doesn’t have a label to attach the visuals to, we just end up with a blank space. There were several options we had for how to address this issue.

1. Drop the Custom Styles

The simplest is to just rely on browser defaults for checkboxes and radios. It’s not a great option, but it is an affordable one for tight budgets.

2. Create the Missing Labels

This ended up being my first approach to fixing this, and became more akin to a game of Whack-a-Mole than I anticipated. After going through various preprocess functions, alters, and render functions I was still encountering inputs that were missing labels. Some I was never able to fully track down where the markup was coming from. Manually finding and fixing every missing label might be a viable solution if your website or application has only a handful of places you need to update. However this is not the most scalable solution, and if your product grows this can quickly become a financial black hole.

3. Create the Missing Labels… with Javascript

Instead of trying to find every place that creates a checkbox or radio on the server side, we could use Javascript to target every checkbox or radio input that is not followed by a label. From there, we just create the label element and insert it after the selected inputs. This is how that might look using jQuery, though it can also be done with Vanilla JS.

This is great, as it solves the problem for every input in one fell swoop. One downside here is the Javascript dependency. Should your Javascript not run for any reason, you’re still left with the original problem of missing inputs. Another is page rendering. User’s might be left with a janky experience as Javascript inserts these elements into the DOM.

4. Drop the Custom Styles… for Older Browsers

In the end, this was the solution that won out. Using CSS Feature Queries and CSS’ appearance property, we’re able to provide styled inputs for most modern browsers and then fall back to default styles in browsers that lack the support we need. This gives us our custom styles, without the scaling problem of #2, and the Javascript dependency of #3. The downside to this solution is that all versions of Internet Explorer and Firefox will use their browser defaults.

Firefox was a surprise to me, as the documentation says it supports appearance. However in practice what I got was a less appealing version of the browser default styles. Also surprisingly was by checking for only -webkit-appearance support, Edge still gets our custom styles applied. This all sat well with me for a working solution. Every team and project has it’s own constraints, so your mileage may vary.

Categories: Drupal

Epic Nerd Camp Coming This August

Tabletop Gaming News - 19 April 2017 - 3:00pm
Many of you have memories of your time at some sort of summer camp. While I never went away to one, we did have a 5th Grade Camp thing we went away to for a week during school. Mostly, it was a way to get the kids out of the house for a bit during […]
Categories: Game Theory & Design

World War Flea Card Game Up On Kickstarter

Tabletop Gaming News - 19 April 2017 - 2:00pm
I’ve had pets that’ve had fleas before. By god are they annoying. And they get everywhere and multiply like you wouldn’t believe. Ugh, it’s awful and nobody (that I can think of) likes them. Certainly the dogs and cats that they bite don’t like them. That’s why they’re teaming up to take out an evil […]
Categories: Game Theory & Design

Fine Image Upload

New Drupal Modules - 19 April 2017 - 1:04pm
Categories: Drupal

Warforged: First Contact Board Game Up On Kickstarter

Tabletop Gaming News - 19 April 2017 - 1:00pm
Warforged: First Contact is a new sci-fi miniatures board game that’s up on Kickstarter now. In it, the human players are looking to infiltrate (well, “blast their way into” more appropriately) into an enemy alien stronghold. Of course, the further in they go, the tougher the aliens they’ll face are. Will they be able to […]
Categories: Game Theory & Design

Aten Design Group: Migrating Wordpress into Drupal 8

Planet Drupal - 19 April 2017 - 12:17pm

Quite a bit has changed for the Migrate module in Drupal 8: the primary module is part of core and some of the tools have been split into their own modules. Recently, we migrated a Wordpress site into Drupal 8 and this article will help guide you in that process. If you’re looking for information about Wordpress to Drupal 7 migrations, check out Joel Steidl’s article on that here.

At the time of writing this post, the migration modules are considered "experimental" so be aware of that as well. The module's location in core also means that all Drupal core modules also have migration-related code to help out with your Drupal upgrades. We used the WP Migrate module (Migrate Wordpress) as a starting point in bringing this content to Drupal.

This module will give you a good basis for migration, but it is missing a few things that you might want to consider:

  • It will create all vocabularies and taxonomies based on what is in Wordpress but you will need to add some code to connect the taxonomies with posts.
  • Also, it will not bring in featured images.
  • WP content might be using the "line break to paragraphs" functionality, which you need to account for either in your text format for posts or in the migration.

And if you are looking for information about Wordpress to Drupal 7 migrations, check out Joel Steidl's article on that here.


There's code existing to pull in Wordpress's terms and vocabularies, but you will need to do some work to put them into the right fields with your posts. For this, I ended up taking a more efficient route by querying the source database in prepareRow():

<?php   // place in Posts.php prepareRow()   // get terms for this blog post $tags = $this->select('wp_term_relationships', 'r') ->join('wp_term_taxonomy', 't', 't.term_taxonomy_id=r.term_taxonomy_id') ->fields('r') ->condition('t.taxonomy', 'tags') ->condition('object_id', $row->getSourceProperty('id'))->execute(); $tags = $tags->fetchAll(); $tags = array_map(function($tag) { return intval($tag['term_taxonomy_id']); }, $tags); $row->setSourceProperty('tags', $tags);   // get categories for this blog post $category = $this->select('wp_term_relationships', 'r') ->join('wp_term_taxonomy', 't', 't.term_taxonomy_id=r.term_taxonomy_id') ->fields('r') ->condition('t.taxonomy', 'category') ->condition('object_id', $row->getSourceProperty('id'))->execute(); $category = $category->fetchAll(); $category = array_map(function($tag) { return intval($tag['term_taxonomy_id']); }, $category); $row->setSourceProperty('categories', $category);

And then I updated the migration template with those new values:

# add to the process section field_tags: tags field_category: tags Featured Images

Wordpress stores featured images as attachment posts and stores the relationship in the postmeta table. To bring these in as image fields, we need to make file entities in Drupal which means configuring a new migration.

First, create a migration template called wp_feature_images.yml. Note that I stole some of this from Drupal's core file module:

id: wp_feature_images label: Wordpress Feature Images migration_tags: - Wordpress migration_group: wordpress source: plugin: feature_images destination: plugin: entity:file process: filename: filename uri: uri status: plugin: default_value default_value: 1 # migration_dependencies: # required: # - wp_users

And then create a source plugin:

<?php /** * @file * Contains \Drupal\migrate_wordpress\Plugin\migrate\source\FeatureImages. */   namespace Drupal\migrate_wordpress\Plugin\migrate\source;   use Drupal\migrate\Row; use Drupal\migrate\Plugin\migrate\source\SqlBase; use Drupal\Core\File\FileSystemInterface; use Symfony\Component\DependencyInjection\ContainerInterface; use Drupal\migrate\Plugin\MigrationInterface; use Drupal\Core\State\StateInterface;   /** * Extract feature images from Wordpress database. * * @MigrateSource( * id = "feature_images" * ) */ class FeatureImages extends SqlBase {   public function __construct(array $configuration, $plugin_id, $plugin_definition, MigrationInterface $migration, StateInterface $state, FileSystemInterface $file_system) { parent::__construct($configuration, $plugin_id, $plugin_definition, $migration, $state); $this->fileSystem = $file_system; }   /** * {@inheritdoc} */ public static function create(ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition, MigrationInterface $migration = NULL) { return new static( $configuration, $plugin_id, $plugin_definition, $migration, $container->get('state'), $container->get('file_system') ); }   /** * {@inheritdoc} */ public function query() { $query = $this ->select('wp_postmeta', 'm') ->fields('p', ['ID', 'guid']); $query->join('wp_posts', 'p', 'p.ID=m.meta_value'); $query ->condition('m.meta_key', '_thumbnail_id', '=') ->condition('p.post_type', 'attachment', '=') ->condition('p.guid', '', '<>') // this prevents some duplicates to get the count closer to even ->groupBy('ID, guid'); return $query; }   /** * {@inheritdoc} */ public function fields() { $fields = array( 'ID' => $this->t('The file ID.'), 'guid' => $this->t('The file path'), ); return $fields; }   /** * {@inheritdoc} */ public function prepareRow(Row $row) { $url = $row->getSourceProperty('guid'); $parsed_url = parse_url($url); $filename = basename($parsed_url['path']); $row->setSourceProperty('filename', $filename); $public_path = 'public://' . $parsed_url['path']; $row->setSourceProperty('uri', $public_path);   // download the file if it does not exist if (!file_exists($public_path)) { $public_dirname = dirname($public_path);   // create directories if necessary if (!file_exists($public_dirname)) { $this->fileSystem->mkdir($public_dirname, 0775, TRUE); }   // try to download it $copied = @copy($url, $public_path); if (!$copied) { return FALSE; } } return parent::prepareRow($row); }   /** * {@inheritdoc} */ public function bundleMigrationRequired() { return FALSE; }   /** * {@inheritdoc} */ public function getIds() { return array( 'ID' => array( 'type' => 'integer', 'alias' => 'p', ), ); }   }

In Migrate, the template defines what source, processing, and fields are created. The source plugin is used by that migration to allow you to specify what is created. The source plugin above will get the feature images for posts, but also try and download the image into Drupal's files directory.

You can add this as a dependency for the wp_posts migration. A word of warning though: if one migration (Migration A) depends on a different migration (Migration B), all of the content from A must be migrated before B can be run. If there are images that cannot be resolved for some reason (maybe leftover DB references after an image or post is deleted), this might stop the migration because the dependency cannot be resolved.

And finally, you will also need to add "wp_feature_images" to your manifest_wordpress.yml before running the migration.

Converting content

So far we have updated migration source plugins, but there are also process plugins, which can be used to change row values. As mentioned, the WP content often uses the autop filter to create paragraph/line breaks automatically so we need to change those to HTML for Drupal. (You can also just use this functionality in your text format and skip this step if having this on will not cause issues with other content)

First, create a "src/Plugin/migrate/process" directory if one does not exist in the module and add this processor:

<?php   namespace Drupal\migrate_wordpress\Plugin\migrate\process;   use Drupal\migrate\MigrateExecutableInterface; use Drupal\migrate\ProcessPluginBase; use Drupal\migrate\Row;   /** * Apply the automatic paragraph filter to content * * @MigrateProcessPlugin( * id = "wp_content" * ) */ class WpContent extends ProcessPluginBase {   /** * {@inheritdoc} * * Split the 'administer nodes' permission from 'access content overview'. */ public function transform($value, MigrateExecutableInterface $migrate_executable, Row $row, $destination_property) { return _filter_autop($value); }   }

Then, update the "process" section of "wp_posts.yml" to include this processor:

'body/value': plugin: wp_content source: post_content

All of this should put you on the road to getting Wordpress content migrated into a Drupal 8 site, although you’ll probably have to adjust code to your specific circumstances along the way.

Categories: Drupal

Awaken RPG Now Available Digitally

Tabletop Gaming News - 19 April 2017 - 12:00pm
It’s always nice to see games that were funded via Kickstarter end up for general sale. In this case, it’s the Awaken RPG from The Games Collective. Print editions will be forthcoming, but they’ve got the digital version available now for your downloading and reading pleasure. From the announcement: Awaken, a roleplaying game made by […]
Categories: Game Theory & Design

Midweek Snippets

Tabletop Gaming News - 19 April 2017 - 11:00am
The week continues on. Most of my friends had a really busy weekend, so they’re having a bit of a time making it through the week. But it’s halfway over. The next weekend is making its way here as fast as the natural laws of time will allow. What might help is by filling up […]
Categories: Game Theory & Design

eSports to join 2022 Asian Games as a medal-eligible sport

Social/Online Games - Gamasutra - 19 April 2017 - 10:56am

The Olympic Council of Asia is seemingly eyeing sports titles like FIFA and both multiplayer online battle area and real-time strategy games for inclusion in future Asian Games events. ...

Categories: Game Theory & Design

Lacquered Coffins WWII Air Combat Game Now Available

Tabletop Gaming News - 19 April 2017 - 10:00am
During WWII, over many battles, another battle was taking place. Planes of all sorts, from scout planes to agile fighters to bombers were fighting their own war. Lacquered Coffins lets you relive those days of close-combat dogfights with their simple set of aerial combat rules. About the game: Ostfront publishing is excited to announce the […]
Categories: Game Theory & Design

Acquia Developer Center Blog: Acquia in action at DrupalCon Baltimore!

Planet Drupal - 19 April 2017 - 9:01am

If you’re coming to DrupalCon Baltimore and you’re curious about Acquia, there are a couple of ways to meet the company and see what we’re about beyond the marketing and sales efforts that get directed at potential clients. One great way is to come to our sessions!

Tags: acquia drupal planet
Categories: Drupal

Tequendria RPG Now Available

Tabletop Gaming News - 19 April 2017 - 9:00am
When many of us think of a “Fantasy RPG world,” we think of something rather Tolkien-esque. But there are plenty of other fantasy writers out there that can be used as inspiration for your game. One such is Lord Dunsany. His works are certainly different from Tolkien’s. Now, you can head into that world in […]
Categories: Game Theory & Design

ThinkShout: Meet the ThinkShout Team at DrupalCon Baltimore

Planet Drupal - 19 April 2017 - 9:00am

We’re packing our bags for Baltimore and polishing up our slide decks for DrupalCon! We’re so excited to join the Drupal community for a full week of Drupal-y things. We’ve got some great content planned for this year’s conference, and we’re very excited to share it with you all - here’s what you need to know:

Exhibit Hall

The ThinkShout Headquarters this year is booth 432! We’ll be giving away free t-shirts and raffling off an Amazon Echo. You can enter to win for the low, low price of one business card. If you have any questions about our work, current available job opportunities, or what the weather’s like in Portland (spoiler: it’s probably raining), stop by - we’d love to chat with you!

ThinkShout Sessions

The ThinkShout team has two sessions in the DrupalCon agenda this year. We’re also very excited to be leading a discussion in our first DrupalCon Nonprofit Summit. Take a look at our lineup and mark your calendars

Rapid Response Campaigns & Digital Tools” - Monday (4/24), 12:30 - 1:15pm, Nonprofit Summit

The news cycle doesn’t stop, and your website must help you respond to emergencies, not act as a barrier. Drupal can help you react quickly, in concert with your other channels, to turn current events into opportunities to spread your message and further your mission. In this breakout session, Brett Meyer and Lev Tsypin will talk about the tools you have at your disposal in Drupal, scenarios that call for rapid response solutions and how to implement them, and strategies that will help you turn these situations into lasting engagement with your constituents.

Demystifying Rendered Content in Drupal 8 Twig Files” - Tuesday (4/25), 3:45 - 4:45pm

Amy Vaillancourt-Sals is going to show you the ins and outs of Twig! Twig is a robust and elegant template engine for PHP. It’s lightweight, fairly quick to pick up, very readable, and it grants users ultimate control over the markup, including wrapping elements and rendering exactly the output you need. In this session, you’ll learn about the debugging process of sorting through twig variables, using xdebug in PHPStorm, the other helpful debugging tools at your disposal, plus common patterns Amy found helpful for rendering content in twig files.

Content Strategy in Popular Culture, Part Deux” - Thursday (4/27), 10:45 - 11:45am

Brett Meyer’s got a sequel to his session from DrupalCon New Orleans. Another year, another array of pop culture obsessions to examine and apply to the work we do. By exploring how crucial aspects of content strategy play out in movies, music, comic books, and video games, we’ll continue to expand the palette of language we can use to explain and convince more people about the importance of content strategy online, and ensure they understand that it’s not just vital, but fun as well.

Let’s Chat

If you’d like to schedule some time to chat with us in advance, drop us a line via our contact form. We’d be happy to meet up with you in Baltimore!

Categories: Drupal

Asmodee Announces New Expansion for Kharnage

Tabletop Gaming News - 19 April 2017 - 8:45am
Your army is determined to take that hill. Why do you want it? Because, apparently, your opponents want it. And you’ll be damned if you let even the most insignificant hill fall into enemy hands. But the fight isn’t going well, and you need to change up your strategy. Maybe grab some mercenaries or employ […]
Categories: Game Theory & Design

Lullabot: Cross-Pollination between Drupal and WordPress

Planet Drupal - 19 April 2017 - 8:27am

WordPress controls a whopping 27% of the CMS market share on the web. Although it grew out of a blogging platform, it can now can handle advanced functionality similar to Drupal and is a major (yet friendly) competitor to Drupal. Like Drupal, it’s open source and has an amazing community. Both communities learn from each other, but there is still much more to share between the two platforms.

Recently I had the opportunity to speak at WordCamp Miami on the topic of Drupal. WordCamp Miami is one of the larger WordCamps in the world, with a sold-out attendance of approximately 800 people.

undefined What makes Drupal so great?

Drupal commands somewhere in the neighborhood of 2% of the CMS market share of the web. It makes complex data models easy, and much of this can be accomplished through the user interface. It has very robust APIs and enables modules to share one another’s APIs. Taken together, you can develop very complex functionality with little to no custom code.

So, what can WordPress take away from Drupal? Developer Experience: More and better APIs included in WordPress Core

The WordPress plugin ecosystem could dramatically benefit from standardizing API’s in core.

  • Something analogous to Drupal’s Render API and Form API would make it possible for WordPress plugins to standardize and integrate their markup, which in turn would allow plugins to work together without stepping on each other’s toes.
  • WordPress could benefit from a way to create a custom post type in the core UI. Drupal has this functionality out the the box. WordPress has the functionality available, but only to the developer. This results in WordPress site builders searching for very specific plugins that create a specific post type, and hoping it does what they want.
  • WordPress already has plugins similar to Drupal’s Field API. Plugins such as Advanced Custom Fields and CMB2 go along way to allowing WordPress developers to easily create custom fields. Integrating something similar to this into WordPress core would allow plugin developers to count on a stable API and easily extend it.
  • An API for plugins to set dependencies on other plugins is something that Drupal has done since its beginning. It enables mini-ecosystems to develop that extend more complex modules. In Drupal, we see a module ecosystems built around Views, Fields, Commerce, Organic Groups, and more. WordPress would benefit greatly from this.
  • A go-to solution for custom query/list building would be wonderful for WordPress. Drupal has Views, but WordPress does not, so site builders end up using plugins that create very specific queries with output according to a very specific need. When a user needs to make a list of “popular posts,” they end up looking through multiple plugins dedicated to this single task.

A potential issue with including new APIs in WordPress core is that it could possibly break WordPress’ commitment to backwards compatibility, and would also dramatically affect their plugin ecosystem (much of this functionality is for sale right now).

WordPress Security Improvements

WordPress has a much-maligned security reputation. Because it commands a significant portion of the web, it’s a large attack vector. WordPress sites are also frequently set up by non-technical users, who don’t have the experience to keep it (and all of its plugins) updated, and/or lock down the site properly.

That being said, WordPress has some low-hanging fruit that would go a long way to help the platform’s reputation.

  • Brute force password protection (flood control) would prevent bots from repeatedly connecting to wp-login.php. How often do you see attempted connections to wp-login.php in your server logs?.
  • Raise the minimum supported PHP version from 5.2 (which does not receive security updates). Various WordPress plugins are already doing this, and there’s also talk about changing the ‘recommended’ version of PHP to 7.0.
  • An official public mailing list for all WordPress core and plugin vulnerabilities would be an easy way to alert developers to potential security issues. Note that there are third-party vendors that offer mailing lists like this.
Why is WordPress’ market share so large?

Easy: It can be set up and operated by non-developers—and there are a lot more non-developers than developers! Installing both Drupal and WordPress is dead simple, but once you’re up and running, WordPress becomes much easier.

Case in Point: Changing Your Site's Appearance

Changing what your site looks like is often the first thing that a new owner will want to do. With WordPress, you go to Appearance > Themes > Add New, and can easily browse themes from within your admin UI. To enable the theme, click Install, then click Activate.


With Drupal, you go to Appearance, but you only see core themes that are installed. If you happen to look at the top text, you read in small text that "alternative themes are available." Below that there is a button to “Install a New Theme.”


Clicking the button takes you to a page where you can either 1) paste in a URL to the tarball/zip, or upload a downloaded tarball/zip. You still have to know how to to download the zip or tarball, and where to extract it, and then browse to appearance, and enable the theme.

So it goes with Drupal. The same process goes with modules and more. Drupal makes things much more difficult. 

So, what can Drupal learn from WordPress?

To continue to grow, Drupal needs to enable non-developers. New non-developers can eventually turn into developers, and will become “new blood” in the community. Here’s how Drupal can do it:

  • A built in theme and module browser would do wonders for enabling users to discover new functionality and ways to change their site’s appearance. A working attempt at this is the Project Browser module (available only for Drupal 7). The catch 22 of this is that you have to download this the old-fashioned way in order to use it.
  • The ability to download vetted install profiles during the Drupal installation process would be amazing. This would go a long way to enable the “casual explorers," and show them the power of Drupal. A discussion of this can be found here.
  • Automatic security updates is a feature that would be used by many smaller sites. Projects have been steered toward WordPress specifically because smaller clients don’t have the budget to pay developers to keep up with updates. This feature has been conceptually signed off on by Drupal’s core committers, but significant work has yet to be done.
Mitigating Security Risks

The downside for this functionality is that Drupal would need to have a writable file-system, which at it’s core, is less secure. Whether that balances out with automatic updates is debatable.

Automatic security updates and theme/module installation would not have to be enabled out of the box. The functionality could be provided in core modules that could be enabled only when needed.

What has Drupal already learned from WordPress?

Cross-pollination has already been happening for a while. Let’s take a look at what the Drupal community has already, or is in the process of, implementing:

  • Semantic versioning is one of the most important changes in Drupal 8. With semantic versioning, bug fixes and new features can be added at a regular cadence. Prior to this, Drupal developers had to wait a few years for the next major version. WordPress has been doing this for a long time.
  • A better authoring experience is something that Drupal has been working on for years (remember when there was no admin theme?). With Drupal 8, the default authoring experience is finally on par with WordPress and even surpasses it in many areas.
  • Media management is the ability to upload images and video, and easily reference them from multiple pieces of content. There’s currently a media initiative to finally put this functionality in core.
  • Easier major version upgrades is something that WordPress has been doing since it’s inception.

Drupal has traditionally required significant development work in between major versions. That however, is changing. In a recent blog post, the lead of the Drupal project, Dries Buytaert said,

Updating from Drupal 8's latest version to Drupal 9.0.0 should be as easy as updating between minor versions of Drupal 8.

This is a very big deal, as it drastically limits the technical debt of Drupal as new versions of Drupal appear.


Drupal and WordPress have extremely intelligent people contributing to their respective platforms. And, because of the GPL, both platforms have the opportunity to use vetted and proven approaches that are shortcuts to increased usability and usage. This, in turn, can lead to a more open (and usable) web.

Special thanks to Jonathan Daggerhart, John TuckerMatthew Tift, and Juampy NR for reviewing and contributing to this article.

Categories: Drupal

Migrate Joomla

New Drupal Modules - 19 April 2017 - 8:15am

Migrate from Joomla 3.5 to Drupal 8 with this extension of the core Migrate module (requires migrate_plus).

Categories: Drupal

Fantasy Flight Games Announces Legend of the Five Rings LCG

Tabletop Gaming News - 19 April 2017 - 7:55am
This is one I’ve been waiting for. A while ago, Fantasy Flight Games announced that they were taking over the license for the Legend of the Five Rings card game. They were going to make it a Living Card Game and relaunch it at Gen Con 2017. It seemed so far away, then. But it’s […]
Categories: Game Theory & Design


Subscribe to As If Productions aggregator