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

HTML, CSS and javascript to build the page.

Abhishek Kulshrestha•30
@abhikulshrestha22
A solution to the Pricing component with toggle challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


How to toggle the price (annually or monthly) without JS. As toggle button and price are not being direct parents /child or sibling relationship.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Nitya Gulati•665
    @nityagulati
    Posted over 5 years ago

    Nice work, Abhishek! The page looks good and is responsive. Few suggestions to improve upon the code --

    1. Instead of using <div> tags for the card details, you should use <ul> as they are a list of features.

    2. Use meaningful, descriptive class names to style the elements such as card-list or card-details instead of row.

    3. Instead of adding another div - extra-height and applying height to it, you can simply add padding-top and padding-bottom to the card-selected element.

    4. I believe you are overusing the display: flex property on some elements that don't necessarily require it. The main element that needs it is cards container that holds and aligns all three cards next to each other.

    • card class (applied to each card) doesn't require flex property because <div> elements are block elements and are naturally aligned in columnar/vertical orientation.
    • row doesn't require flex as you don't have any child elements within the rows that need to be aligned. Also if you use <ul> instead of row divs then they will be listed as a list (column) naturally.
    • you can remove all the accompanying flex properties from these elements as well. flex-direction align-content justify-content align-items.
    1. You can instead use text-align: center on card class to align the content within the cards.

    2. Removing Flex from card will resize the buttons. You can use width: -webkit-fill-available for the buttons to stretch or specify a width using % (responsive) or px.

    Keep up the good work!

  • Saurav Chamoli•370
    @sauravchamoli17
    Posted over 5 years ago

    Very well done on your project. Keep up the good work!

  • Matt Studdert•13,611
    @mattstuddert
    Posted over 5 years ago

    Really nice work Abishek! You've received some amazing feedback from Nitya already, so I'll just jump straight to your question. In order to get the toggle working without JS you'd need to re-structure your HTML to make the input element a sibling of the element you've currently got an ID of cards on. Then your selector would look something like this: input:checked ~ #cards .yearPrice.

    Great work on this challenge. Keep it 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

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