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.
Thanks to everyone who attended this week’s meeting. If you couldn’t attend or want to read back what was said, here are the meeting notes for you. You can also read the full transcript on our Slack channel.
In March we will triage GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ design tickets. If you want to help move things forward, please join us for half an our in our SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel on next monday 17:30 UTC.
Showcase designs have moved to Figma, thanks to Rich Copping. Feedback and notes are welcome, but do note that the last round of feedback hasn’t been iterated on as we write this down.
@hedgefield is still working on this, in collaboration (amongst others) with the 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) team.
On short term, there’s help needed getting new dashicons in 5.2. This doesn’t concern the bigger picture of the future of dashicons that was discussed recently. @empireoflight says there’s no update on that front, although more feedback would be welcome.
@mapk updates us on Gutenberg phase 2. Currently, the team is looking to integrate a block management system. Gutenberg needs a way to organize blocks so it doesn’t get out of control. There’s also testing needed on the Classic (Legacy) widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. 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.. This is important to ensure that non-converted widgets have a home.
There’s also a proposal on the navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. block design. Please go check it out if you haven’t read it yet.
The marketing team requests to implement Navigation Change at make.wordpress.org. Design wise, we’re looking for volunteers to mockup what this could look like, to move the ticket forward.
The page proposals for mobile need design / UX feedback. If anyone wants to take a look and give their feedback, that would be appreciated.
Read this Slack thread if you want details, but in short, there are some concerns that the range slider as used in the blockeditor (for instance when selecting the number of columns, or the size of the dropcap) isn’t as accessible as it could be. As this could turn into a long discussion, @karmatosed suggests opening a GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issue for this.
The idea is to have a reminder to make sure your email is correct for admin. Please leave feedback on the Trac ticket if you have thoughts on this.
@tinkerbelly has a short remark on the use of different fonts in Figma. The suggestion is to keep it simple and therefore use one typeface consistently throughout all designs. @boemedia suggests using Comic Sans, but apparently that’s not one of the options.
Last topic tonight is documenting workflows for the design team. @karmatosed has made a start on writing out some of the processes the design team follows. It’s basically nothing new, but the main goal is to surface what we do as a team. Please leave your thoughts on this in the Google ‘work in process doc.
You must be logged in to post a comment.