The ezplatform-standard-design package must ensure that the kernel's templates can be overridden using the design engine. The outcome should be that any template from our packages can be customized by an integrator by redefining them in their own, enabled design.

Expectations

As an eZ Platform integrator, I can replace templates used by eZ Platform

Given any template from the following packages:
  "ezsystems/ezpublish-kernel"
  "ezsystems/repository-forms"
  And an URI that uses a given template from those packages
 When I copy that template to the same path inside "app/Resources/views/themes/standard"
  And I render that URI
 Then my copy is used instead of the original template

Possible approach

Make existing templates part of the standard design.

First, we must add the existing templates directories (such as kernel's) to the standard design. ezplatform-design-engine has support for that:

ezdesign:
  templates_theme_paths:
      standard:
        - "%kernel.root_dir/../vendor/ezsystems/ezpublish-kernel/eZ/Bundle/EzPublishCoreBundle/Resources/views"
        - "%kernel.root_dir/.../vendor/ezsystems/ezpublish-kernel/eZ/Bundle/EzPublishDebugBundle/Resources/views"

We may want to add those templates directories from the package they are defined in, since ezplatform-design-engine will error out if a path that doesn't exist is added to this list.