Over the past few days, I've been reviewing the mockups in #2600634: Implement Panels In-place editor display builder in panels_ipe module with Sam, DyanneNova, and EclipseGC. There are a few changes (big and small) that we're hoping to implement over the coming weeks.

  1. Test the current IPE experience with current users -- DONE. (Sorta), Tested on some technical and non-technical DA staff. Provided some interesting results. (below)
  2. 2) Make some new mockups emphasizing a 'quickedit' style experience for creating and placing blocks (this issue)
  3. 3) Implement improvements to blocks within ctools. Bring some of the backbone code used in IPE to support #2604178: Modify core block UI to seperate blocks into categories with tabs. This will replace the tray that we have in IPE currently.
  4. 4) Improve quickedit in general, probably through ctools first, with an aim to get the improvements into core.

Comments

japerry created an issue. See original summary.

dyannenova’s picture

User testing notes

Larger issues

Managing content separately from managing layout was confusing. i.e. Users didn’t understand why, when using the Edit mode, clicking the configure gear on a block threw them out of the editing screen that they were on. They also didn't see how to place a block from Place Content, finally deciding they needed to do that in Edit mode.

The tray wasn’t generally scalable. i.e. The large number of blocks available was hard to wade through. Testers wanted a search bar to search for the content to add. The configuration tray ended up taking over the whole page and the user lost context of what was being edited and where it was going.

Users were confused by seeing three columns when they selected a two column layout because of sidebar blocks in the theme.

Smaller fixes

Users expected all available layouts to be visible in the tray at once.

  • Configurable categories of layouts

Users also expected the system to more clearly convey if the layout they selected was the one that was currently being used on the page. Instead they got no visual feedback.

  • Highlight the selected layout anywhere it appears
  • If a layout doesn’t provide configuration just submit the form

No move icon on the blocks meant that users didn’t know they could drag the block

  • On hover, surround the entire block with dashed line and change cursor to indicate that the whole block is movable

The arrows and select box confused users further in that regard.

  • Remove arrows to just use the Move menu

Minus does not mean remove

  • Should be X instead of -

The users did not notice the layout select box in the block configuration before placing content.

  • Should be able to drag blocks and skip the initial configuration step

The text field for title should automatically override the title if changed (The override title checkbox was always completely missed.)

  • Panels Bug that Override title is unchecked but field still shows
  • Would be nice to just override if the text is changed, otherwise use default

The lack of text on the Edit and Save buttons were confusing when placed next to Layouts and Manage Content

  • Add text to Edit and Save.
  • Only show Save when something can be saved.
dyannenova’s picture

Interaction Wireframes

Here is a link to the current wireframes I've been working on:
http://aienea.axshare.com/#p=start_1&hi=1

I'll publish any changes directly to that url.

Any area in the wireframes that currently has an interaction available is highlighted in green.

samuel.mortenson’s picture

Component: User interface » In-Place Editor (IPE)
samuel.mortenson’s picture

For me the best way to summarize the problem the mockup addresses is: "The IPE in D7 and D8 doesn't actually in-place edit anything.". We move Panels/Blocks around the page, but the actual editing (and configuration, style application, etc.) has always happened in a modal or tab-flyout.

samuel.mortenson’s picture

For the "Create a new list" section of the mockup, anyone want to port SimpleViews to D8? :-)

eclipsegc’s picture

Fwiw, that part gives me some pause. We're choosing where we want something, picking the something we want, placing it, and then configuring it. This gives us decidedly less control over the user experience, and also has some technical ramifications (like bail out for instance). Being able to do an in-modal (or whatever) wizard gives us a lot more certainty over the user experience, and they can bail at any time without affecting our page.

That being said, a "SimpleViews" like solution would be pretty cool for this.

Eclipse

samuel.mortenson’s picture

"Panels Bug that Override title is unchecked but field still shows" has been addressed in #2682993: IPE badly mangles complex block forms :)

eclipsegc’s picture

StatusFileSize
new58.77 KB
new65.48 KB
new129.18 KB
new85.91 KB
new108.37 KB
new84.62 KB
new95.26 KB
new110.74 KB
new116.09 KB
new118.3 KB
new118.59 KB
new118.52 KB
new113.92 KB
new112.47 KB
new113.94 KB
new109.62 KB

So I wanted to add my efforts to this as well. We can debate where we want to go, but I didn't want this to disappear into the ether.

Eclipse

sylus’s picture

I just wanted to say thanks for all the work with the mockups, I actually kind of like that direction and how most of the operations are in the toolbar.

I think this would help the user's existing mental model for how to work with the site.

samuel.mortenson’s picture

My (brief) takeaways from EclipseGC/DyanneNova's mockups are:

  1. We need inline add buttons
  2. We need to integrate with Toolbar and move away from the current bottom-tray
  3. Inline forms, either as inline modals, in the actual Block div (IPE-Mock-12.jpg), or anywhere where you can see the Block and the form at the same time
  4. Other modules like Page Manager should be able to easily add onto the UI to provide features like like Contexts
  5. More actions need to start from editing, not from the tray

As I've discussed in IRC, one of my goals over the next few weeks is to research better Toolbar and Outside In integrations for Panels IPE, which would include integrating these mockups into my design. Hopefully I'll have something shiny to look at in the coming months.

eclipsegc’s picture

Awesome, just as an FYI here, we cannot do ANYTHING that touches experimental core code. I'm sure we all know this, but I wanted to explicitly state it.

Eclipse

samuel.mortenson’s picture

Agreed, I would wait to commit anything until Outside In's offcanvas.js moves into the core/misc folder.

dsnopek’s picture

Title: [META] Design UX updates for IPE / Panels » [META] Design new UX for Panels IPE

Re-titling to make it clear that this is about creating a new UX for Panels IPE, as opposed to incremental improvements to the current UX. I'm planning to make some incremental improvement issues in a little bit :-)

damienmckenna’s picture

Version: 8.x-3.x-dev » 8.x-4.x-dev

Is this being done or is everyone focusing on core instead?