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

Responsive layout using CSS flexbox

P
VirginiaPatrika•260
@VirginiaPat
A solution to the Blog preview card 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 am proud that I completed the challenge and now I am getting used to "read" better the figma files. I didn't read all the instructions before starting coding, so I used media queries. Next time I will be more careful.

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

Any feedback is helpful!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Kamran Kiani•2,780
    @kaamiik
    Posted 6 months ago

    Some notes which may improve your code:

    1. Decorative images do not need an alt message. The alt attribute in your img tag should be empty, like alt="". It seems that the top image is decorative here. Additionally, note that avatar images do not need alt text either.

    1. It is recommended to use a proper CSS reset at the start of your CSS file. Both Andy Bell and Josh Comeau offer excellent CSS resets. You can easily find them by searching on the internet.

    1. Using font-size: 62.5%; is generally considered a bad practice. It was also mentioned in the last challenge. It is better to adopt the habit of considering 1rem as equal to 16px. This will help maintain consistency and readability.

    1. It is advisable to use a unitless value for line-height. This approach ensures better scalability and consistency across different font sizes.

    1. There is no need to use media queries for the max-width of a container in this challenge. You should only have one max-width defined in your CSS.
    Marked as helpful
  • Tathiani Lima•120
    @TathianiLima
    Posted 6 months ago

    Você foi muito bem, Parabéns!

    Minha sugestão é apenas mudar o <html lang="en"> para

    <html lang="pt-br">.
    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