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

Pricing component using HTML, CSS and JS

Arthur Reis Bello•75
@ThurzinRB
A solution to the Interactive pricing component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


As it happens for almost every project I've improved my HTML, JS and CSS skills. My biggest challenge was making the slider because it's my first time building one and making it interacts with the other elements. The toggle was pretty fun to make as I didn't have to research a lot to make. I gave a special attention on the animations, so my project differs from the other solutions.

With the project code getting big, it was hard to find some classes on my styles.css code. I don't know what is the best solution for this, I would say I have to separate it in several files contemplating different areas of the page but it's so common to find pages with just one file for styling.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Greetings, Arthur Reis Bello! 👋

    Nice job on this challenge! 👏 Your solution looks good and the slider works pretty well! 👍 It's good to hear you learned a lot from creating this solution (I always do when I complete challenges, as well)! 😀

    I suggest looking into using a preprocessor such as Sass for your CSS. Using Sass, you can separate your styles into a bunch of different files (called partials, I think) and then combine them into one big file that will get converted into normal CSS and sent to the browser along with your HTML. It'll make organizing and finding your styles much easier, and you'll benefit from a bunch of other features that Sass has, too! It's not hard to pick up once you know CSS, so consider giving it a try. 😉

    Keep coding (and happy coding, too)! 😁

  • Samuel Palacios•615
    @samuelpalaciosdev
    Posted over 4 years ago

    Hi, Arthur👋

    Great job on this challenge. Your solution looks good and it scales pretty well👍

    I only suggest some things 😉:

    -Changing the buttons to an <a> (anchor link). If this would be an actual webpage, those buttons should redirect somewhere.

    -Maybe, you don't need height. I mean, setting an explicit height, could cause you some problems, when talking about responsivenes.

    I hope this would help you, have a nice day, keep coding!💙

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

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