Skip to content

Conversation

muffinresearch
Copy link
Contributor

@muffinresearch muffinresearch commented May 31, 2016

Add the link to amo as per mozilla/addons#9616

discover_add-ons

- There was no detailed spec for this but I'm happy to tweak this PR to whatever the details need to be.

@pwalm Currently the hover is a lightened version of the background color I grabbed from the docs. Let me know what the exact colours + paddings etc should be and I can update this PR or we can do that separately if you need more time since we need to get this string in to be localized.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 3aa34b5 on muffinresearch:add-button-to-amo into fddd915 on mozilla:master.

color: #fff;
text-decoration: none;
font-size: 13px;
transition: background .2s;
Copy link
Contributor

Choose a reason for hiding this comment

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

I prefer using 200ms when it's less than a second, but it probably doesn't matter. I think we wanted the leading zero for decimals, though?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep I like the idea of ms for this. I'll change that and we should add that to the style guide when we get around to writing one :)

@muffinresearch
Copy link
Contributor Author

@pwalm, I'm going to land this so we can get the localizations going. I'll file a new bug for the detailed specs.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling fe40c9b on muffinresearch:add-button-to-amo into fddd915 on mozilla:master.

@muffinresearch muffinresearch merged commit 41bc721 into mozilla:master Jun 1, 2016
@muffinresearch muffinresearch deleted the add-button-to-amo branch June 1, 2016 08:27
</div>
</header>
{results.map((item, i) => <Addon {...camelCaseProps(item)} key={i} />)}
<a className="cta" href="https://addons.mozilla.org/">{i18n.gettext('See more add-ons!')}</a>
Copy link
Contributor

Choose a reason for hiding this comment

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

I wrote this up yesterday but forget to submit it.

I'm starting to get concerned about our CSS. We are reusing some classes like and cta looks like it will probably get reused without whoever uses it knowing this style exists. We have some styles on just header and header h1 too which seems fragile. There are also some styles that are nested 4 levels deep that could likely be reduced to 1 or 2 if we had more specific class names.

I know we discussed using some sort of methodology before and didn't settle on anything but I think we should try and come up with something. London might be a good place to discuss this.

Copy link
Contributor

Choose a reason for hiding this comment

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

If we can enforce the system with tooling that'd be great too.

Copy link
Contributor Author

@muffinresearch muffinresearch Jun 1, 2016

Choose a reason for hiding this comment

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

Definitely up for discussing this in London and coming up with a plan - might be better to file an issue with the details you want to cover - as this buried in a merged PR is likely to get lost.

I'll see about de-nesting in the RTL updates.

@pwalm
Copy link
Contributor

pwalm commented Jun 1, 2016

screen shot 2016-06-01 at 9 23 27 am

all:
height: 40px
width: 140px min, variable max (8px L/R padding)

normal:
background: #2EA3FF;
border: 1px solid #0675D3;

hover:
background: #0996F8;
border: 1px solid #0461AE;

active:
background: #0675D3;
border: 1px solid #025295;

copy:
font-family: [platform default];
font-size: 14px;
color: #FFFFFF;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants