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

Blog Preview Card Responsive and Active State

Aria Rouzegar•150
@Ariarzg
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Barnabas001•180
    @Barnabas001
    Posted 3 months ago

    I love your work, most importantly the idea of that hover effect brilliant design i must confess

    Marked as helpful
  • P
    Øystein Håberg•13,260
    @Islandstone89
    Posted 3 months ago

    HTML:

    • I would wrap the date in the <time> element: <p class="published-date">Published <time datetime="2023-12-21">21 Dec 2023</time></p>.

    • As this is a blog card, the heading requires a link within it.

    • "Greg Hooper" is not a heading, but a <p>.

    CSS:

    • Including a CSS Reset at the top is good practice.

    • Move font-family: "Figtree", sans-serif and color: #121212 from * to body.

    • I recommend adding a bit of padding, for example 16px, on the body, to ensure the card doesn't touch the edges on small screens.

    • Descendant selectors like .card .published-date increase specificity, making the styles harder to override. Instead, use published-date as the selector.

    • Move the styles on .container to the body. Remove width: 100%, as block elements are 100% wide by default.

    • Except for the author image, remove all widths in px.

    • Add a max-width of around 20rem on the card to prevent it from getting too wide on larger screens.

    • font-size must never be in px. This is a significant accessibility issue, as it prevents the font size from scaling with the user's default browser setting. Use rem instead.

    • line-height must also never be in px.

    • On .author, you can remove flex-direction: row and justify-content: flex-start ,as these are default values.

    • Remove margin-left: 10px on "Greg Hooper". Instead, set gap: 10px on the Flex container, .author.

    • On the top image, add display: block, height: auto and max-width: 100% - the max-width prevents it from overflowing its container. Without this, an image would overflow if its intrinsic size is wider than the container. max-width: 100% makes the image shrink to fit inside its container.

    • Media queries must be in rem or em, not px. We usually style for mobile first, then use min-width media queries for larger screens. Instead of using media queries to change font-size, you can use the clamp() function.

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