Details
-
Story
-
Resolution: None
-
High
-
None
-
None
-
[2.2] Sprint 6
-
2
Description
With this story, the design engine should be fully integrated to eZ Platform, for the frontend and backend.
ezsystems/ezplatform-standard-design package
This package sets the default configuration for ezplatform-design-engine.
It defines a standard theme, and make existing templates (kernel & repository forms) part of this theme. How the second part can be achieved is described in EZP-28870.
app design
The frontend app uses the standard theme, as well as an app one, in an app design. This is configured in the meta-repositories:
ezdesign: design_list: app: [app, standard] ezpublish: system: frontend: design: app
The app theme is mapped by default to app/Resources/views.
admin theme & design
The admin-ui needs to use the "admin" design, that uses the standard + admin themes:
ezpublish: system: admin: design: admin ezdesign: design_list: admin: ["admin", "standard"]
Existing templates in the admin-ui must be loaded through the design engine. There is an open pull-request by Edi Modric that does this, but it moves templates around, in a themes/admin directory. We suggest that the app/Resources/views directory is instead mapped to the admin theme, using the ezdesign configuration.
Acceptance
Background: Given that my frontend uses the "app" design And the "app" design contains the "app" and "standard" themes Scenario: the design engine can load app templates When I create a template in {{app/Resources/views}} And I refer to this template using the @ezdesign notation And I render a page that uses that template reference # This can be found in the Twig tab of the Sf profiler Then it has been rendered using the template from the "app" design Scenario: built-in templates can be overridden using the design engine Given an eZ Platform feature that gets rendered using a given template And that template is loaded from the standard design When I create a template with the same path in "app/Resources/views/themes/standard" And I render the feature again Then it uses my custom template Given an eZ Platform admin feature that gets rendered using a given template And that template is loaded from the admin design When I create a template with the same path in "app/Resources/views/themes/admin" And I render the feature again Then it uses my custom template
Attachments
Issue Links
- blocks
-
EZP-28870 Make existing templates part of the standard design
- Closed
- is duplicated by
-
EZP-28759 Add support for eZ Design Engine to eZ Platform Admin UI
- Closed
- testing discovered
-
EZP-29308 Standard Design: disable overriding Kernel templates
- Closed
-
EZEE-2098 Page Builder should not override Twig form_themes for frontend templates
- Closed
-
EZEE-2117 Invalid pagelayout being rendered in Create mode due to use of @ezdesign
- Closed
-
EZP-29237 Creating template in app/Resources/views overrides that template in other themes
- Closed
-
EZEE-2024 Landing Page field should be hidden
- Closed
-
EZEE-2111 Landing Page field is visible while creating new Page with COTF
- Closed
-
EZEE-2133 Page Builder preview should restore Admin context when handling exception
- Closed
- links to
1.
|
Standard Design: disable overriding Kernel templates | Closed | Unassigned |