Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

Solution Pricing component with toggle

tailwind-css
Stefan Bojkovski•720
@xStephx
A solution to the Pricing component with toggle challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mahmood•2,130
    @MahmoodHashem
    Posted 7 months ago

    Great job 👏

    You could also practice toggling prices without using javascript by CSS like this:

    
    .card .basic::after{
        content: '19.99';
    }
    
    .card .professional::after{
        content: '24.99';
    }
    
    
    .card .master::after{
        content: '39.99' ;
    }
    
    
    main:has(.toggle-input:checked) .card .basic::after {
        content: '199.99'
    }
    
    main:has(.toggle-input:checked) .card .professional::after{
        content: '249.99';
    }
    
    main:has(.toggle-input:checked) .card .master::after{
        content: '399.99';
    }
    
    

    Good luck

    Marked as helpful
  • Marzia Jalili•7,270
    @MarziaJalili
    Posted 7 months ago

    Hello Stefan Bojkovski 👋, I am such a great fun of you. After I saw your solution, I downloaded the challenge and gave it a try😁😁. I don't know if you will consider this petty suggestion important or not because I am just a beginner here, but I badly want to share it🥲. While solving the challenge I realized that the size and position of the dollar sign and the price itself aren't the same🤔. Then, I wrapped a <span> and a <strong> element inside a <div> that had a display of flex and finally put the value of align-items to center and change the font-size of the dollar sign😎. Over all, you have done a great job girl🙌, you could also check out my solution if you don't mind.

    Marked as helpful
  • Abdalla Essam•110
    @Abdalla2200
    Posted 7 months ago

    Great job, but I have a question: how do you use customized styles in config.js with CDN? I'm trying to use it, but the styles don't appear on the website. i also copied your config.js code but didn't work

  • P
    Richard•410
    @Richard1876
    Posted 7 months ago

    Group study to share ideas

  • P
    Richard•410
    @Richard1876
    Posted 7 months ago

    would you like to team up

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.

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

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

Oops! 😬

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

Log in with GitHub