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

Mobile-first design using flexbox

Dragosh Gheceanu•140
@dragoshcode
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey, I'd be happy to hear what I did wrong in my design, especially about the media query part, I don't know how to improve it, it's messed up a bit. Thank you

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 3 years ago

    Hey, awesome work on this one. Layout in desktop seems fine, the responsiveness could be better since right now, the container shifts based on the text-wrapping right. The mobile layout could use some more width.

    Grishmita already said some useful feedback, just going to give some suggestions as well.

    • Always have a main element to wrap the main content of the page. The .container selector could have used main instead of div. This way, contents are inside a landmark element.
    • Avoid using height: 100vh on a large container like your .container selector. This limits the element's height based on the screen. Use min-height: 100vh instead, this takes full height as well but allows the element to expand if needed.
    • For this one , I would put the .attribution inside the footer tag, so your markup should look like:
    <main />
    <footer />
    
    • Avoid using multiple h1 on a page. Use only at least 1 h1, change those into h2. But in a page, you need an h1 for this one, you will make the h1 a screen-reader only text by having an sr-only stylings. This means, the text will be hidden visually but visible for screen-readers. The h1 text-content should describe what is the content of the main is all about. Have a look at Grace's solution on this one inspect it and see how she used the h1 and copy as well the styling applied on it, you will used that a lot.
    • Each car icons could use aria-hidden="true" attribute so that the image will be visible for all tech.
    • Lastly, just those that I mentioned at the beginning, the responsiveness and mobile layout.

    Aside from those, great work again on this one.

    Marked as helpful
  • Grishmita•105
    @Grishmita
    Posted over 3 years ago

    I am not an expert but i have recently finished this challenge while. coding for frontend make sure to code the solution close to the given challenge as possible 1)padding
    2) giving height to your div 3) regarding media query just understand whats the meaning of min-width and max-width after that there is a online media query breakpoint generator which are very cool and very helpful . From that website you can surely learn about media query

    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