Design Meeting Notes for 4 March 2020

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.

Housekeeping

There is a reminder about Daylight Saving Hours. The proposal is to move forward meeting times by an hour on March 29. If people would also like a different time that is an option. Leave your comments at the bottom.

The design team is looking for notetakers. It’s imperative for the global community to share the notes on our meetings async. If you need any information, reach out to @karmatosed or any member of the team.

A second call is for triage volunteers, either coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./metaMeta 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. or 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/. @karmatosed and @mapk can help.

Updates

Several PRs got into WordPress 5.4 RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 on 3 March. The improvements coming in WordPress 5.4 include:

  • 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. Content Areas (full site editing)
  • Global Styles
  • Patterns
  • The new G2 UI work

Some other work that needs ideas, suggestions and your design skills:

https://github.com/WordPress/gutenberg/issues/20345

https://github.com/WordPress/gutenberg/pull/20354

https://github.com/WordPress/gutenberg/issues/20631

Open Floor

A question was raised whether if the design team maintains discussions on Figma as opposed to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/. The design team doesn’t have much discussions on Figma, we try to maintain the discussions on either the PRs, GitHub or the 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. But comments or design iterations are welcome. If you need access to the Figma account, please request it on the Slack channel.

@joyously presented an idea to link areas of an image to a URL. Some members recommended a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party or to look for a third-party block. It would be a great enhancement to add.

A topic for discussion: the overall state of the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. elements in Figma. Feel free to add your comments below or leave them in the Slack chat.

Design meetings are:

  • Core/meta triage: Monday 17:30 UTC
  • Gutenberg triage: Tuesday 17:00 UTC
  • Design Team: Wednesday 19:00 UTC

#meeting-notes

#weekly-design-chat

Design chat agenda for October 13

This week’s chat is happening today, at 17:00UTC

On this weeks agenda:

If anyone has other tickets the needs attention or other matter for the meeting, feel free to leave a comment with it. See you in a bit in the #design channel in Slack!

#weekly-design-chat

Design chat agenda for September 15

This week’s chat is happening tomorrow, at 17:00UTC

On this weeks agenda:

  • #27159 – Remove/re-arrange TinyMCE buttons to improve user experience, and new related tickets:
    • #38049 – Rename Headings in TinyMCE
    • #38050 – Replace `formatselect` with `styleselect` in TinyMCE
  • CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. Tickets (brought in by @celloexpressions):
    • #34343 – Make panel headers sticky? – thoughts on the gif showing the interaction?
    • #38002 – provide a path to editing posts created in nav menus – brainstorming session for how to provide users with links to edit newly-published content.
    • #37661 – A New Experience for Discovering, Installing, and Previewing Themes in the Customizer – make a schedule of deadlines for feedback and testing
    • #35210 – Add notification area to Customizer
      • Review of the 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. of comment 81 and how to clean up the styling
  • #22058 – Improve custom background properties UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. – give feedback on the new proposal and patch from @cdog
  • Open Floor
  • If anyone has other tickets the needs attention or other matter for the meeting, feel free to leave a comment with it. See you tomorrow in the #design channel in Slack!

    #weekly-design-chat

    Design chat summary for September 8

    This is the design chat summary on September 8. (Slack log).

    In attendance was: myself, @hugobaeta, @helen, @melchoyce, @foliovision, @celloexpressions and @afercia.

    • #37860 was talked about. We ended up thinking this needs a make.blog post about the bigger picture CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. wise and design patterns. @helen will write a post about this.
    • We looked at several customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. tickets #34343, #29158, #22058
    • @aferica would like input on #37969

    It was a great and active chat! Thanks everyone for participating. Next week we’ll meeting at. See you on Thursday September 15th, 17:00 UTC!

    #weekly-design-chat

    Design chat agenda for August 25

    I’m sorry for the late post, this week’s chat is happening in a few minutes, at 17:00UTC

    Since I didn’t get to post an agenda yesterday, we’re gonna keep it simple today:

    • Design projects for 4.7
    • Plan of action for #27159
    • Open Floor

    If anyone has other tickets the needs attention or other matter for the meeting, feel free to leave a comment with it. See you in a few minutes!

    #weekly-design-chat

    Design chat summary for August 18

    This is the design chat summary on August 18. (Slack log).

    In attendance was: myself, @michaelarestad, @foliovision, @mapk, @melchoyce, @jorbin, @helen, @westonruter, @remediosgraphic

    • I brought up the WordPress 4.7 Design Wishlist post, and @jorbin mentioned there are a lot of design-focused ideas on Helen’s post on make/core. Comment on one of the other, either is fine.
    • We decided to move the weekly chat time back to 17:00 UTC, starting next week.
    • @celloexpressions brought up a few tickets in the agenda comments that we discussed:
      • #34923 – Allow users to more seamlessly create page-based nav menus during customization – needs better wording for the link to edit a newly-published page. The discussion resulted in a consensus to actually remove the link.
      • #37661 – A New Experience for Discovering, Installing, and Previewing Themes in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. – It needs a lot more 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. thought, it wasn’t an easy ticket to talk during the chat as it’s quite intricate. If anyone wants to contribute some UX thinking there, that would be very welcomed!
      • #29158 – Customizer UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. Design lacks contrast for visual hierarchy and does not match wp-admin – @celloexpressions believes it needs a strategy for back arrow hover/focus styles. in the conversation it became clear that the ticket is becoming too broad, and that some of the things in there needs a prototype for testing. Everyone agreed that the left-border blue indicator should be committed, and that the rest of the ticket should be broken up into smaller tickets.
      • #22058 – Improve custom background properties UI – he wanted us to focus on the last comment that mentions an idea of leaving these decisions up to the themes. The conversation went into a notion that these options are visualizing what the CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. is doing, not necessarily helping the user make a decision. Overall everyone feels that the solution in the ticket is a tad heavy and not really focused on the users. The conversation continued on the ticket itself.
    • @mapk asked for us to help out with some critique on the implementation of the screenshots portion of the plugin page on the new Plugins Repository (in beta). The generalized consensus was that the screenshots should be in order and include the description very clearly, as in current pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party directory they are used to guide users through the usage of the plugin mostly. Questions like “should this be a separate tab” were brought up as well. @melchoyce suggestion was for @mapk to step back and sketch other ideas and consider how both users and plugin developers are using and could use this.
    • We skipped @karmatosed Old Ticket Sweep (but, please, go through them in the chat agenda post!

    It was a great and active chat! Thanks everyone for participating. Next week we’ll be moving to the new(old) meeting time. See you on Thursday August 25, 17:00 UTC!

    #weekly-design-chat

    Design chat agenda for August 18

    This week’s chat is on Thursday, August 18 at 20:00 UTC

    • WordPress 4.7 Design wishlist discussion
    • Design Weekly chat meeting time change
    • Tammie’s Old Ticket Sweep:
      • #29076 – The Minor Publishing Actions (Buttons) need some breathing room
      • #25419 – Add icon support for widgets on the admin page and customize screens
      • #22976 – Remove reference to categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. to tag converter from the tools page
      • #23477r21789 creates a breaking change in behavior for get_submit_button
      • #33141 – Search form clear button is clipped in Safari (OS X)
    • Open Floor

    If anyone has other tickets the needs attention or other matter for the meeting, feel free to leave a comment with it. See everyone tomorrow!

    #weekly-design-chat

    Design chat summary for August 11

    This is the design chat summary on August 11. (Slack log).

    In attendance was: myself, @karmatosed, @mapk, @foliovision, @melchoyce, @afercia

    • @celloexpressions had requested for us to bring up #34923 during the chat. It’s a complex ticket, but hopefully it will get some eyes on.
    • During open Floor, @karmatosed shared a list of tickets that need attention:
      • #37384: Text alignment in options-discussion.php – @foliovision is gonna spend some time on this
      • #30599: media views: improve keyboard 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) avoiding confusing tab stops – We came to the conclusion it doesn’t need ui feedback, it’s a purely accessibility issue
      • #32194: Post Locked Notification Dialog is not Responsive – @mapk found a bug in there and is opening up another ticket for it. @foliovision is also looking into it
      • #26605: Appearance of recent/future posts in dashboard looks off on mobile.
      • #27253: Enhancement Request: direct link to Drafts under Posts and Pages on the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. – I added a quick inspector mockup screenshot to the ticket to help visualize it.

    We’ll be back next week on Thursday August 18th, 20:00 UTC!

    #weekly-design-chat

    Design chat summary for August 4

    This is the design chat summary on August 4. (Slack log).

    In attendance was: myself, @hugobaeta, @foliovision, @ocean90, @petya, @melchoyce, @samuelsidler, @afercia, @presskopp

    • The about page was discussed #37246. It’s close to release and @hugobaeta led us through the latest iteration.

    We’ll be back next week on Thursday August 11th, 20:00 UTC!

    #weekly-design-chat

    Design chat summary for July 21

    This is the design chat summary on July 14. (Slack log).

    In attendance was: myself, @karmatosed, @foliovision, @mapk, @voldemortsen.

    • I gave a short update on the status of the about page #37246. Things are moving along and I’ll begin working on the layout of the page this week (here is a collection of past About page designs). @mapk is continuing the work on the shiny updates interactive bit (fallback for when the users have no updates), and I’ll circle back to the Native Font one.
    • WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Brighton is happening this weekend and there’s a contribution day. @karmatosed will be there and is asking for tickets to work on – se feel free to reach out to her!
    • @FolioVision brought up #36999 – he updated the ticket with the requested screenshots and it seems ready for commit. @karmatosed and @voldemortsen +1’d it.
    • A discussion about the overuse of `!important` spawned off of the previous ticket, and there’s a ticket for an `!important` audit: #26350

    We’ll be back next week on Thursday July 28th, 20:00 UTC!

    #weekly-design-chat