Welcome! This all-volunteer team needs designers of various kinds. See our handbook and drop into #design once signed up for volunteer opportunities.
Our vision is to be the go-to resource for design for other teams across the WordPress open source project.
X-comment from +make.wordpress.org/updates: Comment on 5.0 Release Retrospective Wrap Up
This is the agenda for the weekly design chat meeting on Wednesday, 1st May 2019, 18:00 UTC.
This meeting is held in the #design channel in the Making WordPress Slack.
Leave a comment if you would like something reviewed, design help or something added to the agenda.
You can read the full transcript of this meeting on our Slack channel. You can also read the agenda for this week.
@mapk just posted a proposal for Widgets-to-blocks UX flow on make/design.
It’s that time of a release when the about page is thought about. If you’d love to get involved, @melchoyce has already boosted us by adding a lot of the past work to Figma. Feedback on the ticket is most welcome.
@boemedia created a prototype/user flow for a new screen in the login process, where WordPress validates the general admin email as entered in the settings page. She’d love some design/UX feedback on the prototype. Please read her comment on the ticket and check out the link to the prototype.
@lessbloat created a proposal for simplifying the WordPress Admin Navigation. You can check out his early explorations on Trac and give feedback on the ticket. Next steps will be to iterate based on feedback and pull together a working proof of concept plugin for people to test.
With the introduction of Gutenberg and blocks comes the need for a way to install new blocks, just like plugins or themes. Step one in this project, for the design team, is installing blocks contextually within Gutenberg. Check out this thread for more details and prior explorations.
The WordPress.org API will provide an endpoint for searching for blocks by name and description, and return metadata similar to that of plugins. Gutenberg’s Inserter could use that endpoint to also show relevant block plugins that are available to install, with a button and process for seamless installation.
@tellyworth
This project is limited to installing one block at a time from within the Gutenberg editor. That might encompass:
This scope is intentionally kept small so we can focus on shipping an iterating. A larger exploration of how to download or install blocks from within a Blocks screen in wp-admin, and WordPress.org, will take place in a future project.
| Task | Stage | Facilitator | Due | Status |
| Create repo | Scope | @karmatosed | April 26 | ✅ |
| Create project board for design tasks in GitHub | Scope | @karmatosed | April 26 | ✅ |
| Create issues in GitHub for design | Scope | @karmatosed | April 26 | ✅ |
| Make/design kick off post | Scope | @melchoyce | April 26 | ✅ |
| Make/meta kick off post | Scope | @tellyworth | May 3 | |
| Competitive analysis | Research | TBD | May 17 | |
| Research into plugin directory | Research | TBD | May 17 | |
| Experimental explorations | Exploration | TBD | May 24 | |
| Flow diagram | Exploration | TBD | May 24 | |
| Iterate on experimentations | Refine | TBD | May 31 | |
| Make/design post of designs | Refine | TBD | May 31 | |
| Prototyping (click prototype/Figma) | Prototyping | TBD | June 7 | |
| Testing/feedback on prototype | Prototyping | TBD | June 14 | |
| Update GitHub issue to start development | Development | TBD | June 21 | |
| Prototype (technical prototype) | Development | TBD | June 28 | |
| Testing/feedback on prototype | Development | TBD | July 5 |
See the complete timeline on Google Drive.
Interested in joining @iviolini and I on this project? Let us know in the comments, and follow along on GitHub.
If you don’t have time to devote to working on design tasks, that’s cool — feedback is always welcome, and a great way for you to contribute.
Due to the recent holidays and other happenings, various design contributors had some time off including me. Taking this into account, there’s still some good work getting done.
While the PR is still being worked on, there have been some great feedback from designers and accessibility.
A post was recently published about the UX flow for introducing blocks into the widgets screens in both wp-admin and the Customizer. The thought is to leave the current navigation labels (ie. Widgets) in the wp-admin navigation sidebar and just refresh the UI. This would be similar in the Customizer too.
Due to the new Group block being introduced, some patches needed to be created for the default Twenty Nineteen and Twenty Thirteen themes. If you have some time to test these out, please do and leave feedback.
Thanks for reading, staying informed, and contributing anywhere you can!
As noted in an earlier Gutenberg design update, I wanted to communicate a proposed UX flow for rolling out the widgets-to-blocks interface changes. It’s a proposal and still up for discussion along with further communication in the Github PR, Add blocks in widget areas RFC.
The Github issues include: wp-admin interface and the Customizer.
Widgets are now blocks which require a new Gutenberg interface to help people transition to this new paradigm. What is the best way to introduce the new widget-block screens to users? How can we do this with the least amount of development time, use existing patterns, and clearly communicate the gradual transition to blocks?
I began by segmenting the use cases:
My initial work included using different menu items in wp-admin and the Customizer based on if the user had existing widgets in their site. A user with existing widgets would need more help transitioning to a new interface than a user without any prior widget paradigms.
After further investigation of this, I opted out. If the menu items segmented, it might cause more confusion because there would be some users with the new menu items while another may have the old. Documentation and internet tutorials could get difficult to follow at that point. I’d like to do this with the least amount of development time, and confusion on the user’s end.
To achieve a simple and non-confusing rollout, keeping the wp-admin menu items the same might be the best option. The user would still see “Widgets” under the “Appearance” menu item. When clicking that to view the widgets, the user would now get the new Gutenberg Widget Areas screen.
We’d need to make sure the proper messaging or tips are displayed on this page to help orient the user to the new layout.
This scenario would work similarly to the one above. When clicking into the Customizer, the user would still see “Widgets” as an option if the Theme provides it. This shouldn’t require any additional work on the part of the theme outside what is currently required. Once clicked the user sorts through the blocks and can add 3rd party unconverted widgets with the Legacy Widget block.
So that everyone’s aware, the discussions around why blocks are being introduced in the widget screens is already explained in the Github issues, and in comments on other sites. This is one of the 9 projects for 2019, and aims at helping everyone slowly make the transition to the block paradigm.
The feedback I’m looking for here is:
This is the agenda for the weekly design chat meeting on Wednesday, 24th April 2019, 18:00 UTC.
This meeting is held in the #design channel in the Making WordPress Slack.
Leave a comment if you would like something reviewed, design help or something added to the agenda.
Gutenberg 5.5 is released! The long-anticipated Group block is now available. In addition to a strong list of enhancements, there’s even a bit of a performance boost. This release included 48+ contributors, thanks, everyone!
This is a short post this week. For more information, read up on the release notes linked above, and visit the GitHub issues/PRs labeled Needs Design Feedback or Needs Design.
Prior to the release of WordPress 5.0, @jarahsames conducted a survey with WordPress users regarding the new Gutenberg experience. Here are the results.
Thanks for reading, staying informed, and contributing anywhere you can!
X-comment from +make.wordpress.org/community: Comment on The Get Involved table at WCEU 2019
You can read the full transcript of this meeting on our Slack channel. You can also read the agenda for this week.
The designs are progressing nicely. They aren’t quite at a stage of soliciting feedback yet, but Tim is making headway working through the good feedback on the previous iteration that was spearheaded by Rich Copping.
Tim’s main iterations are in styling things according to the existing elements and colors, and the page has been shortened without losing feature. If you’re curious you can take a look at the Figma file.
The team had some discussions on a few points, and we can look forward to a formal state next week for review.
@CK Lee left us a ticket for feedback on a screenshot user interface for the plugin directory. There’s a screencast on the ticket, and some additional context in Slack on the feedback that’s needed.
Estela finished reading all of the handbooks and found 18 mentions of color. A Trello card has been created and @melchoyce wants to work on the color pages for the handbook.
Nothing specific today.
