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

Responsive Landing Page Using CSS Flexbox

DayaA•130
@Aishaakin
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone, i tried using media query property but i can get it to meet the project challenge. Can someone please help me.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Edoye•170
    @DoyeDesigns
    Posted over 2 years ago

    Hello Aishaskin,

    media query is a condition that has to be met before the elements on a webpage changes it’s layout structure to adjust to the user’s screen size.

    For example /Default background color / Body{ Background: white; } / On screens that are 400px or less, set background color to red/ @media only screen and (max-width: 400px){ Body{ Background: red; } } /On screens that are 800px or greater, set background color to blue/ @media only screen and (min-width: 800px){ Body{ Background: blue; } } Hope this helps

    Here is a link to better understand it https://www.w3schools.com/css/css_rwd_mediaqueries.asp

    Also you should wrap all the work to be done in the body in a main tag.. html semantics, it make your page more accessible. So you can remove the div with the container class and use a main tag instead

    You should not put a main tag inside a div. In terms of hierarchy a main tag comes before a div tag. So a div tag should be inside a main tag not the other way around.

    To center the old price and new price add these codes in the parent element holding both of them. That is the div with the “inline” class;

    .inline{ Justify-content: center; Align-items: center; }

    Feel free to reach out to me for more clarification. Happy coding:)

  • Amaar Chowdhury•30
    @amaarchowdhury11
    Posted over 2 years ago

    Hey there!

    My attempt at this project was my first time using media queries, and I also was a bit stumped online about how to do it.

    Kevin Powell on youtube has a fantastic tutorial on doing this very FrontEndMentor challenge, and I learned from him how to do it.

    I would try and explain myself - however I'm not sure I'm the best authority on it, so I will link to his tutorial :)

    https://www.youtube.com/watch?v=B2WL6KkqhLQ&list=PL4-IK0AVhVjPregcc6pgAIerVqSWaJEM4

    I hope this helps :)

  • Fritz•300
    @fritzadelbertus
    Posted over 2 years ago

    Hello @Aishaakin. First of all, congratulations on finishing this challenge!

    Here are some few suggestion I can give:

    • I think w3schools explanation of media queries is easy to digest. I recommend you to start learning media query from there. You can visit their documentation here

    • I see you haven't use the <picture> tag. The <picture> tag helps you display different image source for different medias. You can see how to implement it here. It will make you easier to apply responsive images.

    I hope it's helpful and happy coding!

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub