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.
@karmatosed started with some points of housekeeping.
WordPress 5.2 is out! Congrats to all that helped there.
Next up, there will be an a11yAccessibility 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) audit design triage Friday at 14:00 UTC. You may notice we’ve had a few lately and this is so we really push through the report from the Gutenberg Accessibility audit. The project board for the issues that have come out of that report can be found here: https://github.com/WordPress/gutenberg/projects/25.
@luke_pettway thanks everyone helping out there.
@mapk started with 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/ updates. Some issues that need feedback:
@hegdefield continued with a WordPress Showcase update:
He processed the few points of feedback on the design from last week and posted another iteration of the design to Figma. The past few iterations have been presented in the marketing meeting too and they were very happy with the result.
It wa agreed the design looks good, and is now ready for dev. Any further tweaking can happen in code during implementation. @Sjardo is standing by to be the dev on this, next step is to create a tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket. Super exciting!
@hedgefield also mentioned that the marketing team was doing interactive prototypes in Google Sheets, might be cool for designers to jump in for low-stakes wireframing stuff like that too early in some of these processes.
@mapk brought a call for design help from WP HelpHub, @kenshino is project lead. Helphub replaces the codex, lives at https://wordpress.org/support/. HelpHub is the non-dev equivalent of WP DevHub which is https://developer.wordpress.org/
There are some issues logged on their github repo, but the whole project probably needs fresh redesign + UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. review. @Ibdz offered to help.
Discussion topic: the ‘Needs Design’ label on trac.
Problem: it’s quite big. @karmatosed wants to see if we can pull out good first issues, and maybe also a few ‘featured ones’ each week. Might also be good fuel for contributor days. We want to keep the lists on trac so it doesn’t get stale, so maybe we add as extra tags to help filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. and audit once a month.
@hedgefield brings up adding more tiers than just “good first bugs” and “the rest”. “good first bugs” seems like entry level stuff that anyone could solve in a day basically, but there may also be small quick wins that still need a more advanced contributor to look at them. @karmatosed brings up a fair point that we don’t want to ‘grade’ people on their skill, but the exact distinction can be left vague, it’s more a way to leave info for future visitors about the complexity of an issue.
@karmatosed also suggests adding tags for categories of issues: ui/ux/icons/typography etc.
@melchoyce remarks we gotta make sure good first issues are actually easy, often they are more complex than they seem. Boemedia reminded us that there had been talk of adding design TL;DRs to make it easy for people to jump in.
@karmatosed will start by triaging the current list to define some possible filtering categories and we’ll continue discussion next week.
