Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Blog preview card using HTML, CSS Flexbox and media queries.

Juan Carlos Moreno J•120
@juancmdev
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´m so proud to finish this new procject and see how my knowlege is going bigger day by day learning new things.

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

Using flexbox and media queries has beea a good challenge for me necause I have learned a lot.

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

If you can give some feedback about my procject it will be so great.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chirag•490
    @chirag-bishnoi
    Posted over 1 year ago

    Hello there, the card is good but I'm seeing two problems in the layout. The background shadow only appears when we hover over it even though it was part of the card so it was suppose to stay there without hover. Another thing that I noticed is that there is horizontal and vertical scrolling this is because the content is overflowing because you have given your main tag width: 1440px; and height: 960px; to fix this issue remove both width and height from the main tag. To fill the white space from underneath give your body minimum height of 100vh

    body {
    min-height:100vh;
    background-color: #f4d04e;
    display: flex;
    flex-direction: column;
    justify-content: center;
    }
    

    remove the flex from the main tag and give it to the body instead. And don't forget to change the flex direction!

    and this will solve the issue :)

    Marked as helpful
  • KISHAN YADAV•120
    @kishanyash
    Posted over 1 year ago

    good

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

Oops! 😬

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

Log in with GitHub