>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3269948. --> Reported by: [andrewozone](https://www.drupal.org/user/3430095) >>> <p>Monthly Meetup for March 2022 - <a href="https://www.meetup.com/Fox-Valley-Drupal/events/hghbgsydcfbvb/">https://www.meetup.com/Fox-Valley-Drupal/events/hghbgsydcfbvb/</a></p> <p>Intro Slides: <a href="https://docs.google.com/presentation/d/1n4YXVT18QxOO-4mEs7WE4Qk2jqaUI-XatqbjQUbyaJM/edit?usp=sharing">https://docs.google.com/presentation/d/1n4YXVT18QxOO-4mEs7WE4Qk2jqaUI-XatqbjQUbyaJM/edit?usp=sharing</a></p> <p>Notes: <a href="https://pad.drutopia.org/p/Fox_Valley_Drupal_Meet_Up_2022-03-16">https://pad.drutopia.org/p/Fox_Valley_Drupal_Meet_Up_2022-03-16</a></p> <p><strong>Make comment on the issue for participation credit!</strong></p> <h2>Presentation: Drupal State and the Need for a JavaScript SDK by Brian Perry</h2> <p>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.</p> <p>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:</p> <ul> <li>How Drupal State helps reduce the time necessary for JavaScript developers to start experiencing the benefits of Drupal as a decoupled CMS.</li> <li>How individual Drupal State utilities could be consumed by other Decoupled Drupal projects.</li> <li>Why having an SDK-like library available under the @drupal namespace on NPM is important for the future of Drupal.</li> <li>A proposal for how that core library could help support a future ecosystem of Drupal-friendly components and starter kits.</li> </ul> <h2>About the Speaker</h2> <p><a href="https://www.drupal.org/u/brianperry">Brian Perry</a> is a versatile developer with experience building complex, interactive web applications in support of large-scale localized sites. Recently he has focused his efforts on evolving Drupal front-end development practices, decoupled Drupal, and design systems and has spoken on the topic at various Drupal events. Brian is a Drupal 7 and Drupal 8 Acquia Triple Certified Drupal Expert and loves all things Nintendo.</p> <h2>Agenda</h2> <ul> <li>Social Time and Introductions</li> <li>Announcements</li> <li>Presentation: Drupal State and the Need for a JavaScript SDK</li> <li>Q&amp;A with Brian Perry</li> <li>Wrap Up</li> </ul>