These are the weekly notes for the design meeting that happens on Wednesdays. You can read the full transcript on our Slack channel and find the meeting’s agenda here. You can join the Slack 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 by following the instructions in our handbook.
During the month of August, both triages (core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and Gutenberg 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/) will be short, for 30 mins only. We will resume our normal, one hour long triage session on 1 Sept. Also, if anyone would like to volunteer to take notes or lead a triage session, please lleave a comment or reach out to @mapk (for Gutenberg triage) or @estelaris for core triage.
@michael-arestad brings us an update on Gutenberg design work:
Gutenberg 8.7 was released today! And here is the plan for Gutenberg in August.
If you are new to the design team, go ahead and click on those links, check out the great work the design team is doing in the block 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. editor.
Calls for Help/Feedback
The Training team sent us a call for help on designing the new learn.wordpress.org. @melchoyce has agreed to help them out.
The WCUS team has reached out to ask if the design team is interested in participating on a 24hrs contribution day. There are no details yet, they are asking around to find out how many teams would be interested.
The Theme team has also been interested in participating and would love it if we could team up and work through some designs for long outstanding tickets they have been wanting to get through.
So we can say there is interest in this, and we’ll keep bringing this up in the next few meetings to get more input. If you have thoughts about this, please leave a comment.
@mapk was wondering how we might get more people working on Gutenberg issues. What can we do to share more current work, and request feedback or even use some time to help community designers jump into specific Gutenberg tasks? The triage sessions have been wonderful, but those tend to focus on older issues, and the Gutenberg updates don’t really spawn much activity.
The idea of a design mentorship or dedicated Gutenberg sessions during our design meetings was floated. What do you think? What would you need to start contributing (more) to the visual development of the block editor? Let us know in the comments.
Lastly, @aristath brought up the point that the font size on .org is too small. This is a point that has been raised by accessibility 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) experts before in regards to the WP interface too. There has been work done to see if we can increase the size, but WordPress is a massive project, and not every area fully adheres to the style guidelines – insofar as those exist. We have guidelines for core, but not for meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.. @estelaris will take charge on writing a draft for those and bring them to the a11y 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) and meta team, and to us, next week in the design meeting.