When UGC was added, usage of Views was tried, but abandoned: https://github.com/ezsystems/repository-forms/pull/62. Given that frontend content editing will serve as the basis for UI content editing, it could be valuable to explore that option again.

The most obvious benefit of having a content_edit view is override: custom controllers and templates can easily be set for content editing, and may make the whole system easier to configure for us as well as for implementors. For instance, a custom template could be used to edit articles. In our case, it would allow us to override the content edit template when in the admin.

This spike should determine:

• if this approach allows for a good integration in hybrid UI
• if it is reasonably feasible (changes to matchers, configuration...)
• other questions