Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-20340

Support twig design/theme system for eZ Platform

    Details

    • Story Points:
      4

      Description

      Scope of this story:

      • make it work twig templates
      • setup fallback order
      • if time permits: deal with cache

      Not part of scope (followups):

      • cache
      • assets (js + css + images)

      These parts are not part of scope as it is currently not yet supported by upstream (LiipThemeBundle) so need to be added there.

        Activity

        Show
        Jérôme Vieilledent (Inactive) added a comment - https://github.com/ezsystems/ezpublish-kernel/pull/478
        Hide
        André Rømcke added a comment -

        After discussion last sprint planning we agreed that theming(design) support for assets is not inside scope for this story.

        Show
        André Rømcke added a comment - After discussion last sprint planning we agreed that theming(design) support for assets is not inside scope for this story.
        Hide
        Rui Silva (Inactive) added a comment -

        QA needs information regarding this, what exactly to test, and how (providing some use case or detailed steps).
        Also the PR seems to have been declined, so, what is to be tested here?
        The only comments on this jira issue date back to more than two years ago and, as specified on the provided doc, info in it may also be (and surely is) out-of-date.
        QA was also unable to find any spec data regarding this, on the doc. We searched here:
        https://doc.ez.no/pages/viewpage.action?pageId=7438527
        so, regardless the need for more detailed info on how to test this, if there is any other location on doc for specs, specifically on this, can anyone inform wherefrom?
        Thank you.

        Show
        Rui Silva (Inactive) added a comment - QA needs information regarding this, what exactly to test, and how (providing some use case or detailed steps). Also the PR seems to have been declined, so, what is to be tested here? The only comments on this jira issue date back to more than two years ago and, as specified on the provided doc, info in it may also be (and surely is) out-of-date. QA was also unable to find any spec data regarding this, on the doc. We searched here: https://doc.ez.no/pages/viewpage.action?pageId=7438527 so, regardless the need for more detailed info on how to test this, if there is any other location on doc for specs, specifically on this, can anyone inform wherefrom? Thank you.
        Hide
        Rui Silva (Inactive) added a comment -

        Since there is no current provided use case for QA to test this, nor detailed information whatsoever since more than two years ago on this, QA is sending it back to dev-needed since we are unable to test anything here.

        Show
        Rui Silva (Inactive) added a comment - Since there is no current provided use case for QA to test this, nor detailed information whatsoever since more than two years ago on this, QA is sending it back to dev-needed since we are unable to test anything here.
        Hide
        Bertrand Dunogier added a comment -

        What needs to be tested is this package: https://github.com/ezsystems/ezplatform-design-engine/releases/tag/v1.0-beta.

        It will be integrated into ezplatform at some point (either 1.10 or later), and will be suggested as the default way to implement design & themes using eZ Platform.

        The package is documented at https://github.com/ezsystems/ezplatform-design-engine/blob/v1.0-beta/doc/index.md. Do you think it is worth testing the features in the context of QA ? It is very developer oriented. We tend to not test those that way. We plan on using it on ezsystems/ezplatform-com in order to demo how it is used; the plan is that Jérôme does it when he works with us in june.

        I suggest that we close this story for the time being. What do you think ?

        Show
        Bertrand Dunogier added a comment - What needs to be tested is this package: https://github.com/ezsystems/ezplatform-design-engine/releases/tag/v1.0-beta . It will be integrated into ezplatform at some point (either 1.10 or later), and will be suggested as the default way to implement design & themes using eZ Platform. The package is documented at https://github.com/ezsystems/ezplatform-design-engine/blob/v1.0-beta/doc/index.md . Do you think it is worth testing the features in the context of QA ? It is very developer oriented. We tend to not test those that way. We plan on using it on ezsystems/ezplatform-com in order to demo how it is used; the plan is that Jérôme does it when he works with us in june. I suggest that we close this story for the time being. What do you think ?
        Hide
        Paulo Nunes (Inactive) added a comment -

        Bertrand Dunogier Thank you for your feedback. Indeed by what you said, I think we'll leave QA out of this for now.

        Show
        Paulo Nunes (Inactive) added a comment - Bertrand Dunogier Thank you for your feedback. Indeed by what you said, I think we'll leave QA out of this for now.
        Hide
        Paulo Nunes (Inactive) added a comment - - edited

        Since this issue is not on QA column, I won't close it.
        @Dev: please close this issue, if it's intended to be closed now.

        Show
        Paulo Nunes (Inactive) added a comment - - edited Since this issue is not on QA column, I won't close it. @Dev: please close this issue, if it's intended to be closed now.

          People

          • Assignee:
            Unassigned
            Reporter:
            Damien Pobel (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 4 days Original Estimate - 4 days
              4d
              Remaining:
              Time Spent - 2 days, 4 hours Remaining Estimate - 1 week
              1w
              Logged:
              Time Spent - 2 days, 4 hours Remaining Estimate - 1 week
              2d 4h

                Agile