How you can help with the Network Admin UI during contributor day

A previous write-up explains how you can help test and capture the network admin UI. Here’s a specific version for how you can help during contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. this weekend.

There are four steps to the workflow at the moment:

  1. Capture a visual record of networknetwork (versus site, blog) adminadmin (and super admin) screens.
    • Ideally on a device/browser combination that has not yet been captured.
    • If comfortable, post the screen captures and notes on make.wordpress.org/flow.
    • If you need access to Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)./Flow, ask in #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-flow 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/. or around the physical room you’re in (if it’s full of contributors).
  2. Observe screens, actions, and results throughout the network admin.
    • This can happen during or after step 1. You can also just do this without the first step.
    • Look for things that don’t make sense, visual errors, pieces that are difficult on mobile, etc…
  3. Document observations in the screen sweep sheet.
    • This can be with or without a TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker.. With or without a screenshot.
    • Acts as a note so that we know that to come back to as part of the overall admin UIUI User interface improvement effort.
  4. Help with the screen sweep sheet.
    • Open a ticket if there is none. Add screenshots if there are none. Confirm/deny the issue.
    • And patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. If there’s a ticket on the screen sweep sheet that you can patch, submit away.

While this is an ordered list, you do not need to treat it like one. Pick a step that feels comfortable and concentrate on that. If you need guidance, there are folks in Slack that are always happy to help.

Current captured visual records:

By all means, if you have a device that is already captured, don’t hesitate to capture it in your own way or to skip step 1 entirely and start observing.

Thanks for the help!

#contributor-day, #multisite