Drupal State and the Need for a JavaScript SDK

With JSON:API, Drupal offers an extremely low friction approach to make content from Drupal available to any consuming application. However, Drupal doesn't currently offer any tools to make consuming this data in a JavaScript front end just as frictionless. This leads to developers repeatedly solving the same problems in decoupled builds, and may also contribute to the perception that Drupal isn't JavaScript friendly.

Drupal State aims to bridge this gap by offering a common set of framework agnostic utilities that allow JavaScript developers with limited knowledge of Drupal or the JSON:API spec to take advantage of the best features of Drupal’s APIs. This session will examine the concepts behind Drupal State, along with the role a library like Drupal State could play within the wider Decoupled Drupal ecosystem, including:

- How Drupal State helps reduce the time necessary for JavaScript developers to start experiencing the benefits of Drupal as a decoupled CMS.
- How individual Drupal State utilities could be consumed by other Decoupled Drupal projects.
- Why having an SDK-like library available under the @drupal namespace on NPM is important for the future of Drupal.
- A proposal for how that core library could help support a future ecosystem of Drupal-friendly components and starter kits.

Last but not least, we'll wrap up with the ways in which Drupal State needs community support, including how you can contribute at DrupalCon and beyond.