Currently ContentViews and ContentPresenter APIs are tightly coupled to concrete JCR containers and - and even JCR adapters or util in the case of tree view's inplace editing.

Responsibilities and APIs should be reconsidered between what belongs to workbench vs. what belongs to content presenters, so that config-wise, there would be almost no difference between registering e.g. tree view for a JCR workbench or Filesystem workbench.

Ideally we can do something like ContentPresenter.start(ContentPresenterDefinition, Container containerDataSource).

More info in linked concept page (Level 4)