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

Single Price Card component

Sibasish Sinha•125
@SibasishSinha
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey everyone, CSS has always been a challenge for me, but I am going to conquer it someday ! ( Feedbacks are more than welcome ) Happy coding and cheers.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hey Sibasish, great to see you working on your CSS skills. The more you practice the better you'll get! Nice work on this challenge. Here are some pointers after taking a look at your code:

    • Avoid using inline styles in your HTML. Instead, put all of your styles in your CSS file and target the elements you'd like to style.
    • Always be sure to have one h1 heading. For this design, I'd say it would be the "Join our community" heading.
    • If a piece of content isn't a heading for another piece of content, don't use a heading element. The "30-day, hassle free..." and "Gain access to our..." blocks aren't headings, so I'd recommend using paragraph tags. Likewise for "$29 per month" and "Full access for less than...".
    • You don't need to use position: absolute; to position the card. You could use Flexbox or Grid to centre it instead. Avoid using position: absolute; except for very specific circumstances when you have a clear reason. It's a declaration that can easily cause problems with your styles.
    • You've done well with the overall layout of the component. I'd recommend having a go at refining your styles to try getting your project to match up closer to the design. Training your eye for detail is definitely worth the time investment!

    I hope this helps. Keep up the great 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 1st-party linked stylesheets, and styles within <style> tags.

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.

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