DrupalCamp NJ 2016

Progressive Decoupling and Drupal's Front-end Future

Update: This BoF is in room 111.

Recently there has been a great deal of discussion about the future of Drupal's front end, the drawbacks of fully decoupled Drupal, and how to achieve better UX and DX without jettisoning all of the things that make Drupal so great on the front end. Let's talk about what the future of Drupal's front end looks like for 8.x, 9, and beyond.

This will be a neutral and unopinionated BoF with no particular stance, so it is a discussion, not a debate. We want to hear everyone out without preconceptions, because after all, we all want to see Drupal succeed. Any and all are welcome, especially those with opinions on the subject!

Key questions are not at all limited to the following, but this is a starting point (please feel free to suggest other discussion questions on Twitter):

  • How should Drupal address increasingly demanding UX expectations (e.g. optimistic UI, non-blocking workflows, and especially immediate no-latency feedback and offline capabilities)?
  • How should Drupal address increasingly demanding front-end DX expectations?
  • Should Drupal adopt a client-side MV* framework or a view library?
  • Should Drupal adopt a server-side solution such as WebSockets (asynchronous PHP)?
  • Should Drupal focus solely on becoming API-first?

Required reading for background and to frame the discussion (familiarity with all of the following content will be presumed):

Further (optional) reading:

Advanced (sysadmin, module developer)
Birds of a Feather
Drupal 8

Diamond Sponsor

Platinum Sponsors

Corporate Supporters

Gold Sponsors

Silver Sponsors