Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

Responsive pricing component using Sass, BEM, and JS for the toggle

Syed Ali Mansoor•460
@syedalimansoor
A solution to the Pricing component with toggle challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello!

I tried my best to match the design in this challenge. Used some semantic markup for the elements as well. Do check out my approach to switch the billing from monthly to annually in the app.js file.

I also designed a new responsive attribution footer for myself which I have put in this solution, and will be adding to all my future solutions, so I would like some thoughts on that as well!

Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted about 4 years ago

    Hi, Syed Ali Mansoor! 👋

    Good job on this challenge! 👏

    I only suggest adding a focused state to the toggle-switch so that users know when it is the active item on a page. 😉

    Your attribution section looks pretty great, BTW! 👍 I really wasn't expecting something like that but it's cool! 😎

    Keep coding (and happy coding, too)! 😁

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted about 4 years ago

    Hey, great work on this one, the layout is really good and the toggle works just fine. Though I suggest making it accessible via keyboard presses only, so supporting tabbings right. I am refactoring my solution on this to approach that, but if you were to consider it, check out Grace Snow' solution on this, it is really accessible for all and it is really an amazing solution.

    For that custom footer, well for me personally, that works well and good choice in color picking, for me okay. Points for that

    Suggestion/s would be that;

    • At point 1097px going down to the mobile breakpoint, there is a scrollbar at the bottom. Since your content are bigger, then overflowing appears, thus creating scrollbar. Check that one out. Referring to toggled state, for the untoggled, no scrollbar.

    • The text besides the toggle could have been a label for the toggle. It will be really good if they were label right, so that it can used to toggle it as well.

    So those two only, more like preferences.

    Overall, this is a really good work^^

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub