Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugins (wpcom): Update design and text #4995

Merged
merged 7 commits into from
Apr 27, 2016
Merged

Conversation

davewhitley
Copy link
Contributor

@davewhitley davewhitley commented Apr 25, 2016

This addresses some feedback. fixes #4986

  1. Make the plugins more active by making them green.
  2. Update text.
  3. Make it more obvious that the links are external.

@dmsnell For 3, can we change the plugin icon on hover, if the link is external? Currently this is all but the Google Analytics plugin. My idea is to change the plugin icon to the external one on hover.

Another solution would be to add a tooltip for each link.

Before:

obhyaltluaaaaasuvork5cyii

After:

acyhettljyusqaaaabjru5erkjggg

Hover state:

screen shot 2016-04-26 at 9 21 34 am

dmsnell and others added 2 commits April 25, 2016 15:00
Previously, it was noted that there isn't much to distinguish external
links on the WordPress.com plugins page.

This patch adds the behavior that a plugin Gridicon will change when
hovering over the plugin to show the external glyph if the plugin link
is outside of Calypso.

Currently this only impacts the Google Analytics plugin on the Business
plugin panel. I haven only included the code changes, therefore, on the
business plugin component. If we include external links in the future on
the other classes of plugins, we can add the same changes there.
@davewhitley
Copy link
Contributor Author

Thanks Dennis, the icon replacement is working well.

Previously we had three separate plugin components for the three plan
levels: Free, Premium, and Bussiness in order to facilitate differences
in the underlying representation of those features.

The differences ended up being insignificant and this patch merges them
into one generic plugin component to reduce code size and surface area
for bugs to appear.
@dmsnell
Copy link
Member

dmsnell commented Apr 25, 2016

@drw158 I have merged the plugin components and now this PR has more red than green!

@davewhitley davewhitley added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. [Status] Needs Design Review Add this when you'd like to get a review / feedback from the Design team on your PR and removed [Status] In Progress labels Apr 26, 2016
@folletto
Copy link
Contributor

All looks good to me design wise.

The only doubt I have is this:

Make the plugins more active by making them green.

Can I ask why green instead of our medium blue which seems equally "highlighting" but at the same time more aligned with the overall page look?

@davewhitley
Copy link
Contributor Author

First iteration was blue, but then it looked like "too much blue." Second iteration was gray as shown in the "before" screenshot.

We received feedback that the active plugins may not look very active, so I changed it to green. I also thought it was a good opportunity to introduce some color other than blue.

But, if the green does not look good, I'd be fine with going back to gray.

@mtias
Copy link
Member

mtias commented Apr 26, 2016

@drw158 wonder if this is a chance to try the color-code @adambbecker was exploring for plans (a color for each plan, basically).

@davewhitley
Copy link
Contributor Author

davewhitley commented Apr 26, 2016

Worth a shot! @adambbecker can I just pick the colors from the screenshot on your mega Plans post a few weeks ago?

Edit: Looking at it again, the Free plan would be yellow, and using yellow for the standard plugin icons might look strange — like something was wrong. It's a good idea for the future, but I'm not sure about for this PR.

@folletto
Copy link
Contributor

First iteration was blue, but then it looked like "too much blue." Second iteration was gray as shown in the "before" screenshot.

Between "too much blue" and "too much green" I'd go for blue given the "not active enough" feedback, which is fair.
Just my take, it's ok if we decide to rather go green. :)

@dmsnell
Copy link
Member

dmsnell commented Apr 26, 2016

I'd go for blue given the "not active enough" feedback

yeah the whole idea of adding color here because it's "too blue" always seemed strange to me. blue is our entire app's color scheme…

@@ -18,11 +28,29 @@ export const StandardPlugin = React.createClass( {
descriptionLink
} = this.props;

const { isUnderMouse } = this.state;

const isExternalLink = hasHttpProtocol( descriptionLink );
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add this as a prop, instead of testing for this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gwwar we deliberated on this point and I think it's best to keep the logic contained inside this component. it's only effect is visual and I don't think there's any need to couple that to the "outside world" I like being able to only care about adding the URL in the plugin data structure instead of having to think about how to represent that data.

@gwwar
Copy link
Contributor

gwwar commented Apr 26, 2016

👍 Codewise this is good to ship, after we change back the analytics page slug to /plans/features/google-analytics/{siteSlug}

Are we okay with having a blue hover state vs a lighter green, like we do for our notice actions? This kind of stuck out to me:
screen shot 2016-04-26 at 2 03 04 pm

@davewhitley
Copy link
Contributor Author

Blue hover state was intentional, just to emulate a blue text link. I didn't think about doing a lighter green though. I'm not sure where I stand on the color in general. Not sure whether to do green, blue, or gray.

@adambbecker
Copy link
Contributor

@mtias, @drw158: Ah, yeah I see what you mean about the plan colors. I think it could work, but I agree with Dave that the yellow might look a little like a warning. I'm also still playing around with trying those colors outside of the plans page & unfortunately the connection just isn't very strong between remembering those colors & associating them with plans (until you see all the plans on the page).

Seeing this action, I actually really dig the green because it enforces the active state, but I can also see what others have mentioned that it can be a little much once a lot of plugins are visible. I was playing around a bit here just to see what some other versions could look like and I settled on something like this:

screen shot 2016-04-26 at 5 53 55 pm

Take that with a grain of salt mostly because I was just testing things out. But a few things that caught my eye were:

  • Active state: wanted to try the green idea, but visually scaled down a bit.
  • "Purchase" button: when I first saw it, I was a little afraid that clicking it would automatically send me down a checkout path, so I wanted to see what an informative nudge version would look like.

This is really great though. All of the above is totally up to your discretion, just throwing a few more ideas into the pot just in case you were still exploring.

Overall, I do like the green direction. I would also probably remove the blue bar underneath the section header and keep the hover color the same in that particular case. Or, keep the color bar beneath the section header, but make it dynamic so that active sections get green, purchasable sections get blue.

@folletto
Copy link
Contributor

The green check marks I feel work really really well. We might get away also with the ✓ Active label in the bar with that. Feels clear enough already. :)

@mtias
Copy link
Member

mtias commented Apr 27, 2016

I would also probably remove the blue bar underneath the section header and keep the hover color the same in that particular case.

👍 to this. The notion of "primary SectionHeader" also didn't make much sense to me.

@davewhitley
Copy link
Contributor Author

The blue bar underneath was to address feedback that the Premium and Business sections did not stand out as "headers", and visually got lost. Currently we don't have a standard way to do something like this. But, if you feel that the header stand out enough, then I'm fine with removing it.

@davewhitley
Copy link
Contributor Author

I also like the green check marks. When I first saw the nudge component in the mockup, I thought that was a really interesting idea. It sort of makes sense in the Calypso context. After letting it sink it though, it does look strange in the context of what a "normal" website looks like.

# Conflicts:
#	client/my-sites/plugins-wpcom/plugin-types/business-plugin.jsx
@davewhitley
Copy link
Contributor Author

Ok, I changed the active state to blue for now. I will explore the check marks in another PR.

I updated from master, so no more conflicts. Are we ok to merge now?

@roundhill
Copy link
Contributor

I updated from master, so no more conflicts. Are we ok to merge now?

:shipit:

@roundhill roundhill added [Status] Ready to Merge and removed [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. [Status] Needs Design Review Add this when you'd like to get a review / feedback from the Design team on your PR labels Apr 27, 2016
@davewhitley davewhitley merged commit 6de008b into master Apr 27, 2016
@davewhitley davewhitley deleted the fix/wpcom-plugins-ux branch April 27, 2016 19:39
@lancewillett lancewillett removed the [Feature] Plans & Upgrades All of the plans on WordPress.com and flow for upgrading plans. label Sep 5, 2016
@lancewillett lancewillett added the [Feature] Plugins Features related to plugins on WordPress.com, including search, management, and installation. label Oct 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Plugins Features related to plugins on WordPress.com, including search, management, and installation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WPCOM Plugins: Plugin names don't all fit in the available space
9 participants