Tag Archives: Weekly Design Chat

Hugo Baeta 1:04 am on June 17, 2016
Tags: Weekly Design Chat   

Design Chat Summary for June 16

This is the summary from the Design Chat on June 16 (Slack log)

Attendees: @karmatosed, @voldemortensen

We had no agenda today, so it was all open discussion. But since it was only 3 of us, we didn’t had much objective topics to talk about.

Next week @karmatosed and I will be in Vienna for 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. Europe! If you’re around, come say hi and join us on Sunday for the contributors day in the Design table. We’ll coordinate with @ocean90 to try and move some pending design tickets along while we’re all together there!

There won’t be a chat next week. We’ll be back to the weekly chats on Thursday June 30, 20:00 UTC!

#weekly-design-chat

Hugo Baeta 6:18 pm on June 2, 2016
Tags: Weekly Design Chat   

Design Chat Summary for June 2

This is the summary from the Design Chat on June 2 (Slack log)

Attendees: @karmatosed, @mapk, @johnragozzine, @voldemortensen, @afercia

Topics

  • Design Chat, starting next week, is moving to Thursday June 9, 20:00 UTC – I’ve asked for the meetings page to be updated with the new time.
  • We discussed #35191 and it seems like the ticket will be divided into two: one about the tool tips, another about the visual changes to the table. @afercia mentioned he wants some more feedback on the link/text placement and wording, and that can happen in the existing ticket. So comment away!
  • That discussion spinned off (ha!) into a side conversation on the need to add a spinner to the shinny updates project, and how it’s important to keep consistent with the existing spinners in the admin.
  • I gave an update to the 50 Shades of Gray project. @voldemortensen helped me compile a list of colors, a total of 174 unique color declarations were found in the admin css. I’ve started organizing it in a codepen and the next step is to start making changes and then doing some QA (@johnragozzine offered to help with this) to make sure the changes are not messing anything up.
  • Open Discussion didn’t get any takers, so I shared an idea to replace Open Sans on the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ sites now that coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is moving to system fonts. I made an exploration with a pairing of Source Sans Pro and Noto Serif on a codepen in an attempt to bring back a serif typeface to WordPress.org. Feedback welcomed!

That is all for this week. Thanks to the attendees! @karmatosed will lead next week’s chat (on the new time slot) on Thursday June 9, 20:00 UTC!

#weekly-design-chat

Hugo Baeta 4:49 pm on June 2, 2016
Tags: Weekly Design Chat   

Design Chat Agenda for June 2

the design weekly chat happens in a few minutes, at 17:00 UTC. Short agenda today, feel free to add more topics in the comments or bring something up during open discussion:

  • @karmatosed brought up some time conflicts and is proposing we move the time of the Design Chat, starting next week, to June 9, 20:00 UTC. Let’s discuss and if everyone agrees, we’ll switch it.
  • @afercia needs some feedback on #35191
  • The 50 Shades of Gray – Continued.
  • Open Discussion

See you in a few minutes!

#weekly-design-chat

Tammie Lister 5:59 pm on May 26, 2016
Tags: Weekly Design Chat   

Design Chat Summary for May 26

Archives can be found here.

We had a shorter meeting with a few main points brought up.

Thoughts are still wanted for #36922.

We discussed #36424 as requested by @ocean90. I added a comment that sums up our thoughts, we need to know why this is important on this screen, before we even look at the visual idea.

@westonruter brought up #34923. @mapk is going to update the ticket with our feedback discussed.

There was an open floor but no other subjects were brought up.

Next week’s meeting will be lead by @hugobaeta and at the same time in #design on 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/..

#weekly-design-chat

Tammie Lister 11:31 am on May 26, 2016
Tags: Weekly Design Chat   

Design Chat Agenda for May 26

The weekly design meetings continue today at 17:00 UTC in #design on 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/.. Topics to include this week:

  • Opinions on widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. message: https://core.trac.wordpress.org/ticket/36922.

As you can see, we only have one agenda item, so we need more! Feel free to bring things up in the open discussion or leave a comment here for discussion.

#weekly-design-chat

Hugo Baeta 10:58 pm on May 20, 2016
Tags: Weekly Design Chat   

Design Chat Summary for May 19

This is the summary from the Design Chat on May 19 (Slack log)

Attendees: @mapk, @voldemortensen, @melchoyce, @kenshino, @empireoflight, @isaackeyet, @zetaraffix, @celloexpressions, @westonruter, @obenland, @emanweb.

Topics

  • Shades of Gray – the never-ending story update
    With the help of @voldemortensen, who generated a list of admin colors for us, I was able to start compiling them in a list on codepen. The idea is to use this list to help visually merge some close values. We’ll need to also figure out context before we start opening tickets with patches to change the values.
  • #34893: Improve 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. setting validation model (slack log)
    @celloexpressions and @westonruter jumped in the chat to explain what is going on here. Essentially, the ticket adds the ability for customizer settings to provide feedback to the user when there are errors, warnings, or info that should be provided regarding the validity of a setting. There was a lengthy discussion about this, where it was decided to add a section outline and/or a field outline for affected fields with errors.
  • Shiny Updates Review
    @mapk and @obenland stepped in to share the progress of the project. Basically they need design reviews and testing testing testing!
  • Open Discussion
    • #34923 needs design feedback and testing
    • The redesign of WordPress.tv came up, but the project is stalled (at least the community involvement is) since it’s an Automattic site.

Thanks to everyone who attended. @karmatosed will be leading the chat next week on Thursday May 26, 17:00 UTC!

#weekly-design-chat

Hugo Baeta 4:28 pm on May 19, 2016
Tags: Weekly Design Chat   

Design Chat Agenda for May 19

The weekly design meetings continue in less than an hour at 17:00 UTC. This week subjects will include:

  • Shades of Gray – the never-ending story update.
  • #34893: Improve 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. setting validation model
  • Shiny Updates Review
  • Open discussion.

Not a lot of topics in the agenda, so feel free to bring things up in the open discussion or leave a comment here! See you in a bit!

#weekly-design-chat

Tammie Lister 8:57 pm on May 12, 2016
Tags: Weekly Design Chat   

Design chat summary 12th May

Thanks to @zetaraffix for taking amazing notes again, (Slack log).

Attendees: @hugobaeta, @zetaraffix, @designsimply, @mindsize, @ocean90, @voldemortensen, @karmatosed, @mapk, @swissspidy, @celloexpressions, @aubreypwd, @chrissmith.

Agenda

    • Shades of Gray – the neverending story update.
      @hugobaeta has been having a hard time getting the actual list of colors used: cssstats.com needs .css urls to make a list, but wp-admin (at least the one running on make sites) uses a compiled .php, so it can be done manually for every single one. Looking for better ways, @voldemortensen offered to run a grep on trunk and did so before the end of the meeting.There are a few duplicate colors because of comments and stuff, but he narrowed it down from 1082 lines to 314. You can find it here.
    • Shiny updates deep dive. We dug into several issues with this as @mapk guided and summarized issues while asking for more opinions. The following is from that.

      Issue 1.

      There’s a disconnect between installing 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 from the directory, and then knowing where to go to activate it. Right now, with Shiny Updates, the user installs and the button changes over to “installed”… but there’s not indicator to ‘activate’ it. So we’re exploring ways in which we can have them activate it right from the directory, or something.On the the Plugins > Add screen, Shiny Updates kinda keeps the experience inline with the action, since we no longer have a second screen after you click “Install”, the screen that has a “Activate plugin” link on it, and we’re just doing all the installation directly on the same page, we need a new solution, as ‘activation’ will most likely require a page reload.

      The question now becomes ‘when’ this appears if there are multiple installs inline, we can’t reload the page. But rather than trying to figure out the tech difficulties… I think, our discussion here, it should be around experience.Issue seems to be related to multiple installs.

      Also, the issue seems to also include “why” the process is at the moment so clumsy: why we only install and then activate now? (not to introduce a new flow that will cause domino issues we’re not aware of).

      According to @ocean90, we can’t install and activate at the same time because some plugins are doing redirections on activation and other stuff. Another reason is that new menus won’t be visible until a refresh.

      A possible solution (latest proposal) will be to change whatever was a “install” button, into an “activate” link. @mapk asks for more eyes to be better sure. In particular to see if users manifest issues of morphing button fear.

      @mapk proposes to as initial solution around that to have the ‘installed’ button fade out, and in it’s place show a blue primary button which might offer the visual difference needed to help that issue.

      Here’s the link to the tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket:
      https://github.com/obenland/shiny-updates/issues/64

      Issue 2
      https://github.com/obenland/shiny-updates/issues/5#issuecomment-218593910

      Trying to figure out what to do with the bunch of buttons that appear at the top of the WordPress Updates page. So far, we’re thinking of dropping the ‘download’ stuff. The ‘update’ button would be inline with the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. software row in the new table. But the ‘re-install’ button needs a home. It seems like an edge case… so I’m proposing we move it to the bottom of that page.Below the updates.

      One suggestion is for it to be a link, not a button (so it’s obviously less relevant) but it’s being that ‘re-install’ is performing an action seems to legitimize it being a button, as in general links are for changing views.

    • #33007: Add a dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. that encourages users to translate WordPress. Looking for a general feedback/opinion on that, so please add your thoughts to the trac.
      Interesting to know how the preferred language is established.
    • User testing handbook page: we now have one thanks to @designsimply. She lead us through this and the following is in her words. A little background:
      • my goal was to make it short but still prescriptive enough to really encourage people to get started (think low barriers to entry)
      • it focuses mainly on a hallway usability testing style because I think that will get the max return for the least effort for this group
      • purposely didn’t mention paid tools like UserTesting.com because the context is open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. & volunteer I’m thinking of adding another, more detailed page at @karmatosed‘s suggestion. This page compliments the main User Testing page and is intended to give more detail and tips once someone has made it past the hurdle of getting started with testing. You can find it here.
  • Open discussion: we had only a minute so nothing else came up.

Next week @hugobaeta will be leading the meeting. Thanks all who came and don’t forget we have this meeting every week, same time and same 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.

#weekly-design-chat

Tammie Lister 7:25 pm on May 11, 2016
Tags: Weekly Design Chat   

Design chat agenda for May 12th

The weekly design meetings continue with one Thursday at 17:00 UTC. This week subjects will include:

We’ve not got that many subjects on the agenda so please add anything you’d like covered to the comments here. If you want some help from the designers in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., just come along as you will have a great opportunity to get some assistance this meeting.

#weekly-design-chat

Hugo Baeta 2:38 am on May 7, 2016
Tags: Weekly Design Chat   

Design Chat Summary – May 5

This is the summary from the Design Chat on May 5 (Slack log)

Attendees: @zetaraffix, @afercia, @adamsilverstein, @ocean90, @michaelarestad, @eric, @johnragozzine, @frozzare, @rousseln, @mjcoop, @shramee, @voldemortensen, @andg, @aduth, @codeart, @tddewey, @mikehale, @macmanx, @katzwebservices, @ruknaree, @mgratch, @melchoyce, @arush, @beatstore, @ueli, @helen, @karmatosed, @danw33, @chriscamplejohn, @timothybjacobs, @eightbits, @paaljoachim

Topics

  • The Shades of Gray project (ticket #35783)
    @afercia shared the progress of this project, and explained how its objective is to reduce the number of grays used in wp-admin by merging hues close to each other, with 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) in mind. I (@hugobaeta) explained that the WordPress Color Palette I have going on in codepen should evolve along with this project. It was suggested to use a tool like cssstats to generate the list of existing hues, and do a more visual mapping of these. I offered to work on this moving forward, since @afercia doesn’t have much time for it. the goal is to have a bit push on this for 4.6.
  • Theme installer upload button improvements (ticket #35457)
    @afercia explained briefly what the issue was and asked for help with feedback on this ticket.
  • Revamp 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. boxes (ticket #36474)
    One of the larger tickets for 4.6 needing design attention. @michaelarestad explains it’s part of a larger set of changes that will hopefully improve the publishing flow, and we need to solidify what we hope to gain from it. This ties into the “Improving Post New” list. It’s important to keep the discussion moving forward in the ticket.
  • “Permalink Settings” admin page is largely blog/post specific (ticket #35796)
    @eric asked for this ticket to be brought up in the chat. The ticket is specifically about the language used around the Permalink settings, but has evolved to a discussion about 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.. It was agreed that this discussion should move to a new ticket about a redux to the whole Settings area. @michaelarestad offered to help with this. Him and @eric should touch base about this topic soon.
  • The design of the focus outline on buttons/elements could be improved (Ticket #34904)
    @michaelarestad brought this up during Open Discussion. He wants to commit it, but some concerns were raised about the styling. All feedback should be added to the ticket asap before it gets commited.
  • Other tickets needing attention
    • #34323 Make 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. media control placeholders clickable
    • #9777 add delete button to edit-tags.php
    • #36175 Simplify the Customizer Image Control action buttons
    • #34923 Introduce basic content authorship in the Customizer

Thanks to @zetaraffix for taking notes during the chat 🙂

Next meeting is on Thursday May 12, 17:00 UTC

#weekly-design-chat