Voting starts in March for the Drupal Association Board election.
The scope of this issue is currently limited solely to site building and content administration UIs within the admin experience, such as Views UI, Field UI, and block placement. Nonetheless, UIs for authenticated users that lie outside the confines of admin themes, such as Quickedit, Toolbar, and Contextual Links, would also benefit from a new unified framework.
Seefor emerging discussion on where and how a framework superseding Backbone would be used.
Key Drupal contributors have teamed up with experts on important client-side frameworks (including Angular 2, Ember, and Elm) to produce a comparison matrix to help determine what framework would be most appropriate for Drupal core. The matrix assesses Angular 2, Ember, React, Elm, and a few less promising frameworks: Backbone, Angular 1 and Knockout.
- Are these the correct criteria with which to evaluate client-side frameworks to supersede Backbone (for progressive decoupling)?
- Are there other frameworks that meet our minimum criteria?
- Are the conclusions we’ve made about these criteria appropriate?
- Develop proofs of concept that show the right framework for the job of controlling those UIs to be amended while still preserving key functionality (e.g. Drupal configuration, themes, and localization).
- Determine when / in which Drupal version (8.1? 8.2? 9.0?) to add the framework. Note that core code can’t leverage the framework until the framework is in core.
- Reach out to framework maintainers to resolve any considerations around licensing, release cadence, and inter-project cooperation.
- Draft a change notice similar to that created for Backbone adoption.
User interface changes
Leveraging the chosen framework to improve core UIs would be separate follow-up issues.
Data model changes
TBD, but likely none.