WordPress.org

Make WordPress Design

Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • designsimply 6:25 pm on March 15, 2015 Permalink
    Tags: accordion vs sliding panels, , theme switcher,   

    Usability Testing for WordPress Customizer Theme Switcher Improvements 

    I did five usability tests for theme switcher and sliding panels in the customizer.

    Summary

    • Users found the customizer very user-friendly overall.
    • Expected clicking on a theme thumbnail to open a preview, not the details modal.
    • Difficulty navigating back using the current 4.2-alpha design (pre-31289.diff).
    • Expected clicking the “Save & Activate” button to not kick them to the front end.
    • “Save & Publish” is clicked a lot more often for sliding panels.
    • I asked two users (note small sample size) which navigation style they preferred, both picked accordion.

    Full Videos

    1. 1406491a-usertesting.mp4 (17m5s)
    2. 1408362a-usertesting.mp4 (8m53s)
    3. 1408760a-usertesting.mp4 (7m58s)
    4. 1408936a-usertesting.mp4 (11m15s)
    5. 1414874a-usertesting.mp4 (15m35s)

    (More …)

     
    • Weston Ruter 10:53 pm on March 15, 2015 Permalink | Log in to Reply

      People love widgets. :) cc @westonruter (because you do awesome work with widgets)

      Thanks for that feedback! I bet they would find the Customizer experience even better with the Customize Partial Refresh plugin active. When implemented, it eliminates the need to refresh the full preview when making a widget change; instead, it will just fetch the single widget’s contents and replace it inline, so it is much faster and less jarring. Reordering of widgets is done without any server round-trip at all.

      Widgets get stuck half way when first selected (#, #)

      Yes, this is a known issue. See #31014.

    • Davide 'Folletto' Casali 11:48 am on March 16, 2015 Permalink | Log in to Reply

      I’d back all your suggestions. Solid. :)
      I think the biggest one is probably “Save & Publish” that doesn’t close it. It wasn’t something we were testing for, but it’s the main issues that impacted all the tests a lot.

      I’d also add that currently the slider patch is not 1:1 with the latest design discussed in #31336, so worth re-doing it after it’s implemented. :)

    • designsimply 5:29 pm on March 16, 2015 Permalink | Log in to Reply

      I received some (good) critical feedback :) about the part of the tests where I asked users which option they preferred saying that part was flawed—I added some notes inline and would love to continue testing around this.

    • Nick Halsey 1:34 am on March 17, 2015 Permalink | Log in to Reply

      I haven’t had a chance to watch the last two tests, but based on the notes, I think we should look at the following changes:

      • Switch theme details/live preview (needs a ticket & patch for 4.2)
      • Commit the latest patch on #31289 (for 4.2)
      • Add the section-back arrow back to the header, over the close button, to address navigation confusion and the desire to constantly save & publish
      • Continue iterating on and testing the navigation changes, aiming to get that into 4.3 very early
  • Siobhan 7:36 am on March 11, 2015 Permalink
    Tags:   

    Thanks everyone who attended the meeting last week (and apologies for my tardiness with the notes!).

    Process
    We had a serious discussion about the current process. After discussion of the prototype, we decided that in its current state it’s ready for testing the basic flow. There are a few bits of polishing that need to be done:

    • fixing the CSS on the back of the card
    • ensuring that full-width images remain selected when browsing through the images

    However, no more major development will be done on the prototype. We don’t think it is a good use of time to work on getting the editing features working. We’re going to start building the plugin and get the groundwork for that done while morten is testing.

    Therefore, next week’s meeting will be dedicated to scoping out the next steps for the plugin and getting that process going.

    Actions

    • @mor10 to share his procedure for testing so that other members of the team can run tests too (complete
    • fix selection issues when in full-width (complete
    • fix styling issues on metadata screen (complete

    (great job on getting everything complete before I even write up the notes 😀 😀 :D)

     
  • Siobhan 6:48 pm on February 12, 2015 Permalink
    Tags:   

    Image Flow Update 12th February 

    Thanks to everyone who attended the image editing meeting today. Here’s what we discussed:

    • prototype: the prototype is progressing. You can see the current version here.
    • @mor10 pointed out that the current version of the PT isn’t ready for testing. He has created a number of issues in the tracker to get the issues addressed
    • we discussed the ease with which people can get involved with the project. We agreed that it would be better to break the scenarios out into discrete issues for each screen

    Actions

    • @siobhan to create a new list of issues for the devs to work on
    • @mor10 to add issues he’s come across to github
    • @mor10 to share his user testing process once it’s complete

    The dev meeting is on Friday at 17:30 UTC for anyone who wants to join.

     
  • Kelly Dwan 3:48 pm on February 6, 2015 Permalink
    Tags:   

    Dashicons 2/5 Notes 

    Slack Archive

    We Discussed

    • SVG For Everybody was merged into github, the mockup can now be seen on IE9+
    • Debate over creating a core set of Dashicons, and leaving any icons not used by core in a downloadable pack.

    Dashicons “core set” Discussion

    Started from Michael’s comment about applying the core philosophies to dashicons. If we can narrow our focus on only the core icons, any improvements and changes only need to happen on this smaller subset of icons. For current dashicons users, creating your own icons in SVG should be simple- or they can download the SVG they want from somewhere.

    There was a lot of reluctance from the developers in attendance, I think because we use those icons :)

    We left off the discussion at this: for backwards compatibility it’ll be best to keep all dashicons in core. This may change as we move to implement this in core, it’ll depend how we handle backcompat.

    Since we haven’t made any final decision, any extra discussion should happen on the github issue for grouping icons.

    To Do

    • Note if/where icons are used on the google doc in this github issue.
    • Continue working on the mockup: refine the grunt tasks, browser test.

    We’ll meet again next week, February 12, 2015 18:00 UTC.

     
  • Siobhan 6:18 pm on February 5, 2015 Permalink
    Tags:   

    Image Flow Update 5th February 

    Thanks everyone for attending the meeting today. Here’s what we discussed:

    1. Prototype

    • Scenarios 1 and 5 are complete, and scenario 2 is nearly complete
    • @pabloperea has nearly completed the full width screen. There’s an issue with swipe on mobile which Roy is going to look into
    • @mor10 is going to start user testing scenarios 1 and 5

    2. TinyMCE

    We had a brief discussion about what happens to the image outside of the flow. TinyMCE isn’t the most fun to use on a mobile device and it has some jarring behaviours when you’re dealing with the image. @iseulde suggested that we keep track of any issues. These should be reported on trac.

    3. Icons

    @teamadesign has created a list of icons, which @empireoflight is going to run by the dashicons team.

    Actions

    • @mor10 to start user testing scenarios 1 & 5
    • @royboy789 to fix swipe issues in prototype
     
  • Kelly Dwan 8:00 pm on January 29, 2015 Permalink
    Tags:   

    Dashicons 1/29 Notes 

    Slack Archive

    We discussed:

    • Merged the grunt task pull request.
    • Dropped in SVG For Everybody for IE support, works out-of-the-box for IE9+
    • IE7-8 will use PNG fallbacks, and we recommend just 2 color sets, a light and dark.
    • Subsetting Dashicons into groups based on use(?), ongoing discussion will take place on Github.
    • We also touched on creating new icons for 4.2, but new icons are not a priority

    To do:

    • @ryelle will update the repo to use SVG For Everybody.
    • @michael-arestad‘s going to work on the grunt tasks; and rename the pngs as needed.
    • Once those things are done, anyone can work on browser testing :)

    There’s also been work on the Dashicons style guide, so check that out & leave comments.

    We’ll meet again next week, February 5, 2015 18:00 UTC.

     
  • sonjanyc 10:36 pm on January 27, 2015 Permalink
    Tags:   

    Meeting Notes and Discussion around Image Cropping 

    A sub set of the #feature-imageflow team met on Slack yesterday to discuss a few things, namely:

    1. Can we tackle to improve the image cropping experience in 4.2 ?
      Should we save versions of cropped images on a post level or crop and overwrite the original?
    2. We’re currently working on a prototype to prove out our UX strategy and to come up with an ideal solution before we go into development. However we wanted to look at features or improvements that could potentially be worked on already. Since the image cropping experience is so broken, we think this could be something we can work on separately and up front – and make a lot of people happy!

    I was meeting with several people in slack to discuss these questions yesterday: @dh-shredder, @ericlewis, @markoheijnen, @royboy789, and @antoniancu – after the official meeting was over we also had @boren, @mor10, @samuelsidler and a few others join in.

    DISCUSSING #1:

    I’ve created some flows for an ideal image cropping experience and shared those with the group: https://docs.google.com/file/d/0Byz0aohoFoOcUi02M1NHdTItVnM/edit

    The conclusion of the meeting in was that we agree that we should make iterative changes to improve the image cropping functionality and experience. We should come up with a full wish list of changes that need to be made to get to the ideal solution, and then decide which ones we can tackle now and which ones we’ll phase out. I will start working on this list and will get some help from the group refining it. Important will be to make this work on desktop as well as mobile!!

    @boren shared Vizrecs of three cropping flows, which helps identify pain points: https://make.wordpress.org/flow/2015/01/26/uploading-and-cropping-an-image-in-the-media-lib-grid-view-and-list-view-macnchrome/

    IMAGE CROPPING WISHLIST:

    • No tool should be selected in initial state of editing mode, image cropping icon shouldn’t look “inactive”
    • When user clicks on cropping icon, full image should have a crop selection
    • User can change crop area with handles and reposition crop area by dragging (this should also work on mobile!)
    • Aspect ratio should have common pre-defined aspect ratios to choose from and an option to input a custom aspect ratio
    • Selecting an aspect ratio should lock selection of aspect ratio, so user can still drag corners to change image selection
    • Action buttons to apply/discart the crop should be “APPLY” or “DISCARD”
    • Should there be an option to crop the “original” vs. create new “post image version”?

    Please add anything in the comments I might have forgotten. Help us refine this list.
    Thanks!

    DISCUSSING #2:

    When an image is being cropped it’s confusing to the end user whether it crops the original image or saves a new version. The discussion what would make most sense I’m sure came up internally many times already. So we talked about it as well. People have different opinions and ideas for this, but I soon realized that this discussion will need to be held in a much bigger circle. The overall consensus was that we do want to work towards what @dh-shredder calls “post image”. This means that if an image is being edited / cropped in a post context it will create and save a version of the image for that post and not effect the same image in different locations. If a user however edits an image within the Media Library, he/she edits the original image.
    This functionality would need to be worked out with a set of rules, there are obviously concerns about over-cluttering the media library… etc.

     
    • Mike Schinkel 2:17 am on January 29, 2015 Permalink | Log in to Reply

      I would really be great if the original image could *always* be maintained and never modified. In the media library modifying it could create a default image, but you should always be able to recover the original image. If the end user needs to think they are modifying the original image, let them, but still make sure to offer a “Recover original image” option.

    • teamadesign 8:26 am on January 29, 2015 Permalink | Log in to Reply

      Looking great, some really excellent points coming out of this conversation. The only element I would add (and it is present in both @sonjanyc‘s flows and her trac ticket) is that the pre-set crop ratios should be presented with a visual rep so that a user can quickly scan the icons and make a decision based on the look, rather than the completely abstract w x h formula.

      I like what @dh-shredder and @mikeschinkel have to say around a ‘post-image’ and an original image. It seems that having a canonical image that all others are iterative of would allow for a simpler organizational scheme in the media library…

    • Fabien Quatravaux 8:54 am on January 29, 2015 Permalink | Log in to Reply

      One feature I would really appreciate and that is buggy today is the ability to crop only the thumbnail version of an image. For example, I upload a picture of a friend in full-length, the cropped scare thumbnail would be centered on his chest instead of his face. I wish I could be able to correct that wrong thumbnail with the cropping tool.

      Today (in 4.1), the “Apply changes to:” settings with “Thumbnail” choice seams to have no effect, and I have no way to check the thumbnail version of the image after the crop. Instead, we could see a list of available picture sizes, with a preview for each, and a click on the thumbnail preview would load the thumbnail version into the cropping tool.

    • Graham Armfield 8:32 pm on February 3, 2015 Permalink | Log in to Reply

      Two points I’d like to add…

      Firstly, in the wishlist please can the list include a point that all functionality should be able to be used with keyboard only – from an accessibility perspective.

      Secondly re Discussing #2. I think a new image should be created from any cropping done. There may be situations when a site owner may wish to show both the cropped and original versions of an image on their site, or potentially show differeing crops of the same image to draw attention to specific elements within the image.

  • Mel Choyce 8:34 pm on January 26, 2015 Permalink
    Tags: community hub   

    Here’s a reminder for those who haven’t seen it. Please take a few minutes to fill in the Community Hub Poll as the poll closes Thursday at 00:00UTC.

    For more information on the Community Hub, please check out this post.

     
  • Kelly Dwan 6:57 pm on January 22, 2015 Permalink
    Tags:   

    Dashicons 1/22 notes 

    Slack Archive

    We discussed:

    To do:

    • AnyoneCheck out the PR & leave any feedback.
    • @michael-arestad‘s going to keep tweaking the tasks – there are some things we don’t need, and can do in other ways. Also looking into alternatives that don’t generate a billion pngs.
    • Anyone: Leave any suggestions/resources/questions for the style guide as comments on that page.

    We’ll meet again next week, January 29, 2015 18:00 UTC .

     
  • Siobhan 10:03 am on January 22, 2015 Permalink
    Tags:   

    Image Flow Agenda 22nd January 

    Image Flow meeting is this evening. First thing to note is that we will move our regular Thursday meeting to Slack. We’ve reached the limit of how many people we can fit on the Google Hangout. Also, Slack is better for encouraging participation and for logging. We’ll likely continue to do smaller user testing meetings on google hangout.

    This evening’s meeting:

    • review of last week’s actions
    • feedback from dev meeting
    • team plan for 4.2
    • anything else?

    See you all at Thursday 17:30 UTC in #feature-imageflow in Slack!

     
    • sonjanyc 3:55 pm on January 22, 2015 Permalink | Log in to Reply

      slack channel is called #feature-imageflow
      // just for those joining for the first time and can’t find it.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel