Welcome! This all-volunteer team needs designers of various kinds. See our handbook and drop into #design for volunteer opportunities.
Our vision is to be the go-to resource for design for other teams across the WordPress open source project.
The full transcript of our meeting this week, based on the previously posted agenda, can be found on our Slack channel.
The conversation continued with a brief discussion on recent experiences in WordCamps. You can catch up here.
The weekly design meeting is Wednesdays at 17.00 UTC. If you have anything else to add, please comment below or mention it on our Slack channel.
See Inbox column on Trello board.
See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc.
Filter Trello board for ‘needs discussion’ label. If none, triage any Trello cards that are not yet owned.
The full transcription of this weeks meeting can be found in our Slack channel.
We started off with another bit of information sharing amongst the group — this time focused on the tools we use to design and communicate.
This is a summary of the tools that were mentioned in the meeting:
No new cards this week
juliekuehl brought up Design for learn.wordpress.org
boemedia pointed to WordPress logo usage style guide for WordCamps
Let’s look at a couple Trac tickets
1. Activating a new theme on multisite is very long-winded https://core.trac.wordpress.org/ticket/18301. Needs updated screenshot/flow
2. Option to view condensed diffs for post revisions https://core.trac.wordpress.org/ticket/42086
The weekly design meeting is Wednesdays at 17.00 UTC (see it in your time). We’ll be discussing the topics below. If you have anything else to add, please comment below or mention it on our Slack channel.
See Inbox column on Trello board.
See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc. If time allows, see #needs-design tickets from Trac.
Filter Trello board for ‘needs discussion’ label. If none, triage any Trello cards that are not yet owned.
The full transcription of this weeks meeting can be found in our Slack channel.
We start off with a brief introduction round: who is who? It’s been a while and this way new and old contributors get to know each other and each other’s background.
What has been the experience of leading and attending the design table at contributor days at local WordCamps recently?
@karmatosed kicks of by posting a few talking points:
The team shares some recent experiences and @karmatosed suggest creating guidance for leading contributor day, but at the same time keeping different cultures, knowledge and skillsets of designers present in mind. A lot of suggestions come up and we conclude with @karmatosed making a Trello action item with some ideas in it that we can work from.
See Inbox column on Trello board.
Finally, @joyously asks if we can maybe change the order of the agenda, so we can spend more time following up on older design requests.
Thanks again to everyone who actively participated in this week’s meeting. Feel free to add your thoughts to the comments of this post.
The weekly design meeting is Wednesdays at 17.00 UTC (see it in your time). We’ll be discussing the topics below. If you have anything else to add, please comment below or mention it on our Slack channel.
A brief introduction round: who is who? So new and old contributors get to know each other and each other’s background
What has been the experience of leading and attending the design table at contributor days at local WordCamps recently?
See Inbox column on Trello board.
See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc. If time allows, see #needs-design tickets from Trac.
Filter Trello board for ‘needs discussion’ label. If none, triage any Trello cards that are not yet owned.
The weekly design meeting is Wednesdays at 17.00 UTC. We’ll be discussing the topics below. If you have anything else to add, please comment below or mention it on our Slack channel.
See Inbox column on Trello board.
See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc. If time allows, see #needs-design tickets from Trac.
Filter Trello board for ‘needs discussion’ label. If none, triage any Trello cards that are not yet owned.
Today’s meeting agenda was a bit light, so we opened did open hours to allow for folks to chat about anything specific items. You can also read the Slack chat log.
@cathibosco asked for feedback on the latest page designs for “Create a Blog”, great job Cathi! We discussed the pages that have been created so far and had some ideas for improving readability and breaking up the long (but important) copy on the pages. If you’re interested in giving feedback feel free to jump in!
We discussed several of the Trello cards briefly, but didn’t have a major update.
@EstelaRueda asked for some ideas as she is planning for Contributor Day at WC Nijmegen next week. We discussed some great analog ways to get folks prototyping and sketching as they contribute to current design needs in WordPress. You can checkout the Slack chat to jump to that section. Specifically speaking for this event it was recommended to focus on improving the handbook for design.
—
And that’s it for today. If you want to get involved feel free to jump into Slack and weigh in. We’d love to have you!
The weekly design meeting is Wednesdays at 17.00 UTC. We’ll be discussing the topics below. If you have anything else to add, please comment below or mention it on our Slack channel.
See Inbox column on Trello board.
See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc. If time allows, see #needs-design tickets from Trac.
Filter Trello board for ‘needs discussion’ label. If none, triage any Trello cards that are not yet owned.
In keeping with the loose structure, we spent the meeting focusing on a topic of the week and open floor.
Problem: a lot of information is there but not always where people expect it, or presented in a way that’s not easy to digest, or with labels people don’t understand.
@boemedia has begun work on a content audit of the 45 or so existing pages. This review will determine:
@hugobaeta suggested that making the structure more visual might help us to audit and update too.
@karmatosed will get people to help at WordCamp Brighton too.
Others, please weigh in on this async after reviewing the Trello card.
@kjellr is working on a pending update of the Gutenberg design handbook. Feedback welcome.
Note that this is geared towards people designing for Gutenberg — either contributing to the project, or designing a custom block.
@karmatosed: Gutenberg feedback is being processed. Now is a great time to jump in and leave design reviews.
There are several ways to test, and you don’t need a local install:
