Make WordPress Design

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Hugo Baeta 4:32 pm on August 25, 2016 Permalink |

    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!

  • Mel Choyce 2:15 pm on August 25, 2016 Permalink |
    Tags: dogfooding   

    Better Dogfooding Tips 

    This was originally written by @karmatosed. I’ve adapted it for WordPress.org.

    Dogfooding is a great way we can use WordPress and test our features. By testing WordPress ourselves, we get to unearth all manner of bugs, issues and fun things. Try setting up a new site from scratch, especially thinking about specific use-cases like a new photoblog, or a company website.

    I thought it would be great to come up with some tips for so new folks doing dogfooding can have a resource to start with. So, without further ado here’s just that!


    How you present the post really helps for people to read and also how we can use later on. A rough format for reporting your observations via video that works is:

    • Title: Make sure your title has the word “dogfooding” in it somewhere, so it’s easy to scan. Also include what feature you’re testing in title. ex: Dogfooding: Theme Setup
    • Use the more tag to shorten posts. It helps keep the p2 streamlined so it’s easier to scan.
    • Talk about your perspective as a user, and what you’re trying to accomplish.
    • Embed the video in your post.
    • Under the video, pull out any key points at minute marks. ex: 01:00: here’s where I spent a whole minute trying to search for directory themes from my installed screen. Keep this list short; don’t worry about pulling everything out, as if this is long, people will be less likely to read. Just make sure to list the biggest finds.
    • After that, it’s often useful to chop up the video (if it’s very long) and pull out significant clips. Making clips like this is useful for bug reporting and summaries. Clips can go after or next to minute marks, and also next to bugs for easier visual reference. Just consider that not everyone will want to watch your entire video. 🙂
    • Bugs: List out any bugs you found while testing. You can even do a fun thing by putting the bug emoji at end to make them stand out: 🐛
    • Summary: Summarize the main issues and conclusions you found from testing. ex: I stumbled a lot with the theme installation process because… If we did x or y it might improve this feature…
    • Tags: Tag it #dogfooding and anything else relevant.

    Here’s what the above would look like laid out:

    1. Dogfooding: Feature You’re Testing
    2. As a user, I’m trying to accomplish x
    3. Video embed
    4. 1:00: something amazing, 2:00: something else amazing
    5. Significant clips
    6. Bugs 🐛
    7. Summary
    8. #dogfooding


    If you see a bug, report a bug. It’s important we follow through on the bugs and don’t just leave them on this p2.

    The same goes for things you think are issues, or even enhancements. Sometimes you may think of something awesome nobody else has thought of before, and it could become something that changes the life of our users. Pretty cool right? That’s why it’s very important to report on trac.

    Enjoy and please dogfood 🐶

    The caveat here is that not everyone can post to p2s. It might be worth opening up make/flow, or liberally granting Authorship over there. I’ll be x-posting this post on that p2 as well.

    Maybe we should do a series of posts around a specific dogfooding topic, that people can comment on? This needs some additional discussion. 🙂

    • Tammie 3:01 pm on August 25, 2016 Permalink | Log in to Reply

      Yay awesome to see this 🙌❤

      I’d be happy to get involved in the starter posts and calls for dogfooding. I would love to see more people get involved. It’s incredible how it opens your eyes and gives you ideas. Also, I’ve yet to do dogfooding anywhere and not find a bug! This means we can fix bugs as we go!

    • Nick Halsey 1:11 am on August 26, 2016 Permalink | Log in to Reply

      I think this also underscores the importance of publishing with WordPress regularly. And going through processes like redesigning your site. There’s no better way to test flows than using them to publish real content.

  • Hugo Baeta 1:48 am on August 19, 2016 Permalink |

    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 Customizer – It needs a lot more UX 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 UI 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 CSS 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 plugin 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!

  • Hugo Baeta 3:19 am on August 18, 2016 Permalink |

    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 category 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!

    • Nick Halsey 3:43 am on August 18, 2016 Permalink | Log in to Reply

      The following tickets need design feedback, and would particularly benefit from discussion during the meeting (see specific points needing discussion in parentheses):

      • Content authorship in nav menus – #34923 (needs better wording for the link to edit a newly-published page)
      • A new experience for discovering, installing, and previewing themes in the customizer – #37661
      • Improving contrast and UI consistency in the customizer – #29158 (needs a strategy for back arrow hover/focus styles)
      • Custom background properties – #22058 (see latest comment, what about leaving it up to themes and taking the burden off of users)

      Depending on the new time, I should be able to start attending the meetings next week.

    • Mark Uraine 5:20 pm on August 18, 2016 Permalink | Log in to Reply

      We’re exploring ways in which screenshots would be displayed in the new Plugin Directory and can use some more feedback.

      As many of you know we’re building a single page layout. So rather than having a full page where we can list several screenshots on top of each other, we have a limited space to show them.

      There are a few examples here where the discussion is continuing:

      Recently, there’s been an idea to use the Jetpack carousel, but how do these screenshots get displayed on the page? Mosaic tiles, square tiles, a slider?

  • Hugo Baeta 9:48 pm on August 17, 2016 Permalink |
    Tags: 4.7, , wishlist   

    WordPress 4.7 Design Wishlist 

    Hello designers!

    First off I’d like to congratulate everyone on a great 4.6 release yesterday! During this cycle we brought back regular weekly meetings around design – It’s been a learning experience for @karmatosed and I, so we appreciate everyone who’s been actively engaged and supportive.

    Now it’s time to start focusing on what we want to see in 4.7. Had a conversation with @helen (the 4.7 release lead) and she suggested we have a design-focused wishlist post here to expose what is important to focus on in terms of design and user experience. She posted today on make/core about this as well, so you can comment on either post with your ideas. I’ll make sure whatever gets posted here reaches her for consideration. She also wrote a great post with some ideas for the release.

    Let’s get a conversation started!

  • Hugo Baeta 9:13 pm on August 11, 2016 Permalink |

    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 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 sidebar – 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!

  • Tammie 9:57 pm on August 4, 2016 Permalink |

    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!

  • Hugo Baeta 9:17 pm on July 21, 2016 Permalink |

    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.
    • WordCamp 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!

  • Hugo Baeta 7:31 pm on July 21, 2016 Permalink |

    Design chat agenda for July 21 

    This week’s chat is at the usual time today at 20:00 UTC, in about 30 min from now.

    Not much on the plate, as we get closer to the release:

    • About page for 4.6.
    • Open Floor

    Look forward to seeing you there!

  • Tammie 8:38 pm on July 14, 2016 Permalink |

    Design chat summary for July 14 

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

    In attendance was: myself, @hugobaeta, @mapk, @melchoyce, @FolioVision, @ocean50.

    • @hugobaeta updated us on the status with the about page #37246. Things are moving on there and @mapk is going to work on the shiny updates graphic with @hugobaeta working on the native fonts.
    • @FolioVision brought up #36999 that needs feedback.
    • WordCamp New York is happening this week and there’s a contribution day. There will be a design team lead by @melchoyce – woohoo!

    We’ll be back next week Thursday July 21st, 20:00 UTC!

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar