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

Subscription page( Grid)

Emmanuel Ziggah•50
@blackcoderx
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had difficulties with the mobile view, so I decided to use flex instead of grid.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • aykutminikli•280
    @aykutminikli
    Posted over 2 years ago

    Hi, congratz on completing the challenge.

    I think i saw your problem with mobile grid. It seems like you wrote your css for desktop version first and mobile version after. When you gave grid-template-columns to your .parent_section and grid-column to child sections, they still stay when you go mobile. So with your css code, in mobile there is still 3 columns at .parent_section.

    You can approach this with more than one way.

    Way One:

    1. First, you can change grid-template-columns at your .parent_section to grid-template-columns: 1fr. After making your .parent_section a grid you can delete flex-direction: column;
    2. Then you can change grid-column at your section css classes(section_one, section_two, section_three) to all grid-column: 1/2 in your media to make it they are only using 1 column at mobile version.
    3. You can also add grid-template-rows: repeat(3, auto); to your .parent_section to make it 3 rows with auto heights.

    with this your media code should look like this

    @media screen and (max-width:425px){
      .parent_section{
        margin: 13px;
        display: grid;
        grid-template-columns: 1fr;
        grid-template-rows: repeat(3,auto);
      }
      .section_two{
        grid-column: 1/2;
        border-bottom-left-radius: 0em;
      }
      .section_three{
        grid-column: 1/2;
        border-bottom-left-radius: var(--sect_rad);
      }
      .attribution{
        grid-column: 1/2;
        font-size: 12px;
        font-weight: 700;
      }
    }
    

    Way Two:

    You should start with mobile version and make desktop version after with @media screen and (min-width: your breakpoint choice). When you start with mobile version, there are less problems with making it desktop version. It's like building a house from floors.

    Hope this was helpful.

    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

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