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

As an eZ Platform user, I would like to access the preview options when viewing content

    Details

      Description

      The preview options (mobile, desktop, tablet) are currently only visible when editing a piece of content - in the right action drawer. We would like to also have the preview options available within the action drawer when viewing content.

      You can find the wireframes on this page: https://doc.ez.no/display/PR/%28n01%29+Basic+Edit+via+tree+navigation
      Wireframe in particular: https://doc.ez.no/download/attachments/7438520/n01_01.01%20Object%20%28container%29%20discover%20action.png?version=3&modificationDate=1368452439000&api=v2

        Activity

        Hide
        Jince Kuruvilla (Inactive) added a comment -

        [~damien.pobel@ez.no] & Roland Benedetti - did I do this ticket correctly? There was no option for me to assign it to DP.

        Show
        Jince Kuruvilla (Inactive) added a comment - [~damien.pobel@ez.no] & Roland Benedetti - did I do this ticket correctly? There was no option for me to assign it to DP.
        Hide
        Roland Benedetti added a comment -

        [~jince.kuruvilla@ez.no]
        Not so bad
        Two things, you picked an Epic which is weird and not on the Epic board.
        I moved to "Content CRUD" , which is to me the basic of content management : view, create, edit.
        I believe the preview should be part of it on both edit and view.

        However, we just talk here abotu the basic preview.
        of course all the advanced preview stuff that you designed a few months ago should go into another Epic.

        Second thing:
        You pushed it to InputQ. If you discussed it with Damien, I think it's fine. We now have 28 tickets in inputQ so it's still less than 30, but in general we should not overload the InputQ. So it should be only things that are "ready" to be tackled, and of course of high priority.

        Last small thing:
        We should probably point to the wireframe whree this was done. Also, I think they are old, they would probably deserve a refresh with the new look.

        beside, I think it's good

        Show
        Roland Benedetti added a comment - [~jince.kuruvilla@ez.no] Not so bad Two things, you picked an Epic which is weird and not on the Epic board. I moved to "Content CRUD" , which is to me the basic of content management : view, create, edit. I believe the preview should be part of it on both edit and view. However, we just talk here abotu the basic preview. of course all the advanced preview stuff that you designed a few months ago should go into another Epic. Second thing: You pushed it to InputQ. If you discussed it with Damien, I think it's fine. We now have 28 tickets in inputQ so it's still less than 30, but in general we should not overload the InputQ. So it should be only things that are "ready" to be tackled, and of course of high priority. Last small thing: We should probably point to the wireframe whree this was done. Also, I think they are old, they would probably deserve a refresh with the new look. beside, I think it's good
        Hide
        Damien Pobel (Inactive) added a comment -

        overall ok, just use the "PlatformUI (Admin UI & Content UI)" component so that it appears in my own filtered list I also removed it from the inputQ as we have more than enough PlatformUI tasks at the moment (tabs, field description, translations, online editor related tasks, various technical stuff, ...) but that's definitively something we can tackle quite soon.

        Show
        Damien Pobel (Inactive) added a comment - overall ok, just use the "PlatformUI (Admin UI & Content UI)" component so that it appears in my own filtered list I also removed it from the inputQ as we have more than enough PlatformUI tasks at the moment (tabs, field description, translations, online editor related tasks, various technical stuff, ...) but that's definitively something we can tackle quite soon.
        Hide
        Damien Pobel (Inactive) added a comment -

        that said, I've just realized there an issue because the preview button is a bit special. It actually has 3 options (desktop, tablet, phone) but if you minimize the action bar those 3 devices buttons can not be displayed so when the toolbar is in the minimized state, how can the user choose which version he wants to see ?

        Show
        Damien Pobel (Inactive) added a comment - that said, I've just realized there an issue because the preview button is a bit special. It actually has 3 options (desktop, tablet, phone) but if you minimize the action bar those 3 devices buttons can not be displayed so when the toolbar is in the minimized state, how can the user choose which version he wants to see ?
        Hide
        Jince Kuruvilla (Inactive) added a comment -

        If the action drawer is minimized, the behavior should match that of the other Action Drawer items that have multiple options, which is to collapse the options within a main button that the user can access. So the interaction, when the Action Drawer is minimized, would be: User clicks on the Preview icon (the eye). A Menu would slide out from the Preview Icon with the three preview options: Mobile, Tablet, and Desktop. The User would then click on one of those options and be brought directly to the preview.

        • I'll be sure to use the right component next time - it was a bit difficult to figure out which one was the correct one
        Show
        Jince Kuruvilla (Inactive) added a comment - If the action drawer is minimized, the behavior should match that of the other Action Drawer items that have multiple options, which is to collapse the options within a main button that the user can access. So the interaction, when the Action Drawer is minimized, would be: User clicks on the Preview icon (the eye). A Menu would slide out from the Preview Icon with the three preview options: Mobile, Tablet, and Desktop. The User would then click on one of those options and be brought directly to the preview. I'll be sure to use the right component next time - it was a bit difficult to figure out which one was the correct one

          People

          • Assignee:
            Unassigned
            Reporter:
            Jince Kuruvilla (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: