Want to get involved? See the handbook and optionally drop into #design to chat. Most active design work happens in the block editor project, consider dropping into Needs design or Needs design feedback.
There’s a WordPress Component Library in Figma. Duplicate to edit, direct access is reserved for the design team.
Most links and buttons in the admin don’t have clear :focus and :active styling. This is a big problem when using the Tab key to navigate. There is usually no indication of what element is focused and if there is some, like on the admin menu, it’s quite weak/unnoticeable.
Thinking we should add clear and visible styles for :focus and :active everywhere by default. If this is impossible to do without making the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. “ugly”, can add another global screen option “Enhanced AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)” or similar that would turn these styles on.
Pinging all designers, if you come up with a nice solution, please add a screenshot (and possibly a patch) to ticket 21324.
Heads up: I’m taking a leave of absence! See the post on wpdevel make/core for details.
One of the goals for 3.5 is to redesign and improve the workflows for uploading and selecting media in WordPress. Over the next week or so, we’ll be working to flesh out exactly what this will entail from both a technical and design perspective.
To ensure we stay on track, our focus and top priority is to improve the “Upload/Insert” modal window. Anything outside of that modal UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. is technically out of scope — nice to have, but by no means necessary.
For the 3.5 cycle, we have allotted two months for feature development. Due to the size of this project, a lot will be going on at once. Development on basic structures will begin this week.
Over the next few days, feel free to comment with:
We should also be keeping an eye towards the future: we should build modular components that can be adapted for other workflows and potentially be reused in inline UIs.
The media modal currently covers media in posts, galleries, custom headers, and custom backgrounds. Several elements in the modal also blend into the media section of the admin.
Most workflows include a handful of processes:
I highly recommend reviewing our current media model. It is fairly complex, and reducing it to a simple system will be quite the challenge.
If you’d like to chat with myself and other UI team members about media, comment here, or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” us in #wordpress-ui (especially during office hours).
The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team recently began holding daily office hours in IRC (in the form of bug scrubs). I would like to extend them to the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. team as well, to encourage frequent discussion of core UI issues for 3.5. Office hours will allow newer contributors to become more involved and hopefully help keep the weekly UI chats a bit shorter in length.
For development office hours, go to #wordpress-dev — same time, different place.
Since 3.5 hasn’t officially started yet, I thought I’d play around with a quick proof of concept for the “Spotlight” search functionality this morning. Here’s what I’ve got so far:
There are still heaps of rough spots.
Here’s the plugin if you’re interested in taking it for a spin: http://cl.ly/0E3G2Y1J33372C3f3W3Q
Let me know if you think this is worth pursuing (even just as a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party).
In reviewing the first 6 user tests, one thing really stands out to me (it’s a glaring problem in each of the tests). Can you guess what it is?
It might not be what you’d expect…
Scope meeting in #wordpress-dev tomorrow, July 11, at 20:00 UTC is an official go. Not being a developer-type doesn’t mean you shouldn’t be there, even if you just lurk. Discussion will be had about scheduling and planning features. See you there!
http://wpdevel.wordpress.com/2012/07/11/version-3-5-scope-session-on-wednesday-july-11/
Round 3 of the “WP as a CMS” cycle is ready for your viewing enjoyment. 🙂 Previous user tests for this discovery cycle can be found here and here.
This one’s audio is a bit fuzzy at times. I changed up a few of the tasks to be a bit more clear on what I was wanting this guy to do. Have a look, and please highlight anything you spot (that could be fixed) in the comments.
Experiencing technical difficulties with the video – Sorry – I’ll get it posted as soon as I get that sorted…
Here’s round 2 of the “WordPress as a CMS” user test. You can view round one here.
As much as I love spending 2+ hours making notes on each user test video, I’m going to try a different approach with this one. As you watch this one, please make a note in the comments if you spot anything that could be fixed. I’ve found the “2:23 – Something happened here” format to work pretty well.
We’re in the middle of testing some users through a few “WordPress as a CMS” scenarios. One of the items that really stands out as needing some attention is the static front pageStatic Front Page A WordPress website can have a dynamic blog-like front page, or a “static front page” which is used to show customized content. Typically this is the first page you see when you visit a site url, like wordpress.org for example. setting in Settings->Reading (I’m sure this comes as no surprise to many of you ;-)).
I worked on a quick concept (with some helpful feedback from Jane) to get things rolling in #16379. Feel free to add your thoughts to that ticket.
If any of you devs want to work on a patch for this, you’d get a big gold star in my book! 🙂
