-
Notifications
You must be signed in to change notification settings - Fork 0
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-1593: Small Biz Overview Section Refactor (ESB) #112
EM-1593: Small Biz Overview Section Refactor (ESB) #112
Conversation
…tainers for each row. removed content-left styles as they're no longer needed
sass/directives/_visual-guides.scss
Outdated
@@ -125,7 +118,7 @@ $visual-guide-breakpoint-small: 750px; | |||
} | |||
|
|||
// The step must be within a <span>, not a <div>, and must contain another <span> for the actual counter | |||
span.visual-guide__step { | |||
div.visual-guide__step { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typically, we don't bother with this level of specificity - it reduces the portability/re-usability of this code, requiring that any use of this class be applied to a div. I think our code can make the safe assumption that if you're using the class, you want its styles in every case for any kind of element. Also, your comment above says the step /must/ be within a span
. Besides that comment needing updated to say div
, is any of this truly required?
If we end up deciding to change this, there are other places in the Overview code that could incorporate this change as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@toastercup The comment and structure was a carryover from the old version of the guide. It was originally written that way due to styles that were being inherited elsewhere. However, because <div>
is being used now, this no longer applies.
I went ahead and removed the comment and the specificity. This also removed the need to have the extra <div>
in the container. I'm just able to use :after
on .visual-guide__step
and achieve the same results. Thus a developer would only need to include .visual-guide__step
in the template.
Could you elaborate on the last bit?
sass/directives/_visual-guides.scss
Outdated
@@ -137,8 +130,9 @@ $visual-guide-breakpoint-small: 750px; | |||
width: $visual-guide-step-size; | |||
color: $text-color-dark; | |||
|
|||
span:after { | |||
div:after { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a class we could specify for the after
instead, rather than applying these styles to any div? I understand we're assuming the structure of this element, but I'd like to avoid that if at all possible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just went ahead and pulled this and am now basing :after
off .visual-guide__step
. So a developer would only need to include .visual-guide__step
in the template, and nothing else.
…specificity of visual-guide__step
@toastercup This is ready for re-review. |
…loyer-style-base into topic/EM-1593-Small-Biz-Overview-Fix
…l-Biz-Overview-Fix EM-1593: Small Biz Overview Section Refactor (ESB)
Purpose:
This ESB PR updates the Visual Guide mixin to use flexbox's ordering system. This allows a PO to reorganize the
<li>
elements whichever way they want without needing to edit the guts of these blocks. This will order those blocks based on even / odd rules.I was able to successfully wrap the entire section in a snippet and edit its source in Cortex. But there are some quirks. See Side effects here https://github.com/cbdr/employer/pull/909
This also resolves the issue with the IPE adding additional markup when copy is edited, resulting in different colored text as seen on https://hiring.careerbuilder.com/recruiting-solutions/small-business-subscription-plans-and-pricing (the header of the first section).
JIRA:
https://cb-content-enablement.atlassian.net/browse/EM-1593
Changes:
Changes to setup
Architectural changes
See
Architectural changes
in https://github.com/cbdr/employer/pull/909Migrations
Library changes
Side effects
Side effects
in https://github.com/cbdr/employer/pull/909Screenshots
N/A - This section (including its carousel) should look exactly as it currently does on https://hiring.careerbuilder.com/recruiting-solutions/small-business-subscription-plans-and-pricing (minus Stephanie's edits, like the grey header in the first step)
N/A
QA Links:
http://web.cortex.development.c66.me/legacy#/webpages (small business subscription plans and pricing EM-2)
http://web.employer-2.development.c66.me/recruiting-solutions/small-business-subscription-plans-and-pricing
How to Verify These Changes
Specific pages to visit
small business subscription plans and pricing EM-2
)Steps to take
small business subscription plans and pricing EM-2
. You should notice that the entire Overview section is editable now.<li>
block. The step indicators should update. The rows should show even / odd ordering without needing to reorder the two blocksvisual-guide__content
(the main copy / content block) andvisual-guide__image
(the large image).<li>
blocks. Again, the step indicators should update, and you should still see the even / odd ordering without needing to reordervisual-guide__content
(the main copy / content block) andvisual-guide__image
(the large image).Responsive considerations
Source
.Relevant PRs/Dependencies:
https://github.com/cbdr/employer/pull/909
Additional Information