WordPress.org

Make WordPress Design

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Siobhan 5:21 pm on April 16, 2015 Permalink |
    Tags:   

    Just a reminder that the image flow meeting is now on Thursday at 20:00 UTC. That’s:

    • 21:00 London
    • 16:00 EST
    • 13:00 PST
     
  • Hugo Baeta 7:59 pm on April 5, 2015 Permalink |
    Tags: 4.2, colors   

    Default Admin Color Scheme Update 

    Earlier in the 4.2 cycle, I opened a ticket proposing changes to the default color scheme for wp-admin. After much consideration and a few changes, it is being brought into core. I’d like to explain the changes made, and the reason for them in this post!

    This started as part of an exercise to document the colors used by core for the Design Handbook (work in progress). My instinct to iterate on the colors and try to make them more harmonious kicked in, and so I ran an experiment that resulted in this:

    color-changes-chart

    Here’s a breakdown of HEX color changes:

    Grays
    Old New
    #111111 #191e23
    #222222 #23282d
    #333333 #32373c
    #4b4b4b #464b50
    #888888 #82878c
    #aaaaaa #a0a5aa
    #bbbbbb #b4b9be
    Blues
    Old New
    #0074a2 #0073aa
    #2ea2cc #00a0d2
    #45bbe6 #00b9eb

    In essence, the grays were given a slight blue hue, and the for the blues I removed the red channel almost completely, for a purer blue. In both cases, I attempted to keep the value of the colors (lightness/darkness), so the change would be as seamless as possible, while giving the admin a new sense of refinement and identity.

    @iammattthomas commented on the ticket, summarizing this change quite eloquently:

    My subjective feeling is that the shift in colors is so slight, it doesn’t really change the feeling we intended to convey with the original MP6 colors. If anything, it makes the grays look more intentional, a color palette designed to work harmoniously rather than pairing a signature shade of blue with a lot of neutral grays.

     

    And here’s a side-by-side comparison of the old (left) and new (right) colors in use on the admin:

    color-wpadmin

    I believe this updated color scheme can still be iterated upon, specially regarding concerns of contrast and accessibility (that weren’t addressed in this round, but are certainly a priority for the next release cycle).

    I’d love to hear your thoughts!

     
  • Siobhan 5:52 pm on April 2, 2015 Permalink |
    Tags:   

    Image Flow Update 2nd April 

    Thanks everyone who attended the meeting this week. Note that in future the meetings will be at 16:30 UTC, i.e. normal time for everyone now that daylight savings has happened.

    Here’s what we discussed:

    1. Feedback – there’s a lot of feedback scattered around which we need to get into one place so we can make sure it’s properly addressed. We have a Google Doc here which we’ll consolidate it into.
    2. @teamadesign has tried an edited flow with the metadata first. It’s available for testing should anyone want to.
    3. Once @wonderboymusic is caught up on where we are, we’ll start ploughing forward with the plugin.

    Actions

    • @siobhan to pull together feedback from UT videos, make/ui post, and boren notes
    • @teamadesign to review feedback in Slack channel
     
  • Kelly Dwan 7:09 pm on March 19, 2015 Permalink
    Tags:   

    Dashicons 3/19 Notes 

    Slack Archive

    We Discussed

    To Do

    Next week, we’ll have a discussion to confirm what approach we should take, and how to get there. If you want to join in, that’ll be March 26th, at 18:00 UTC in #design-dashicons.

     
  • Siobhan 10:29 am on March 18, 2015 Permalink
    Tags:   

    Image Flow Catchup 

    Now that we’re ready to start making a plugin, this post will catch you up on some of the important things to read before diving in.

    Wireframes and Flow Charts

    The interactive wireframes will give you a pretty accurate visual overview of where we’re going with the project. Note that the wireframes are based on a large amount of research into how different platforms and applications handle image storage, upload, and editing.

    There are also user flow charts which show the planned user flows through the interface. It’s worth comparing these with the current flows through the modal.

    Prototype

    The in-browser prototype is a skeleton representation of how we see the basics working. It isn’t perfect, but the basics are there. We’ve decided that at this point it’s best for us to move onto the plugin. However, @mor10 is doing some user testing on the prototype and we’ll use that feedback for refining the plugin.

    Prototype Resources

    Background Reading

    if you’re interested in some more background reading that should give you insight into various decisions, these are some things worth looking at (this is not essential to read before getting started):

    Next Steps

    The next step is to break the plugin down into discrete, achievable tasks. This should get things moving more quickly. we can use the Image Flow Github account. As soon as it’s in a usable state we’ll put the plugin in the repo so it’s easy to test and we can get feedback.

    The regular meeting is at 17:30 UTC on Thursday.

     
    • Ryan Boren 4:23 pm on March 18, 2015 Permalink | Log in to Reply

      My initial impressions from my first time running through the prototype a few days ago.

      I went in with the goal of publishing a single captioned image. After clicking add media, I’m greeted with a media lib type view. There’s no greyed out button bottom right to indicate the possible next step. When comparing the prototype flow to production flow, I realized I missed having a persistent button bottom right. That’s what I’m used to after years of using the media modal.

      I click an image, again with the goal in mind of creating a captioned image. I go from no buttons to three. That More button feels very in the way. I tend to like the primary action anchored right and aloof from other buttons. So, I have three buttons, three decisions lined up in a row now. I want to caption, so I shouldn’t insert yet. More is just something I’m going to have to develop blindness to, so I get started on that by ignoring it. I click View.

      Still no details. I have Insert and more bottom right and a ton of stuff at the top. Grid, Select Media, info, Edit, close. Plus two arrows. And a big checkbox. And image numbering (1 of 7). This is overwhelming. I came here looking to add a caption. I think someone looking to add a caption could very naturally try Edit, but that’s not it. Info is what you want.

      Once info shows, I put in a caption and make another decision. Am I ready to publish? The Insert button is active and ready, but what exactly am I publishing? The arrows and numbering make me wonder if I’m publishing a gallery. I’m here for one image and don’t want to do that. Do I need to back up a level? How do I do that? Where am I? When I get lost, I seek context and a way back. I look for a persistent context keeper and escape route. I don’t feel a nav anchor.

      I appreciate the power of all of this, but this attempt at a single captioned image has me doubting the image details flow. The non-persistent, top left escape route nav feels inadequate as a nav anchor. The latest customizer work uses a persistent header and stacked nav. The MT riff mock has a persistent bottom left escape route. I like the way those give a consistent escape route.

    • Andrew Ozz 5:56 pm on March 18, 2015 Permalink | Log in to Reply

      I also went through the different flows in the prototype. Did that before reading any feedback or looking at the conversations in Slack in an attempt to be as impartial as possible :)

      Was surprised by the “dynamic” buttons at the bottom a bit. Probably better to have at least the “Insert” there at all times, greyed out when nothing is selected? Wouldn’t mind if the other buttons were there and greyed out. Can probably get used to them being dynamic, just a bit surprising how the whole modal goes from being pretty plain/minimalistic to having many places to click/draw attention as soon as you click on an image. Also the width of the buttons should probably be constant/unchanged when showing more or hiding existing.

      Really dislike the horizontal list of selected images at the bottom left. It is pretty much unchanged from the current modal and has no good functionality. It is really hard to see what is on the super tiny thumbnails. Also the horizontal scrollbar that shows when more images are selected takes about 1/4 of the space and makes the whole thing look like something went wrong or something is buggy. This is hidden on smaller screens, IMHO best to remove it completely.

      After selecting several images another surprise was that clicking on “View” removed that button and shifted the name/label from the top/left (the opposite part of the modal). Then a “Grid” button appeared there. Had to click that small/different/far away button to go back. Also “Grid” being the opposite of “View” (as you have to click one to reverse the other) doesn’t feel right. Perhaps better if “View” was “Single view” and changes to “Grid” instead of being hidden after clicking on it.

      Having to click the smaller “Info” button in the top bar to get to the image properties was pretty hard to find/understand. The label “Info” doesn’t seem to correspond to “Edit Metadata”, “Image Details”, “Post Settings” (the names/labels of the sections that are shown). Maybe “Settings”? Generally I wouldn’t mind having a gear icon next to the checkmark icon for accessing the image properties/settings. Also I am (probably like most people) used to have “controls” at the top/right or top/left, having that big checkmark at the bottom/left feels somewhat out of place.

      All of the rest feels pretty good. Really like the ability to browse the selected images either as big “previews” or as image settings “boxes”. Starting to wonder why it is only for selected images, should probably be available for all the media library.

      Of course there are still places where behaviors can be improved. For example after selecting more than one image, the default should probably be “Create Gallery” instead of “Insert”. It is relatively very very rare for more than one image to be inserted in a post at the same time (frankly, not even sure we need to support that). In almost all cases a gallery is created.

    • Siobhan 6:30 pm on March 18, 2015 Permalink | Log in to Reply

      Thanks for your feedback! I’m not going to be at the meeting tomorrow but that’d be a great time for everyone to process it.

      Just a note on this:

      For example after selecting more than one image, the default should probably be “Create Gallery” instead of “Insert”. It is relatively very very rare for more than one image to be inserted in a post at the same time (frankly, not even sure we need to support that). In almost all cases a gallery is created.

      When I was doing a lot of longform article writing I used that -all- the time. It makes it easy for me to insert all of the images at once and then move them around within the content. What I used to have to do was:
      1. Insert all of the images in one go
      2. Go to Text View
      3. Copy and paste the html for the images into the right place

      That was fairly hacky. I can just drag the images into position now :)

      Anyway, I’m just saying that it’s something that I would really, really miss.

      • Andrew Ozz 9:04 pm on March 18, 2015 Permalink | Log in to Reply

        Yeah, that is an “advanced user” feature” :)

        Dragging images inside TinyMCE is somewhat problematic and not really recommended. Currently it is disabled if the images have a caption as you will drag them out of the caption elements. Also links are typically not dragged together with the images.

        So for most users that workflow will be quite harder than inserting 3-4 images separately :)

        This shouldn’t be the default IMHO.

    • Konstantin Obenland 10:24 pm on March 18, 2015 Permalink | Log in to Reply

      Some small observations from me:

      The first thing I notice after opening the modal is the big blue Add New icon. It reminds me of the one on the Appearance screen, but there it’s the last item. It probably makes sense to have it be the first item in the media modal, especially once there are more than ten media files. I’d expect the entire square to be clickable though.

      I click on the second picture to insert it and the action bar appears. Personally I’m not a fan of transitions, it makes the interaction feel very slow. The tiny thumbnail of the selected image is not really helpful, it makes the bar just feel more cluttered, in addition to the three action buttons. I also wish it would be more obvious that I selected that picture. A big blue border like in iPhoto or something. That check mark is small and not easy to see.

      I click on view. I don’t know why it’s there, I can view the image right now, but it must be important otherwise there wouldn’t be a button. I get a magnified view of the first available image, not the one that I selected. It also has a check mark even though I did not select it. I click the X on the top right to get back to the overview but that closes the modal.

    • teamadesign 4:54 pm on March 19, 2015 Permalink | Log in to Reply

      Thanks for the feedback folks, much appreciated! We’ll discuss these at our next meeting and iterate the prototype to incorporate these notes and get feedback.

  • 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 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
     
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