In the original issuethe investigation/feedback step is missing from the process. From the previous thread what needs to be addressed is enabling a standard way to do optimistic feedback (aka progressive decoupling).
This issue is about gathering this feedback properly so we can agree on the scope of what this thing should be. Starting with looking at where and how a frontend framework could be used for in Drupal admin UI.
As attiks said in the other thread:
Maybe a first step is to create separate issues and define a single use case in each so we have a list of pain points, this will make it easier to define what needs to be solved and how it might be solved.
- Investigate potential frameworks and agree on the criteria to select such a framework.
- Demonstrate that such a framework would work for our situation (Create proofs of concept).
- Determine when the frameowkr should be implemented and implement it.
User interface changes
The child issue is ignoring all the UX work needed to achieve some of the goals. In any case the amount of JS work will be tiny (whatever solution we choose, including custom) compared to the amount of work needed to come up with a design and agree on it.
Application-like UIs in Drupal (e.g. Views UI and block placement) would benefit from a standard framework to enable a fluid experience.
Data model changes