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

EM-1242: Why CB Success Section (ESB) #124

Merged
merged 32 commits into from
Aug 28, 2017

Conversation

mrfantasticwonders
Copy link
Contributor

Purpose

As a potential buyer or high-level decision maker, I want to visit Hiring Dot and know what CareerBuilder can offer me as a vendor/partner.

This creates a mixin based off @arelia 's animated play button.

https://codepen.io/arelia/pen/wdWwym

JIRA
https://cb-content-enablement.atlassian.net/browse/EM-1242

Changes

  • Improvements and fixes

    • N/A
  • Changes to developer setup/environment

    • N/A
  • Architectural changes

    • Adds play-rippling-button to _button.scss
  • Migrations or Steps to Take on Production

    • N/A
  • Library changes

    • N/A
  • Side effects

    • N/A

Screenshots

  • Before

  • After
    screen shot 2017-08-22 at 10 23 17 am

screen shot 2017-08-22 at 10 23 36 am

Feature Server
http://web.employer-6.development.c66.me/company/why-careerbuilder

How to Verify These Changes

  • Specific pages to visit

    • In the Feature Server link, thumb / scroll to the Success section
  • Steps to take

    • See if everything looks good, and compare it to the Desktop and Mobile Invision mocks in the Jira
    • Compare the play button to the Codepen link above
    • Hover over the play button, its color should change (based on Arelia's codepen)
    • Click on the play button, the Wistia video should play
  • Responsive considerations

    • The close button should remain the same (size and width) all the way down to mobile

Relevant PRs/Dependencies

Additional Information
N/A

arelia and others added 24 commits August 15, 2017 14:57
to adjust for the padding that the rest of the content lives within

this fixes the buy box being 20px outside of the area that the rest of the content is in

see https://trello.com/c/OzxNjQma/34-buy-box-is-out-of-alignment-with-content-area and https://cb-content-enablement.atlassian.net/browse/EM-1480
b/c flag needs to not quite be on the edge
@@ -222,6 +222,101 @@ $massive-button-horizontal-padding: $base-input-font-size * 2;
}
}

// Fancy Play Button
// Initial state
$ripple-diameter: 24em;
Copy link
Member

Choose a reason for hiding this comment

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

Should we be putting these in the variables file, @arelia?

Copy link
Contributor

Choose a reason for hiding this comment

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

no, going forward this is something I'd prefix with an _ and leave it in the file where it's used

$ripple-diameter: 24em;
$play-button-size: 4em;
$ripple-color: white;
$ripple-hover-color: #447777;
Copy link
Contributor

Choose a reason for hiding this comment

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

I think I chose this color myself. Ask Justin what color he'd like to use from our defined colors

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will verify with him when he gets in tomorrow.

$play-button-size: 4em;
$ripple-color: white;
$ripple-hover-color: #447777;
$ripple-hover-transition: 1500ms ease;
Copy link
Contributor

Choose a reason for hiding this comment

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

take a look at the animation documentation and consider how this should be documented ther

  • should $ripple-hover-transition, $ripple-duration, and $ripple-count go in the variables/animations style sheet?
  • should generic variables be defined in animations.scss that are then used in place of the number values here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Looking over the stylesheet, I agree that the variables mentioned should go into that sheet. I went ahead and moved those, but am using the namespace video-play-button-ripple to better identify those variables.

Regarding your second comment, because there is so little in the animation sheet as of now, I think keeping the values as they are would make more sense. Considering that these values, currently, are very specific to this feature.

@@ -222,6 +222,101 @@ $massive-button-horizontal-padding: $base-input-font-size * 2;
}
}

// Fancy Play Button
Copy link
Contributor

Choose a reason for hiding this comment

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

this is all so different from everything else in button.scss. I'd leave it in this folder so that it gets documented with buttons in the pattern library, but I'd make a separate file for it. we can work on documentation together

@arelia arelia force-pushed the topic/EM-1237-why-cb branch from 3510aea to 9b9ce45 Compare August 23, 2017 19:14
@mrfantasticwonders
Copy link
Contributor Author

@arelia This is ready for your review again (excluding asking Justin about the color of the play button)

@mrfantasticwonders mrfantasticwonders changed the base branch from topic/EM-1237-why-cb to master August 24, 2017 16:55
@mrfantasticwonders
Copy link
Contributor Author

Base branch for this PR has been updated to master.

@mrfantasticwonders mrfantasticwonders merged commit 663f712 into master Aug 28, 2017
@mrfantasticwonders mrfantasticwonders deleted the topic/EM-1242-WCB-Success branch August 28, 2017 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants