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

CSS Grid

NBD•240
@bdal90
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 All,

Again a next challenge (my 10th, yaay) using CSS grid for the first time. It didn't seem hard though I feel like I have too much typing in my CSS. Any advice on how I could shorten it somehow? Or does it seem okay?

Cheers to you all,

Dalma

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matias Ludueña•1,990
    @matiasluduena23
    Posted over 1 year ago

    Hi Dalma! Congratulation you finished the challenge!!! It looks really good! Just one advice.

    1. to add a hover effect in you button , use button{ cursor:pointer ; transition: opacity 200ms ease-in-out }, and in you buttton:hover { opacity: 0.7; } you can play with this number. Here you have an example using the background-color.

    keep improving (;

    Good code!!!

    Matias

    Marked as helpful
  • Bryan Li•3,530
    @Zy8712
    Posted over 1 year ago

    The desktop version of your site looks pretty good. The only main changes I'd make is the breaking point of your website and the choice of having a scroll bar inside your container. Right now there is an awkward in-between on the desktop version, where certain screen sizes are too small for the container to fit (causing everything inside your container to shift), but the screen isn't small enough for your website to change to the mobile format which would be better.

    Also to answer your question, your CSS is pretty minimal, so I wouldn't worry about it too much. Though one thing I'd remove is the redundant code I found in your style.css:

    .subscription__price {
        color: var;
    }
    

    Besides that your site is pretty solid. Great work 👍

    Marked as helpful

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