While ezsystems/ezplatform-design-engine has been part of the ezplatform requirements, it has no default configuration, and isn't used by our own packages.

This story aims at defining that default configuration, with a standard design. In addition, the templates used by the kernel should be made configurable with it.

Benefits

• Any of our templates that uses the ezdesign namespace becomes very easily overridable by customers.
• Allows us to make our own features, such as custom tags, customizable without any extra code.
• Provides customers with the basics for hierarchical templates override, as in legacy

Tasks

• Create the specification