Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Single Price Grid Card Component using HTML and CSS

Priyanka Roy Choudhury•100
@PriyankaRC16
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone

I have changed some colours in my project as the text was difficult to read, the contrast was poor

Some changes:

  • The .headline,.headlinetwo classes in .white-card class colour have been changed
  • The lightcyan-card background colour, "per-month" text colour, button colours have been changed
  • The darkcyan-card background colour, paragraph text colours have been changed

Edit after submitting solution: I notice that in the screenshot comparison, my design looks completely different than the one that I tested in my localhost and live browser. I am not sure why it is behaving in this way. Can somebody help?

Any other feedback is appreciated!

Thank you Priyanka

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Arshad Ali Kaldane•650
    @IamArshadAli
    Posted over 1 year ago

    Greetings @PriyankaRC16

    The challenge's screenshot provided to us are captured at a width of 1440px for desktop and 375px for mobile screens. So, it's important to pay special attention to these screen sizes.

    You might have a display with a screen resolution of 1920x1080 or something else, which is why the design looks perfect on your machine and breaks in the screenshot, as the screenshot mechanism looks for our design at 1440px width.

    You might want to consider simulating your screen using the developer tools of your browser. Most of the browsers follow the same path to access the developer tools i.e. options > more tools > developer tools or you can simply use the following key combination Ctrl (or Cmd) + Shift + I.

    Then set the dimensions of the screen to the desired size and you are good to go.

    Hope this helps. Thank you🤓

  • Niroop R•40
    @NiroopR1999
    Posted over 1 year ago

    Hi there,

    • When in mobile view, consider removing the border radius (bottom) for monthly subscription box.
    • Follow the README.md document instructions and update the README-template.md file. Overall, it looks great. Happy Coding
  • Yonten•340
    @yozidst
    Posted over 1 year ago

    Hi there,

    Right below Design Comparison where they show the comparison of design to your solution; to the top right of that, there is a "Generate New Screenshot" button which updates the screenshot from the latest update from your provided link to the site. Note that there is a limit of 5 quantities for generating new screenshots which refresh every month for non-premium members. Also, the # of New Screenshots does not stack every consecutive month. Hope that helps. Cheers!

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.

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