DrupalCon Nashville 2018: What's possible with WordPress 5.0

Wordpress By Builder

SLIDES: https://docs.google.com/presentation/d/11PEgmoaKUFMWw7d4OwTBsYlVVeUaq2TgyBKqgYu9srY/edit?usp=sharing

script type="text/javascript" src="http://aos-creative.prf.hn/creative/camref:100l3Rd/creativeref:10l3694">

Drupal has a sibling CMS. WordPress runs on the LAMP with a mix of code written yesterday and code written in the early 2000s. WordPress is currently undergoing a major modernization of the code that controls the editorial experience. The WordPress community’s angst and excitement over the upcoming WordPress 5.0 release and its React-based Gutenberg editor feel a lot like the build up to Drupal 8.

Drupal and WordPress are similar enough that they face the same technical and cultural questions. Yet WordPress is also different enough so as to challenge our assumptions about how we answer them:

Will a large and diverse community of PHP-centric developers embrace React?
Can contrib code keep up with drastic changes to an admin UI?
Would the ability to schedule deployments of config changes help site owners?
What are the repercussions of supporting older versions of PHP?
How much modernization can a toolchain take while still claiming backwards compatibility?

source