Various Web Store Flow Explorations

Along the lines of this post from @helen, and in relation to the Plugin Directory IA, I’m sharing some flows from other popular web store experiences. This is exploratory research for the 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.

 

FLOWS

Code Canyon (https://cloudup.com/cbQSIYi5jUf)

Sketch App Resources (https://cloudup.com/cEq1yIwY5NM)

Steam (https://cloudup.com/cHiTsgm1U9R) via @markjaquith

XBOX Store (https://cloudup.com/cUcVXIynaPa)

Playstation Store (https://cloudup.com/cyK7tf-YlcC)

Amazon App Store (https://cloudup.com/cng1vG1MzhT)

Mac App Store (https://cloudup.com/c-annTJSdGh)

Windows App Store (https://cloudup.com/cBLTp69gtv4) via @michael-arestad

Google Play Store (https://cloudup.com/cpwbEDBa94v) via @ryan

NPM Packages (https://cloudup.com/cX2qE9HThDs)

Atom Package Manager (https://cloudup.com/cA073Aae_FU) via @michael-arestad

Chrome Extensions (https://cloudup.com/ck-GUY0sjoO)

Firefox Plugins (https://cloudup.com/cbHEKKMxY36)

Safari Plugins (https://cloudup.com/ch_bI5-Cajd)

 

FEATURE COMPARISON

Web Store Feature Comparisons

Web Store Feature Comparisons

 

TOP COMMONALITIES

  1. Description (Often times this ONE section contained the description/FAQs/Other Notes, etc.)
  2. Author
  3. Download/Install Button
  4. Screenshots
  5. Reviews
  6. Ratings

 

FEEDBACK

What are your likes and dislikes between these? Are there popular design patterns that would be useful for our Plugin Directory? Please leave feedback below.

If you have other flows that you think would be helpful, please link to those as well.

The Future of Dashicons

During the WordPress Community Day following WCSF, a group of us (@ryelle, @empireoflight, @michael-arestad, @liljimmi — am I missing anyone? Maybe @markjaquith was there?) got together and discussed the future of Dashicons. Here are the notes from that meeting:

Icon font, or SVG?

Inline SVG vs Icon Fonts [CAGEMATCH]

Pros:

  • SVGs better rendered in browsers
  • Easier to maintain
  • The grunt process would be in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., so anyone can do it

Cons:

  • Different steps of building
  • Drop icon (svg) into folder, run grunt
  • IE9,10,11 don’t support external svgs
  • JS library fallback
  • Originally this was a font due to IE8
  • grunt would compile light/dark pngs
  • Modernizr or hacky thing to add a class

What’s the process for the new font?

  • Icons are all 1 .ai, each as a layer or artboard, exported to SVG
  • Or shortcut to SVGs
  • Grunt compiles a folder of SVGs to generate png, css, etc.
  • Optimize SVG
  • Grunticon to create pngs-> can be different colors
  • Combine SVGs into sprite
  • Pulled into core

How to BackCompat?

  • Old fonticons would use .dashicons, new would use .dashicon
  • Enqueue old font for a while
  • Check JS to see if anyone’s using old font

Steps

  • We already have the folder of SVGs
  • Micheal going to Gruntfile
  • Ben use this process for Palm Tree, Tracy bringing in things that missed 4.0
  • Upload SVG to a ticket
  • Stay on the 20×20 grid, for consistency
  • Official guidelines and template (Mel)
  • Style guide!
    • Redirect to dev hub
  • Blog: where we’re going, pros and cons, btw demo page.

Purpose of Dashicons?

How far are we going? Everything ever?

  • No new third party icons
  • Keep small as possible, things are hard to remove
  • Keep focus on wordpress admin
  • Approval process for icons
  • Ben is best for stylistics, but whether the icon belongs is democratic

Following the meeting, we redirected the githubGitHub GitHub is a website that offers online implementation of git repositories that 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/ resource to Dashicon’s new official home at developer.wordpress.org/resource/dashicons/.

Next up, we’ll want to start having meetings to get this process rolling. @ryelle has agreed to lead meetings, and has a preliminary mockup for the new process that we can talk about at our first meeting, which will take place some time during the week of the 12th-16th. What day/time works best for people?

#dashicons

Image Flow Update 29th October: WCSF Progress report

We’ve had another productive day in San Francisco – thanks to all who have been assisting. @sonjanyc @mor10 and I took some initial feedback from @mel and @lessbloat regarding the rough sketches and moved into Balsamiq to make some example flows based on specific scenarios.

We met with @markjaquith, @ericlewis and the remote team (thanks to all who could make it!) this morning to walk through the flows and get some feedback on whether the major build effort required by our approach is worth the possibilities presented by the vision. The consensus was that while there are many details to get right, this is a BIG task worth pursuing.

Later in the day, after we refined the Balsamiq flows more completely, we met again with @dhshredder, @lessbloat, @filletto, @samuelsidler to walk through the flows based on each scenario. There were some specific notes and details that were discussed at length, but the overall feeling was that this should move forward.

The next steps for the team are:

  • create wireframes for in the browser
  • spec the flows to solve for the following scenarios

** add a single image (new image)
** add a gallery
** add and edit an existing image

  • begin githubGitHub GitHub is a website that offers online implementation of git repositories that 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/ project for flat HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites./CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site./javascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. prototype
  • build prototype!

The flows can be accessed here:

https://wordpress.mybalsamiq.com/projects/imageflowmobilefirst/grid

You should even be able to play with prototype, though I am totally unclear on what the Balsamiq sharing experience is.

#image-flow

@saracannon has posted her take on a new…

@saracannon has posted her take on a new direction for post format 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., addressing some of the concerns that surfaced after @lessbloat‘s tests. Re-thinking WordPress Post Format UI.

The one that is closest to what I was thinking, and the best balance between showing the new UI (to people who are already using post formats or who have a theme with special support), and getting it out of the way once you’ve chosen, is the “In Page decision with post editor greyed out” one.

post-formats-classic-i-copy-1024x698

I’m curious to know what the UI team thinks. I’d like action taken on this ASAP, so that we can get the UI settled for betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 2.

#post-format-ui

MP6 version 0.3

Thank goodness it’s Friday! Because Friday means it’s time for an update to MP6. As we’ve mentioned before, this is not intended for the general public, just for savvy WordPress enthusiasts eager to preview or contribute to a re-imagination of our collective home, wp-admin.

On Monday we met on IRC in #wordpress-ui to discuss feedback on last week’s iteration. We’ve taken that feedback, plus the comments left here on this P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/., into account in what we’ve done this week. Here’s what’s new:

  • Almost all icons are now served from the Dashicons font. Work continues on the remaining raster icons.
  • The Plugins page now has borders and more padding between rows in the table. Opacity is only used for text, so their checkboxes stay fully opaque.
  • .widefat tables, .postbox divs and other containers have a deeper drop shadow and a new headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. design that more clearly defines the container from the background, and the header from the rest of the element.
  • Folded menus now get a small arrow for the current section. The way the arrow appears/disappears with the submenu isn’t great; if we remove the delay on submenus this might not be an issue.
  • The tabbed style of the Appearance section header has been removed.
  • The WordPress logo on the About page is now an SVG.
  • Page headers are now regular instead of light weight.
  • Admin color options are hidden when MP6 is present, as the plan is to only ship with one color scheme (though it will be even easier than before to customize your own).
  • The new comments/updates notification bubble is now #d54e21 instead of gray, to give it more emphasis.
  • We’ve included an example of 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 icon in SVG format. We chose Jetpack as a common plugin that users might have installed alongside MP6. This is our suggested design for plugin icons, but not yet the final suggested method of implementation.

Here are things that we discussed in feedback, but didn’t implement this week:

  • Test new values for green/amber/red status text.
  • Make adjustments to the secondary button styles for more contrast with the background.

This week includes contributions from Ben, Mel, Isaac, Joen, Otto, and myself. Many thanks as well to those who gave their feedback, ideas, patches, and bug reports during Monday’s meeting.

Like last time, we’ll do office hours on Monday to discuss next week’s iteration, followed by version 0.4 on next Friday; March 22. To save myself the time zone embarrassment from last time, let’s aim for 1800 UTC, whatever time that happens to be wherever you are in the world. Arrive an MP6 enthusiast; depart an MP6 contributor!

#mp6

Media Wireframes

Over the past week or so, I’ve worked closely with @lessbloat (Dave), @nacin, and @markjaquith to create a set of media workflows that will hopefully serve as a foundation and guide for the improvements in this release. (This is the fifth version of these wireframes — you can see the first four on Dave’s site.)

The usual disclaimers: None of this is final. These are wireframes, so please focus your feedback on the experience, not the aesthetics. As for scope, we are focusing our changes on improving the modal experience. This focuses on the overall picture; not all of this will necessarily make it into the final release.

So, without further ado…

Wireframes and workflows — fullscreen recommended.

The media library.

The media library, while uploading three files.

The attachment details screen.

Relevant TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets: #21390, #21391.

#3-5, #media