Menus (admin) with Windows Phone on 4.2

  • WordPress 4.2.2
  • Old menus admin screen (to be compared with Menu Customizer)
  • Windows Phone 8.1, IE11 Mobile (only browser allowed on this device)
  • Testing on an actual site whose menu I actually needed to make a couple edits to… because why not 🙂

#4-2, #customize, #customizer, #flow-comparison, #menus, #mobile, #phone, #visual-comparison, #winphone

Remove a widget with the customizer, iPhone 6+

The goal is to remove a widget from the hamburger accessed sidebar menu in Twenty Fifteen.

Notes:

When in preview mode, the stacked nav of widgets is pretty subtle. There is no transition other than < changing to X.

I accidentally move widgets when swiping to scroll all the time. I’ve taken to very carefully swiping along the edges to avoid the widget headers, similar to what I have to do in the post editor. I notice there’s a Reorder button at the bottom of the widgets panel. Should widget rearrangement be confined to it?

 

4.2-beta4-31998

#4-2, #customize, #customizer, #ios, #mobile, #phablet, #web, #widgets

Image rotation and editing, mobile vs. desktop

Images uploaded from my phone via Press This or post-new.php seem oriented as I wish when viewed from a phone.

When viewed from desktop, they look like this.

After rotating them in WP’s editor, they show correctly in the image details modal.

But they still show incorrectly in the editor and on the front page.

This happens to me often. I’ve learned not to trust images uploaded from mobile or the image editor.

4.2-beta4-31998 on Macnchrome and iPhone 6+.

#4-2, #desktop, #image-editor, #image-rotation, #ios, #macos, #media, #mobile, #phablet, #sideways

Previewing and switching themes in the customizer, iPhone 6+

4.2-beta3-31985

Switch back to Twenty Fifteen, this time using the Theme Details flow.

#4-2, #customize, #customizer, #mobile, #theme-switcher

Single image post with preview, Press This, iPhone 6+

4.2-beta3-31975

#4-2, #mobile, #press-this

Visual survey of dismissable admin notices

Auditioning 31233.13.diff for #31233.

#4-2, #desktop, #mobile, #patch-testing

4.2 Nux Group Recap, March 17, 2015

Slack log (Requires Slack login to view. Set one up if you don’t have a Slack account)


Last week, and the week before, we sought volunteers to examine each of the flows out of the Welcome Panel. This week we went over the reports that came in about the various flows.

Settings

Set your timezone and date format” – @courtneyengle

Issues

  • Users don’t do this at the start. They don’t discover that they need to change things until they actively post something and noticed date/time aren’t how they expect them to appear. They don’t know where to change that.
  • There is a hazard with the proximity of these settings to other settings that could have potentially hazardous consequences, i.e. users also changing site/home URL?

Suggestions

  • Change the corresponding date/time settings when you manually change the language – have WordPress suggest it, but not do it automatically.
  • Group in the week-starts-on value with that automagicallness might be helpful as well.
  • Add warning text about changing your site/home URLs

Change URL structure” – @bethsoderberg

Issues

  • Confusion of what the “custom structure” could mean and lack of explanation of the parameters accepted by it.
  • The header “optional” isn’t really descriptive for the category/tag base settings section
  • The page “number of tags are available” links to is pretty complicated https://codex.wordpress.org/Using_Permalinks
  • New users rarely know what “permalink” means.

Suggestions

  • Educating users on Permalinks: we all loved the help tab description – “A permalink is the web address used to link to your content. The URL to each post should be permanent, and never change — hence the name permalink.” That should be reused elsewhere.
  • Group Permalinks settings with change site/home URLs settings.
  • This may be less of an issue once 4.2 ships and “Day and name” is the new default.

Appearance

View your site” – @liljimmi

Issues

  • The icon isn’t enough of an indicator that the Site name link links to the Dashboard.
  • The problem is that users don’t typically realize that’s a link back to the Dashboard.

Suggestions

  • Make the link “Dashboard” when viewing the front end and “Visit Site” when in the admin (keep the icons as is).
  • Absence of the site name will be an issue on Multisite. A suggestion to address this is to add the site name to the right end of the sitebar next to “Howdy, Display Name {gravatar}” This would be the same for single/Multisite.
  • If the Sitename is added to the right end of the sidebar should it link to anything? Some say it should link to the front page and others think it does not need to link to anything. Either way, long site names should be truncated.

#4-2, #nux

4.2 NUX Group Agenda, March 17, 2015

Here’s the agenda for Tuesday’s NUX working group chat in the #core-flow channel on Slack.

This is the sixth weekly chat for the 4.2 NUX working group. Just as a reminder, group discussions are open to anyone who would like to attend and participate. So please, join us!

Time/Date: Tuesday March 17 2015 19:00 UTC

DST Reminder:The Time/Date link above should display the correct time for you, whether you’re in DST or not. If you’re in Daylight Saving Time, the meeting will be an hour later than usual for you until March 31st.

Chat Leader: @DrewAPicture
Topic: Reviewing Welcome Panel flow reports

Welcome Screen Final from 2 24 2015 NUX meeting

  1. Last week and the week before, we sought volunteers to examine each of the flows out of the Welcome Panel.
  2. This week, we’ll go over any of the reports that came in about the various flows, check the comments on the above-linked recap post.

#4-2, #nux

4.2 NUX Group Agenda, March 10, 2015

Here’s the agenda for Tuesday’s NUX working group chat in the #core-flow channel on Slack.

This is the fifth weekly chat for the 4.2 NUX working group. Just as a reminder, group discussions are open to anyone who would like to attend and participate. So please, join us!

Time/Date: Tuesday March 10 2015 19:00 UTC

DST Reminder: If you changed over to Daylight Saving Time over the weekend, the NUX chat will be an hour later for you, though still 19:00 UTC.

Chat Leaders: @DrewAPicture
Topic: Working Meeting: Examining Welcome Panel Flows

  1. Last week we sought volunteers to examine each of the flows out of the Welcome Panel.
  2. This week, we’ll use the meeting time as a working meeting to continue documenting those flows. If you haven’t yet volunteered to document a flow, check out the recap posted over the weekend and leave a comment with the flow you’d like to work on.
  3. Next week, group members will report back with their findings and recommendations

#4-2, #nux

4.2 Nux Group Recap / Call to Action, March 3, 2015

Slack log (Requires Slack login to view. Set one up if you don’t have a Slack account)


This week’s chat was dedicated to looking at the proposed new Welcome Screen, assigning folks to “own” one of the links, identify several things and report back next week:

  1. The importance of highlighting that flow for new users in the Welcome Panel
  2. Once you’ve clicked through to it, what is currently good or bad, or could be improved
  3. Bonus: Whether this is a “Day 1″ link and if so, what should replace it?

Attendance at last week’s chat was sparser than usual, so we didn’t find volunteers to cover all of the Welcome Panel action links. If you’d like to volunteer to examine one of remaining the flows below, let us know in the comments.

The following people volunteered:

Settings

  • “Set your site front page” – @juliekuehl
  • “Turn comments on or off” – @suzettefranck
  • “Set your timezone and date format” – @courtneyengle
  • “Change URL structure” – @bethsoderberg

Appearance

  • “View your site” – @liljimmi @drewapicture
  • “Change or customize your theme” – @liljimmi
  • “Find new themes” – You? Looking for a volunteer
  • “Manage your site widgets” – @ipstenu

Content

  • “Write your first post” – @DrewAPicture
  • “Add a new page” – @abuango
  • “Edit your site title and tagline” – @jenniferbourn

Reporting Back

When reporting back with your findings, it would be helpful to document the current “workflow” for whichever action link you’re examining. Identify the pain points, possibly suggest alternatives, and provide vizrecs (visual records, i.e. screenshots) of your main points.

Things to keep in mind when writing your report.

  • Is this a must-have for the Welcome Panel?
  • Describe the flow from the point of clicking the link to following through the process
  • What is good or bad with the way it currently works?
  • Bonus: Suggestions for improvement

Reports can be shared in the comments and/or presented at next week’s NUX meeting.

#4-2, #nux