Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

Responsive Landing Page using Flexbox and media queries.

Abdelrahman Emara•10
@AbdalrahmanEmara
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I proud that i could do the shape of product view is close same what the task need. I used flexbox, but I see that I can't make it very well. I can guess that there are more solutions and methods to style. Even I want get feedback if there is a good method to using flexbox in different way. And if there is other method like using grid system i hope you to tell me. I learned using more picture and hide some of them.

What challenges did you encounter, and how did you overcome them?

In mobile version, I want to style the image in top, but I take some time to see what the width is good for that to show the picture and the details under it. I will talk in trust, I try to change the width and height to get the good view.

What specific areas of your project would you like help with?

font family, I try to use font family that is included in style-guide, but I observe that isn't like in the task.

And customize the picture and the text if i use flex in good way and i strictly select width and height for the component.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    SrkiMax•390
    @SrkiMax
    Posted 6 months ago

    Hi Abdelrahman,

    You can try using Bootstrap, it will save you a lot of time of writing code. They have a good grid system and responsive div containers so it gets easier than using Flexbox. Also, do not use both width and height dimensions, as you will end up with the text and components going out of borders of the parent elements when downsizing to smaller sized screens. Set only width, without setting height. Happy coding!

    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