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.
Now that we’ve got a couple of rough patches (welcome screen, color picker, “view” my site) it’s time go back and test a few users in our first discovery cycle with these patches applied, and see if we’ve made any progress.
Here’s the video, and here are my notes:
Step two notes – Log in
No problems.
Step two notes – Explain what you see
No problems.
Step Three notes – Preview your blog
Step Four notes – Change your background color
Step Five notes – Change your site title
Step Six notes – Add your first post
No problems.
Step Seven notes – Preview your new post
No problems.
Step Eight notes – Publish an image
She found how to upload the image – not going to worry about anything after that for now, since media manager is being revamped. We’ll do plenty of user testing on the new media manager once it’s complete.
Recap
I’d like to get the color picker bug fixed before I run another user through these changes, but overall, I’d say these patches have already really improved things for first-time users. Thoughts?
Patches needed
Status update
Note: meeting on 8/7 did not really happen, as many were traveling or otherwise out of commission post-WCSF.
Meeting was largely focused on status check of various items and really bearing down on assignments and breaking down tasks into what can be realistically accomplished within a given time period (the next week) so we can regularly check in. Setting the goal is not the maximum that can be achieved – only the minimum. Things finished early or with aplomb are highly encouraged 🙂
Reminder: devs should ideally be focused on one large item at any given moment. Working on your own pet projects and roaming around is always fine, but would prefer to stay away from overcommitment, especially for point people. This includes me 🙂
We did some brainstorming at Dev Day today around improving the Help and Screen Options tabs in the admin. Keep in mind nothing here is a final decision, just some exploration of what we thought would be easy wins to make these tabs more useful.
Here are the problems with them right now:
Here are some of the possibilities we brainstormed (see notes below image):
Ideas:
We discussed possible changes to the labels:
I did a hi-fi mockup of what the new Help dropdown might look like:
Logs: https://irclogs.wordpress.org/chanlog.php?channel=wordpress-ui&day=2012-07-31&sort=asc#m49644
And finally, a reminder that open office hours are every weekday at 19:00 UTC (3PM EDT). #wordpress-ui is always open for discussions, but if you’re a little more nervous about just poking your head in or want to schedule something with a group, it’s a great time to do just that!
We’re working on HiDPI (“Retina”) support for WordPress. Of course, most people don’t have a Retina MacBook Pro at their disposal. So here’s how OS X-using WordPress developers can do HiDPI development without dropping $3,000 US on a laptop.
You can now use Safari 6+ or Chrome 21+ to view your WordPress development siteDevelopment Site You can keep a copy of your live site in a separate environment. Maintaining a development site is a good practice that can let you make any changes and test them without affecting the live/production environment. and do HiDPI development. Note that while you can do this with lower resolution screens, I’m not sure I’d recommend it — it’d be very cramped.
Over the past week or so, I’ve worked closely with @lessbloat (Dave), @nacin, and @markjaquith to create a set of media workflows that will hopefully serve as a foundation and guide for the improvements in this release. (This is the fifth version of these wireframes — you can see the first four on Dave’s site.)
The usual disclaimers: None of this is final. These are wireframes, so please focus your feedback on the experience, not the aesthetics. As for scope, we are focusing our changes on improving the modal experience. This focuses on the overall picture; not all of this will necessarily make it into the final release.
So, without further ado…
Wireframes and workflows — fullscreen recommended.
The media library.
The media library, while uploading three files.
The attachment details screen.
Relevant TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets: #21390, #21391.
There are a number of recent tickets about 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) improvements in the admin, several of which raise questions that relate directly 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. group. In particular:
#21283 Keyboard focus in the theme customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. should be on left options panel
#21310 Need skip link(s) at top of admin pages
#21312 How to log out of WordPress without a mouse?
#21324 Visible Focus within Admin Screens could be much clearer
#21326 Screen Options in Admin – Accessibility Enhancement
#21334 Accessibility of Quick Edit panel in Posts/Pages/etc
Please check them out and comment in-ticket with any feedback you may have; the same goes for any of the open tickets in the Accessibility component. Also, there are some tickets in the most recent batch that should be fairly easy for people who are just learning how to contribute. As always, you can ask here or in #wordpress-ui or #wordpress-dev any time if you need help with the whole process of working with tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. and trunk, applying and building patches, and the like.
In general, we want to be keeping accessibility in mind with all UI work and working closely with the accessibility group. Major thanks to everyone who has been stepping up and raising these issues lately!
I’d like to get the ball rolling on the new welcome screen redesign for 3.5. I started playing around with a few ideas and I’d love to hear your thoughts:
My hope for this screen is that it will serve as a proper “home” that users can come back to again and again to find anything they need in the admin. As I mentioned here, this was a big stumbling blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. for each of the users we tested.
A couple of notes:
Here’s the balsamiq source file if you’ve got some ideas based on this wireframe: http://cl.ly/1K3R2u383f28
This is all still very rough, and I expect that we’ll go through a couple rounds of iteration before we get it right. Thoughts?
The current goal is to HiDPI/2x current assets, whether that’s through making new versions of various images/icons or converting to CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. solutions (pretty much gradients and perhaps comment bubbles). Longer-term we may end up using other solutions, but for the moment let’s focus on the task at hand.
I’ve left a long comment about things I’m seeing as still needed. No need to know how to do the CSS patching – a dev can jump in and do that part if you’re more comfortable with the graphics side. What we need is people helping out with creating 2x versions of things, sometimes in various colors. We may need to coordinate with @empireoflight (Ben) to make sure there’s no duplicate effort.
You’ll want to be uploading files to TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. for the most part – if you want to have somebody take a look first, feel free to post a comment here or talk about it in IRC (office hours are a great time for that). Note that uploading files to Trac does not trigger an email notification, so you’ll want to leave a comment noting what you’ve added so it’s not overlooked. Again, feel free to ask questions here or in IRC if you’re not sure what to do and we’ll try to get you sorted!
You must be logged in to post a comment.