Help Test and Capture the Network Admin UI

One of the wider objectives of WordPress 4.3 is to improve on the Networknetwork (versus site, blog) Adminadmin (and super admin) UIUI User interface. This includes refining the experience on different device sizes. We first need to capture a baseline of existing screen flows and identify tickets from that.

We need help capturing this data. 🙂

Having access to a local, multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site WordPress installation is the preferred method, as you’ll have an easier time making changes, applying patches, and generally having control over the data. Here are some guidelines for testing locally:

Realizing that installing and configuring multisite locally can be a barrier, a test server is available for anyone to access. This test server has two network installations, one for subdirectory and another for subdomain. Data will be reset on a regular basis. This allows anyone to go through the various network admin tasks.

Both networks are running trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. as of about 20 minutes ago. I’ll be making an effort to automate the maintenance of that setup.

If you’d like a super admin account to these networks, leave a comment below or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @jeremyfelt anywhere. #core-multisite is preferred. I’ll create a matching username to your 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/ profile name and set you loose to capture and break things at will. 🙂

Once you have a test network available, here are the things we need captured:

  • Add a new user to a sitesite (versus network, blog) when the user does not currently exist as a network user.
  • Add a new user to a site when the user does exist as a network user.
  • Install, enable, and then activate a theme for a single site on the network.
  • Install a theme and enable it for use on a network.
  • Install and then activate 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 for use on a single site on the network.
  • Install and then network activate a plugin.
  • Create a new site on the network.
  • Update a plugin.
  • Update a theme.
  • Edit the domain/path for an existing site on the network.

Once captured, it’s great to share all of the data on the 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 site, with a description of the screens tested and the device/browser configuration. If you need access to Make/Flow to post your results, leave a comment here or in #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-flow.

Specific details on each of these screens should also be added to this spreadsheet that the overall Admin UI team is using to coordinate efforts. Feel free to capture one workflow or many.

If you notice a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. in the screens you have captured, or in the screens captured by somebody else, it should be reported. Ask in #core-multisite or #core-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/. if you need any help.

#flow, #multisite, #testing